diskimage-builder/elements/ramdisk
Chris Jones 09eb230ea3 Detect udevd version and behave accordingly.
We can no longer rely on the name of the udevd binary as a hint for its
version, so instead we query the binary and behave accordingly.

Change-Id: Id4c869dfeeca5ed970169343b6b5f0f2c4499ca3
2013-11-20 11:13:06 +00:00
..
cleanup.d /bin/bash all the things. 2013-11-17 16:59:31 -06:00
extra-data.d Detect udevd version and behave accordingly. 2013-11-20 11:13:06 +00:00
init.d Split network bringup out of base ramdisk init. 2013-11-17 20:37:26 +00:00
post-install.d Remove BUSYBOX variable from ramdisk-defaults 2013-11-11 14:36:15 +01:00
README.md Document ramdisk troubleshooting. 2013-11-18 19:45:59 +00:00

This is the ramdisk element.

Almost any user building a ramdisk will want to include this in their build, as it triggers many of the vital functionality from the basic diskimage-builder libraries (such as init script aggregation, busybox population, etc).

An example of when one might want to use this toolchain to build a ramdisk would be the initial deployment of baremetal nodes in a TripleO setup. Various tools and scripts need to be injected into a ramdisk that will fetch and apply a machine image to local disks. That tooling/scripting customisation can be easily applied in a repeatable and automatable way, using this element.

See the top-level README.md of the project, for more information about the mechanisms available to a ramdisk element.