all 71 comments

sorted by: hot top controversial new old
[–] 68 points 5 days ago (5 children)

Debian is honestly goated. Like I love me a nice boring stable distro that just keeps on chugging. I have done such crazy stuff to Debian and it just refuses to care. It's like a nokia phone that got run over by a car and still works.

  • source
  • hideshow 5 child comments
  • [–] 8 points 5 days ago (4 children)

    It’s the same for me for my Fedora install on my laptop, I installed version 38 when I got my laptop and now it’s on version 44, next week I’ll upgrade it to 45. It’s been rock solid, never had any issues with it.

  • source
  • parent
  • hideshow 4 child comments
  • [–] 4 points 5 days ago

    Jumped on the Fedora ship with 36.

    Updating to 43 or 44 broke my install so seized the occasion to try Silverblue instead of Workstation.

    It’s even better although the immutable side has its limitation, so I’m happy to have another computer for these.

  • source
  • parent
  • [–] 0 points 5 days ago (2 children)
  • [–] 60 points 5 days ago (1 child)

    I always looked at their pace as a feature, not a bug.

  • source
  • hideshow 1 child comment
  • [–] 35 points 5 days ago (1 child)

    Debian the foundation of the modern world. Or at least we wish it was.

  • source
  • hideshow 1 child comment
  • [–] 86 points 5 days ago (11 children)

    Also Debian user remembering the last official release:

  • source
  • hideshow 11 child comments
  • [–] 17 points 5 days ago (9 children)

    It's interesting to me that Debian has this image of long time between releases. Mint for example is based on Ubuntu LTS which releases every 2 years, but I haven't seen the same jokes about Mint.

  • source
  • parent
  • hideshow 9 child comments
  • [–] 3 points 5 days ago* (last edited 5 days ago) (5 children)

    Not only with intervals but also with quite old software. Sometimes software versions are so old that they are no longer compatible with the upstream version. Although, to be honest, I haven't used Debian for so long that I can't even name the applications that lagged behind like that.

    In general, Debian is indeed incredibly stable, but if you need to install it on the latest laptop (for example, Intel Core Ultra X9), it will be a real hell.

    UPD: except perhaps for using sid. But then you lose the only advantage - stability.

  • source
  • parent
  • hideshow 5 child comments
  • [–] 3 points 5 days ago* (last edited 5 days ago) (3 children)

    Honestly, in the age of Flatpak and containerization (as well as Debian often being well-supported by upstream projects for script or package-based install), I feel like the age of Debian packages isn't that annoying anymore; anything important gets security patches, and it's easier than ever to use 3rd party software without breaking your system. I will add that Debian seems to be much better these days at making sure either a reasonably up-to-date version ships with a release (and can be kept secure during a stable cycle) or not shipping it at all as to allow the user to install it themselves.

    I remember back in just 2021 when it took months after Firefox ESR 78 went EOL for them to update Bullseye to 91; recently, it only took them a few days after 140's EOL to switch to 153 (and 91-115 and 115-140 happened without much note either), which isn't perfect, but much better than it was.

    If you need to install it on a new laptop, backports often has you covered. I ran a backports kernel for about a year on Debian Bookworm to get my laptop's Wi-Fi modem working; I was able to quit using the backports kernel once Trixie came out.

  • source
  • parent
  • hideshow 3 child comments
  • [–] 3 points 5 days ago

    Honestly, in the age of Flatpak and containerization (as well as Debian often being well-supported by upstream projects for script or package-based install), I feel like the age of Debian packages isn’t that annoying anymore; anything important gets security patches, and it’s easier than ever to use 3rd party software without breaking your system.

    i was pleasantly surprised in 2023 to learn that debian was still king in the server space and precisely because of this -- i remember doubting trying debian on my personal hardware because of the age of the packages back around 2004.

  • source
  • parent
  • [–] 1 point 4 days ago (1 child)

    If you are using only Docker, you don't need a Linux distribution at all. Just install alpine slim, busybox, or any Kubernetes worker node build.

    Flatpak, much like snap, appimage, and other programs trying to shove old, hole-ridden libraries down my throat under the pretext that "the build is too complex," is not the kind of software I would welcome on my PC. I'd rather build the application by hand.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 1 point 4 days ago
    1. Alpine is still a Linux distro, just a lighter one. Also, busybox is a set of standard utilities as an alternative to coreutils; I have no idea how it’s particularly relevant here.
    2. The thing is, I’m not using only Docker. I also use native nginx as a reverse proxy, for which I like Debian’s defaults, as well as SyncThing, which are both well-maintained packages in Debian. Also I kind of prefer glibc distros. While glibc kind of sucks, so much stuff I like using prefers or requires it; for instance, last I saw, mDNS/Avahi resolution on BusyBox was kind of a pain in the rear.
    3. Most of what I use Flatpak for isn’t network-facing or opening unverified files anyway; the most important applications I do run the native Debian version. Honestly, truth be told, you are correct that I do often prefer native versions and will run the native Debian package if possible (and considering the current age of stable, a lot of them really aren’t that old; Inkscape is basically still the latest version, for instance, while Firefox is always kept to the latest ESR); at some point, though, I do find a Debian package that is too behind to do what I do (though rare, TBH), and despite some issues with Flatpak, at the end of the day, I need to just get a piece of software installed and get on with my day. In that case, I just do a Benjamin Sisko:

    Benjamin Sisko says “I can live with it”

  • source
  • parent
  • [–] 1 point 5 days ago

    I've found I don't need bleeding edge most of the time. But if I do need something more up to date, there's usually a package for Debian available. Wine is one example; I needed a more updated version than Debian stable ships, and WineHQ has it packaged for that. Installs easily and stays updated automatically.

  • source
  • parent
  • [–] 2 points 4 days ago (2 children)

    Because Mint does release minor releases every 6 months

  • source
  • parent
  • hideshow 2 child comments
  • [–] 1 point 4 days ago (1 child)

    Debian does minor releases every so often, too. For example the current version of Trixie is on its 7th point release (12.7). Trixie was released last August.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 1 point 3 days ago

    True, though I guess they don't change the OS (only the repos), and don't advertise/celebrate it as much...

    But complaining or anything, just thinking “out loud” why people could feel this way about Debian but not Mint

  • source
  • parent
  • [–] 21 points 5 days ago (19 children)

    Amazing for a server. Both my servers run Debian and I have had no issues.

  • source
  • hideshow 19 child comments
  • [–] 17 points 5 days ago (4 children)

    I run it with KDE for my daily driver & gaming and it is very boring and stable, which is what I want in my PC. Debian is 99% of the time supported.

    I recommend it.

  • source
  • parent
  • hideshow 4 child comments
  • [–] 3 points 5 days ago (3 children)

    I’ve invested so much time and effort into CachyOS. I’ve been running it for over 2 years now. A switch would be very hard and unnecessary work for me since it works no issues for me. Otherwise, Debian would be on my machine.

  • source
  • parent
  • hideshow 3 child comments
  • [–] 4 points 5 days ago (1 child)

    Not only does cachy work perfectly, Debian needs so much fiddling around to get latest software versions it's a hindrance for a lot of stuff including gaming

  • source
  • parent
  • hideshow 1 child comment
  • [–] 1 point 5 days ago

    Gaming and getting the latest kernel is a big one for me. My gpu and cpu are very new and they require the latest kernels. I’m sure there are ways to bring in the newest kernel to Debian, or just use Sid or testing, but why do that and what I have works no problem?

  • source
  • parent
  • [+] -13 points 5 days ago (11 children)

    Due to slow update cadence it's not a great idea for a server exposed to the internet

  • source
  • parent
  • hideshow 11 child comments
  • [–] 7 points 5 days ago (7 children)

    If that server includes the security repository in its source files, I disagree. In fact, the use of the security repository in Debian has a history spanning more than 20 years.

  • source
  • parent
  • hideshow 7 child comments
  • [–] -4 points 5 days ago (6 children)

    Until some fucking php vulnerability grants root access

  • source
  • parent
  • hideshow 6 child comments
  • [–] 3 points 5 days ago (2 children)

    would arch have fixed this? no, what is your point?

  • source
  • parent
  • hideshow 2 child comments
  • [–] -1 points 4 days ago (1 child)

    Rolling releases better at updates, by definition, that's my point. This can backfire, but also can save you sometimes.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 2 points 4 days ago

    we are talking abou specificly security updates, upstream for most projects that are important for security have a concept of LTS releases, e.g the kernel's LTS, debian updates their stable packages rellying on upstream's LTS, debian does sometimes switches to newer LTS releases even if it means breaking the no new feature general rule of thumb, e.g kernel LTS goes EOL, debian maintainers sometimes do try to backport fixes themselves but generally debian prefers to follow upstream's LTS EOL where possible, generally updating to the oldest LTS not in EOL yet

    debian has a specific team dedicated to security, updating packages, contacting and colaborating with upstream, reporting potential vulnerabilities e.g the xz backdoor first was reported to the ssh package maintaince team from which the importance and the nature of the issue was discovered and then reported to the debian security team which confirmwd the findings and made reports to other teams and tried contacting the old owner of xz since xz was effectively taken over by the malicious actor

  • source
  • parent
  • [–] 2 points 5 days ago (2 children)

    If you are speaking about the latest php bug, debian stable and old stable were updated days ago, see https://security-tracker.debian.org/

  • source
  • parent
  • hideshow 2 child comments
  • [–] 1 point 5 days ago* (last edited 5 days ago) (1 child)

    it might be a failure to read on my part but this reads as unfixed on Debian but fixed on Arch

    Edit: Oh, yeah ok, in the security repo it's fixed, why is the vulnerable version distributed to stable though?

  • source
  • parent
  • hideshow 1 child comment
  • [–] 1 point 4 days ago

    Technically, you are right. But this is due to the different release systems.

    In Debian, security updates for the stable version are distributed via the security repository until a new point release is created. The last point release was two months ago.

    However, in practice, on Debian Trixie, you get the fixed version by running a standard apt update & apt upgrade.

  • source
  • parent
  • [–] 16 points 5 days ago*

    I picked Debian with absolutely no knowledge of Linux, have yet to switch or try other distros, it’s been well over two years now.

  • source
  • [–] 32 points 5 days ago*

    Running my workstation and server on Debian stable. Debian always. Debian forever.

  • source
  • [–] 11 points 5 days ago

    I should install Debian to replace my current Ubuntu install at some point. Might move some services I run to a VM to reduce effort when reinstalling my OS. Then it's just install steam and copy over my game backup folders. Plus with a VM I can easily move it to a proxmox mini PC if I ever get round to buying one.

  • source
  • [–] 10 points 5 days ago (2 children)

    Yeah, Debian is my favorite server software by a mile.

  • source
  • hideshow 2 child comments
  • [–] 10 points 5 days ago

    Debian has become my favorite server OS. Some more specialized distros are great for specific use cases, but for 90% of my stuff, I just install Debian and chill.

  • source
  • [–] 8 points 5 days ago

    I surfed a few distros before landing on Debian. It solved (almost) all the issues I had with Linux. Debian for life.

  • source
  • [–] 5 points 5 days ago (2 children)
  • [–] 5 points 4 days ago* (last edited 4 days ago)

    I only ever deploy and develop on Debian. Community run distros all the way. I had bad experiences with Redhat decades ago and do everything I can to avoid it or its siblings.

    Debian has faults but it is often a taste thing. I like systems that give me upstream with minimal patches, like Arch. I moved to Arch on all desktops/laptops. The Debian devs repeatedly doing dumb shit with ssh patches was part of that. Arch is not unreliable but it is unstable. All that means is that software updates which aren't backwards compatible sometimes require intervention . To be clear that is not a fault with Arch but it does make it much less suitable for long hassle free server deployments. Also Arch doesn't have the Debian security announce list or maintain a stable production environment for years with backported security fixes and unnattended security updates.

  • source
  • [–] 8 points 5 days ago (4 children)

    How does Debian do level and security updates? Are they generally a good pace but userland starts consistent?

  • source
  • hideshow 4 child comments
  • [–] 19 points 5 days ago (3 children)

    They backport security updates to the existing software versions on stable, which causes the packages to be secure without introducing new behavior. Feature updates only occur with a new stable release I believe.

  • source
  • parent
  • hideshow 3 child comments
  • [–] 9 points 5 days ago (1 child)

    Exceptions exist, for example rsync recently got a new upstream version to fix 33 CVEs: rsync.NEWS

  • source
  • parent
  • hideshow 1 child comment
  • [–] 3 points 5 days ago

    I also saw that recently. I'd like to highlight this bit from the news:

    This update contains behavior changes, all of which stems from the CVE fixes themselves, not exclusive to the version bump.

    So it looks like the package is still mostly kept stable despite the exception made.

  • source
  • parent
  • [–] 2 points 5 days ago

    it is rare but some feature updates do get to stable, most software that is important to up to date with security fixes have the concept of an LTS or somethinf akin to it, firefox has ESR for example, basically it is a version where the devs will continously backport security fixes to it but not the features

  • source
  • parent
  • [–] 4 points 4 days ago

    Also, don't worry, Debian has plenty of Toy Story characters left for many years of releases to come!

  • source
  • [–] 4 points 5 days ago

    I really need one of these shirts

  • source
  • [–] 2 points 5 days ago

    DietPi, anyone? 🥹

  • source
  • [–] -1 points 5 days ago

    Too bad they too bit the AI bullet.

  • source
  • [+] -6 points 5 days ago (5 children)

    sid exists you fucking dorks.

  • source
  • hideshow 5 child comments
  • [–] 1 point 4 days ago*

    I ran sid in serious production when I was younger and more foolish. The trick with unstable distributions is to test before you deploy and know the incompatibilities and have the fixes ready in advance. The problem is you are basically taking a snapshot approach and doing the work of the debian release system yourself and doing it half-arsed. An urgent security update comes out and you can't rush to deploy it without risking a dependency being pulled in that breaks under your config. For servers it ends up being a huge amount of work for no gain and you can actually miss out on security updates.

    BTW this approach is why Valve can release Steam OS based on Arch or Google can base ChromeOS on Gentoo and release them to millions of consumers safely. They freeze updates to create a release candidate and test it and they deploy a limited subset of packages.

    At home I update one arch desktop machine to work out what breaks, how to fix it and seed the package cache on our server before I do the rest and break everyone's systems. I could do the same with Sid but Arch, despite being unstable intentionally isn't all that unreliable compared with Sid though my experience with Sid is dated.

  • source
  • parent
  • [–] 1 point 5 days ago (2 children)

    sid does not has a dedicated security team, it may actually get crucial security fixes later than stable

  • source
  • parent
  • hideshow 2 child comments
  • [–] -1 points 4 days ago*

    They broke apt-get and I don't like apt

  • source
  • [–] -5 points 5 days ago