e90d6ef662
v0.5.11 used `systemctl mask plymouth-*.service` in generated kickstart %post chroot block. systemctl needs systemd running, which it isn't in anaconda chroot — calls failed silently (|| true). Boot test confirmed: post-reboot showed both: Started plymouth-start.service - Show Plymouth Boot Screen Started systemd-ask-password-plymouth.path - Forward Password Requests Fix: write /dev/null symlinks directly (`ln -sf /dev/null /etc/systemd/system/<unit>`). Achieves what mask does without needing systemd. Also adds the path-activated unit (systemd-ask-password-plymouth.path) which actually pulls plymouth in during dracut-initqueue. |
||
|---|---|---|
| .. | ||
| veilor-doctor | ||
| veilor-firstboot | ||
| veilor-installer | ||
| veilor-power | ||
| veilor-update | ||