- We could consider to auto logout (exit) after rads decided to start a graphical login manager.* rads forces to keep tty0 open
- Instead of using autologin and the /etc/profile.d mechanism to start rads we could try to run rads as a tty1 login program. When rads then started a graphical login manager, it could continue in tty1 with a usual login prompt.* rads tty0 still running after it started a graphical login manager
- A good approach to solve this could be to run rads before getty using * rads is broken on #jessie that uses #systemd.
Could work similar as https://github.com/Whonix/whonix-initializer/blob/master/lib/systemd/system/whonix-initializer.service
Currently tty1 is set to autologin with user "user", so rads can decide to whether start a graphical login manager or not. When the user types exit in that virtual terminal, /etc/inittab will cause auto relogin by default.
We can autologin on boot and if the user exits that virtual terminal, we can just show the usual login prompt by using a small script configured in /etc/inittab.
## This file is part of Whonix.
## Copyright (C) 2012 - 2014 Patrick Schleizer <email@example.com>
## See the file COPYING for copying conditions.Solution:
#set -xA good approach to solve this could be to run #rads before getty using #systemd.
true "$0: whoami: $(whoami)"Could work similar as:
if [ -f "$lock_file" ];Alternative, then
true "$0: $lock_file exists."
true "$0: running: exec /sbin/getty 38400 tty1"non-preferable fallback solutions:
#sleep 10 &See old github tickets. Migrated from:
#wait $!- https://github.com/Whonix/Whonix/issues/291
exec /sbin/getty 38400 tty1
true "$0: $lock_file does not exist."
true "$0: running: exec /sbin/getty --autologin user 38400 tty1"
#sleep 10 &
exec /sbin/getty --autologin user 38400 tty1