Hello, On Sun, 19 Jun 2016, Eugenio 'g7' Paolantonio wrote: > The After=local-fs.target rule introduced in commit 63ab809 made systemd > go in timeout while waiting for the local-fs target to be reached. > > This is due to the fact that the Before= rule in the live-config unit > prevents the startup of udev.
This explanation alone is not sufficient... If they are executed in this order then all requirements are met: local-fs.target -> live-config.service -> udev.service So what other requirements are there that make this ordering impossible? Are there mount points that can only be mounted if udev has been run? > I'm not raising severity on this one because I suspect this only happens > on installed environments, where live-config-systemd is largely useless. > But still, it shouldn't break the boot process in this way. > > I'm attaching a small patch that resolves the problem for me, also > available as a git commit at [1]. In fact I don't even know why it's ordered before udev.service. This has been introduced in commit 51b06113785f19bdf60a3a9fd383d11c252d4d6d and there are almost no explanations in the log message: commit 51b06113785f19bdf60a3a9fd383d11c252d4d6d Author: Daniel Baumann <[email protected]> Date: Tue Aug 13 22:03:52 2013 +0200 Improve boot order in systemd service file before getting a final (upstream) solution, thanks to Michael Stapelberg <[email protected]>. > I unfortunately haven't had the time to test it in a live environment. Thus I'm unlikely to apply it currently. Cheers, -- Raphaël Hertzog ◈ Debian Developer Support Debian LTS: http://www.freexian.com/services/debian-lts.html Learn to master Debian: http://debian-handbook.info/get/
