User avatar
🇨🇦Samuel Proulx🇨🇦 @fastfinge@interfree.ca
1y
Even completely headless, command line doesn't prioritize in any way. Today I had to reinstall an entire system from scratch because a drive listed in my /etc/fstab died. That makes boot into emergency mode, where you get no SSH, no network, no sound, and no screen reader. There is no quick way to force it to try and boot even though drive 7 of 11 has died, and it could absolutely bring up SSH and the network to let me fix it if it wanted to, just like sysvinit used to do. You can't even force systemd to add SSH and the network to emergency mode because of circular dependencies. nofail will only continue the boot if the drive doesn't exist, but if the filesystem has issues...emergency mode for you. In short: if your drive dies on Linux, fuck you. Be able to see, or reinstall your entire system, because nobody in Linuxland gives a shit about or your needs.
:black_sparkling_heart@fire.asta.lgbt:1:blobcat_cactus@very.tastytea.de:1:drgn_heart@not.an.evilcyberhacker.net:1💙1💜2
17
95
83
6
User avatar
lizzy ☭ heart_lesbian_diagonal2 cuwu @lizzy@social.vlhl.dev
1y
@fastfinge you can add the nofail flag in fstab to make it boot regardless of failure
1
0
0
0
User avatar
🇨🇦Samuel Proulx🇨🇦 @fastfinge@interfree.ca
1y
@lizzy Yes, as I said in my post, that works if the hardware is dead or removed or otherwise borked. But if there's issues with the filesystem, it'll halt the boot and ask you what to do/how to recover it, landing you in emergency mode.
0
0
1
0