Bug#756103: systemd should be more forgiving of fstab errors

Michael Biebl biebl at debian.org
Mon Aug 11 22:53:54 BST 2014


Am 11.08.2014 23:35, schrieb Andrei POPESCU:
> I have been thinking about this incident since then and watching all the 
> "system doesn't boot due to fstab errors" reports (I'm subscribed to 
> both -user and -pkg-systemd-maintainers).
> 
> I'm not sure it's a good idea to just fail the boot completely whenever 
> there are errors like mine in fstab, but instead it would be much 
> friendlier if systemd would try to bring up as much of the system as 
> possible and start the emergency console only if e.g. / and /usr are 
> missing.


I already commented on that. I think it's wrong to just continue booting
and starting potentially critical services.
How is systemd supposed to know which file systems are vital?

You might have database on separate partitions and you might risk losing
data if the services are started but the partitions aren't available.


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20140811/b8347d8c/attachment-0002.sig>


More information about the Pkg-systemd-maintainers mailing list