You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 
 
Harald Hoyer c7d8334d26 ci: don't use `rpm` to determine the kernel version 4 years ago
.github ci: build container images and push to ghcr.io 4 years ago
docs chore(tree): move html files to the dosc directory 4 years ago
dracut.conf.d
install.d
man fix: deprecate gummiboot 4 years ago
modules.d feat(systemd-journald): introducing the systemd-journald module 4 years ago
pkgbuild feat(systemd-journald): introducing the systemd-journald module 4 years ago
shell-completion/bash
src fix(install): handle $LIB in ldd output parsing 4 years ago
test ci: don't use `rpm` to determine the kernel version 4 years ago
tools
.astylerc
.dir-locals.el
.editorconfig
.gitignore
.kateconfig
.kateproject
.mailmap
.packit.yml
.shellcheckrc
.vimrc
AUTHORS
COPYING
Makefile chore(tree): move html files to the dosc directory 4 years ago
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 fix: deprecate gummiboot 4 years ago
lsinitrd.sh

README.md

dracut

dracut is an event driven initramfs infrastructure.

Contributor Covenant Fedora-32 Fedora-33 Fedora-latest

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