On Fri, 21 Feb 2020 15:03:41 +0100 "Carlos E. R." <robin.listas@telefonica.net> wrote:
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.
You mean because the multimedia files get written to the underlying mount point, which is in some filesystem such as / ? If so you can try the technique I always use when setting up a new mount point. Set the permissions of the underlying mount point to 000. That way nothing can write into the directory on the underlying filesystem. When the extra filesystem is mounted over the top, it's permissions are used instead.
It is not theoretical, it is my case.
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org