Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Linux 7.1

lore.kernel.org

Post reply on HN
Print view View original

121–130 of 137 posts

Re: Linux 7.1

#121

Post by chlorion »

tredre3 wrote: post #110
jcalvinowens wrote: post #16

Earlier quoted context omitted.

> 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.

No, I don't think that's what happening actually.

A stripped down cold build will literally take 90 seconds without caching on modern hardware.

The overwhelming majority of stuff that is being built is drivers, and most of them probably aren't needed for any specific user, so you can disable quite a lot of stuff.

Fwiw a full build of the fedora kernel config takes around 5-10m for my 12core ryzen 3900x, and it's definitely not the fastest CPU around.

Re: Linux 7.1

#122

Post by lionkor »

samhclark wrote: post #107

Personally, 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!

Here's the mail for that for anyone curious

https://lore.kernel.org/all/99Mv9QEceyPrQhSP52MtAVmz0_kWJmzq...

Re: Linux 7.1

#123

Post by bitfilped »

SoftTalker wrote: post #94
TacticalCoder wrote: post #34

> 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.

FreeBSD and NetBSD aren't going anywhere and can be used for older hardware, for the amount of production and load bearing use Linux sees there's an enormous amount of cruft and garbage in it.

Re: Linux 7.1

#124

Post by speed_spread »

conorcleary wrote: post #87
TacticalCoder wrote: post #34

> 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…

Chesterton's Fence...

It's ok, you can let go of Chesterton's ISDN phone pole now. Come, we have cable, we have fiber. Just for you, I'll even fire up a little hotspot from the palm of my hand as we walk away.

Re: Linux 7.1

#125

Post by franktankbank »

dormento wrote: post #82
asgraham wrote: post #78

Earlier quoted context omitted.

Is the parent really being sarcastic? I read it as genuine. There’s presumably plenty of code bloat in the kernel, and while no human would ever scan for bugs in a corner of the kernel that hasn’t been used or touched in decades, AI 100% will. And while those bug reports might be useless as bug reports, they seem promising as “why is this code even here?” flags.

I don't mean to be harsh, but if there's a codepath that is exercised on your hardware, but not on mine, I don't think it would be fair for me to deem it as "bloat". There are a TON of supported devices and use cases that are not my own, but are essential to someone else.

Maybe that points to an architecture issue? Is kernel driver support general enough to support all hardware in theory? If so it should be on hardware to provide a compatible api IMO. Note: I really have no experience in any of this there is probably more important things to consider like security/control or something.

Re: Linux 7.1

#127

Post by zamadatix »

conorcleary wrote: post #87
TacticalCoder wrote: post #34

> 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…

Chesterton's Fence...

Chesterton's Fence only says to learn why the fence was erected, it gives no other guidance on what to do after that. There isn't too much mystery in why a device driver was made, so Chesterton's Fence yields next to nothing here.

Re: Linux 7.1

#128

Post by jcalvinowens »

tredre3 wrote: post #110
jcalvinowens wrote: post #16

Earlier quoted context omitted.

> 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.

No, 90 seconds is the clean build time without ccache.

Re: Linux 7.1

#130

Post by Shellban »

Y-bar wrote: post #26

Did anyone see an anime avatar flash by for a fraction of a second before the content loaded? What was that?

It is a way to block bots, similarly to Cloudflare or Google's captcha. The Arch Linux website uses it.
Post reply on HN