| 1 |
# Keep the greeter off the installer medium. |
| 2 |
# |
| 3 |
# greetd and `alloy install` both want VT1, and on the live medium there is |
| 4 |
# no account to log into yet, so a greeter there has nothing to offer and |
| 5 |
# only races the installer for the terminal. |
| 6 |
# |
| 7 |
# This is the counterpart to alloy-installer.service's own |
| 8 |
# ConditionKernelCommandLine, and the pair is the whole mechanism: one flag, |
| 9 |
# set by the ISO's GRUB entries and nowhere else, decides which of the two |
| 10 |
# owns VT1. Each unit answers for itself rather than one reaching across to |
| 11 |
# stop the other. |
| 12 |
# |
| 13 |
# The stopping-the-other-one version was tried and does not work. As |
| 14 |
# `Conflicts=`, it fires when the start job is ENQUEUED, before the |
| 15 |
# installer's condition is checked, so it killed the greeter on installed |
| 16 |
# machines where the installer never ran and left them with a black VT1 |
| 17 |
# (7b977b2). Moved into the installer's ExecStartPre, it stopped racing the |
| 18 |
# wrong way instead: greetd is Wanted by graphical.target, so stopping it |
| 19 |
# once does not keep it from being started again, and the live medium came |
| 20 |
# up at a login prompt instead of the installer. Both were found by booting |
| 21 |
# the thing rather than by reading it. |
| 22 |
[Unit] |
| 23 |
ConditionKernelCommandLine=!alloy.installer |
| 24 |
|