5 ms·
Wow, another buggy Ubuntu patch breaks something. Why don’t they just stick to what’s upstream?
by symlinkk 4y ago
Wow, another buggy Ubuntu patch breaks something. Why don’t they just stick to what’s upstream?
- fomine3 4y agoAccording to the article, looks reasonable modification (though it's hard) but should be tested.
- baggy_trough 4y agoYeah, I don't really get why they don't use the stable kernel releases, of which there are many, rather than rolling their own.
- kramerger 4y agoSeems like every department at canonical needs to learn this on their own. After all, they reinvented everything from DE to init system at least once in past. (They also have their own containers, LXD. I actually really like that one, please keep working on that canonical)
- leaflets2 4y agoWhat are some other bad mistakes that's been made?
- heurisko 4y ago22.04 uses the 5.15 LTS kernel. https://www.kernel.org/category/releases.html https://www.kernel.org/category/releases.html But I assume as Ubuntu follows an April release schedule, it doesn't always match with an appropriate LTS kernel.
- lproven 4y agoUbuntu was originally designed as a desktop OS and its release cycle was synched with the GNOME 2.x release cycle.
- treesknees 4y agoAgreed. Ubuntu does use a stable kernel by default for LTS, at least for ISO installs. This problem occurred within the HWE (hardware enablement) release train, where they backport non-LTS kernels and features, which for some reason they use as a default in various places like their official cloud images.