Search Criteria
Package Details: dracut-ukify 10-1
Package Actions
Git Clone URL: | https://aur.archlinux.org/dracut-ukify.git (read-only, click to copy) |
---|---|
Package Base: | dracut-ukify |
Description: | Integration layer for dracut and systemd's ukify tool for Arch Linux |
Upstream URL: | https://aur.archlinux.org/packages/dracut-ukify |
Licenses: | MIT |
Conflicts: | dracut-hook-uefi, dracut-uefi-hook |
Provides: | dracut-hook |
Submitter: | Prototik |
Maintainer: | Prototik |
Last Packager: | Prototik |
Votes: | 10 |
Popularity: | 0.38 |
First Submitted: | 2023-02-20 21:54 (UTC) |
Last Updated: | 2025-01-31 12:58 (UTC) |
Dependencies (3)
- dracut (dracut-gitAUR)
- systemd-ukify (systemd-chromiumos-ukifyAUR, systemd-ukify-fmlAUR, systemd-ukify-selinuxAUR, systemd-ukify-gitAUR)
- sbsigntools (sbsigntools-gitAUR) (optional) – secureboot support
Required by (1)
- nvidia-dracut-hook (requires dracut-hook)
Latest Comments
1 2 3 4 5 Next › Last »
Prototik commented on 2025-02-01 22:07 (UTC)
@android_aur that's dracut bug not honoring --quiet option: https://github.com/dracut-ng/dracut-ng/issues/1195
android_aur commented on 2025-02-01 18:58 (UTC) (edited on 2025-02-01 19:07 (UTC) by android_aur)
Since the latest dracut-ukify and/or dracut version (
dracut 106-1
&dracut-ukify 10-1
got installed at the same time today) the output is suddenly overly verbose:I prefered the old version without all the
Creating group 'XYZ' with GID '123'
information. Is there a way to get the old behaviour back?Prototik commented on 2025-01-31 12:59 (UTC)
@gabfv I've added ${esp} and ${boot} variables to the path expansion, and allowing absolute paths as well, so you can define now where to put your uki images, please give a try.
gabfv commented on 2024-12-22 15:43 (UTC) (edited on 2024-12-26 02:23 (UTC) by gabfv)
I'd like to add this feature to choose the XBOOTLDR instead of the ESP partition. I tried to make it as simple as possible so I added another variable (ukify_use_xbootldr) in the .conf and then overriding the ESP path with
bootctl --print-boot-path
if said variable is true. Here's the patch:edit: Fixed missing fi in the patch
phush0 commented on 2024-12-13 10:10 (UTC)
be aware that the new systemd boot do not support lz4
Prototik commented on 2024-12-11 12:33 (UTC)
@ddd my bad, fixed, thanks
ddd commented on 2024-12-11 10:54 (UTC)
Wrong hash of dracut-ukify.conf after the latest change.
jcruz commented on 2024-08-19 11:58 (UTC)
Thanks for the pointers. I will test it out in a VM later. This information should be documented better in the Arch Wiki. The UKI article just links to the Dracut article in the Dracut subsection. And the Dracut article tells you to use the flags/options for Dracut to use it, but then tells you to use this package to get the pacman hooks, but it is not stated that you should not use dracut UKI generation then. Since the systemd-ukify details are in the UKI article, you won't know if you only look at the Dracut article.
Prototik commented on 2024-08-19 05:21 (UTC)
@dngray @jcruz you both got wrong assignment by using dracut's built-in uefi(ukify) mode. You don't need to pass any uefi-related options to the dracut, but generate plain old initrd image, which then will be included in the resulted uki image by systemd-ukify. To avoid this issue further I'll add
--no-uefi
flag to the internal dracut image generation process.TL;DR: remove uefi="yes" option from dracut config, and don't ever use
dracut --regenerate-all
with dracut-ukify.1 2 3 4 5 Next › Last »