d11c10fb6a
The version of depmod in busybox does not work if two versions of the same kernel version are available, as search paths are not honoured correctly. However, we don't need to actually call depmod as it's done during image building anyway. Change-Id: Idd3cd5854e7c86e7ca1f2b0e50758d7db79ab6e7 Co-Author: matthew.gilliard@hp.com Closes-bug: #1302856 |
||
|---|---|---|
| .. | ||
| 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.