3 - let plymouth attach to the terminal (nice text output now)
4 - new kernel command line parameter "rdinfo" show dracut output, even when
6 - rd_LUKS_UUID is now handled correctly
7 - dracut-gencmdline: rd_LUKS_UUID and rd_MD_UUID is now correctly generated
8 - now generates initrd-generic with around 15MB
13 - iSCSI with username and password
14 - support for live images (dmsquashed live images)
15 - iscsi_firmware fixes
21 - dracut: strip binaries in initramfs
24 strip binaries in the initramfs (default)
27 do not strip binaries in the initramfs
30 Usage: ./dracut-catimages [OPTION]... <initramfs> <base image>
32 Creates initial ramdisk image by concatenating several images from the
34 line and /boot/dracut/
36 -f, --force Overwrite existing initramfs file.
37 -i, --imagedir Directory with additional images to add
38 (default: /boot/dracut/)
39 -o, --overlaydir Overlay directory, which contains files that
40 will be used to create an additional image
41 --nooverlay Do not use the overlay directory
42 --noimagedir Do not use the additional image directory
43 -h, --help This message
44 --debug Output debug information of the build process
45 -v, --verbose Verbose output during the build process
51 - dracut: add --kernel-only and --no-kernel arguments
54 only install kernel drivers and firmware files
57 do not install kernel drivers and firmware files
59 All kernel module related install commands moved from "install"
62 For "--kernel-only" all installkernel scripts of the specified
63 modules are used, regardless of any checks, so that all modules
64 which might be needed by any dracut generic image are in.
66 The basic idea is to create two images. One image with the kernel
67 modules and one without. So if the kernel changes, you only have
70 Grub and the kernel can handle multiple images, so grub entry can
73 title Fedora (2.6.29.5-191.fc11.i586)
75 kernel /vmlinuz-2.6.29.5-191.fc11.i586 ro rhgb quiet
76 initrd /initrd-20090722.img /initrd-kernel-2.6.29.5-191.fc11.i586.img /initrd-config.img
79 the image provided by the initrd rpm
80 one old backup version is kept like with the kernel
82 initrd-kernel-2.6.29.5-191.fc11.i586.img
83 the image provided by the kernel rpm
86 optional image with local configuration files
88 - dracut: add --kmoddir directory, where to look for kernel modules
91 specify the directory, where to look for kernel modules
97 - more generic (all plymouth modules, all keyboards, all console fonts)
98 - more kernel command line parameters (see also man dracut(8))
99 - a helper tool, which generates the kernel command line (dracut-gencmdline)
100 - bridged network boot
101 - a lot of new command line parameter
106 - firmware loading support
107 - new internal queue (initqueue)
108 initqueue now loops until /dev/root exists or root is mounted
110 init now has the following points to inject scripts:
113 scripts for command line parsing
116 scripts to run before udev is started
119 scripts to run before the main udev trigger is pulled
122 runs in parallel to the udev trigger
123 Udev events can add scripts here with /sbin/initqueue.
124 If /sbin/initqueue is called with the "--onetime" option, the script
125 will be removed after it was run.
126 If /initqueue/work is created and udev >= 143 then this loop can
127 process the jobs in parallel to the udevtrigger.
128 If the udev queue is empty and no root device is found or no root
129 filesystem was mounted, the user will be dropped to a shell after
131 Scripts can remove themselves from the initqueue by "rm $job".
134 scripts to run before the root filesystem is mounted
135 NFS is an exception, because it has no device node to be created
136 and mounts in the udev events
139 scripts to mount the root filesystem
140 NFS is an exception, because it has no device node to be created
141 and mounts in the udev events
142 If the udev queue is empty and no root device is found or no root
143 filesystem was mounted, the user will be dropped to a shell after
147 scripts to run before the real init is executed and the initramfs
149 All processes started before should be killed here.
151 The behaviour of the dmraid module demonstrates how to use the new
152 mechanism. If it detects a device which is part of a raidmember from a
153 udev rule, it installs a job to scan for dmraid devices, if the udev
154 queue is empty. After a scan, it removes itsself from the queue.
161 - first public version