liblinux

> Now, do I think it would make total sense for syscall wrappers and NSS to be split into their own libs (or dbus interfaces maybe) with stable ABIs to enable other libc's, absolutely! I worked on this a few years ago: liblinux. https://github.com/matheusmoreira/liblinux It's still a nice proof of concept but I abandoned it when I found out the Linux kernel itself has a superior nolibc library that they use for their own tools: https://github.com/torvalds/linux/tree/master/tools/include/... It used to be a single header but it looks like they've recently organized it into a proper project! > This is something the BSD's got absolutely right. BSDs and all the other operating systems force us to use their C libraries and the C ABI. I think Linux's approach is better. It has a language-agnostic system call binary interface: it's just a simple

I'm not using this stuff professionally, it's just my own home lab's virtual machines with little services implemented as freestanding C programs. Not doing anything fancy right now, much of it was just to see if I could do it. I've seen other people commenting here on HN saying they're using the same approach in production so it's defenitely not my invention. Hopefully they'll see this thread and reply. I published some of my work in the form of a liblinux that I use to make system calls: https://github.com/matheusmoreira/liblinux I'm not developing it anymore though because I found out the kernel itself has a superior nolibc library: https://github.com/torvalds/linux/tree/master/tools/include/... It used to be a single header but it looks like they've recently organized it into a proper project! I wonder if it will become some kind of o

That's awesome. I didn't know about rwildcard until now. Is it part of GMSL? I searched for rwildcard on gmsl.sourceforge.io but didn't find it. I think my function is needlessly complicated compared to rwildcard. Here's my code: https://github.com/matheusmoreira/liblinux/blob/modular-buil... https://github.com/matheusmoreira/liblinux/blob/modular-buil... The file? and directory? functions were inspired by GMSL. I think I learned how to check whether a path is a directory from one of your posts. I wrote a general recursion function. It takes a function to apply to lists and a function to compute whether an element is a base case. The recursive file system traversal function applies a directory globbing function to the list of paths and has file? as base case. It returns all files without filtering. The find function recursively traverses

Linux is the only operating system that guarantees kernel binary interface stability. You can discard the entire user space and write dependency-free software that interfaces with Linux directly. You can even boot Linux straight into your own program and bring up the system yourself. This single function is all you need to do literally anything on x86_64 Linux from writing to a file descriptor to graphics card ioctls: https://github.com/matheusmoreira/liblinux/blob/master/sourc... In all others, interfacing with the kernel directly eventually leads to breakage because the people in charge change the system calls. Go binaries broke on OS X because of this. We're not meant to bypass their system libraries.