event based initramfs

[Phillip Susi]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 05/12/2012 08:54 PM, Steve Langasek wrote:
> There are many ways that it could be done; using an event-based system that
> matches the way things are done post-initramfs is probably the simplest and
> most maintainable, however.

Why?  It seems to me that would be much more complex than needed.  What opportunities are there to share init code with what is done post initramfs that aren't already done via udev?  The one example given in the meeting description is cryptsetup, but as I said before, I don't see how that could be done the same way at boot ( which must interact with either the console or plymouth ) and how it should be handled later ( with udisks maybe, interacting with the desktop ).

I guess what I'm trying to say is that the parts that should be event based already seem to be udev rules and share common code, and the parts that don't share common code can't due to requirements that are different at boot time than they are later.  Since udev already provides an event driven framework in the initramfs, why add another one?


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJPrxB3AAoJEJrBOlT6nu75ZPgH/RDlyc3H8WnB3DaiU8MGimOd
A3XgFLCLIztoIK2YybVZkDCk5BZVLOYwto23YVJT/iSvHMBLGx2Ylqy3BmOW82Yb
stPA6MBb583J1LEMCuGmSviVdh4G9REgrXTy1V3YKy4wV4gKXN32G4WqQ9YcL7el
+mGI/vwQiYISh7ZXrniUBoaXwT2hww3FeizF5sgw5EKhP7SbB0G1xVKf43Zo1HnG
MN3kt0YXHDOVKVKp9sTO2Iw9kitpx50GQtEM8Mq0H1IOA52WIiuNCt7FxOrTpXF2
M4cV4N+iTyc3XGbhICBX9PGx5sjiflJ/s/+k4QoCzbZ4HtW2GyTohOnm8nIkysM=
=5sg1
-----END PGP SIGNATURE-----