shell-things/etc/dracut.conf.d
2024-06-01 09:51:20 +03:00
..
10-asahi.conf etc/dracut.conf.d/10-asahi.conf: workaround F40 kernel update failures 2023-12-29 13:26:25 +02:00
99-cmdline.conf.lumina etc/dracut.conf.d: add UKI generation & Lumina cmdline 2024-05-03 16:24:03 +03:00
99-cmdline.conf.sedric etc/dracut.conf.d: add sedric configs 2024-05-03 21:19:32 +03:00
99-uefi.conf etc/dracut.conf.d: add UKI generation & Lumina cmdline 2024-05-03 16:24:03 +03:00
compress.conf.sedric etc/dracut.conf.d: add sedric configs 2024-05-03 21:19:32 +03:00
hostonly.conf dracut: allow hostonly & network everywhere, README 2024-06-01 09:51:20 +03:00
no_rescue.conf.sedric dracut.conf.d: fix name recovery to rescue, add yes_rescue counterpart 2024-05-11 10:41:41 +03:00
omit_modules.conf dracut: allow hostonly & network everywhere, README 2024-06-01 09:51:20 +03:00
omit_modules.conf.sedric etc/dracut.conf.d: omit some more modules as there is no space 2024-05-22 07:55:58 +03:00
README.md dracut: allow hostonly & network everywhere, README 2024-06-01 09:51:20 +03:00
yes_rescue.conf dracut.conf.d: fix name recovery to rescue, add yes_rescue counterpart 2024-05-11 10:41:41 +03:00

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

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.

network

dracut[E]: Module 'cifs' depends on 'network', which can't be installed
dracut[E]: Module 'iscsi' depends on 'network', which can't be installed
dracut[E]: Module 'nvmf' depends on 'network', which can't be installed

I think nvmf might be relevant on ThinkPads, so it gets out of omit_modules

At least it resolves these two…

Error registering initrd: Already started Error starting kernel image: Already started

…which cause fallback to the next UEFI boot entry (why is that grub still around?)

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?