ZacharyZhang-NY/omarchycn
3
4
Fork 0
Code Issues Pull Requests 2 Actions Packages Projects Releases 5 Wiki Activity

Add chrootable_systemctl_enable_only for services we shouldn't start during install

Browse Source 
The previous centralization into enable-services.sh accidentally changed
semantics for three services: docker.socket, iwd.service, and
power-profiles-daemon.service used to be enabled with bare
'sudo systemctl enable' (no --now); chrootable_systemctl_enable promoted
them to 'enable --now' outside chroot.

For iwd this is the riskiest: it's typically what's keeping the installer
online, so starting it mid-install is at best a no-op and at worst can
disrupt the active network connection. For docker.socket and
power-profiles-daemon the change is cosmetic (the socket is already
inactive, the daemon does no harm to start) but the original intent was
deferral to first boot.

New helper in install/helpers/chroot.sh:

  chrootable_systemctl_enable_only <unit>  # plain enable, no --now

enable-services.sh uses it for the three services that were previously
bare-enabled. The other five (bluetooth, cups, cups-browsed,
avahi-daemon, linux-modules-cleanup) keep the --now behavior they had
under chrootable_systemctl_enable.
This commit is contained in:
Ryan Hughes
2026-06-04 18:34:35 -04:00
parent 0e91948b8f
commit 0ebbe34760
2 changed files with 27 additions and 13 deletions
Download Patch File Download Diff File Expand all files Collapse all files
install/config/enable-services.sh
+17 -12
View File
@@ -1,12 +1,17 @@
# Central place for unconditional, safe-to-start-now service enables. # Central place for unconditional service enables. Services that should NOT
# Services that should NOT be started during install (sddm, ufw) live in # be started during install (sddm, ufw) live in their own scripts. Hardware-
# their own scripts. Hardware-gated services (t2fanrd, intel_lpmd, # gated services (t2fanrd, intel_lpmd, thermald, omarchy-nvme-suspend-fix)
# thermald, omarchy-nvme-suspend-fix) also live with their detection. # also live with their detection.
chrootable_systemctl_enable bluetooth.service #
chrootable_systemctl_enable cups.service # Two variants:
chrootable_systemctl_enable cups-browsed.service # chrootable_systemctl_enable -> enable + start now (safe to start)
chrootable_systemctl_enable avahi-daemon.service # chrootable_systemctl_enable_only -> enable only (don't risk starting during
chrootable_systemctl_enable docker.socket # install)
chrootable_systemctl_enable iwd.service chrootable_systemctl_enable bluetooth.service
chrootable_systemctl_enable linux-modules-cleanup.service chrootable_systemctl_enable cups.service
chrootable_systemctl_enable power-profiles-daemon.service chrootable_systemctl_enable cups-browsed.service
chrootable_systemctl_enable avahi-daemon.service
chrootable_systemctl_enable linux-modules-cleanup.service
chrootable_systemctl_enable_only docker.socket
chrootable_systemctl_enable_only iwd.service
chrootable_systemctl_enable_only power-profiles-daemon.service
install/helpers/chroot.sh
+10 -1
View File
@@ -7,5 +7,14 @@ chrootable_systemctl_enable() {
fi fi
} }
# Export the function so it's available in subshells # Like chrootable_systemctl_enable but never passes --now, so the service is
# only enabled for the next boot. Use for services that are either already
# running (and re-starting would interrupt the install — iwd) or that shouldn't
# auto-start during install (docker, power-profiles-daemon).
chrootable_systemctl_enable_only() {
sudo systemctl enable $1
}
# Export the functions so they're available in subshells
export -f chrootable_systemctl_enable export -f chrootable_systemctl_enable
export -f chrootable_systemctl_enable_only