On Thu, Nov 20, 2014 at 06:53:27PM +0100, Marco d'Itri wrote: > On Nov 20, Sam Hartman <hartm...@debian.org> wrote:
> > The first issue (fstab now fatally blocks boot) is something the systemd > > maintainers have considered (as I understand it) and rejected. > The behaviour of systemd will not be changed, but I have plans to add > a fstab sanity check to preinst. This would be a useful improvement, but bear in mind that there might be a device successfully mounted at package install time that subsequently fails to mount at boot - either because it's removable media and it has been removed, or because it's a filesystem that requires something extra beyond what's currently integrated with systemd in order to mount. (e.g. a network filesystem which requires an additional client daemon for mounting, and the client daemon only has an init script running in runlevel 2.) So it's important to provide users with straightforward means of recovery when their system gets into this state on boot. Based on my experience with upstart, I would say this is a hard thing to get right - but it's important to consistently work towards this. -- 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/ slanga...@ubuntu.com vor...@debian.org
signature.asc
Description: Digital signature
