previous: >>108603652#define __NR__sysctl 156https://man7.org/linux/man-pages/man2/sysctl.2.htmltl;dr:control system variablesWOW! so they really can remove syscalls after all. isn't that something? only took them several years lmao. but i should give them credit where it's due. it's good that they did this, even if it took a lot time. not really much to say about this one, though. it's /proc/sys, but worserelevant resources: man manman syscallshttps://man7.org/linux/man-pages/https://linux.die.net/man/https://elixir.bootlin.com/linux/https://elixir.bootlin.com/musl/https://elixir.bootlin.com/glibc/
#define __NR__sysctl 156
man man
man syscalls
>>108609319What a youthful lad!
>>108609399>warnings since 2.6.24 >24 January 2008>removed in 5.5>26 January 2020Honestly, 12 years is a lot quicker than I thought it'd be..
>>108609463I never thought they'd remove any syscalls, desu.
>>108609487yeah, exactly. the "WE DO NOT BREAK USERSPACE" is about the most ironclad rule the kernel enforces
>>108609399Cant be a day over 17.
>>108609319is sysctl a good syscall
>>108612734Considering they removed it, it must have been actively terrible.
>>108612786>it must have been actively terrible>meanwhile open is still allowed to exist
>>108612796Is there some other, better way to open files on POSIX systems?
>>108609319finally a good syscall of the day thread
>_sysctl>control system variablesshouldn't it've been _varctl, or _sysvarctl if you're not into the whole brevity thing
>>108612826>on POSIX systemsAside from openat existing: POSIX is terribly outdated.
>>108613778hello, NT schizo:^)
>>108614854NT isn't exactly better, at least in that regard.At least it never bothered with overcommit.