Bug#756903: systemd: Boot hangs if filesystems unavailable

[Stefan Monnier]

>> - If a mount fails, keep on booting.  And then do your best to try and
>> bring this problem to the attention of someone (mentioning the
>> "nofail" option in that same message).  Only stop the boot if the
>> partition is explicitly marked as "critical" or "stoponfail".
> Well, 'fail', which is the default, means just that.

Not sure what "that" means here.  Does your "that" mean "that which you
just described" or does it mean "fail"?

> Systemd tries to do the corrent and safe thing by default.

I'd hope so, but here's my case:
- a machine somewhat far away with an old and unimportant fstab entry
  that refers to a drive that's rarely connected.
- after upgrading to systemd, the fstab entry caused systemd to stop the
  boot (presumably asking for the operator to do something on console).
- with the boot stopped, I (the operator who is not on console, since
  it's a remote machine), I can't fix the fstab entry.

In which way is it "safe and correct" to interrupt the boot in this case?

I can understand that making the mount wait (rather than just fail
right away) might be made necessary by the fact that systemd changes the
order in which operations are performed.  I.e. I understand why the
change nb 1 might be needed.

But that doesn't explain why change number 2 was needed.
Apparently you think Michael's response explains it, but I failed to
see how.


        Stefan