Let systemd handle terminal setup, fix possible race with NM

Add a systemd-generator script that puts anaconda on the correct console
tty, then puts shells on tty2 and the first virtualization console
(unless we're using it for anaconda).

Adding "TTYPath" to the systemd services means systemd takes care of
setting up all the terminal stuff - picking the right TERM value,
setting the keyboard mode to K_UNICODE, and all that esoteric weirdness.

Also, move anaconda's dependencies into anaconda.target, and make
anaconda start *after* anaconda.target, just so we can be sure that e.g.
NetworkManager is active before anaconda starts.

(as a bonus, it also shuts off plymouth correctly, just in case we ever
want to have a anaconda-specific bootsplash)

1 files changed, 13 insertions, 0 deletions

diff --git a/data/systemd/anaconda@.service b/data/systemd/anaconda@.service
new file mode 100644
index 000000000..903df7a85
--- /dev/null
+++ b/data/systemd/anaconda@.service
@@ -0,0 +1,13 @@
+[Unit]
+Description=Anaconda
+After=anaconda.target
+
+[Service]
+Environment=HOME=/root MALLOC_CHECK_=2 MALLOC_PERTURB_=204 PATH=/usr/bin:/bin:/sbin:/usr/sbin:/mnt/sysimage/bin:/mnt/sysimage/usr/bin:/mnt/sysimage/usr/sbin:/mnt/sysimage/sbin PYTHONPATH=/tmp/updates
+Type=oneshot
+WorkingDirectory=/root
+ExecStart=/usr/sbin/anaconda
+StandardInput=tty-force
+TTYPath=/dev/%I
+TTYReset=yes
+TimeoutSec=0