Package: getty-run Version: 2.3.0-1 Severity: normal X-Debbugs-Cc: [email protected], [email protected] User: [email protected] Usertags: hurd
Dear Lorenzo, Many thanks for your work on integrating runit to work as the init system on the hurd. Things are mostly working, but pointing out here 2 things related to gettys. fuser, which is used in the getty runscripts, is not compiled for the hurd. This does not seem to be a significant problem since the gettys still start, but I wonder if some conditional statement should be added to the script. More importantly is that for the hurd /dev/console should also have a getty associated with it since it works like a backup console. It is not that uncommon that the hurd console is not running on the different /dev/tty?, and in /etc/default/hurd-console one can choose not to start the hurd console. In such cases one should still be able to access the gnumach console on /dev/console so we should have a getty starting there. From /etc/ttys the getty on /dev/console should work at 9600 baud (I don't know if that is all it can do). With thanks, João -- System Information: Debian Release: forky/sid APT prefers unreleased APT policy: (500, 'unreleased'), (500, 'unstable') Architecture: hurd-i386 (i686-AT386) Kernel: GNU-Mach 1.8+git20260129-up-486/Hurd-0.9 Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en Shell: /bin/sh linked to /usr/bin/dash Init: runit (via /run/runit.stopit) Versions of packages getty-run depends on: ii hurd [login] 1:0.9.git20251029-4 ii login 1:4.16.0-2+really2.41.3-2 ii runit-helper 2.16.4 Versions of packages getty-run recommends: ii psmisc 23.5-1 Versions of packages getty-run suggests: pn fgetty <none> -- no debconf information
