Skip to main content

max / alloy_tui

1.2 KB · 28 lines History Blame Raw
1 # Alloy system-service presets
2 #
3 # systemd reads this at boot / on first user login to decide which
4 # units are enabled or disabled by default. Rationale for each entry:
5 #
6 # - greetd: boot lands on the tuigreet TUI on VT1.
7 # - initial-setup: first-boot account creation. greetd carries
8 # Alias=display-manager.service and initial-setup
9 # declares Before=display-manager.service, so it runs
10 # to completion before tuigreet takes the VT. It
11 # disables itself once setup succeeds. Without it an
12 # install has no loginable account at all.
13 # - tailscaled: opt-in only. Enrollment happens via `alloy tail`
14 # (see docs/CONTINUITY.md — Alloy does not phone home
15 # before the user says yes).
16 #
17 # The base image ships Firefox as an RPM; ungoogled-chromium and any
18 # other Flathub apps are user-installed on demand (see docs/STACK.md),
19 # so no first-boot Flatpak provisioning is needed.
20 #
21 # Format: `enable|disable <unit>`. First match wins; entries without
22 # a match fall through to /usr/lib/systemd/system-preset/ defaults.
23
24 enable greetd.service
25 enable initial-setup.service
26
27 disable tailscaled.service
28