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
remmy @remmy@treehouse.systems
1y
@fastfinge

While the entire way the emergency and rescue modes work really needs to be re-worked taking accessibility into account, until that happens (if ever...) you can disable it entirely by masking emergency.target and emergency.service, (systemctl mask emergency.target emergency.service,) which will make your system keep booting instead. (Though then it becomes extra important to make sure that services requiring those mounts have explicit dependencies on them, so they don't get accidentally started and start doing things on the wrong filesystems.)
1
0
1
0
User avatar
🇨🇦Samuel Proulx🇨🇦 @fastfinge@interfree.ca
1y
@remmy Instead of messing with the terrifying mess that is systemd dependencies, I just have permissions set on the mounting directory so processes can't write there. They can only write to the actual mounted filesystem. So thanks for the tip! This will help.
0
0
0
0