openstack/diskimage-builder

History

Jenkins 1324f5b7db Merge "Remove use of 'which'."		2017-06-11 09:30:34 +00:00
..
binary-deps.d	Move elements & lib relative to diskimage_builder package	2016-11-01 17:27:41 -07:00
dracut-drivers.d	Move elements & lib relative to diskimage_builder package	2016-11-01 17:27:41 -07:00
environment.d	Move elements & lib relative to diskimage_builder package	2016-11-01 17:27:41 -07:00
extra-data.d/scripts/module	Move elements & lib relative to diskimage_builder package	2016-11-01 17:27:41 -07:00
init.d	Move elements & lib relative to diskimage_builder package	2016-11-01 17:27:41 -07:00
install.d	Move elements & lib relative to diskimage_builder package	2016-11-01 17:27:41 -07:00
post-install.d	Remove use of 'which'.	2017-05-19 12:43:36 -07:00
element-deps	Move elements & lib relative to diskimage_builder package	2016-11-01 17:27:41 -07:00
pkg-map	drop deprecated map-services/packages from zypper element	2017-05-25 23:43:21 +02:00
README.rst	Move elements & lib relative to diskimage_builder package	2016-11-01 17:27:41 -07:00
source-repository-dracut	Move elements & lib relative to diskimage_builder package	2016-11-01 17:27:41 -07:00

README.rst

dracut-ramdisk

Build Dracut-based ramdisks

This is an alternative to the ramdisk element that uses Dracut to provide the base system functionality instead of Busybox.

For elements that need additional drivers in the ramdisk image, a dracut-drivers.d feature is included that works in a similar fashion to the binary-deps.d feature. The element needing to add drivers should create a dracut-drivers.d directory and populate it with a single file listing all of the kernel modules it needs added to the ramdisk. Comments are not supported in this file. Note that these modules must be installed in the chroot first.

By default, the virtio, virtio_net, and virtio_blk modules are included so that ramdisks are able to function properly in a virtualized environment.