mustang
linux
mustang | linux | |
---|---|---|
20 | 982 | |
792 | 170,551 | |
- | - | |
7.5 | 10.0 | |
14 days ago | 7 days ago | |
Rust | C | |
GNU General Public License v3.0 or later | 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.
mustang
-
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
- Mustang
-
Rust criticism from a Rustacean
On Linux there has been some attempts to get exactly this solutions, most notibly https://github.com/sunfishcode/mustang but the topic did not seem to fetch a prominent position on the supported feature list.
-
Microsoft rewriting core Windows libraries in Rust
For Linux, Mustang already exists because Linux has a stable syscall API
- Mustang: Rust target with std and no linking to a Libc
-
The Rust Implementation Of GNU Coreutils Is Becoming Remarkably Robust
Why bother with a libc at all, when you can skip it entirely on Linux!
-
Why so few, if any, pure Rust apps?
Mustang is a project which is able to run some non-trivial programs written in Rust, such as ripgrep, without using any libc, on Linux.
-
Can rust be entirely written in rust and drop C usage in its code base ?
Mustang is one way to take care of the tiny amount of "C" that runs before main().
-
How do I use Zig as Rust's Standard C Library?
This is more a Rust question than a Zig question. In Rust, the choice of a specific libc (or to not use a libc) is part of the "target", for example many hardware platforms have gnu/musl/none targets. See also relibc or mustang for pure-rust alternatives. Each libc alternative require some work to integrate into Rust.
-
memmapix: A pure Rust library for cross-platform memory mapped IO, which replace libc with rustix.
There's a separate project for that, called Mustang. It's built on top of rustix and provides all those things. It's not super mature yet, but it is able to run ripgrep by itself: https://github.com/sunfishcode/mustang
linux
- Memory is cheap, new structs are a pain
-
The File Filesystem
FFS predates FreeBSD and is in some capacity supported by all 3 major BSDs. I'm fairly confident that Linux actually supports it through the ufs driver ( https://github.com/torvalds/linux/tree/master/fs/ufs ); whether the use of different names in different places makes it better or worse is an exercise for the reader.
-
Linus Torvalds adds arbitrary tabs to kernel code
These are a bit easier to see what's going on:
https://github.com/torvalds/linux/commit/d5cf50dafc9dd5faa1e...
https://github.com/torvalds/linux/blob/d5cf50dafc9dd5faa1e61...
Unfortunately Github doesn't have a way to render symbols for whitespace, but you can tell by selecting the spaces that the previous version had leading tabs. Linus changed it so that the tokens `default` and the number e.g. `12` are also separated by a tab. This is tricky, because the token "default" is seven characters, it will always give this added tab a width of 1 char which makes it always layout the same as if it were a space no matter if you use tab widths of 1, 2, 4, or 8.
- Show HN: Running TempleOS in user space without virtualization
-
PfSense Software Embraces Change: A Strategic Migration to the Linux Kernel
There was also a Gentoo effort to run atop FreeBSD[0]. The challenge of course is that afaik none of the BSD kernel ABIs are considered stable. The stable interface is the BSD libc. That said, with binfmt_misc, I don't see a reason you couldn't just run (at least some) FreeBSD binaries on Linux with a thin syscall translation layer (rather something like qemu-system) and then your layer hooked via binfmt_misc. I'm not aware of anyone who has done this for FreeBSD, but prior efforts existed as alternate binfmts for SysVr4/5 ELF binaries[2]. Either way would take some elbow grease, but you *might* even be able just reuse binfmt_elf and just have a new interpreter for FreeBSD elf.
[0] https://wiki.gentoo.org/wiki/Gentoo_FreeBSD
[1] https://docs.kernel.org/admin-guide/binfmt-misc.html
[2] https://github.com/torvalds/linux/blob/master/fs/binfmt_elf....
-
Improvements to static analysis in GCC 14
> The original less-than check was deemed incorrect
It was only deemed incorrect because of an information leak. Not because it's a valid use-case for user space to copy smaller portions of *hwrpb into user space. https://github.com/torvalds/linux/commit/21c5977a836e399fc71...
- Linus Torvalds accepts a merge commit to the Linux kernel
-
TinyMCE (also) moving from MIT to GPL
Correct. And the combined work needs to carry the MIT license text and copyright attributions for the MIT software authors. With binary distribution it must also be overt, not hidden in some source code drop, but directly accompanying the binary.
Many people who talk about relicensing never credit the MIT developers or distribute the MIT license text. "Because it's GPL now."
I don't think that you believe that, but many developers do.
Some don't see the need for source code scans for Open Source compliance, because the license.txt says GPL, so it's GPL. Prime example is the Linux kernel. There is code under different licenses in there, but people don't even read https://github.com/torvalds/linux/blob/master/COPYING till the end ("In addition, other licenses may also apply.") and conclude it's simply GPL 2 and nothing else.
Also be aware that sublicensing is not the same as relicensing.
-
Linus Torvalds is looking for a more modern GUI editor
> Does he have something against it?
He notoriously hates GNU Emacs, yes.
https://marc.info/?m=122955159617722
https://github.com/torvalds/linux/blob/master/Documentation/...
-
The Linux Kernel Prepares for Rust 1.77 Upgrade
So If we would only count code and not comments, it is only 9489 LoC Rust. Which would be about 0.03% and if we take all lines and not only LoC it would be around 0.05%
[0] https://github.com/XAMPPRocky/tokei
[1] https://github.com/torvalds/linux/commit/b401b621758e46812da...
What are some alternatives?
ziglibc
zen-kernel - Zen Patched Kernel Sources
relibc - Mirror of https://gitlab.redox-os.org/redox-os/relibc
DS4Windows - Like those other ds4tools, but sexier
liblinux - Linux system calls.
winapps - Run Windows apps such as Microsoft Office/Adobe in Linux (Ubuntu/Fedora) and GNOME/KDE as if they were a part of the native OS, including Nautilus integration.
rustix - Safe Rust bindings to POSIX-ish APIs
Open and cheap DIY IP-KVM based on Raspberry Pi - Open and inexpensive DIY IP-KVM based on Raspberry Pi
jython3 - A sandboxed attempt at v3 (not maintained)
serenity - The Serenity Operating System 🐞
libc - Raw bindings to platform APIs for Rust
DsHidMini - Virtual HID Mini-user-mode-driver for Sony DualShock 3 Controllers