> While this will eventually reduce workload for boot/installation components (grub2 reduces surface area, syslinux goes away entirely, anaconda reduces surface area)
For heaven sake please stop using grub, it's a nightmare. You need multiple levels of scripts/programs to take your confusing human configuration & kick out the verbose complex full grub.cfg, which you then need to run another tool to install onto the drive. It's absurd, it sucks.
Systemd-boot (nee Gummiboot) is just amazing. There's some very very simple text files, on the EFI partition, that you can freely edit, and the bootloader will work with. There's a live editor you can use if things go wrong.
The much loved Pop!OS uses systemd-boot if it detects UEFI. Let that be your guide for what's good for users, I swear, it's so much better. I'm not sure whether I support abandoning legacy boot yet- I hate to just drop support quite so soon, but really, support in hardware has been quite awesome, albeit not quite for a decade yet. But moving to drop legacy support would be a great step, some day, and will make moving to systemd-boot an obvious & vast improvement over horrific terrible grub2.
Hearing that OVH & many many Amazon instances use legacy BIOS is cry-into-your-hands sad. This is like IPv6 transition hard: there's just such a huge userbase that'll never be incentivized to move on. Woe.
I've happily used systemd-boot in the past, but it's definitely less featureful than grub. Notably, it doesn't support the use of a (LUKS) encrypted boot partition. I'm not even sure it supports /boot on btrfs? Both are necessary if you want to have an encrypted root AND include the matching kernel / initramfs in any snapshots of root.
You can still get a ton of useful work out of 12 year old machines like dual xeon servers that never had UEFI or even 1st and 2nd gen core i7 machines. Piling it all into landfill while it still works is wasteful and shortsighted.
I guess this makes sense to me. Each OS maintainer should be able to decide when legacy code is just too much work to maintain. Some people may not be able to use Fedora on their older hardware and may have to use something else. I imagine this decision will eventually find its way into RHEL and the CentOS forks?
I am currently using Qubes OS as a browsing desktop and quite happy with it thus far, but it does not support UEFI on my hardware despite the installer recognizing it. I probably could have figured out what was going on but I just needed to quickly load a new OS. I am contemplating turning one of my little Protectli firewalls into a Qubes browsing desktop.
12 comments
[ 3.3 ms ] story [ 32.4 ms ] thread> While this will eventually reduce workload for boot/installation components (grub2 reduces surface area, syslinux goes away entirely, anaconda reduces surface area)
For heaven sake please stop using grub, it's a nightmare. You need multiple levels of scripts/programs to take your confusing human configuration & kick out the verbose complex full grub.cfg, which you then need to run another tool to install onto the drive. It's absurd, it sucks.
Systemd-boot (nee Gummiboot) is just amazing. There's some very very simple text files, on the EFI partition, that you can freely edit, and the bootloader will work with. There's a live editor you can use if things go wrong.
The much loved Pop!OS uses systemd-boot if it detects UEFI. Let that be your guide for what's good for users, I swear, it's so much better. I'm not sure whether I support abandoning legacy boot yet- I hate to just drop support quite so soon, but really, support in hardware has been quite awesome, albeit not quite for a decade yet. But moving to drop legacy support would be a great step, some day, and will make moving to systemd-boot an obvious & vast improvement over horrific terrible grub2.
Hearing that OVH & many many Amazon instances use legacy BIOS is cry-into-your-hands sad. This is like IPv6 transition hard: there's just such a huge userbase that'll never be incentivized to move on. Woe.
You can still get a ton of useful work out of 12 year old machines like dual xeon servers that never had UEFI or even 1st and 2nd gen core i7 machines. Piling it all into landfill while it still works is wasteful and shortsighted.
Yes exactly that!
https://www.eset.com/int/about/newsroom/press-releases/resea...
I am currently using Qubes OS as a browsing desktop and quite happy with it thus far, but it does not support UEFI on my hardware despite the installer recognizing it. I probably could have figured out what was going on but I just needed to quickly load a new OS. I am contemplating turning one of my little Protectli firewalls into a Qubes browsing desktop.