Rendered at 22:04:39 GMT+0000 (Coordinated Universal Time) with Cloudflare Workers.
GreenSalem 29 minutes ago [-]
Current default for Arch is 7.0.10
Looking forward to 7.1 rolling out soon.
TacticalCoder 2 hours ago [-]
> Linux 7.1 is also notable for its code removals. Driven by AI-assisted bug reporting, ISDN and other old network driver code was removed to avoid that influx of bug reporting against those very rarely touched or used drivers for obsolete hardware.
Moving really old and unused code out of the kernel just to get less AI-assisted bug reports is IMO one of the best consequence ever of AI.
I love it.
We should start trimming the fat out of everything.
fn-mote 28 minutes ago [-]
> Moving really old and unused code out of the kernel just to get less AI-assisted bug reports
Obviously, the parent is /s, but when I read this, I thought Linux was removing exploit paths that exercise rarely-used features.
On phone OSes at least, quirky rare formats and features are (were?) a common source of exploitable bugs.
knorker 5 minutes ago [-]
Code is liability. AI just made it harder to ignore.
stefantalpalaru 45 minutes ago [-]
[dead]
1over137 1 hours ago [-]
How about we stop adding the fat in the first place. cough. electron. cough.
fhdkweig 50 minutes ago [-]
Presumably that old code was actually useful at the time it was added. It might not be used now, but it helped someone back then. One of the great things about early Linux was that it tried to run on every piece of hardware available. If Linus only wrote drivers (or allowed others to submit drivers) that worked on his personal computer, Linux would have never flourished this far.
Y-bar 2 hours ago [-]
Did anyone see an anime avatar flash by for a fraction of a second before the content loaded? What was that?
But not a very accurate blogpost. "Here's why this literally cannot work (in theory)" to denigrate a system that actually works (in practice). Their goal is to convince people to stop using it because it personally inconveniences them, but they never provide an alternative solution that actually solves the problem (in practice) that Anubis actually solves (in practice). If leaving the problem unsolved (in practice) was a desirable option, the site owner would not have turned to Anubis in the first place.
yunwal 6 minutes ago [-]
I'm totally out of the loop here, where's the evidence that this works in practice?
notafox 1 hours ago [-]
uBlock Origin filter to block the anime girl from loading:
For me, it's a personal preference and in my opinion, it's less professional.
lukeify 48 minutes ago [-]
People always seem surprised when someone in CS or SWE doesn't care for anime or cutesy pictorial graphics of girls.
anonymous908213 33 minutes ago [-]
It's mostly surprising how many grown adult men go into a blind rage when confronted with a picture of a cartoon woman. In a lobsters thread about Anubis, a community member of 12 years got themselves permanently banned because they were frothing at the mouth with accusations of pedophilia against the developer and refused to apologise when given an opportunity by moderators. Telling on themselves, perhaps? It's funny, in a bizarre way, that this is a hill people will die on.
fn-mote 20 minutes ago [-]
Parent: your post takes a legitimate point and muddies it with an overly emotional tone.
> grown adult men
On the internet, nobody knows you are a dog. I won’t look for original threads, but in general assumptions about posters age and gender are just that - assumptions. If they were female posters, would you feel differently??
> Telling on themselves, perhaps?
Get rid of this sentence. By itself it will be the cause of disengagement and downvotes.
> this is a hill people will die on.
Getting an account banned in no way equates to death. Oh no, lost my karma!
anonymous908213 16 minutes ago [-]
> If they were female posters, would you feel differently??
Obviously not. Neither "Grown adult men and women" nor "Grown adult persons" have the same rhetorical impact, though. Sometimes things are just too mouthy to bother being precise. Human conversation typically allows for fuzzy matching, outside of forums frequented by people known to be particularly pedantic, I suppose :)
> By itself it will be the cause of disengagement and downvotes.
I will respond to this with your own quote:
> Oh no, lost my karma!
---
> Getting an account banned in no way equates to death.
"A hill to die on" is a metaphorical expression, not a literal implication that a person will find a raised landform and engage in activity that will lead to their departure from this mortal plane.
I would note that the consequence is slightly more severe than "losing karma", since lobsters is an invite-only forum. Being banned from it, in this case, does mean being excluded from a community you've partaken in for over a decade, for some surprisingly trivial reason.
p_l 25 minutes ago [-]
Places that want to use Anubis but find the logo not professional enough are free to pay the author, IIRC it was major "professional support" benefit :D
Cassell 49 minutes ago [-]
its the only weakness of the corpo-capitalist gestalt!
Is it safe to assume we can see this in Debian Stable around 2036?
4 minutes ago [-]
throawayonthe 2 minutes ago [-]
doesn't debian usually stick to LTS kernels? afaik 7.0 was designated as an LTS release so it'll probably be the version that next major release will ship with (next year maybe?)
throw0101c 4 hours ago [-]
The most recent Linux kernel releases are: 7.1, 7.0, 6.19, 6.18, …:
The default kernel for trixie/stable is 6.12, initially released in November 2024, and officially supported upstream until December 2028.
hdgvhicv 3 hours ago [-]
Just hope there’s never a Lillypad version
juujian 3 hours ago [-]
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...
sharts 40 minutes ago [-]
Debian unstable/testing? Is quite good too. As well as OpenSUSE.
jinnko 2 hours ago [-]
Check out FastFlowLM for AMD NPU support.
irishcoffee 3 hours ago [-]
I’ll never understand why people like Ubuntu. It’s a really hard toss up for me if I’d rather be stuck with Ubuntu or windows.
pmontra 2 hours ago [-]
Probably because it got popular as the easy Linux distro back in the 2000s and that label is sticking.
I remember that I attempted to install Debian on my laptop in 2009. It was ugly. I installed Ubuntu 8.04 and it was a totally different and much nicer experience. Because of that I've been on Ubuntu until they started pushing snaps very aggressively. I live booted Debian 11 and realized that its UI was exactly the same. I don't know when it happened during that dozen of years but there wasn't anymore a reason to stick to Ubuntu. I installed Debian 11 and got a faster machine with less background processes. I'm on Debian 13 now. I've been told that KDE is much better than what I attempted to use in 2014 so maybe I could give it a try, but it's unclear to me what I have to gain.
robertlagrant 1 hours ago [-]
I prefer KDE (on Ubuntu, because I tried it and it's good enough) - it's got more stuff built into the OS in terms of settings. I tended to find that Gnome needs you to install more things to expose configuration settings, whereas KDE's configuration UI is pretty good.
fhdkweig 47 minutes ago [-]
I'm of the belief that the more popular an OS is, the more maintainers it will have (and thus less bugs). The only thing about Ubuntu that I hated was its choice of windowing manager. That's why there are so many variants like KUbuntu, XUbuntu, etc. Are there other reasons to not like Ubuntu other than the windowing manager?
fn-mote 12 minutes ago [-]
> Are there other reasons to not like Ubuntu other than the windowing manager?
Snap applications are still not “equal enough” to installed apps.
They have gotten better, but it’s not seamless and when you get burned it’s 2 hours debugging. Each time.
An app I use/help maintain regularly gets bug reports about sandboxed behavior. It’s understandable but the easiest fix is to install an unsandboxed version.
I personally have some extra steps in my workflow for printing from a snap application because it doesn’t just work and I don’t want to spend the hours needed to debug it.
arcade79 1 hours ago [-]
For me, it was kubuntu. Back in late 2005 or early 2006. The reason? They were always pretty good at shipping the latest KDE. I had grown tired of hoping someone would compile a new version for my preferred distro.
So kubuntu it was, and has been ever since. I'm currently looking into whether I should change to something else - as I've started growing tired of Ubuntu/Kubuntu after some 20 odd years.
fn-mote 16 minutes ago [-]
Come on - at least make one substantive criticism in your post putting down Ubuntu.
I came to Ubuntu because Wine worked on it with no effort. Yes, this was a long time ago. I have certainly cursed some of their changes since then, but I don’t want to spend my time doing yet another sysadmin job, so the less I change the better.
irishcoffee 1 minutes ago [-]
Well, it starts with when I have to opt out of location services during install, and Ubuntu reserving usernames (admin, for example) and ends with how aggressively they shut down upstream repos… if they’re not being DDoSd. Package conflicts are miserable, so they tried to paper over it, adding yet another bullshit layer of things to debug when something invariably breaks.
I’d rather flip the question back on you, how is Ubuntu better than, say, Rocky? If you say “upgrading is easier” I’ll chuckle for the rest of the day.
imoverclocked 4 hours ago [-]
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 3 hours ago [-]
> 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.
kro 3 hours ago [-]
I did that for a while because of compatibility issues with a newer laptop, it works but generally if there is no reason it's way easier to stay with the provided packages. Compiling weekly due to security patches becomes annoying over time for no real gain other than the version number
cesarb 1 hours ago [-]
> It’s fairly easy to build your own kernel packages from vanilla sources in Debian.
IIRC, Debian has a command called "make-kpkg" which does nearly all the work for you, ending up with a installable package which works identically to the standard Debian kernel packages.
wolfi1 4 hours ago [-]
I miss the days when my 486 took about 12 hours to compile a kernel
throw0101c 4 hours ago [-]
Or it took >15 minutes to generate PGP 2.x private keys due to entropy generation and prime calculations/tests.
z3ratul163071 4 hours ago [-]
what about your carbon footprint
imoverclocked 3 hours ago [-]
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 3 hours ago [-]
Turn the shed light off overnight and you’re at net zero
yjftsjthsd-h 4 hours ago [-]
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.
stevenrj 2 hours ago [-]
Yes, best guess is forky will adopt the LTS kernel that will release at the end of this calendar year.
4 hours ago [-]
hagbard_c 4 hours ago [-]
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 4 hours ago [-]
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:
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 2 hours ago [-]
> 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.
Which is just as well, because that's not generally a good idea unless you really know what you're doing:
Granted, the kernel is probably the best thing to do it with, on account of their aggressive stance on compatibility and the narrowness of impact (no .so files in play).
yjftsjthsd-h 2 hours ago [-]
> The last time I worried over which kernel was used in Debian Stable was... never.
It was briefly a little annoying to deal with wireguard. But it was only a bit annoying, and then they updated. That's the only time I recall specifically caring.
hagbard_c 1 hours ago [-]
Yes, when that was a thing I just compiled the wireguard module myself to feed it to the virtual router. It was only needed for a short interval and was thereafter handled by dkms, i.e. no problem.
globular-toast 4 hours ago [-]
Is there anything particularly interesting about this? The first number of the version changes when the second number gets too big, not for any other reason.
Yeah, my favorite $6 Linux machine is now supported (somewhat). :)
throwaway85825 2 hours ago [-]
What SoC?
nijave 2 hours ago [-]
AI says probably Rockchip RV1103B which is Luckfox Pico Mini
betimsl 30 minutes ago [-]
what a legend!
imoverclocked 5 hours ago [-]
Breaking: Linus is on travel.
Did I miss something about this or is it just another number?
bombcar 4 minutes ago [-]
Surprised nobody will spring for the inflight WiFi for Linus. Has to be some of the best return per dollar that could be spent!
dietr1ch 3 hours ago [-]
Yeah, it gets boring when the number change doesn't change and try improving everything at once, but the great thing is that freshness improves driven by number fomo and that tightens the improvement loop.
Exciting and risky things are always under flags, so if you really care you just build, configure, and bench your own kernel+system.
dimiprasakis 5 hours ago [-]
- "Anyway, possible slight hiccups in the merge window aside, the news
today is 7.1."
- "nothing particularly interesting or scary stands out, which is as it should
be."
So, a number.
megous 2 hours ago [-]
He's just writing about the changes since last week. Not about 7.1 as a whole. No last minute scary things means 7.1 released as planned.
Looking forward to 7.1 rolling out soon.
Moving really old and unused code out of the kernel just to get less AI-assisted bug reports is IMO one of the best consequence ever of AI.
I love it.
We should start trimming the fat out of everything.
Obviously, the parent is /s, but when I read this, I thought Linux was removing exploit paths that exercise rarely-used features.
On phone OSes at least, quirky rare formats and features are (were?) a common source of exploitable bugs.
blog post (pretty sure I've seen it on HN before) on the topic:
https://lock.cmpxchg8b.com/anubis.html
> grown adult men
On the internet, nobody knows you are a dog. I won’t look for original threads, but in general assumptions about posters age and gender are just that - assumptions. If they were female posters, would you feel differently??
> Telling on themselves, perhaps?
Get rid of this sentence. By itself it will be the cause of disengagement and downvotes.
> this is a hill people will die on.
Getting an account banned in no way equates to death. Oh no, lost my karma!
Obviously not. Neither "Grown adult men and women" nor "Grown adult persons" have the same rhetorical impact, though. Sometimes things are just too mouthy to bother being precise. Human conversation typically allows for fuzzy matching, outside of forums frequented by people known to be particularly pedantic, I suppose :)
> By itself it will be the cause of disengagement and downvotes.
I will respond to this with your own quote:
> Oh no, lost my karma!
---
> Getting an account banned in no way equates to death.
"A hill to die on" is a metaphorical expression, not a literal implication that a person will find a raised landform and engage in activity that will lead to their departure from this mortal plane.
I would note that the consequence is slightly more severe than "losing karma", since lobsters is an invite-only forum. Being banned from it, in this case, does mean being excluded from a community you've partaken in for over a decade, for some surprisingly trivial reason.
[0]: https://anubis.techaro.lol
* 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.
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...
I remember that I attempted to install Debian on my laptop in 2009. It was ugly. I installed Ubuntu 8.04 and it was a totally different and much nicer experience. Because of that I've been on Ubuntu until they started pushing snaps very aggressively. I live booted Debian 11 and realized that its UI was exactly the same. I don't know when it happened during that dozen of years but there wasn't anymore a reason to stick to Ubuntu. I installed Debian 11 and got a faster machine with less background processes. I'm on Debian 13 now. I've been told that KDE is much better than what I attempted to use in 2014 so maybe I could give it a try, but it's unclear to me what I have to gain.
Snap applications are still not “equal enough” to installed apps.
They have gotten better, but it’s not seamless and when you get burned it’s 2 hours debugging. Each time.
An app I use/help maintain regularly gets bug reports about sandboxed behavior. It’s understandable but the easiest fix is to install an unsandboxed version.
I personally have some extra steps in my workflow for printing from a snap application because it doesn’t just work and I don’t want to spend the hours needed to debug it.
So kubuntu it was, and has been ever since. I'm currently looking into whether I should change to something else - as I've started growing tired of Ubuntu/Kubuntu after some 20 odd years.
I came to Ubuntu because Wine worked on it with no effort. Yes, this was a long time ago. I have certainly cursed some of their changes since then, but I don’t want to spend my time doing yet another sysadmin job, so the less I change the better.
I’d rather flip the question back on you, how is Ubuntu better than, say, Rocky? If you say “upgrading is easier” I’ll chuckle for the rest of the day.
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.
IIRC, Debian has a command called "make-kpkg" which does nearly all the work for you, ending up with a installable package which works identically to the standard Debian kernel packages.
The resources behind your post likely have a larger carbon footprint.
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.
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:
Now the system can access the latest kernel from unstable (and backports), while keeping everything else on stable: 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.Which is just as well, because that's not generally a good idea unless you really know what you're doing:
https://wiki.debian.org/DontBreakDebian#Don.27t_make_a_Frank...
Granted, the kernel is probably the best thing to do it with, on account of their aggressive stance on compatibility and the narrowness of impact (no .so files in play).
It was briefly a little annoying to deal with wireguard. But it was only a bit annoying, and then they updated. That's the only time I recall specifically caring.
Did I miss something about this or is it just another number?
Exciting and risky things are always under flags, so if you really care you just build, configure, and bench your own kernel+system.
So, a number.
But 7.1 new features can still be exciting.