039df638d6
With this switch processes (such as xconsole) can open /dev/console without breaking login on the text or serial console. This can be trivially triggered by enabling xdm in rc.conf and hitting Ctrl+Alt+F1 or equivalent once booted. The changes: - Add entry for /dev/console or /dev/constty if missing - If a port's had /dev/console 'on' switch it off and enable /dev/constty - If a port did not have /dev/console 'on', leave /dev/constty off Some ports had /dev/console off and /dev/ttyE0 enabled, presumably to avoid just this issue. It may make sense to adjust these also (but not in this pass) As discussed on current-users
30 lines
931 B
Plaintext
30 lines
931 B
Plaintext
# $NetBSD: ttys,v 1.10 2019/09/25 23:09:22 abs Exp $
|
|
# from: @(#)ttys 5.1 (Berkeley) 4/17/89
|
|
#
|
|
# name getty type status comments
|
|
#
|
|
# If the console is marked insecure, single-user requires
|
|
# the root password.
|
|
#
|
|
# /dev/console is always valid, regardless of the board type.
|
|
#
|
|
console "/usr/libexec/getty Pc" dumb off secure
|
|
constty "/usr/libexec/getty Pc" dumb on secure
|
|
|
|
#
|
|
# Hardwired lines are marked off, by default, so getty(8)
|
|
# is quiet when they don't exist.
|
|
#
|
|
# The first three would be used on MVME-147, MVME-162 and MVME-172
|
|
#
|
|
ttyZ1 "/usr/libexec/getty std.9600" unknown off secure
|
|
ttyZ2 "/usr/libexec/getty std.9600" unknown off secure
|
|
ttyZ3 "/usr/libexec/getty std.9600" unknown off secure
|
|
|
|
#
|
|
# These three would be used on MVME-167 and MVME-177
|
|
#
|
|
ttyC1 "/usr/libexec/getty std.9600" unknown off secure
|
|
ttyC2 "/usr/libexec/getty std.9600" unknown off secure
|
|
ttyC3 "/usr/libexec/getty std.9600" unknown off secure
|