When building a custom ISO using archiso, pacman post_install / post_upgrade hooks are not reliably executed (or are intentionally skipped), which is expected behavior because archiso builds a non-running filesystem and not a live system.
However, in the official CachyOS live ISO, several services (e.g. wireplumber) appears enabled at boot time, even though:
pacman hooks are not allowed / not effective in archiso
there are no pre-created symlinks under
archiso/airootfs/etc/systemd/system/ or
archiso/airootfs/etc/systemd/user/ in the repository
This creates confusion for users building custom ISOs, as it looks like pacman hooks were applied, even though they were not.
Would you mind providing details on how such services were enabled/links created for some services in Live ISO created via archiso?
When building a custom ISO using archiso, pacman
post_install/post_upgradehooks are not reliably executed (or are intentionally skipped), which is expected behavior because archiso builds a non-running filesystem and not a live system.However, in the official CachyOS live ISO, several services (e.g. wireplumber) appears enabled at boot time, even though:
pacman hooks are not allowed / not effective in archiso
there are no pre-created symlinks under
archiso/airootfs/etc/systemd/system/orarchiso/airootfs/etc/systemd/user/in the repositoryThis creates confusion for users building custom ISOs, as it looks like pacman hooks were applied, even though they were not.
Would you mind providing details on how such services were enabled/links created for some services in Live ISO created via archiso?