[systemd-devel] Stricter handling of failing mounts during boot under systemd - crap idea !

[Lennart Poettering]

On Mon, 29.06.15 19:20, jon (jon at jonshouse.co.uk) wrote:

> Reversing the logic by adding a "mustexist" fstab option and keeping the
> default behaviour would fix it.

At this time, systemd has been working this way for 5y now. The
behaviour it implements is also the right behaviour I am sure, and the
"nofail" switch predates systemd even. Hence I am very sure the
default behaviour should stay the way it is.

> Bringing up networking/sshd in parallel to the admin shell would also
> mitigate my issue....

That's a distro decision really. Note though that many networking
implementations as well as sshd are actually not ready to run in
early-boot, like the emergecny mode is. i.e. they assume access to
/var works, use PAM, and so on, which you better avoid if you want to
run in that boot phase.

> I can see that both proposed solutions have issues, but I suspect I am
> not the only one who will not be pleased about this behaviour change.
> 
> Changes seem to made with a bias towards desktops or larger data
> centres, but what about the people using discarded PCs and maintaining
> small servers, lots of these floating around smaller organisations. 

As you might know my company cares about containers, big servers
primarily, while I personally run things on a laptop and a smaller
server on the Internet. Hence believe me that I usually care about
laptop setups at least as much as for server setups.

Lennart

-- 
Lennart Poettering, Red Hat