On Fri, 21 Feb 2020 18:44:19 +0100 Per Jessen <per@computer.org> wrote:
zb4ng wrote:
Am 21.02.20 um 16:29 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.
My apologies. I had assumed you added it yourself - I wasn't aware YaST does this when you check the 'mount it' option. So not your fault.
Imho - assuming they want to get more users for openSuSE or Linux in general - getting into maintenance mode might scare them away, so changing the defaults in YAST etc might help making the system more beginner-friendly.
Yep, agree on that. But the solution is to fix YaST - the drop to maintainance mode on mount failure is definitely needed for many other cases.
If there are many cases where this is necessary, then I agree with that.
One case is really enough. If a filesystem could not be mounted, you generally don't want the system just marching on.
Err, see below.
But the same issue happens, if you have two Linux systems - say openSuSe + Ubuntu - on your hard disk and remove a partition in Ubuntu, then openSuSE doesn't know anything about it and it will go into maintenance mode while booting.
That is expected behaviour. If you have asked your openSUSE to mount that filesystem on that partition, and it suddenly does not exist, what would expect your system to do ?
To be fair, the current usual? environment of a single desktop different considerably from a typical? server. If there's a desktop, then what the (a?) user typically wants is for the desktop to come up and then perhaps ask questions about what do you want to do about this missing filesystem or whatever other resource is missing. On a server, I might want it to stop and bleat "something's wrong", yes. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org