write our own mkinitcpio.conf

gives us more control over its content than using the default and only
adding hooks
This commit is contained in:
Harald Sitter
2024-03-14 10:16:57 +01:00
parent 14558c0c7f
commit 90998bb889

View File

@@ -202,12 +202,18 @@ plymouth-set-default-theme bgrt
# Could move to config instead of manual command passing
# NOTE: plymouth MUST be after systemd as per the wiki!
cat <<- EOF > /etc/mkinitcpio.conf
MODULES=()
BINARIES=()
FILES=()
HOOKS=(base systemd autodetect modconf kms keyboard block filesystems fsck systemd-extension plymouth)
EOF
cd /tmp
echo "native ro root=PARTLABEL=KDEOSLive systemd.volatile=overlay systemd.firstboot=false systemd.hostname=kdeos kdeos.live=1 \
rd.systemd.debug_shell=on systemd.debug_shell=on SYSTEMD_SULOGIN_FORCE=1 \
console=ttyS0 console=tty0 \
systemd.log_level=debug systemd.log_target=kmsg log_buf_len=1M printk.devkmsg=on" > cmdline
mkinitcpio --addhooks "systemd,systemd-extension,plymouth" --generate initrd --kernel "$kernel_version"
mkinitcpio --generate initrd --kernel "$kernel_version"
ukify build \
--linux /boot/vmlinuz-linux \
--initrd initrd \
@@ -217,7 +223,7 @@ echo "native ro root=PARTLABEL=KDEOS rootflags=subvol=@kdeos_$IMAGE_VERSION \
rd.systemd.debug_shell=on systemd.debug_shell=on SYSTEMD_SULOGIN_FORCE=1 \
console=ttyS0 console=tty0 \
systemd.log_level=debug systemd.log_target=kmsg log_buf_len=1M printk.devkmsg=on" > cmdline
mkinitcpio --addhooks "systemd,systemd-extension,plymouth" --generate initrd --kernel "$kernel_version"
mkinitcpio --generate initrd --kernel "$kernel_version"
ukify build \
--linux /boot/vmlinuz-linux \
--initrd initrd \