how many new code came from AI ？
3
Linux 7.1
101–110 of 137 posts
Re: Linux 7.1
#102> 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 tri…
I’ve tried to submit code that removed old drivers from the kernel build in some distros, and they were universally rejected.
Everyone is afraid of breaking users until Torvalds says it’s ok.
Re: Linux 7.1
#103Looking forward for a new NTFS driver to try. I hope this new iteration will be better than ntfs3 from Paragon.
What is lacking in the previous one? NTFS support in linux is mostly to read and write files from windows disks, right? I think all the NTFS linux drivers - even the fuse one before the Paragon one - have been alright at that.
Re: Linux 7.1
#104> 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 tri…
[flagged]
Re: Linux 7.1
#105Looking forward for a new NTFS driver to try. I hope this new iteration will be better than ntfs3 from Paragon.
What is lacking in the previous one? NTFS support in linux is mostly to read and write files from windows disks, right? I think all the NTFS linux drivers - even the fuse one before the Paragon one - have been alright at that.
The Paragon v3 NTFS driver was in perpetual beta with a scary warning about data loss whenever it was enabled.
I think users moved on when they saw no real harm in continuing to use it.
Re: Linux 7.1
#106> 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 tri…
This is the sort of thinking that had organizations buying all new desktops because the perfectly working ones they had won't run Windows 11. I have 10 year old servers I'm still using because they run fine with linux.
The old unmaintained ISDN hardware for which the code has been removed is likely 20 years old, or so. The perfectly good laptops are usually 3-4 times younger.
Re: Linux 7.1
#107Personally, I'm pretty excited for this commit which fixes the slow WiFi I've had with the combination of my ISP's modem/router and my laptop.
https://github.com/torvalds/linux/commit/711a9c018ad252b2807...
Hope it gets to Fedora soon!
Re: Linux 7.1
#108Looking forward for a new NTFS driver to try. I hope this new iteration will be better than ntfs3 from Paragon.
What is lacking in the previous one? NTFS support in linux is mostly to read and write files from windows disks, right? I think all the NTFS linux drivers - even the fuse one before the Paragon one - have been alright at that.
Ubuntu switched to the Paragon NTFS driver by default. When I upgraded to kernel 6.5 (I think) from Ubuntu, I started getting frequent kernel panics, like every day. Soon, I noticed that I couldn't even compile a Rust project on an NTFS partition because the compiler was getting random file system errors, and compiling was at high risk of causing a kernel panic. The NTFS driver in that kernel version is just totally broken. I switched to the FUSE NTFS-3G, and then I stopped getting panics and can compile stuff again no problem.
Looking at kernel commits, it looks like the driver may have been fixed since, but I'm scared to use it after it had such major brokenness in that version.
Re: Linux 7.1
#109Earlier quoted context omitted.
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 Deb…
Actually, I'm running the backports kernel which is at 7.0 today. $ uname --kernel-release 7.0.10+deb13-amd64 If you run stable, Debian backports takes care of a lot of the popular stuff. Kernels, kernel modules, Rust/Cargo, CMake, Clangd, GPU firmware (AMD/Intel), GDB, LibreOffice, OpenShot video editor, and Wireguard are all kept current in backports. And there's way more than I mention here, of course. Worst case…
The full list of what's available in trixie-backports, if anyone is curious: https://backports.debian.org/uploads/trixie-backports/
Re: Linux 7.1
#110Earlier quoted context omitted.
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.
> 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.
You're being a bit disingenuous, it builds in 90 seconds because you build it daily and the vast majority of objects are unchanged and cached by ccache.