fix(dracut.sh): unfreeze /boot on exit

If SIGWHATEVER will be processed after fsfreeze -f, but before fsfreeze
-u we will end up with /boot/ never unfrozen, let's try to minimize risk of this.
1 file changed
tree: 1d722ed7161dc5462b9be05e18d5a7af38dea3af
  1. .github/
  2. docs/
  3. dracut.conf.d/
  4. examples/
  5. install/
  6. modules.d/
  7. skipcpio/
  8. test/
  9. .dir-locals.el
  10. .editorconfig
  11. .gitignore
  12. .kateconfig
  13. .kateproject
  14. .mailmap
  15. .vimrc
  16. 50-dracut.install
  17. 51-dracut-rescue.install
  18. AUTHORS
  19. configure
  20. COPYING
  21. dracut-bash-completion.sh
  22. dracut-catimages.8.asc
  23. dracut-catimages.sh
  24. dracut-functions.sh
  25. dracut-init.sh
  26. dracut-initramfs-restore.sh
  27. dracut-logger.sh
  28. dracut.8.asc
  29. dracut.asc
  30. dracut.bootup.7.asc
  31. dracut.cmdline.7.asc
  32. dracut.conf
  33. dracut.conf.5.asc
  34. dracut.css
  35. dracut.modules.7.asc
  36. dracut.png
  37. dracut.sh
  38. dracut.spec
  39. dracut.svg
  40. dracut.usage.asc
  41. fedora-test-github.sh
  42. fedora-test.sh
  43. git2spec.pl
  44. HACKING.md
  45. logtee.c
  46. lsinitrd-bash-completion.sh
  47. lsinitrd.1.asc
  48. lsinitrd.sh
  49. Makefile
  50. mkinitrd-dracut.sh
  51. mkinitrd-suse.8.asc
  52. mkinitrd-suse.sh
  53. mkinitrd.8.asc
  54. NEWS.md
  55. PKGBUILD
  56. profile.py
  57. README.cross
  58. README.generic
  59. README.kernel
  60. README.md
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