dracut_mkdir(): create parent directories as needed.

[thirdparty/dracut.git] / HACKING

diff --git a/HACKING b/HACKING
index 7c9b996ea3fc5e2c5860c50edebdc4ad9b920136..3c3a52da5ab3ff71f6d5f7d0c4f2c4b4e5b0b368 100644 (file)
--- a/HACKING
+++ b/HACKING
@@ -1,15 +1,23 @@
-Right now, I'm doing most of my testing using a qemu/kvm guest and
-generating the initramfs on another box.  I then can boot the guest
-using qemu's -kernel and -initrd options.  Currently supported rootfs
-types are regular partitions, root-on-lvm and root-on-lvm-on-encrypted-pv.
-
-generate.sh exists and will build an image.  Right now, it depends on
-some existing pieces of the Fedora initrd infrastructure, but moving
-those out is a priority now that the basic functionality has been
-proven.
-
-To use, just run generate.sh with an output file for the initrd.  It
-will copy over some binaries as well as the appropriate shared library
-dependencies.  If you are doing a rootfs type that requires modules
-(on Fedora, this is just encrypted root now), you'll want to have the
-modules tree to copy in in a modules/ sub directory.  
+Right now, most of the testing is done using a qemu/kvm guest and
+generating the initramfs on another box but the support is all present
+to build for the "running" machine.  For the former, you can boot the guest
+using qemu's -kernel and -initrd options.
+
+dracut exists and will build an image.  It is command-line equivalent
+to most mkinitrd implementations and should be pretty straight-forward
+to use.
+
+To use, just run dracut with an output file name and, optionally, a
+kernel version (it defaults to using the current).   The appropriate
+modules will be copied over and things should be good to go.  If you'd
+like to customize the list of modules copied in, edit /etc/dracut.conf
+and set
+  dracutmodules="foo bar baz"
+
+Note that dracut calls functional components in modules.d "modules"
+while kernel modules are called "drivers".
+
+Requirements:
+* udev
+* nfs module: nfs daemon and rpc helper
+* iscsi: iscsi