[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#769907: A small suggestion on constructive engagement [Was, Re: Bug#769907: general: non-sysvinit init systems are made of fail]



On Thu, Nov 20, 2014 at 01:45:55PM -0800, Octavio Alvarez wrote:
> On 19/11/14 21:32, Steve Langasek wrote:
> >> 1) the problem with new feature in systemd which considers all 
> >> filesystems in fstab vital for system boot and stops boot if they
> >> fail. It's been decided that although it is a change in behaviour
> >> that might render some systems unbootable it's technically correct
> >> implementation and only enforces that non-vital filesystems are
> >> marked as such in fstab which should have been the case from the
> >> start.

> > As regards the two issues you've described: the first is not a bug.
> > It's a necessary change in how we view the boot in a truly
> > event-driven system. There is no sane default policy for how to
> > interpret entries in /etc/fstab on upgrade except to regard them as
> > all mandatory - *but* it's important that the admin be given the
> > opportunity to intervene to override this policy.

> Question: is it safe to say that systemd doesn't yet support the full
> /etc/fstab specification from util-linux [1]?

.... No?

-- 
Steve Langasek                   Give me a lever long enough and a Free OS
Debian Developer                   to set it on, and I can move the world.
Ubuntu Developer                                    http://www.debian.org/
slangasek@ubuntu.com                                     vorlon@debian.org

Attachment: signature.asc
Description: Digital signature


Reply to: