Hi Bastian, Michael Stapelberg <stapelb...@debian.org> writes: > Bastian Blank <wa...@debian.org> writes: >> On Wed, Aug 14, 2013 at 08:49:02PM +0200, Michael Stapelberg wrote: >>> Debian users who use systemd sometimes have trouble booting their >>> machines (see e.g. http://bugs.debian.org/718190). Here at DebConf I had >>> the chance to reproduce the issue and noticed that the lvm2 package does >>> not ship the systemd generator that upstream provides. >> >> The init-script calls vgchange -ay. Why does this not work? > Because the init script is called only once during boot, whereas new > devices may also appear later. As an example, in the case that Vincent > Bernat brought up, the lvm2 init script runs after the first hard disk > is crypto-unlocked and available, but does not run again (obviously) > after the second hard disk becomes crypto-unlocked (with a key file that > is stored on the first one). > > systemd in general does things based on events and whenever appropriate, > so this generator is required to make things work. > > I hope this clarifies, if not, please let me know. Thanks. Nearly a week has passed without hearing anything from you. Was my explanation not sufficient? Can I be of any help in moving this forward?
-- Best regards, Michael -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
