84d10dce57
Instead, either use the bash built-in of type to ensure it exists. Since which is an external dep, things can fail oddly in a constrained environment. Also add a dib-lint test for this. Change-Id: I645029f5b5bfe1198c89ce10fd3246be8636e8af Signed-off-by: Jesse Keating <omgjlk@us.ibm.com> |
||
---|---|---|
.. | ||
binary-deps.d | ||
init.d | ||
install.d | ||
post-install.d | ||
element-deps | ||
pkg-map | ||
README.rst |
======= ramdisk ======= 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. NOTE: ramdisks require 1GB minimum memory on the machines they are booting. See the top-level README.md of the project, for more information about the mechanisms available to a ramdisk element.