Show HN: I've updated my Linux System Call website and API
101 points - today at 9:29 AM
I first released those in back in 2020 and now I finally added more architectures, Kernel selector, syscall descriptions and a few other niceties. It should work a bit better on mobile devices too but I am no CSS expert.
The API is at https://api.syscall.sh
Comments
DustinBrett today at 2:31 PM
That website messes with my graphics for some reason.
bkallus today at 11:49 AM
On x86_64 and x32, the syscall number goes in eax, not rax. The upper 32 bits of rax are ignored and can be anything.
guitmz today at 12:49 PM
I also made a CLI for consulting the syscall API when I originally released the website. I think I can tidy up the code and make it public too. It uses a embedded dataset so it does not have to query the API endpoint all the time
hmokiguess today at 1:38 PM
I am not familiar with the internals, so excuse my question, but how does one builds this? Separately, how often can it get stale?
wg0 today at 12:24 PM
This is really great resource, didn't know about it. But one question not related to the website above - why the syscalls vary per architecture if the linux API is the same?
Or is it I am confusing it with the C standard library/POSIX and assuming that it should be the same everywhere?
shoobiedoo today at 12:17 PM
This is very handy, thank you. Currently learning aarch64 assembly
ReDress today at 10:41 AM
If syscalls are so similar, for instance, like 'read' and 'readv' or 'pread', 'sendmsg' and 'sendmsgv' or 'fork' and 'vfork'.
Does it still make sense to term or classify them as two distinct syscalls?