If you need to run a five year old version of [PHP|Apache|Nginx|Caddy|whatever], Ubuntu is a solid bet. None of that "we need to update our configuration to a new format to solve a criticial CVE issue" nonsense, for much longer than Debian is offering free labour.

Debian has its own flaws, like its controversial patches, lack of real LTS releases, and lack of business contracts guaranteeing support directly from the source if you're a business.

I have yet to encounter any issues with either sudo-rs or their coreutils rewrite. From what I've come to expect from utcc.utoronto.ca, I'm not surprised they're using some obscure feature that Canonical chose to remove, though. I'm surprised they're even running Ubuntu.

I started off with Ubuntu in the 2010s because I wanted to try out Linux but was sure as hell didn't have the patience nor resources to make consumer conveniences like WiFi just work. The local LUG was also heavily promoting it; that's even more inertia.

Then I got fancy and started really customizing my configuration---I got a dotfiles repo. The oldest commit touching a top-level file in my dotfiles is 11 years ago (almost unthinkable to me!). I haven't really tried it out on any other distro but I'm pretty sure I've written some shim or personal bash command relying on something Ubuntu-specific.

I happen to be in the market for a new laptop right now. I'm looking at Starlabs but unfortunately they do not ship with Debian. Today, however, I saw a random woman in a cafe with Linux Mint so that might be my sign to investigate that ecosystem.

Also, Gnome and KDE are both horribly unintuitive for newcomers. Ubuntu makes a several tweaks to Gnome to make it more user-friendly. Debian just gives a list of names and says to choose one or more.

It is mostly just inertia though.

I want the simplest possible experience. There is more documentation for Ubuntu, which means things are more likely to work. Or if they don’t work, someone might have posted about the issue.

sudo being slightly different doesn’t make a difference for me when my laptop experience of sudo is “sudo apt …”.

Those days are likely done.

The GPU and unified memory is great though.

I should note I am a Debian diehard been using it 20 years my main workstation is still on deb12 lol. But recently I have been pivoting away from Debian and towards Fedora. Running Fedora 44 on my Framework 13 Pro and my Chuwi N150 netbook and it has been very stable and pleasant. Relatively cutting edge, too. I am on KDE 6.8 for instance.

Despite that it was just upgrade to new OS version and SSD replacement.

Though one of servers is getting upgraded to Debian from Ubuntu adware.

It's not a bug, it's a deliberate incompatibility, as noted by the article's author:

>> Wildcards in command line arguments are not supported—using these in original versions of sudo was usually a sign of mis-configuration and consequently sudo-rs simply forbids using them. The only supported use is ‘’ as the final argument to indicate “zero or more subsequent arguments as noted above.*

> I do not really have words for this. The Rust sudo has apparently opted to keep the single most dangerous wildcard while disallowing all of the wildcards that allow one to be narrow and specific about what you're allowing, and it buries this at the end of a section that devotes a bunch of words to describing functionality it doesn't have and doesn't support, with absolutely nothing else in that section to say this (either up front or in the descriptions of how all the wildcards would work if sudo-rs supported them, which it doesn't).

If someone tries to do an in-place upgrade to Ubuntu 26.04, sudo-rs could potentially be installed instead of 'regular' sudo, and now you have a potentially system with borked functionality.

> It's open source, so I think reporting bugs or submitting a PR is just good citizenship.

LOL, the author's very next weblog post:

> One reaction to my entry on how the Rust Sudo is not fully compatible with proper Sudo is that I should have filed a bug report about this behavior. One of the reasons I have not done this comes down why I was using the Rust Sudo, and in my view it's a wider issue with bug reporting in general. To put it simply, I am (or was) an involuntary user of the Rust Sudo, not a voluntary one.

[…]

> In a project centered view, all people using Rust Sudo 'should' report issues to the project because that's how FOSS projects improve (this is not really true, the project unquestionably only wants what it considers 'good' bug reports and will be unhappy about ones that, for example, revisit decisions it has no intentions of changing). In the people centered view, many people have not chosen to use the new Rust Sudo or the Rust Coreutils, they've been stuck with them by Canonical's decisions. These people are under no obligation to help out with Canonical's apparent project of improving these projects (or help out the projects themselves); the Ubuntu project does not get to make everyone using Ubuntu into obligatory bug reporters through its own choices.

* https://utcc.utoronto.ca/~cks/space/blog/sysadmin/BugReports...

Canonical don't owe them anything. . I really think some people just need to keep their opinion to themselves.