On Sat, Jun 26, 2010 at 04:20:17PM +0200, Christoph Anton Mitterer wrote: > On Sat, 2010-06-26 at 14:02 +0200, Mario 'BitKoenig' Holbe wrote: > > I'm not really sure what's the intended boot-sequence but I personally > The problem is, there is not "intended" way of doing it,... many users
Well, there surely was some intention behind having cryptdisk-early and
cryptdisk :) I know, there is no "good" boot-sequence currently, but
there surely was an "intended" one :)
> I'm currently looking into these problems,.. but I guess there is no
Yes, a while ago I did the same :)
> AFAIK Jonas is also looking for a way to generically solve this,.... but
> all the other packages (lvm2, mdadm) are in principle also affected...
Well, the easiest and most flexible solution that came to my mind was
some vbd-common package which offers a plug-in-mechanism for other
virtual-blockdevice-packages, i.e. a directory to put start/stop scripts
in, and to circulary call them until no new blockdevice got created in a
whole pass (or - on shutdown - got removed).
regards
Mario
--
As a rule, the more bizarre a thing is, the less mysterious it proves to be.
-- Sherlock Holmes by Arthur Conan Doyle
signature.asc
Description: Digital signature
