Live data from Hacker News

Ubuntu 26.10 completes transition to Rust-based coreutils

omgubuntu.co.uk

141–150 of 271 posts

Re: Ubuntu 26.10 completes transition to Rust-based coreutils

#141

I 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…

yeah, this is a bug. And yes, it should be fixed. But I don't think it will affect many users, I mean who has a 32000 -evels deep directory on their system?

It's less about the specific issue and more indicative of bad/insufficient test coverage

Re: Ubuntu 26.10 completes transition to Rust-based coreutils

#143
post #119

Earlier quoted context omitted.

Yes, please. Linux distros is better with macos approach. And making appimage first class makes a lot of sense.

Appimages are bloated and unreliable. You can't guarantee that your app will run on any machine because it might depend on different system libraries. Flatpak uses shared stable runtimes that are the same everywhere and don't take up space more than once. It also comes with a native update system and sandboxing. Snap is the same thing but worse.

My problem with flatpak is that the underlying runtime has a limited lifespan. I used the Sublime Text 3 flatpak for many years, and it was deprecated a few months ago because the runtime it was using was no longer supported. This caused people to update the flatpak to Sublime 4, which is good, but I only have a license for 3. In the end I just downloaded the binary for 3 from their website, and it still just worked. Flatpak still doesn't save you from bitrot.

Re: Ubuntu 26.10 completes transition to Rust-based coreutils

#144
post #28

Earlier quoted context omitted.

That way of thinking just means it'll never be fixed

"The Linux philosophy is 'Laugh in the face of danger'. Oops. Wrong One. 'Do it yourself'. Yes, that's it." Linus Torvalds

It's complicated to do it yourself when upstream won't accept your code.

Re: Ubuntu 26.10 completes transition to Rust-based coreutils

#148

I 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…

to enable GPL free embedded Ubuntu, field tested on all platforms (because it happens to be the default).

Re: Ubuntu 26.10 completes transition to Rust-based coreutils

#149
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 execution.

Re: Ubuntu 26.10 completes transition to Rust-based coreutils

#150

If 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.
Post reply on HN