6b220a044f
If you build a ramdisk with ramdisk-image-create and forget to specify -o, you end up with a .kernel and .initramfs file as the image outputs. This commit defaults the $IMAGE_NAME value to image so you'd end up with image.kernel and image.initramfs Change-Id: I10f3ac9ad178c32119523e4da930070e3ade4f73 |
||
|---|---|---|
| .. | ||
| cleanup.d | ||
| extra-data.d | ||
| init.d | ||
| post-install.d | ||
| README.md | ||
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.