|
| ▲ | throw0101c an hour ago | parent | next [-] |
| The most recent Linux kernel releases are: 7.1, 7.0, 6.19, 6.18, …: * https://en.wikipedia.org/wiki/Linux_kernel_version_history 7.0 is already present in forky (current testing), and available as a backport for trixie (current stable): * https://packages.debian.org/search?keywords=linux-image-amd6... * https://packages.debian.org/trixie-backports/linux-image-amd... The default kernel for trixie/stable is 6.12, initially released in November 2024, and officially supported upstream until December 2028. |
| |
|
| ▲ | juujian 12 minutes ago | parent | prev | next [-] |
| I know it's a bit of a meme but I'm on Debian Stable and I am running the backport kernel, which is on version 6.19. So only one minor version away from the current 7.0. I wish more people would consider Debian for their devices. It is a very stable system, which I appreciate, and, unlike Ubuntu, it was really an "it just works" experience, without any of the friction points that smaller distros have. I installed Debian Trixie on a very recent device (granted, all AMD for compatibility) when Trixie was still the Testing version, and all the necessary drivers were present. Now if only I could figure out how to build packages and contribute back to Debian... Also if only AMD could get their NPU support for Linux figured out... |
|
| ▲ | imoverclocked an hour ago | parent | prev | next [-] |
| It’s fairly easy to build your own kernel packages from vanilla sources in Debian. I’m running the latest 7.0.x within a few hours of its release. The build takes about 30-45 minutes depending on how much time I spend on skimming the ChangeLog. YMMV. |
| |
| ▲ | jcalvinowens 33 minutes ago | parent | next [-] | | > The build takes about 30-45 minutes If you don't actually need all the drivers, you can use "make localmodconfig" to substantially reduce that. My local kernels build in 90 seconds on a 32-thread desktop machine :) The kernel is a lot more stable than people think: I run the daily linux-next on my Debian stable gaming PC to look for bugs, and I don't find very many. | |
| ▲ | wolfi1 an hour ago | parent | prev | next [-] | | I miss the days when my 486 took about 12 hours to compile a kernel | | |
| ▲ | throw0101c an hour ago | parent [-] | | Or it took >15 minutes to generate PGP 2.x private keys due to entropy generation and prime calculations/tests. |
| |
| ▲ | z3ratul163071 an hour ago | parent | prev [-] | | what about your carbon footprint | | |
| ▲ | imoverclocked 40 minutes ago | parent | next [-] | | I build using excess solar from my house. The build host is a small arm64 SBC that doesn’t require cooling in my passively cooled garage. The resources behind your post likely have a larger carbon footprint. | |
| ▲ | dymk 31 minutes ago | parent | prev [-] | | Turn the shed light off overnight and you’re at net zero |
|
|
|
| ▲ | hagbard_c an hour ago | parent | prev | next [-] |
| Not a serious question but I'll give a serious answer anyway. The last time I worried over which kernel was used in Debian Stable was... never. If I want a more recent kernel I run Debian unstable (Sid) which currently is at 7.0.12 (the current 'stable' kernel where 7.1 is 'mainline') but on my servers Stable (currently 'Trixie') does just fine with its 6.17.3 kernel. Debian 'Forky' will be released somewhere in 2027 with either a 7.0.x or 7.1.x kernel depending on how things go. The current kernel used in 'testing' (which will become 'stable' on the next release) is 7.0.10. |
| |
| ▲ | waych an hour ago | parent [-] | | People don't usually understand that apt allows you to configure multiple sources across versions simultaneously, so you can e.g. run stable, but also selectively install from backports or unstable. To do so, add the sources for trixie-backports and unstable, and add the following configuration (e.g. /etc/apt/preferences.d/trixie-sid-pin) so that the system knows which sources your prefer: # Default to trixie
Package: *
Pin: release n=trixie
Pin-Priority: 990
# Very low priority for sid
Package: *
Pin: release n=unstable
Pin-Priority: 100
# Give backports medium priority
Package: *
Pin: release n=trixie-backports
Pin-Priority: 500
Now the system can access the latest kernel from unstable (and backports), while keeping everything else on stable: # apt policy linux-image-amd64
linux-image-amd64:
Installed: 7.0.12-1
Candidate: 7.0.12-2
Version table:
7.0.12-2 500
500 http://deb.debian.org/debian unstable/main amd64 Packages
*** 7.0.12-1 100
100 /var/lib/dpkg/status
7.0.10-1~bpo13+1 500
500 http://deb.debian.org/debian trixie-backports/main amd64 Packages
6.12.90-2 500
500 http://security.debian.org/debian-security trixie-security/main amd64 Packages
6.12.86-1 990
990 http://deb.debian.org/debian trixie/main amd64 Packages
I believe the kernel in backports gets updated only after it is live in unstable for at least a week, which lately still feels like forever. |
|
|
| ▲ | yjftsjthsd-h an hour ago | parent | prev [-] |
| Wouldn't Forky/14 have this or newer when it releases next year? Debian moves slow - deliberately so, if you want fast use Arch or Fedora - but it does move. |
