veilor-org/veilor-os
1
0
Fork 0
Code Issues Pull requests Projects Releases 1 Packages Wiki Activity Actions

v0.5.19: dracut --regenerate-all (fix chroot glob expansion bug)

Browse source 
v0.5.18 added crypt + systemd-cryptsetup to dracut.conf.d/99-veilor-
no-plymouth.conf. Boot test still failed: dracut-initqueue stuck
waiting on dev-disk-by-uuid → systemd-cryptsetup never fired.

Diagnosis: %post chroot used bash glob `for kver in /lib/modules/*/`.
In chroot, shell may be dash + nullglob unset → unmatched glob
expands literally to "/lib/modules/*/" → dracut --kver "/lib/modules/*/"
fails silently with `|| true`. Initramfs never regenerated → still
contains the v0.5.14 omit_dracutmodules-only config without crypt.

Fix: dracut --force --regenerate-all (walks /lib/modules internally,
no shell glob needed). One call regens all kernel initramfses with
the new dracut.conf.d in scope.
This commit is contained in:
veilor-org 2026-05-03 18:39:13 +01:00
parent 04595f77e9
commit f610598196
1 changed files with 5 additions and 5 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

10
overlay/usr/local/bin/veilor-installer
View file

@ -562,11 +562,11 @@ omit_dracutmodules+=" plymouth "
add_dracutmodules+=" crypt systemd-cryptsetup "
install_items+=" /usr/bin/systemd-tty-ask-password-agent "
EOF
# Regenerate initramfs for the installed kernel(s).
for kver in /lib/modules/*/; do
kver=$(basename "$kver")
dracut --force --kver "$kver" 2>/dev/null || true
done
# Regenerate initramfs for ALL installed kernels with our dracut config.
# `--regenerate-all` walks /lib/modules itself; safer than bash glob in
# chroot where shell may be dash + nullglob unset → glob expands literally
# → dracut --kver "/lib/modules/*/" fails silently.
dracut --force --regenerate-all 2>&1 | tail -5 || true
# Layer 2: real-root masks
mkdir -p /etc/systemd/system