Fil-C[0] can compile GNU coreutils, it has stronger* memory safety guarantees than rust, none of the compatibility issues that a wholesale rewrite has, and performance that seems to be within about a factor of two[1] compared to the normally compiled code.. [0]: https://fil-c.org/ . [1]: https://bannalia.blogspot.com/2025/11/comparing-run-time-per... * Guaranteed to crash rather than potentially grant arbitrary code…
Ubuntu 26.10 completes transition to Rust-based coreutils
161–170 of 271 posts
Re: Ubuntu 26.10 completes transition to Rust-based coreutils
#162Was there something wrong with how they are currently written or do they just want the badge that says they converted to Rust?
Neither. They basically see Rust as the future. They want to be able to attract young contributors and to hire young employees who are excited about Rust and who want the safety features. Bear in mind, the average age of the Linux developer is increasing. They also see technical benefits in Rust. And they are increasing test coverage of both the Rust tools and the tools written in C, IIRC. My source is this interview…
Re: Ubuntu 26.10 completes transition to Rust-based coreutils
#163If you ask their motivation? "We want to make them safer" They worked pretty fine for decades, now, who needs these rewrites? Not saying it's useless, but in practice, what benefits did this bring?
it's GPL free. which is good for embedded, the business side of it. like cars.
Re: Ubuntu 26.10 completes transition to Rust-based coreutils
#164So what is the way forward for Linux to have sandboxi g as strong as Android? Appimage everything? I know it's possible now hacking together things, but I mean by default and integrated.
Re: Ubuntu 26.10 completes transition to Rust-based coreutils
#165Re: Ubuntu 26.10 completes transition to Rust-based coreutils
#166Fil-C[0] can compile GNU coreutils, it has stronger* memory safety guarantees than rust, none of the compatibility issues that a wholesale rewrite has, and performance that seems to be within about a factor of two[1] compared to the normally compiled code.. [0]: https://fil-c.org/ . [1]: https://bannalia.blogspot.com/2025/11/comparing-run-time-per... * Guaranteed to crash rather than potentially grant arbitrary code…
"Stronger" is absolute bullshit. No data race prevention. No intra-object protection. Mandatory GC, and 5x the compute cost. Nothing like a statically safe language.
Re: Ubuntu 26.10 completes transition to Rust-based coreutils
#167Hmm, this doesn’t make sense. You simply don’t replace utilities with many decades of maturity and that “just work” with something that is not as mature. It will open all users of the distro to all sorts of subtle and not so subtle bugs. I for one don’t want to find myself staring at a mysterious segfault when I want to build the latest version of nodejs or flash a microcontroller. It’s such a pity; I have used Ubunt…
Re: Ubuntu 26.10 completes transition to Rust-based coreutils
#168 Just because it is Rust, it is not safe!
It worked before, don't replace it!
etc.
Not that these are not valid points of criticism, but in my opinion if we have two core utils we can (and should) pick the better one after careful continous evaluation. And if the old one is the better one on the day of the release, so be it. Having two competing solutions can have benefits for everybody looking for the best core utils they can get in the long run.I had to reimplement and reverse engineer old tech myself as part of my dayjob and had those engineers seen my results it probably would have improved their work as well, since I usually found oddities that they probably did not intend to be that way. This means my work on their work could be seen as another pair of eyeballs, bullet-proofing their original work, instead of seeing me as a threat. That additional pair of eyeballs is crucial to open source software.
This is why it is sad that too much about this whole discussion feels like yet another culture war, heated on the stove of social media figures looking to convert heat into ad revenue.
Which is why I would love to have more concrete points of technical criticism of specific bits maybe even to specific lines in the code or specific reproducable behavior.
If we go the culture-war route nobody wins, if we discuss both solutions on their merits, we all can win.
Re: Ubuntu 26.10 completes transition to Rust-based coreutils
#169I really don't understand why Canonical rushes this. If 'rm' can't remove all possible directory entries, that is a big issue: $ podman run --rm -it ubuntu:26.10 $ apt update -y; apt upgrade -y $ rm --version rm (uutils coreutils) 0.10.0 $ gnumkdir -p $(yes a/ | head -n $((32 * 1024)) | tr -d '\n') $ rm -rf a Segmentation fault (core dumped) rm -rf a $ ls a a $ gnurm -rf a $ ls a ls: cannot access 'a': No such file o…
Re: Ubuntu 26.10 completes transition to Rust-based coreutils
#170Earlier quoted context omitted.
This isn't a port - it's a re-implementation without any use of the original source. That's also not all that's happening. It's also making improvements like better internalization support, better error messages, and a small handful of other extensions.
I have had to tell them repeatedly to stop copying tests verbatim, including the original comments from GNU coreutils. So I doubt this is true, which is frustrating.