liblinux

> That header file is amazing. Thank you for the pointer to that. Yeah, it's an awesome header! It comes straight from the kernel developers too. They use it for their own tools, apparently. It might be missing some of the newer or niche system calls but it has generic mechanisms which can be used to access everything. I found it during my research for my own Linux system calls library project: https://github.com/matheusmoreira/liblinux There's some additional details implemented by my project such as process start up functions which handle argument, environment and auxiliary vectors. I don't see the need to maintain it anymore though since nolibc.h is so amazing and practical. I even asked Greg Kroah-Hartman about nolibc.h on Reddit: https://old.reddit.com/r/linux/comments/fx5e4v/im_greg_kroah...

The Go runtime apparently uses system calls directly. The implementation of every other programming language I know uses the C standard library. Rust has a freestanding mode which is great. I even made a crate for Linux system calls but that needs inline assembly which isn't stable yet. As for user space projects, I know this one: https://github.com/arsv/minibase I meant to start my own but replacing what already exists is a lifetime of work. Haven't had much free time these days nor the willpower to make it happen. I created a liblinux but it's incomplete: https://github.com/matheusmoreira/liblinux I also found out the Linux kernel itself has an excellent system call stubs header which they apparently use for their own tools: https://github.com/torvalds/linux/blob/master/tools/include/...

> the chrt command is broken when built against musl-libc because that project's maintainer decided he didn't like the system calls it depends on, so he removed them¹ from his libc. This software seems to be using Linux-specific functionality through the C library. Wouldn't it be better to use Linux system calls directly in that case? I think it's weird how Linux has no user space library like the kernel DLLs found in Windows. Everyone assumes the C library is the interface to the kernel, even the Linux kernel manuals. Then people end up being burned when the C library maintainers quote POSIX standards at them or omit new system calls people want. I wrote a liblinux² when I first realized this but it's currently unfinished. Eventually the kernel developers made an amazing nolibc.h file³ for their own tools but it doesn't seem to be used o