# $MirSecuCron$
# $MirOS: src/etc/etc.i386/ttys,v 1.10 2009/07/18 14:09:09 tg Exp $
# $OpenBSD: ttys,v 1.17 2002/06/09 06:15:14 todd Exp $
#
# Please note that the word “secure” on the line below starting with
# “console” will leave your system open for attackers in single-user
# mode.  (If they boot a ramdisk kernel, they'll have access anyway,
# but hey!) Similarly, if removing it you should set a root password
# first in order to enter single user mode at all…
#
# name	getty				type	status		comments
#
# main console device – the speed is automatically set from /etc/rc
console	"/usr/libexec/getty acs.000000"	vt220	on  secure
# wsdisplay console – enable if main console is on a serial line
ttyC0	"/usr/libexec/getty Pc"		wsvt25	off secure
ttyC1	"/usr/libexec/getty Pc"		wsvt25	on  secure
ttyC2	"/usr/libexec/getty Pc"		wsvt25	on  secure
ttyC3	"/usr/libexec/getty Pc"		wsvt25	on  secure
ttyC4	"/usr/libexec/getty Pc"		wsvt25	off secure
ttyC5	"/usr/libexec/getty Pc"		wsvt25	on  secure
ttyC6	"/usr/libexec/getty Pc"		wsvt25	off secure
ttyC7	"/usr/libexec/getty Pc"		wsvt25	off secure
ttyC8	"/usr/libexec/getty Pc"		wsvt25	off secure
ttyC9	"/usr/libexec/getty Pc"		wsvt25	off secure
ttyCa	"/usr/libexec/getty Pc"		wsvt25	off secure
ttyCb	"/usr/libexec/getty Pc"		wsvt25	off secure
tty00	"/usr/libexec/getty std.9600"	unknown	off
tty01	"/usr/libexec/getty std.9600"	unknown	off
tty02	"/usr/libexec/getty std.9600"	unknown	off
tty03	"/usr/libexec/getty std.9600"	unknown	off
tty04	"/usr/libexec/getty std.9600"	unknown	off
tty05	"/usr/libexec/getty std.9600"	unknown	off
tty06	"/usr/libexec/getty std.9600"	unknown	off
tty07	"/usr/libexec/getty std.9600"	unknown	off