shared modular initrd

Initrds are responsible for a complex set of tasks and should still remain as lean as possible for given requirements. An initrd might only be required to start lvm, or raid, or crypto or detect if suspend occurred previously and attempt to resume (before falling back to normal boot). Or it could be required to do all of that. It may even be required to setup system resources over a network connection, even a wireless one. The initrd is also useful for recovery, and a generic set of system-recovery tools should be available as a recovery or debug initrd. I thusly propose a shared initrd project be created or selected. Ideally used by most or all major linux distributions. The initrd should be regenerated based off of a set of script directories which would operate like traditional priority numbered lists of tasks. Busybox, small static, or dynamic linked executables (along with their dependencies) should be properly placed under the image directory and then packed in to the target initrd when regenerated. In this way it would be easy for a poweruser to understand and modify the structure if required. Userspace tools for managing startup order and events should also be simple to write.