Re: systemd-fsck?

To: debian developers <debian-devel@lists.debian.org>
Subject: Re: systemd-fsck?
From: Brian May <brian@microcomaustralia.com.au>
Date: Tue, 13 May 2014 11:56:27 +1000
Message-id: <[🔎] CAA0ZO6DG-HFyeFdRL6QxbCCWmn-sbqhRBeBEYh6qr4whCNNwYA@mail.gmail.com>
In-reply-to: <[🔎] 20140513011130.GC31790@auth.logic.tuwien.ac.at>
References: <[🔎] 1399582256.2096.6.camel@PackardBell-PC> <[🔎] 87oaz720d8.fsf@windlord.stanford.edu> <[🔎] 1399631705.2096.16.camel@PackardBell-PC> <[🔎] 87a9ar9lq0.fsf@xoog.err.no> <[🔎] 20140509175643.GC13708@virgil.dodds.net> <[🔎] 536D1EBE.3030500@debian.org> <[🔎] 20140513003006.GC32228@virgil.dodds.net> <[🔎] 20140513011130.GC31790@auth.logic.tuwien.ac.at>

On 13 May 2014 11:11, Norbert Preining <preining@logic.at> wrote:

#743265: systemd: booting with init=/bin/systemd drops into emergency mode

If a device is not available but listed without "noauto" or "nofail"
in /etc/fstab, systemd drops into emergency mode.

Maybe I am mistaken, however I thought this was standard behaviour for SYSV boot systems too????

That bug is closed and archived, BTW.

--
Brian May <brian@microcomaustralia.com.au>

Reply to:

Follow-Ups:
- Re: systemd-fsck?
  - From: Norbert Preining <preining@logic.at>

References:
- systemd-fsck?
  - From: Svante Signell <svante.signell@gmail.com>
- Re: systemd-fsck?
  - From: Russ Allbery <rra@debian.org>
- Re: systemd-fsck?
  - From: Svante Signell <svante.signell@gmail.com>
- Re: systemd-fsck?
  - From: Tollef Fog Heen <tfheen@err.no>
- Re: systemd-fsck?
  - From: Steve Langasek <vorlon@debian.org>
- Re: systemd-fsck?
  - From: Michael Biebl <biebl@debian.org>
- Re: systemd-fsck?
  - From: Steve Langasek <vorlon@debian.org>
- Re: systemd-fsck?
  - From: Norbert Preining <preining@logic.at>

Prev by Date: Re: systemd-fsck?
Next by Date: Re: systemd-fsck?
Previous by thread: Re: systemd-fsck?
Next by thread: Re: systemd-fsck?
Index(es):
- Date
- Thread