previous: >>108548206#define __NR_sysfs 139https://man7.org/linux/man-pages/man2/sysfs.2.htmli don't even know what to put for the tl;dr lol. get filesystem information i guess? it's a completely obsolete syscall and really shouldn't even exist anymore. it's been superseded entirely by /proci mean, just look at this lol>This string will be written to the buffer pointed to by buf. Make sure that buf has enough space to accept the string....>There is no way to guess how large buf should be.fucking lmao. thank god no one really supports this anymore. i'm really not sure how useful it would be in the first place, but i guess it had to have had some use in order to get created at all...we can also discuss https://man7.org/linux/man-pages/man5/proc.5.html if there's interest. this guy is pretty coolrelevant 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_sysfs 139
man man
man syscalls
>>108557703
funnily, similar theme as the ophttps://ops.tips/blog/a-month-of-proc/
>>108559144oh, that looks like an interesting read. thanks for posting it!
>>108557703cutecall of the day
>>108557703>there is no way to guess how large buf should beah yes, classic boomer ingenuity and rock solid design
>>108561928i figure, fuck it. map in a page. surely it'll never be larger than that, right? virtual memory is ``free'' anyway
bampu
