The beta release of Ubuntu 26.10 (Stonking Stringray) is now available for download – a week later than planned. Ubuntu 26.10 Beta runs on the Linux 7.3
For anyone testing the beta, the two lower-level changes are probably the ones most worth poking at before the 15 October release, since they’re the ones most likely to break things silently rather than visibly:
Rust coreutils is now complete, including cp, mv and rm. If you have backup scripts, deploy scripts or anything that parses the output of these tools or relies on less common GNU flags, run them on the beta now and report differences upstream to uutils. Behaviour differences in edge cases (symlinks, sparse files, odd permissions, error messages) are exactly what a beta is for.
dbus-broker replacing dbus-daemon: mostly invisible, but if you have custom D-Bus policy files or services that do unusual things on the session bus, it’s worth checking the journal for warnings after login.
The OOM change (core desktop processes getting lower OOM scores) sounds like a genuine quality-of-life fix for anyone who’s had the whole session killed while a browser ate all the RAM.
I’m a fedora user actually, but, I’m actually a fan of the Coreutils rewrite. And, you’re definitely right for pointing it out.
Some of the responses I saw regarding the rewrite were absolutely ridiculous though (there were people claiming they’d add certain parameters behind subscription model, etc, which wouldn’t be possible).
For anyone testing the beta, the two lower-level changes are probably the ones most worth poking at before the 15 October release, since they’re the ones most likely to break things silently rather than visibly:
cp,mvandrm. If you have backup scripts, deploy scripts or anything that parses the output of these tools or relies on less common GNU flags, run them on the beta now and report differences upstream to uutils. Behaviour differences in edge cases (symlinks, sparse files, odd permissions, error messages) are exactly what a beta is for.The OOM change (core desktop processes getting lower OOM scores) sounds like a genuine quality-of-life fix for anyone who’s had the whole session killed while a browser ate all the RAM.
Parsing the output of
rm,cp,mv, and such tools seems volatile. Better to use their return codes, no?I’m a fedora user actually, but, I’m actually a fan of the Coreutils rewrite. And, you’re definitely right for pointing it out.
Some of the responses I saw regarding the rewrite were absolutely ridiculous though (there were people claiming they’d add certain parameters behind subscription model, etc, which wouldn’t be possible).