liblinux
rustix
liblinux | rustix | |
---|---|---|
16 | 15 | |
195 | 1,321 | |
- | 1.7% | |
0.0 | 9.4 | |
over 4 years ago | 9 days ago | |
Makefile | Rust | |
MIT License | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
liblinux
- Liblinux – architecture-independent access to Linux system calls
-
A standalone zero-dependency Lisp for Linux
> libc isn't really getting in the way here.
For the standard set of system calls, the libc is pretty great. For Linux-specific features, it could take years for glibc to gain support. Perhaps it's gotten better since then, perhaps it still takes years. I don't know.
Years ago I read about the tale of the getrandom system call and the quest to get glibc to support it:
https://lwn.net/Articles/711013/
A kernel hacker wrote in an email:
> maybe the kernel developers should support a libinux.a library that would allow us to bypass glibc when they are being non-helpful
That made a lot of sense to me. I took that concept and kind of ran with it. Started a liblinux project, essentially a libc with nothing but the thinnest possible system call wrappers. Researched quite a bit about glibc's attitude towards Linux to justify it:
https://github.com/matheusmoreira/liblinux#why
Eventually I discovered Linux was already doing the same thing with their own nolibc.h file which they were already using in their own tools. It was a single file back then, by now it's become a sprawling directory full of code:
https://github.com/torvalds/linux/tree/master/tools/include/...
Even asked Greg Kroah-Hartman on reddit about it once:
https://old.reddit.com/r/linux/comments/fx5e4v/im_greg_kroah...
Since the kernel was developing their own awesome headers, I decided to drop liblinux and start lone instead. :)
-
Nolibc: A minimal C-library replacement shipped with the kernel
It gives you access to 100% of Linux's system calls. It eliminates a lot of global state. It gets rid of a lot of legacy libc crap.
Years ago I wrote a fairly referenced rationale in my liblinux project:
https://github.com/matheusmoreira/liblinux/blob/master/READM...
-
Win32 Is the Only Stable ABI on Linux
> 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
I'm not developing it anymore though because I found out the Linux 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 official kernel library at some point. I asked Greg Kroah-Hartman about this and he mentioned there was once a klibc:
https://old.reddit.com/r/linux/comments/fx5e4v/im_greg_kroah...
> This is something the BSD's got absolutely right.
BSDs, every other operating system really, force us to use the bundled 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 calling convention and the system call instruction.
The right place for system call support is the compiler. We should have system_call keywords that cause it to emit code in the aforementioned calling convention. With this single keyword, it's possible to do program literally anything on Linux. Wrappers for every specific system call should be part of every language's standard library with language-specific types and semantics.
-
Oasis: Small statically-linked Linux system
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 so it's defenitely not my invention.
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 nolibc library:
https://github.com/torvalds/linux/tree/master/tools/include/...
It used to be a single header but it looks like they've organized it into a proper project.
-
A Tutorial on Portable Makefiles
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 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.
The find function filters out any items not matching a given predicate function. It was my intention to provide predicates like C_file? and header_file? but I stopped developing that project before that happened.
I think rwildcard is probably simpler and more efficient!
- GitHub - matheusmoreira/liblinux: Linux system calls.
- liblinux: Architecture-independent access to Linux system calls
- Liblinux is a C library that provides architecture-independent access to Linux system calls.
rustix
-
OpenBSD 7.5 Released
It would be great for Rust to have a Linux target that doesn't use libc, but from what I've read, not many people are interested in this.
Found this as well: https://github.com/sunfishcode/mustang
Some discussion here: https://github.com/bytecodealliance/rustix/issues/76
-
Rust criticism from a Rustacean
Without actually having looked into this, how does https://github.com/bytecodealliance/rustix fit into points 1 & 2?
-
Cargo build in debug taking longer than in release?
I find this github issue: https://github.com/bytecodealliance/rustix/issues/575
-
Integrating rustix on NuttX
Hi Rust experts, we are willing to integrate rustix on NuttX RTOS, the initial effort was done by rustix author: https://github.com/bytecodealliance/rustix/tree/nuttx but it hit the wall since we don't know the right way to integrate cargo with the old-school NuttX's Makefiles. Any help or suggestion is welcome. More about NuttX here: https://nuttx.apache.org and here: https://nuttx.apache.org/docs/latest/
-
Pgwm 0.3 a pure rust `no_std` no libc window manager.
Have you considered using rustix? It provides many of the facilities of std without using libc.
- NVIDIA Security Team: "What if we just stopped using C?" (This is not about Rust)
-
Will Rust drop dependency on libc and make direct system calls? when ? (Please don't mention no_std case)
rustix can make syscalls directly to Linux. There's a rustc fork that can use it to build std.
-
Can rust be entirely written in rust and drop C usage in its code base ?
The rustix project claims to use raw syscalls (and vDSO calls) on linux and provides more memory / type safety compared to the libc API.
-
memmapix: A pure Rust library for cross-platform memory mapped IO, which replace libc with rustix.
Hi, the reason is explained by the description of https://github.com/bytecodealliance/rustix.
-
What crates would you add to a "batteries-included" library for Rust?
Please consider rustix as an alternative to nix.
What are some alternatives?
cosmopolitan - build-once run-anywhere c library
relibc - Mirror of https://gitlab.redox-os.org/redox-os/relibc
vscode-gitlens - Supercharge Git inside VS Code and unlock untapped knowledge within each repository — Visualize code authorship at a glance via Git blame annotations and CodeLens, seamlessly navigate and explore Git repositories, gain valuable insights via rich visualizations and powerful comparison commands, and so much more
clap-rs - A full featured, fast Command Line Argument Parser for Rust
libratbag - A DBus daemon to configure input devices, mainly high-end and gaming mice
compiler-builtins - Porting `compiler-rt` intrinsics to Rust
minibase - small static userspace tools for Linux
libc - Raw bindings to platform APIs for Rust
linux - Linux kernel source tree
mustang - Rust programs written entirely in Rust
safestringlib
rust-brotli - Brotli compressor and decompressor written in rust that optionally avoids the stdlib