On Fri, 21 Feb 2020 20:05:54 +0100 "Carlos E. R." <robin.listas@telefonica.net> wrote:
On 21/02/2020 17.03, Dave Howorth wrote:
On Fri, 21 Feb 2020 15:03:41 +0100 "Carlos E. R." <> wrote:
On 21/02/2020 13.54, zb4ng wrote:
Am 21.02.20 um 11:42 schrieb Peter Suetterlin:
zb4ng wrote:
...
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 / ?
Yes.
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.
Interesting trick :-)
It's not a trick, it's a design feauture of linux.
It would suffice to be read only, though. I typically create a file named "not_mounted" which I can use on scripts for testing.
Well yes, but 000 makes it absolutely clear what the intention is and has no downside that I'm aware of. And apparently your solution doesn't actually always solve the problem, since you're complaining! -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org