Comment by Thaxll
16 days ago
Stable Debian is using Linux 6.12, if your laptop has modern hardware what do you do? Can't use wifi?
And don't get me started with Debian testing. I want a LTS distro not a testing one.
16 days ago
Stable Debian is using Linux 6.12, if your laptop has modern hardware what do you do? Can't use wifi?
And don't get me started with Debian testing. I want a LTS distro not a testing one.
> Stable Debian is using Linux 6.12, if your laptop has modern hardware what do you do? Can't use wifi?
And Ubuntu 24.04 LTS is using 6.8.
Ubuntu releases a new version every six months, but an LTS — which is probably what most people run in production — only every two years. Debian releases come out every two years.
So if you only run Ubuntu LTS, the release cadence is the same as Debian.
I think you're forgetting about Ubuntu 26.04 (LTS) that is using kernel 7.0.
> I think you're forgetting about Ubuntu 26.04 (LTS) that is using kernel 7.0.
Which only came out a few months ago, and which only recently released its .1, so the do-release-upgrade message only recently appeared for most people.
I'd be interested to know how many folks have changed their current production over to 26TLS in the last six months. I'm guessing not a lot.
So yes, there is a newer LTS, but what is its current market share as compared to 24 TLS (or even 22LTS)?
Ubuntu releases its LTSes in even years, and Debian does its releases in odd years:
* https://en.wikipedia.org/wiki/Debian_release_version_history...
1 reply →
This is why Ubuntu also has Hardware Enablement (HWE) kernels[1], which are fully supported on LTS releases. The current Ubuntu 24.04 HWE kernel is 7.0.
[1] https://ubuntu.com/kernel/docs/reference/hwe-kernels/
Debian does have the concept of Backports, which includes kernel(s):
* https://wiki.debian.org/Backports
You can use backports if you want a newer kernel, e.g. trixie-backports has 7.2.11.
That, or just pick the kernel package from unstable or testing. Apt is smart enough that mixing packages from different versions of Debian works just fine.
(I mean nothing is 100% but I've been mixing packages for like 2 decades now and literally can't remember any specific trouble resulting from it.)
> That, or just pick the kernel package from unstable or testing. Apt is smart enough that mixing packages from different versions of Debian works just fine.
While I won't deny that this may often work, I disagree that it's a good idea, and that `apt` being smart is sufficient to guarantee that this works (or keeps working in the future).
Pinning specific packages from `testing` or `unstable` is explicitly discouraged, for very good reasons covered by this classic link: https://wiki.debian.org/DontBreakDebian#Don.27t_make_a_Frank... .
Arguably, the backports kernel is the right choice to get a newer kernel on Debian Stable. Indeed, in the past, the backports kernel could take awhile to update, but no more - case in point, `trixie-backports` currently contains `7.2`, same as `unstable`.
1 reply →
It's not apt not being smart that can cause troubles when mixing packages from various suites. There's no reason to mix in cases where you can just use backports instead.
> I want a LTS distro not a testing one.
You either want to have the new stuff or LTS. You can't have both.
Debian testing is way more stable than Ubuntu stable. In Debian's parlance, Testing means "release candidate", actually.
If you want real testing, you should run "unstable". If you're in for fun, try experimental.
Running Testing on my desktops and stable on my servers since forever. None of them broke, none of them created problems.
I don't care Stable running 6.x.x. It gets security updates in less than 24h, and is applied automatically before I wake up, and doesn't ship coreutils with 104CVEs, just because it's Rust.
Testing doesn't get timely security updates. It's not for serious people with production systems. It shouldn't even be a debate.
I believe I need to reiterate: Stable is for servers, testing is for desktops if you're not directly exposed to internet.
Again. Stable is for servers, testing is for personal use.
I never argued otherwise, ever.
Google disagrees - https://itsfoss.com/goobuntu-glinux-google/
2 replies →
The comment you're replying to makes clear that they're not using it on servers. I do the same thing (testing on my laptop(s), stable on my servers); you just have to commit to keeping track of what's going on and manually patch if you think that it's necessary.
I have to add that for me, testing definitely breaks stuff sometimes. Nothing beyond my ability to fix, though. Nothing beyond anyone's ability now that AI is around.
1 reply →
Testing is the staging area for the new Stable release.
However, one thing that many people don't know is that Testing enters a package freeze every time a new Stable release is to come out. And this freeze can last anywhere between 4 to 7 months. So for that time period, it stops having frequent updates and becomes essentially a stable distro.
This and other issues in parent comments is exactly the reason why I switched to Fedora.
You opt into backports and run the shipping 7.2 kernel: https://packages.debian.org/search?keywords=linux&searchon=n...
It's not 'as supported', sure, but I'll also note that wifi, at least, has worked on pretty much every modern laptop which I have installed Debian upon.
> Stable Debian is using Linux 6.12, if your laptop has modern hardware what do you do? Can't use wifi?
Why not just install a newer Linux version from the official backports repository if you need it?
https://backports.debian.org/
Well you may want to know that Ubuntu LTS releases are based on Debian unstable, not even testing...
I hope you realize the irony in your comment. Guess where Ubuntu packages come from?
> Stable Debian is using Linux 6.12
But nobody runs Debian stable on their laptop.
They run Debian unstable or testing, with firmware.
And everything just works
> what do you do?
You get 7.12 from backports?
Building your own kernel is always an option, just like it was 30+ years ago.
[dead]