Aminda Suomalainen
5103f93a22
In the end I was unable to get the chrooted system bootable and I gave up deciding to reinstall, but apparently these changes were left here and I either need to commit them or stash and drop, and I generally think there may be value found in such of things later, so commit it is |
||
|---|---|---|
| .. | ||
| 10-asahi.conf | ||
| 99-cmdline.conf.lumina | ||
| 99-cmdline.conf.sedric | ||
| 99-essential.conf | ||
| 99-hostonly.conf | ||
| 99-uefi.conf | ||
| README.md | ||
| compress.conf.sedric | ||
| no_rescue.conf.sedric | ||
| omit_modules.conf | ||
| omit_modules.conf.sedric | ||
| yes_rescue.conf | ||
README.md
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.
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?