Timeline
Post
Remote status
Context
11
@lanodan@queer.hacktivis.me @volpeon@icy.wyvern.rip Just because Arch is terrible doesn't mean this applies to every other distro though.
@SuperDicq @volpeon Yeah, although grub being painfully unreliable is rather distro-agnostic, yet it's the bootloader of choice of nearly all distros.
@lanodan@queer.hacktivis.me @volpeon@icy.wyvern.rip What's unreliable about GRUB? I can't recall ever having issues with it.
@SuperDicq @volpeon Things aren't always about you, there's a ton of well documented failures of grub and that's the tip of the iceberg.
And I hate this "works for me" (aka "fuck you got mine") attitude with things, do not do this ever again.
And I hate this "works for me" (aka "fuck you got mine") attitude with things, do not do this ever again.
@lanodan@queer.hacktivis.me @volpeon@icy.wyvern.rip
And I hate this "works for me" attitude with things, do not do this ever again.There is no objective way to measure something like "reliability", it will always be very subjective and based on personal experience.
I have always thought it is very reliable because it has never failed me. But you think it is not reliable, so I'm curious as to what experiences you have had that made you think it is unreliable.
This is a normal way how people discuss things and learn for each other. It's not an attitude and I'm not going to promise to "not do this ever again".
@SuperDicq @volpeon The reasons why I'm taking it as unreliable are basically architectural, it'll work for most but the failure modes are the worst for a bootloader to have.
grub-install can literally fail to fully install and not report an error. Combine this with how modules have ABI breaks without backward compatibility, so you get the MBR or EFI executable updated to a new version but without their modules required for bootup.
Similarly grub-install often fails to detect the hardware, which is stuff that ought to be into a configuration (allowing a verification step) instead of magically done every time it's executed.
grub-mkconfig similarly can create config files that it then cannot parse, that one even predates grub 2.x
grub-install can literally fail to fully install and not report an error. Combine this with how modules have ABI breaks without backward compatibility, so you get the MBR or EFI executable updated to a new version but without their modules required for bootup.
Similarly grub-install often fails to detect the hardware, which is stuff that ought to be into a configuration (allowing a verification step) instead of magically done every time it's executed.
grub-mkconfig similarly can create config files that it then cannot parse, that one even predates grub 2.x
@mischievoustomato@tsundere.love @lanodan@queer.hacktivis.me @volpeon@icy.wyvern.rip I don't think a valid alternative really exists. Both Lilo and Syslinux are basically unmaintained.
@SuperDicq @lanodan @volpeon @mischievoustomato If you don't need the half-assed LUKS support (you don't if you trust secureboot :-DDD), refind, limine and systemd-boot are all valid alternatives.
@phnt@fluffytail.org @lanodan@queer.hacktivis.me @volpeon@icy.wyvern.rip @mischievoustomato@tsundere.love Refind and systemd-boot only work on proprietary UEFI crap hardware. I do not use UEFI on any of my computers. They are not valid alternatives for a fully free software bootloader.
@SuperDicq @lanodan @volpeon @mischievoustomato Cringe, clover exists and is still maintained and you can boot all three from that probably.
Replies
0
No replies yet.