Switch from grml-runtty to agetty grml-runtty used to fix most of the pre-systemd environment problems. It seems that it causes more troubles nowadays than it solved back then. First and foremost grml-runtty does not provide a (systemd) login session which prevents us from starting X reliably. Therefor replacing grml-runtty with agetty with autologin where a grml-shell is used so far. tty1 to tty4, where grml-runtty starts run-welcome (grml-quickconfig), two root- and a grml-GNU-screen session, should also be replaced with a proper systemd-unit. Relates to grml/grml#14 and grml/grml#20
Provide consistent header information for all /etc/systemd/ files that are deployed via grml-live
TTY6/VT6 should start a shell if bootoption startx is not given When the bootoption "startx" is given, the helper-script "/etc/init.d/startx" is created during the bootprocess (via grml-autoconfig). That means, that if the booptions "startx" is not given, the helper-script is not created and tty6/vt6 should not try to start X but should just start a grml-user-shell. Related to grml/grml#20
Make startx boot option work with systemd The desired behavior (with systemd and the boot option "startx") is to start the X window system automatically. This is achieved by getty@tty6.service which starts grml-x as user "grml" on vt6/tty6 and switches back to vt1/tty1 after exit. (This alone could be achieved with systemd-unit option Type=oneshot and Restart=no). But when switiching back to vt6/tty6 (again) we would like to start a zsh (for user "grml") and restart the zsh if exited. That means that grml-x should only be started on the very first run and the zsh on every other. We could not figure out how to change the systemd-unit option "Type" dynamically, so we kept it on "idle" which means that the "actual execution of the service binary is delayed until all active jobs are dispatched". That's why we need to switch to vt6/tty6 (via grml-autoconfig) iff the boot option "startx" is given. We also do not know yet how to dynamically change the behavior of the systemd-unit in a safe way. Rewriting the unit-file (override.conf) after grml-x exits (i.e. with ExecStopPost) doesn't seem to work reliably (especially when calling "systemctl daemon-reload" in it). That's why we use a state-file (/var/run/grml_startx.started) to start up grml-x on the first call and the zsh else. This also means that grml-x is started automatically when switching to vt6/tty6 manually (when no "startx" boot option was given) once and the zsh on the following calls. Closes grml/grml#1
Systemd support, providing backwards compatibility via FILE_RC class [Closes: issue1015] Support for file-rc is still available and can be enabled via FILE_RC class.