zlacker

[return to "OpenBSD: Removing syscall(2) from libc and kernel"]
1. __turb+3l[view] [source] 2023-10-27 17:00:14
>>eclipt+(OP)
It looks like golang is going to have to deal with — again — OpenBSD treating libc as the interface with the kernel instead of syscalls being the interface with the kernel.

I wonder if there could be some way to sign a dynamic library to allow it to create direct system calls and then pass that as a kernel command line argument at boot?

◧◩
2. maskli+Sp[view] [source] 2023-10-27 17:24:12
>>__turb+3l
> It looks like golang is going to have to deal with — again — OpenBSD treating libc as the interface with the kernel instead of syscalls being the interface with the kernel.

Something they wouldn't have to do if they'd heeded the warnings they got since they first started going raw syscalls on non linux systems.

But as usual, go is uniquely american, only doing the right thing after it has tried everything else.

◧◩◪
3. PrimeM+nr[view] [source] 2023-10-27 17:30:26
>>maskli+Sp
> go is uniquely american, doing the right thing after it has tried everything else.

That doesn't seem like anything common to an American way of doing things. What an odd statement.

◧◩◪◨
4. kstrau+Js[view] [source] 2023-10-27 17:36:47
>>PrimeM+nr
It's a play on a quote often attributed to Winston Churchill: https://quoteinvestigator.com/2012/11/11/exhaust-alternative...
◧◩◪◨⬒
5. arp242+Dh1[view] [source] 2023-10-27 22:07:56
>>kstrau+Js
Bizarre nationalistic "they're doing it because they're Americans" rantings are still not okay even if they're a "play on a quote". I can "play" with all sorts of quotes to say all sorts of idiotic things.
[go to top]