Re: cryptdisks(-early) initscripts, dependencies and loops
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
Jonas Meurer wrote:
> the problem is that loads of possible setups are possible, all
> introducing different required initscript order. either another
> initscript needs to be invoked before, or after, or between the
> cryptdisks-early and cryptdisks initscripts.
What we have here is a dependency tree of arbitrary height, with each node
requiring an invocation of cryptsetup, lvm, mdadm, nbd or pretty much
anything else. So it's clear that you can never cover all possibilites with
a finite number of init scripts that run in a sequence.
An event-based system might be able handle this, but only if it allows the
same script to be invoked multiple times, taking different actions each
time.
Perhaps we need a little script that walks the dependency tree, and just
calls the necessary helper script for each node in turn.
Cheers,
Marcus
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
iEYEARECAAYFAkwItRYACgkQXjXn6TzcAQnjoACbBXIU2d8ZJ/VeXj/5p+M1t8Uy
hLIAnRzCMC587mrKfRvmLwwepe6hL6zq
=P0c4
-----END PGP SIGNATURE-----
Reply to: