]>
Commit | Line | Data |
---|---|---|
0de91060 HH |
1 | dracut-0.8 |
2 | ========== | |
3 | - iSCSI with username and password | |
4 | - support for live images (dmsquashed live images) | |
5 | - iscsi_firmware fixes | |
6 | - smaller images | |
7 | - bugfixes | |
8 | ||
9 | dracut-0.7 | |
10 | ========== | |
11 | - dracut: strip binaries in initramfs | |
12 | ||
13 | --strip | |
14 | strip binaries in the initramfs (default) | |
15 | ||
16 | --nostrip | |
17 | do not strip binaries in the initramfs | |
18 | - dracut-catimages | |
19 | ||
20 | Usage: ./dracut-catimages [OPTION]... <initramfs> <base image> | |
21 | [<image>...] | |
22 | Creates initial ramdisk image by concatenating several images from the | |
23 | command | |
24 | line and /boot/dracut/ | |
25 | ||
26 | -f, --force Overwrite existing initramfs file. | |
27 | -i, --imagedir Directory with additional images to add | |
28 | (default: /boot/dracut/) | |
29 | -o, --overlaydir Overlay directory, which contains files that | |
30 | will be used to create an additional image | |
31 | --nooverlay Do not use the overlay directory | |
32 | --noimagedir Do not use the additional image directory | |
33 | -h, --help This message | |
34 | --debug Output debug information of the build process | |
35 | -v, --verbose Verbose output during the build process | |
36 | ||
37 | - s390 dasd support | |
38 | ||
39 | dracut-0.6 | |
40 | ========== | |
41 | - dracut: add --kernel-only and --no-kernel arguments | |
42 | ||
43 | --kernel-only | |
44 | only install kernel drivers and firmware files | |
45 | ||
46 | --no-kernel | |
47 | do not install kernel drivers and firmware files | |
48 | ||
49 | All kernel module related install commands moved from "install" | |
50 | to "installkernel". | |
51 | ||
52 | For "--kernel-only" all installkernel scripts of the specified | |
53 | modules are used, regardless of any checks, so that all modules | |
54 | which might be needed by any dracut generic image are in. | |
55 | ||
56 | The basic idea is to create two images. One image with the kernel | |
57 | modules and one without. So if the kernel changes, you only have | |
58 | to replace one image. | |
59 | ||
60 | Grub and the kernel can handle multiple images, so grub entry can | |
61 | look like this: | |
62 | ||
63 | title Fedora (2.6.29.5-191.fc11.i586) | |
64 | root (hd0,0) | |
65 | kernel /vmlinuz-2.6.29.5-191.fc11.i586 ro rhgb quiet | |
66 | initrd /initrd-20090722.img /initrd-kernel-2.6.29.5-191.fc11.i586.img /initrd-config.img | |
67 | ||
68 | initrd-20090722.img | |
69 | the image provided by the initrd rpm | |
70 | one old backup version is kept like with the kernel | |
71 | ||
72 | initrd-kernel-2.6.29.5-191.fc11.i586.img | |
73 | the image provided by the kernel rpm | |
74 | ||
75 | initrd-config.img | |
76 | optional image with local configuration files | |
77 | ||
78 | - dracut: add --kmoddir directory, where to look for kernel modules | |
79 | ||
80 | -k, --kmoddir [DIR] | |
81 | specify the directory, where to look for kernel modules | |
82 | ||
83 | ||
84 | ||
85 | dracut-0.5 | |
86 | ========== | |
87 | - more generic (all plymouth modules, all keyboards, all console fonts) | |
88 | - more kernel command line parameters (see also man dracut(8)) | |
89 | - a helper tool, which generates the kernel command line (dracut-gencmdline) | |
90 | - bridged network boot | |
91 | - a lot of new command line parameter | |
92 | ||
93 | dracut-0.4 | |
94 | ========== | |
95 | - bugfixes | |
96 | - firmware loading support | |
97 | - new internal queue (initqueue) | |
98 | initqueue now loops until /dev/root exists or root is mounted | |
99 | ||
100 | init now has the following points to inject scripts: | |
101 | ||
102 | /cmdline/*.sh | |
103 | scripts for command line parsing | |
104 | ||
105 | /pre-udev/*.sh | |
106 | scripts to run before udev is started | |
107 | ||
108 | /pre-trigger/*.sh | |
109 | scripts to run before the main udev trigger is pulled | |
110 | ||
111 | /initqueue/*.sh | |
112 | runs in parallel to the udev trigger | |
113 | Udev events can add scripts here with /sbin/initqueue. | |
114 | If /sbin/initqueue is called with the "--onetime" option, the script | |
115 | will be removed after it was run. | |
116 | If /initqueue/work is created and udev >= 143 then this loop can | |
117 | process the jobs in parallel to the udevtrigger. | |
118 | If the udev queue is empty and no root device is found or no root | |
119 | filesystem was mounted, the user will be dropped to a shell after | |
120 | a timeout. | |
121 | Scripts can remove themselves from the initqueue by "rm $job". | |
122 | ||
123 | /pre-mount/*.sh | |
124 | scripts to run before the root filesystem is mounted | |
125 | NFS is an exception, because it has no device node to be created | |
126 | and mounts in the udev events | |
127 | ||
128 | /mount/*.sh | |
129 | scripts to mount the root filesystem | |
130 | NFS is an exception, because it has no device node to be created | |
131 | and mounts in the udev events | |
132 | If the udev queue is empty and no root device is found or no root | |
133 | filesystem was mounted, the user will be dropped to a shell after | |
134 | a timeout. | |
135 | ||
136 | /pre-pivot/*.sh | |
137 | scripts to run before the real init is executed and the initramfs | |
138 | disappears | |
139 | All processes started before should be killed here. | |
140 | ||
141 | The behaviour of the dmraid module demonstrates how to use the new | |
142 | mechanism. If it detects a device which is part of a raidmember from a | |
143 | udev rule, it installs a job to scan for dmraid devices, if the udev | |
144 | queue is empty. After a scan, it removes itsself from the queue. | |
145 | ||
146 | ||
147 | ||
148 | dracut-0.3 | |
149 | ========== | |
150 | ||
151 | - first public version | |
152 |