It is funny with Linux (the kernel). From the outside it looks like almost nothing ever changes. You switch the computer on, it works away in the background to bring up the desktop and have everything talk. From that perspective it feels like nothing has changed in decades. But then you look at the change log, and almost everything you see added sounds really useful to someone working on this stuff. 35 years of work…
> From the outside it looks like almost nothing ever changes You should try to compile a custom kernel for your machine and strip the unneeded things out. Good luck. Linux has diabetes.
Linux 7.2
91–100 of 141 posts
Re: Linux 7.2
#92It is funny with Linux (the kernel). From the outside it looks like almost nothing ever changes. You switch the computer on, it works away in the background to bring up the desktop and have everything talk. From that perspective it feels like nothing has changed in decades. But then you look at the change log, and almost everything you see added sounds really useful to someone working on this stuff. 35 years of work…
Now it behaves more like Windows/Mac, even when 100%, my youtube/spotify tab can still run smoothly.
(Of course i think there will be hit in some areas, like my code would be built slower, there is no free meal).
Re: Linux 7.2
#93It is funny with Linux (the kernel). From the outside it looks like almost nothing ever changes. You switch the computer on, it works away in the background to bring up the desktop and have everything talk. From that perspective it feels like nothing has changed in decades. But then you look at the change log, and almost everything you see added sounds really useful to someone working on this stuff. 35 years of work…
Strongly disagree. Hardware support improved by leaps and bounds last decade and a half. Namespace isolation and cgroups driven containerization. eBPF appeared and gained adoption. Async I/O (and later just everything async) converged on io_uring. Btrfs is _stable_ - some people believed it would never be possible, ever. All kinds of scheduling were iterated and iterated over. All these things are visible across the…
Re: Linux 7.2
#94Who is the main audience for this type of content? Genuinely curious because I am not a serious Linux user. What type of info do you get out of this for those who read this? So i can glance your insight?
Re: Linux 7.2
#95Earlier quoted context omitted.
I for one am excited about HDMI 2.1 support on AMD.
It's more than that: free and open support for HDMI 2.1 in general. Previously it was only proprietary implementations that didn't leak the spec which were allowed. AMD is just the only one that has really good open source drivers which can benefit from it, and didn't work around the problem by converting HDMI to DisplayPort in a proprietary on-board GPU chip.
Re: Linux 7.2
#96Re: Linux 7.2
#97Earlier quoted context omitted.
I look for wake from sleep fixes, nvidia the primary offender there (they have at least two bugs affecting it across several driver versions). But my intel wifi driver (BE200) also has an apparent hard lock on wake. Looks like this particular release doesn't have any fixes for me, though claude says its not the full change list.
Intel has a specific series of integrated network cards that softlock themselves and you can only fix by disconnecting power for 30s, reconnecting the power, then rebooting the PC twice. Living through that made me wonder why people would ever swap out their Broadcom or Atheros WiFi card for an Intel one.
Re: Linux 7.2
#98Does anyone understand how HDMI 2.1 support is now no problem? I remember that 2.1 support in AMD's open source driver was blocked by the HDMI forum, but I haven't heard any news about them unblocking it. What changed?
If FOSS drivers support HDMI 2.2 when devices start shipping with HDMI 2.2 ports then this'll be disproven, but the HDMI forum held off on allowing AMD to implement 2.1 support in their Linux drivers for years and only relented when they released HDMI 2.2. Valve with the Gabecube probably didn't have much to do with it considering how low volume it is.
Re: Linux 7.2
#99I just want them to make memory management sane. Is that too much to ask? OOM shouldn't cause a hard reboot. Ok actually I "solved" this by upgrading to 128GB of RAM (before the rampocalypse), but still they should fix it.
Re: Linux 7.2
#100Earlier quoted context omitted.
Strongly disagree. Hardware support improved by leaps and bounds last decade and a half. Namespace isolation and cgroups driven containerization. eBPF appeared and gained adoption. Async I/O (and later just everything async) converged on io_uring. Btrfs is _stable_ - some people believed it would never be possible, ever. All kinds of scheduling were iterated and iterated over. All these things are visible across the…
btrfs is stable?? I used it a couple of years ago and really didn’t have a positive experience. I’ve found ZFS much more stable