c17c5b7604
In the current state, services that depend on network need to use dracut hooks, since nothing with pull in the network targets into the transaction. In the future, it would be nice to provide developers on systemd-only systems the possibility to not use dracut hooks at all, but simply put normal systemd services into the initrd. Also, some modules even right now depend on systemd ordering, like cryptsetup, so let's make sure, that the ordering inside systemd work properly as well. |
||
|---|---|---|
| .github | ||
| docs | ||
| dracut.conf.d | ||
| examples/yocto | ||
| install | ||
| modules.d | ||
| skipcpio | ||
| test | ||
| .dir-locals.el | ||
| .editorconfig | ||
| .gitignore | ||
| .kateconfig | ||
| .kateproject | ||
| .mailmap | ||
| .vimrc | ||
| 50-dracut.install | ||
| 51-dracut-rescue.install | ||
| AUTHORS | ||
| COPYING | ||
| HACKING.md | ||
| Makefile | ||
| NEWS.md | ||
| PKGBUILD | ||
| README.cross | ||
| README.generic | ||
| README.kernel | ||
| README.md | ||
| configure | ||
| dracut-bash-completion.sh | ||
| dracut-catimages.8.asc | ||
| dracut-catimages.sh | ||
| dracut-functions.sh | ||
| dracut-init.sh | ||
| dracut-initramfs-restore.sh | ||
| dracut-logger.sh | ||
| dracut.8.asc | ||
| dracut.asc | ||
| dracut.bootup.7.asc | ||
| dracut.cmdline.7.asc | ||
| dracut.conf | ||
| dracut.conf.5.asc | ||
| dracut.css | ||
| dracut.modules.7.asc | ||
| dracut.png | ||
| dracut.sh | ||
| dracut.spec | ||
| dracut.svg | ||
| dracut.usage.asc | ||
| fedora-test-github.sh | ||
| fedora-test.sh | ||
| git2spec.pl | ||
| logtee.c | ||
| lsinitrd-bash-completion.sh | ||
| lsinitrd.1.asc | ||
| lsinitrd.sh | ||
| mkinitrd-dracut.sh | ||
| mkinitrd-suse.8.asc | ||
| mkinitrd-suse.sh | ||
| mkinitrd.8.asc | ||
| profile.py | ||
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