6377c723aa
It is reasonable that elements may need to include additional kernel modules in a dracut ramdisk. This is done with the --add-drivers option to dracut, but previously the value passed was hard-coded. This change allows an element to put a file containing its desired drivers in a dracut-drivers.d directory, and the list there will be added to the list of drivers added. This functions in essentially the same way as the binary-deps.d directory that already exists for including additional executables in a ramdisk. Change-Id: Ie892b908d36c175a469f7cde7dd803ad4b1942b6
20 lines
801 B
ReStructuredText
20 lines
801 B
ReStructuredText
==============
|
|
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.
|