dracut: allow hostonly & network everywhere, README

This commit is contained in:
Aminda Suomalainen 2024-06-01 09:51:20 +03:00
parent 92a8e99cd5
commit a53fea1333
Signed by: Mikaela
SSH Key Fingerprint: SHA256:CXLULpqNBdUKB6E6fLA1b/4SzG0HvKD19PbIePU175Q
3 changed files with 47 additions and 2 deletions

View File

@ -1,6 +1,21 @@
My dracut configuratino files mainly for generating unified kerneil images My dracut configuration files mainly for generating unified kerneil images
(uki). (uki).
<!-- editorconfig-checker-disable -->
<!-- prettier-ignore-start -->
<!-- START doctoc generated TOC please keep comment here to allow auto update -->
<!-- DON'T EDIT THIS SECTION, INSTEAD RE-RUN doctoc TO UPDATE -->
- [WARNING!](#warning)
- [network](#network)
- [hostonly](#hostonly)
<!-- END doctoc generated TOC please keep comment here to allow auto update -->
<!-- prettier-ignore-end -->
<!-- editorconfig-checker-enable -->
# WARNING! # WARNING!
Sedric has a 96M EFI partition courtesy of Windows and thus it has a lot of Sedric has a 96M EFI partition courtesy of Windows and thus it has a lot of
@ -8,3 +23,33 @@ 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 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 disabling recovery seems dangerous if I can save space by omitting somnething
else. 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…
<code style="color: red">
Error registering initrd: Already started
Error starting kernel image: Already started
</code>
…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?

View File

@ -1 +1 @@
omit_dracutmodules+=" plymouth kernel-modules-extra network-manager network-legacy connman systemd-networkd i18n network net-lib kernel-network-modules qemu qemu-net kernel-modules-asahi nfs asahi-firmware " omit_dracutmodules+=" plymouth kernel-modules-extra network-manager network-legacy connman systemd-networkd i18n net-lib kernel-network-modules qemu qemu-net kernel-modules-asahi nfs asahi-firmware "