371b338a5f
The dependency of multipathd on "udev settle" has recently been removed in
c9689b6 ("multipathd: Remove dependency on systemd-udev-settle.service").
But this dependency has never been necessary in the initramfs environment. It
was only required after switching root, because multipathd would potentially
tear down valid multipath maps after switching from initrd to root FS. This can
happen because dm devices "survive" the root FS switch in the udev data
base (they have the "db_persist" flag set), whereas their component devices
(SCSI etc) do not. But this can only happen after initrd-udevadm-cleanup-db.service
has been run, which happens after initrd processing.
The only dependency that's really needed is that on
systemd-udevd-kernel.socket, because multipathd depends on uevents for
devices being delivered via systemd-udevd.
|
||
|---|---|---|
| .github | ||
| docs | ||
| dracut.conf.d | ||
| install.d | ||
| man | ||
| modules.d | ||
| pkgbuild | ||
| shell-completion/bash | ||
| src | ||
| test | ||
| tools | ||
| .astylerc | ||
| .dir-locals.el | ||
| .editorconfig | ||
| .gitignore | ||
| .kateconfig | ||
| .kateproject | ||
| .mailmap | ||
| .packit.yml | ||
| .shellcheckrc | ||
| .vimrc | ||
| AUTHORS | ||
| COPYING | ||
| Makefile | ||
| NEWS.md | ||
| README.md | ||
| configure | ||
| dracut-catimages.sh | ||
| dracut-functions.sh | ||
| dracut-init.sh | ||
| dracut-initramfs-restore.sh | ||
| dracut-logger.sh | ||
| dracut.conf | ||
| dracut.sh | ||
| lsinitrd.sh | ||
README.md
dracut
dracut is an event driven initramfs infrastructure.
dracut (the tool) is used to create an initramfs image by copying tools and files from an installed system and combining it with the dracut framework, usually found in /usr/lib/dracut/modules.d.
Unlike other implementations, dracut hard-codes as little as possible into the initramfs. The initramfs has (basically) one purpose in life -- getting the rootfs mounted so that we can transition to the real rootfs. This is all driven off of device availability. Therefore, instead of scripts hard-coded to do various things, we depend on udev to create device nodes for us and then when we have the rootfs's device node, we mount and carry on. This helps to keep the time required in the initramfs as little as possible so that things like a 5 second boot aren't made impossible as a result of the very existence of an initramfs.
Most of the initramfs generation functionality in dracut is provided by a bunch of generator modules that are sourced by the main dracut script to install specific functionality into the initramfs. They live in the modules.d subdirectory, and use functionality provided by dracut-functions to do their work.
Currently dracut lives on github.com and kernel.org.
The tarballs can be found here: http://www.kernel.org/pub/linux/utils/boot/dracut/ ftp://ftp.kernel.org/pub/linux/utils/boot/dracut/
Git: https://github.com/dracutdevs/dracut.git http://git.kernel.org/?p=boot/dracut/dracut.git
Project Documentation: http://www.kernel.org/pub/linux/utils/boot/dracut/dracut.html
Project Wiki: http://dracut.wiki.kernel.org
See the github issue tracker for things which still need to be done and HACKING.md for some instructions on how to get started. There is also a mailing list that is being used for the discussion -- initramfs@vger.kernel.org. It is a typical vger list, send mail to majordomo@vger.kernel.org with body of 'subscribe initramfs email@host.com'
Licensed under the GPLv2