History

Aminda Suomalainen 87ade6f0aa dracut/99-cmdline.conf.sedric: restore nouveau blacklisting although it's yet to be applied or tried on Sedric		2024-07-06 12:04:59 +03:00
..
10-asahi.conf	…
99-cmdline.conf.lumina	dracut: cleanup cmdlines	2024-06-21 10:03:34 +03:00
99-cmdline.conf.sedric	dracut/99-cmdline.conf.sedric: restore nouveau blacklisting	2024-07-06 12:04:59 +03:00
99-essential.conf	dracut: add 99-essential.conf for vfat	2024-06-21 08:44:51 +03:00
99-uefi.conf	…
README.md	run prettier (insertPragma, proseWrap, singleAttributePerLine	2024-06-19 08:27:28 +03:00
compress.conf.sedric	dracut.conf.$(HOSTNAME): add vim modelines	2024-06-21 10:06:35 +03:00
hostonly.conf	…
no_rescue.conf.sedric	dracut.conf.$(HOSTNAME): add vim modelines	2024-06-21 10:06:35 +03:00
omit_modules.conf	dracut: resolve the dependency issue of network module by omitting the three others as well	2024-06-02 17:00:13 +03:00
omit_modules.conf.sedric	dracut.conf.$(HOSTNAME): add vim modelines	2024-06-21 10:06:35 +03:00
yes_rescue.conf	…

README.md

My dracut configuration files mainly for generating unified kerneil images (uki).

WARNING!
- hostonly

WARNING!

Sedric has a 96M EFI partition courtesy of Windows and thus it has a lot of attempts for decreasing the kernel size. Since moving it to UKI, I am yet to go through what of it is actually useful and worth keeping around and at least disabling recovery seems dangerous if I can save space by omitting somnething else.

hostonly

Will make a UKI specific to the current hardware and is discouraged as it will obviously prevent booting on a different hardware and hardware changes may render the system unbootable. However I am more of a software person, so I imagine that is unlikely to happen for me.

If planning hardware changes, maybe disable this flag? Or maybe if you have infinite space for kernel, keep it off?