3 ms·
What you claim is technically impossible: there is no way to stop someone coding in assembler from making a kernel system call. I am absolutely arguing against
by Annatar 5y ago
What you claim is technically impossible: there is no way to stop someone coding in assembler from making a kernel system call.
I am absolutely arguing against Rust because it’s a horrible language and even if it weren’t it’s not as ubiquitous as C or Fortran. Rust is absolutely toxic for the industry but especially so are the people who promote it.
If you make syscalls against a backwards-compatible kernel API, nothing will break. One just needs to know how.
- Rusky 5y ago> there is no way to stop someone coding in assembler from making a kernel system call. Take a look at OpenBSD, then- if you make a syscall from any language at all, but it's not from within libc, the kernel will simply kill the process: https://lwn.net/Articles/806776/ https://lwn.net/Articles/806776/ This forced Go to switch from making direct syscalls to making them indirectly via libc: https://utcc.utoronto.ca/~cks/space/blog/programming/Go116OpenBSDUsesLibc https://utcc.utoronto.ca/~cks/space/blog/programming/Go116Op... I don't really care about your opinion of Rust, but if anything can make people who behave like you this upset, I'm all for it.