← Back to context

Comment by voakbasda

16 days ago

Yeah, their lack of a satisfactory response is the final nail in their coffin. This incident escalates my consulting advice about Ubuntu from “not recommended” to “switch immediately”.

Some of my clients may be surprised by this change, as I once advocated for Ubuntu as a good choice for a development and deployment platform. While that has not been true for quite a while, they have now jumped the shark into eel-infested waters; I cannot take them seriously any longer.

Plain Debian was always best option; even RHEL dropped the ball on this CVE and that's distro people pay for support

  • Not always. Notably, if you have compliance requirements like needing FIPS encryption (say because you have government customers), or that requires you to use a commercial vendor, debian won't work. And if you need more up to date system packages, or a reliable release cadence, Ubuntu might be better.

    On desktop, if you need proprietary drivers, Ubuntu is easier to set up.

    But yes, if debian works for you, I wouldn't use Ubuntu.

    • I had to deal with FIPS once because the company I worked for shipped a custom Linux distribution with the product and we had to essentially shoe-horn in some Red Hat OpenSSL packages to get it to meet FIPS requirements. What's funny is that after the customer enabled FIPS, administration became much harder, and the encryption strength was strictly worse.

      Anyway, needing FIPS is something of a niche requirement. Debian or Rocky are very sane choices as a default Linux distribution for general-purpose servers until you run up against special requirements.

      1 reply →

    • Uh, yes it will. OpenSSL in Trixie is a version supported.

      https://packages.debian.org/trixie/openssl-provider-fips

      It's just the library, nothing special about the OS.

      https://csrc.nist.gov/projects/cryptographic-module-validati...

      As far as I know, compliance comes with an external module:

      https://openssl-library.org/post/2025-03-11-fips-140-3/

      This module seems to be in Debian:

      # apt-cache search fips | grep open openssl-provider-fips - Secure Sockets Layer toolkit - cryptographic utility

      # dpkg -L openssl-provider-fips /. /usr /usr/lib /usr/lib/x86_64-linux-gnu /usr/lib/x86_64-linux-gnu/ossl-modules /usr/lib/x86_64-linux-gnu/ossl-modules/fips.so /usr/share /usr/share/doc /usr/share/doc/openssl-provider-fips /usr/share/doc/openssl-provider-fips/changelog.Debian.gz /usr/share/doc/openssl-provider-fips/changelog.gz /usr/share/doc/openssl-provider-fips/copyright

      There seems to be the validation process, which supposedly must run on each machine it is used on.

      openssl fipsinstall -out /tmp/configfile.cnf -module /usr/lib/x86_64-linux-gnu/ossl-modules/fips.so 2>&1 | tee /tmp/result.txt

      --

      The above are from my notes, and a test run. But I don't see how Redhat is "special" here. If the module loads and cites compliance, you comply.

      6 replies →

  • I planned to install Debian in 2009 and in 2014 but the installer was too hard to use, the desktop in 2009 was ugly (maybe in 2014 too), I could not get a running system that I could use to work. Fast forward to Debian 10, same laptop from 2014, and I got a desktop identical to Ubuntu GNOME.

  • Debian for hosting anything, Fedora for development desktop.

    That's been my rule for years at this point, I think I switched back to debian everywhere after the netplan changeover in ubuntu so somewhere around 17-18 (not against it in principle, just the way they did it in practice).

    No real regrets either.

The general advice I've been seeing the past ~8 years is "There is no reason to pick Ubuntu over Debian". I don't know who the opposite advice comes from and why anyone would pick ubuntu for a server.

  • 15-20 years ago the joke was that Ubuntu is a Zulu word that, roughly translated, means "I don't know how to configure Debian". Ubuntu was one of the first distros that allowed one to easily download proprietary WLAN drivers without dealing with the terminal, ndiswrapper, or compiling half-broken OSS implementations; for this reason it caught fire with those who wanted to try Linux but were otherwise unwilling to engage in such shenanigans. I tried it on a laptop around this time and was quite impressed. This reputation for "it just works" has carried them ever since even though other distros now do largely the same thing ( cheap, obscure, or recently-released hardware excepted).

    I took the lazy Mint route with my most recent machine since I wanted to use it for light gaming with minimal fuss. I'm going to redo it with Nix sometime soon because the value prop simply isn't there and I'd like to try a declaratively-configured distro.

    • I recently installed NixOS on my thinkpad z16. I set up a sandboxed pi agent to help me configure it and I think it works great. (I also read enough documentation to understand the nix language).

      I hade some issues with the trackpad (worse issues that it not being an apple trackpad ie). I told the agent about the problem. It inspected the config, wrote some scripts for me to run outside the sandbox that listened to the trackpad while I used in as per some instructions, and then proceeded to add a few configuration lines that solved to problem. I was pretty impressed (though I think there were maybe 3 back-and-forths with scripts to run, tbh).

    • They also sent out free distro CDs. That helped convince me this new fangled Linux thing might be legitimate.

      Christ that was 2008.18 years ago. My Linux 'experiment' is old enough to vote

      2 replies →

    • More like 20. If I remember it right, by 2007 the Debian community was angry discussing the installation team's decision to include non-free packages in the installation media, what ended the problem of needing a wired connection during the install.

    • > Ubuntu was one of the first distros that allowed one to easily download proprietary WLAN drivers without dealing with the terminal, ndiswrapper, or compiling half-broken OSS implementations

      None of which was a good reason to use it on servers. Even if you were familiar with Ubuntu there is very little difference between an Ubuntu server and a Debian one.

      5 replies →

    • Same for servers. 22 years ago you could install Debian, take it offline while you follow the "Securing Debian Manual" to disable NIS and maybe disallow SSH password logins.

      Or you could install Ubuntu which wanted to be secure by default. No open ports in the default install, no shared root password, etc.

      Nowadays most of this is common place for distros.

  • I advocated for Ubuntu for years because it was easier to install and had excellent hardware support. For 2026 I have switched back to Debian because Ubuntu has been making my life more difficult. Ubuntu 26 basically forces you onto Wayland even though it breaks some of my use cases, particularly with screen recording. It turns everything into Snaps which is a hassle because it means I need to mirror both the regular repo and the snaps to my closed network instead of just the repo.

    Ubuntu still has the superior installer by a good margin, but it does sometimes like to crash when run offline. Debian's installer at least has the option to go text only. There is also more work to do after the install is finished on Debian, but since that's a script it's not such a big deal.

    The one bit of the Debian installer I dislike the most is how if you aren't online when you do the install you get a completely empty sources.list, and the Debian sources are a lot more complicated than Ubuntu's. Debian's support for third party drivers like nVidia graphics is also more complicated and confusing than Ubuntu's.

    • Ubuntu is a great starter linux. But you cant live on it, especially in a business.

  • Enterprises love paying for support contracts. If you have one, you can demonstrate something has been accounted for. A secure software without support is worse from an audit perspective than a security disaster with proper paperwork. Most of these people never actually involve support they paid for ever.

    • > Enterprises love paying for support contracts.

      They can pay for Debian support! (I’m not 100% sure who they should go to, but e.g. Freexian are doing Extended LTS for Debian [1], so I suppose they could do a regular support contract as well?)

      [1]: https://wiki.debian.org/LTS/Extended

    • > Most of these people never actually involve support they paid for ever.

      I've only been in an involved role at one enterprise large enough to pay for support contracts like these, but that one had no trouble getting vendors onto the WebEx while troubleshooting things even if it wasn't clear yet that it was the vendor's fault.

      (In fact, they were paying enough that the vendors would actually just hop in to help out with the internal configuration. The most we ever heard were grumblings that we used too high of a priority level on the tickets, but even then, the sentiment from the managers was generally "we're paying for it, and we'll handle those complaints, so do what you need to do to get them on the line.")

    • A quick search shows all sorts of projects choosing Ubuntu. Can you explain a project like mail-in-a-box going with it? And 5.15 kernel at that..

      3 replies →

  • I deployed Ubuntu on a LOT of servers 10 years ago because at the time, they had a track record of doing good things in, with, and for, the Linux and open source community. I had already been using it on the desktop for a long time by that point and knew it well. Ubuntu was far and away the most popular; it was a very safe and sane choice.

    That changed when they started heavily promoting Snaps as the next big thing and started putting features and updates behind their enterprise offerings. Basically, they stopped being "Debian, but better." And Debian also made lots of incremental improvements in user-friendliness in that time. Basically, Debian is now pretty much what Ubuntu always promised to be.

  • Platform support. Oracle Cloud for example only provides images[1] for Oracle Linux, RHEL, Ubuntu, and Windows Server. Anything else you have to bring your own.

    [1] https://docs.oracle.com/en-us/iaas/Content/Compute/Reference...

    • If I try to create a new instance on Oracle Cloud, these are the options: Oracle Linux, Ubuntu, RHEL, (CentOS), Windows Server, AlmaLinux, Rocky Linux.

      Anyway you are right, I would have switched already if Debian was available. I guess AlmaLinux could be an option to consider, since I've read in another comment that they've patched ahead of upstream for several vulnerabilities this year.

      1 reply →

    • This. For llama-cpp and stable-diffusion-cpp, you get official builds only for Ubuntu 24.04 LTS and Win and MacOS. If you want to run ROCm, support is available in the form of an irreversible install script that wrecks any amdgpu driver install and requires run level 3 ie. without GUI. Good luck with running that on anything other than the exact Ubuntu release it was created for.

      1 reply →

  • The only recent reason I’ve managed to come up with is it far and away has the best support for Nvidia’s various drivers and utilities for running GPUs and its assorted ecosystem, like Infiniband and Spectrum-X Ethernet.

    If there’s another option I’m unaware of, I’d love to hear it. Also to be fair, I didn’t evaluate Sid for this, only Stable.

  • I've set up a new server literally couple weeks ago on a droplet on Digital Ocean - Ubuntu LTS is the default choice(you can select other distros but Ubuntu is the default). So I guess I picked Ubuntu because I haven't done Linux admin in over a decade and it's presented as the default choice by a big cloud provider.

  • Certain AMD graphics drivers require specific Ubuntu releases and versions. I guess one might reasonably ask "why would you run AMD graphics drivers?" to which I don't really have a good answer. But that's why I run an Ubuntu box ;p. I'd so much rather be running Alpine.