Hi all, Am 30.05.19 um 21:57 schrieb Stefan Monnier: >> In this case, it is better for the system not to boot and point out >> errors in /etc/fstab instead. > > So it doesn't boot, and I'm screwed because I can't SSH into it to > fix it, so I have to get someone to physically go there and that someone > needs to be up to the task of accessing the serial console and do the > funny dance. And in the mean time, my VPN doesn't work, etc... > > To each his definition of "better", of course ;-)
there is another reason to prefer booting in such a case: Think about the odd hardware defaults of hardware like the Lamobo R1. Per default in such case where booting stops the built-in switch is a major security risk and I'm convinced there is more hardware out there suffering from similar issues. Once its up and configured this risk is gone. A third reason is tolerance over faults. In many situations devices are able to fulfill a part of their jobs still even if some additional storage fails. Some less experienced user might even remove an external device and wonder why the applicance doesn't work any more at all. Sometimes there is not even an attached console for displaying diagnostic messages. (Why would one use it for? Installlation takes place offline using Freedom-Maker.) So failing to boot is a good option for developers but a bad idea in the life of average users. Greetings Florian -- The dream of yesterday Florian Boor is the hope of today Tel: +49 271-771091-15 and the reality of tomorrow. Fax: +49 271-338857-29 [Robert Hutchings Goddard, 1904] [email protected] http://www.kernelconcepts.de/en kernel concepts GmbH Hauptstraße 16 D-57074 Siegen Geschäftsführer: Ole Reinhardt HR Siegen, HR B 9613 _______________________________________________ Freedombox-discuss mailing list [email protected] https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/freedombox-discuss
