79ab95b16e
If scripts are not set -e then errors can be ignored, causing more confusing failures later. Also adds an exclusion comment to the ramdisk init script since we don't want that to exit on failure. Change-Id: Idf43993bd10b1ef16c1d3b0d9df8d0ad94c46458 |
||
|---|---|---|
| .. | ||
| cleanup.d | ||
| extra-data.d | ||
| init.d | ||
| install.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.