On Thu, Aug 15, 2013 at 10:24:42AM +0200, Michael Stapelberg wrote:
> Bastian Blank <wa...@debian.org> writes:
> > 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).

The lvm2 init-script declares a lazy dependency on the udev init-script,
which is unquestionable available. The later makes sure the hardware is
available by waiting.

The description tells me:
| # Short-Description: Start udevd, populate /dev and load drivers.
If this is not longer true, fix this first.

Bastian

-- 
Those who hate and fight must stop themselves -- otherwise it is not stopped.
                -- Spock, "Day of the Dove", stardate unknown


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to