5 ms·
There are lots of stable Linux distros running the stable kernel which is 5.8. it is just distros like RHEL that call themselves stable, but are actually antiqu
by chromedev 6y ago
There are lots of stable Linux distros running the stable kernel which is 5.8. it is just distros like RHEL that call themselves stable, but are actually antiquated and honestly just give users a bad experience because most of the software is outdated. Wouldn't expect anything less from IBM.
- gsich 6y agoRedhat did that before they were bought by IBM.
- chromedev 6y agoI was never a fan of RHEL even before they got purchased. They've done some great things lately with Podman, Buildah, Skopeo, etc but never really been an innovator when it comes to desktop Linux. I see Arch and Alpine being the real innovators, and projects like wlroots.
- deleted 6y ago[deleted]
- fomine3 6y agoJust "not for me". It's for enterprise as the name says.
- chromedev 6y agoSo is Alpine Linux. Almost no enterprise I've worked at lately wants to deal with antiquated software as long as their Kubernetes distro is working well.
- silly-silly 6y agoHow did Arch and Alpine innovate ?
- chromedev 6y agoThey provided a greatly improved package manager and package interface. Fedora and most other distros don't even come close in terms of the amount of high quality modern packages available from the official repos and AUR, but Alpine has also been growing substantially.
- aidenn0 6y agoAnd it's somewhat silly to freeze the kernel. The Linux kernel is meticulous about backwards compatibility. Spin up any distribution user space in docker, and watch it work.
- oarsinsync 6y agoUser space, yes. Try loading (or recompiling) kernel modules. It’s a different story there, as they have no issues breaking that between releases.
- corty 6y agoFreezing the RH kernel is mostly to keep closed source kernel modules working. Some proprietary software has those, unfortunately.
- gravitas 6y agoRed Hat also customizes the kernel they've standardized on to disable hardware functionality which they do not want to support under SLA; they have two general ways of doing it, disable compilation of the entire module (where possible) or add the specific PCI ID to a filter-out on that module's supported hardware. The methods tend to route through a custom routine in their kernel patches which notify the user the hardware has been seen but will not function/be supported by their kernel. This goes the other way around a well, they often cherry-pick new code and pull it back into their curated kernels to support the latest hardware offerings of their partners (Dell, HP, Broadcom, etc.) without pulling in possible unstable newer kernel code around it; they have contractors from those hardware companies assisting in the work to backport hardware module features.
- deleted 6y ago[deleted]
- pferde 6y agoYou are simply not the target audience for enterprise Linux distros. But they have their uses, and I am glad that they exist.