On 21/02/2020 13.54, zb4ng wrote:
Am 21.02.20 um 11:42 schrieb Peter Suetterlin:
zb4ng wrote:
My point is: maybe the maintainers could help to avoid this situation: Please, don't break the boot process if some malfunctioning but unimportant entry in fstab doesn't work! Or at least, make it easier for the user to find out what is going wrong. I had similar issues multiple times over the past years and sometimes it took me quite a time to figure them out.
Stuff that is listed in /etc/fstab and is not explicitely marked as being non-crucial is *supposed* to block the boot process. If you put something in there, it's your responsibility to set proper parameters.....
Well, I wasn't aware changing fstab, I just formatted the drive in YAST and I am learning just now that I could mark an entry as non-crucial. Moreover, looking at my own system, all partitions other than "/" or "/home" would be non-crucial.
That assumption can not be made. There can be, for example, a data partition which if not mounted causes big multimedia files to write to "/" instead, fill it up, and crash the system. It is not theoretical, it is my case. -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)