veilor-os/overlay/usr/local/bin
veilor-org 20929f71c1 v0.5.13: omit plymouth from dracut + regen initramfs
v0.5.12 added /dev/null symlinks for plymouth services on real root.
Boot test confirmed plymouth STILL starts: it lives in initramfs
(dracut module 90plymouth) which has its own bundled service files,
unaffected by /etc/systemd/system/ masks on the installed btrfs.

Two-layer fix:
1. /etc/dracut.conf.d/99-veilor-no-plymouth.conf:
   omit_dracutmodules+=" plymouth "
   Then `dracut -f --kver $kver` to regenerate initramfs sans plymouth.
2. Keep /dev/null symlinks for post-pivot real-root masking.

Result: LUKS prompt rendered as text by systemd-tty-ask-password-agent
on tty1 — sendkey-friendly, hardware-realistic.
2026-05-03 10:10:46 +01:00
..
veilor-doctor v0.6: pre-stage veilor-update + veilor-doctor CLI tools (#11) 2026-05-02 04:39:33 +01:00
veilor-firstboot v0.5.2: move veilor-installer + veilor-firstboot to /usr/local/bin 2026-05-02 05:33:22 +01:00
veilor-installer v0.5.13: omit plymouth from dracut + regen initramfs 2026-05-03 10:10:46 +01:00
veilor-power veilor-os v0.1 scaffold — kickstart + hardening + 3-mode power + DuckSans-ready KDE black theme 2026-04-30 03:43:33 +01:00
veilor-update v0.6: pre-stage veilor-update + veilor-doctor CLI tools (#11) 2026-05-02 04:39:33 +01:00