-
Notifications
You must be signed in to change notification settings - Fork 46
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
arch: add script to generate UKIs #252
Conversation
Thank you! I am sure a lot of people find UKI functionality useful. Could you please add a section to the documentation (https://github.com/anatol/booster/blob/master/docs/manpage.md) about what is UKI and how to use booster with it? |
- The option takes space seperated values. Just specify once for microcodes and initramf image
Looks great, thank you! |
1f9b889
to
7a4175d
Compare
7a4175d
to
9156445
Compare
No problem. Also, one thing to consider is that the result is written to Some users have a separate partition (e.g. |
Sounds good. Let me know once you are done developing the PR and I move with merging it. |
- Systemd ukify is strict when parsing its values passed to --initrd, and will fail if there's a trailing white space
@anatol let me know if you prefer squashing my commits. |
- Make specifying the path to save the UKI for users a requirement when generating UKIs. This gives more flexibility for users whose systems are not configured to execute EFI binaries at /boot
617ec34
to
bcfb694
Compare
I will squash the commits before merging |
- Remove default path
Or you can simply use the booster-ukify or booster-um. |
Currently, booster does not support generating Universal Kernel Images (UKIs) natively and this PR allows creating UKIs via ukify on Arch Linux.
To generate UKIs, we can simply delegate the functionality to external tools such as ukify. The resulting binaries are currently stored in
/boot/Linux/EFI
and manual intervention would be required from the user to configure the appropriate boot loader configution files to load the binary by default. Otherwise, binaries would probably need to be selected at boot time. For instance, in systemd-boot,loader.conf
should be modified.