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

[Lennart Poettering]

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

> On Mon, 2015-06-29 at 20:50 +0200, Lennart Poettering wrote:
> > 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.
>
> I disagree strongly.  As I said the "option" did not do anything... so
> the change only really happened when systemd coded it. Very people are
> using systemd, so this change may be "stable old code" in your world, in
> my world it "new" and its behaviour is "wrong" !

Well, it has been out there for a while, and it has been shipped for
quite some time in commercial distros like RHEL.

I understand that everbody thinks his own usecase is the most relevant
one, the important one we should focus on when designing our
stuff. But actually it's more complex than that. There are tons of
usecases, and when we pick defaults we should come up with something
that covers a good chunk of them nicely, but also fits conceptually
into how we expect systems to work.

Let's just agree to disagree on this issue.

> Hmmm ... it used to be possible with telnetd, so I suspect it is still
> possible with sshd.

Well, bring it up with your distro. We do not maintain sshd nor its
integration intp the distro.

Lennart

-- 
Lennart Poettering, Red Hat