On Sat, 10 Mar 2001, Tracy J. Di Marco White wrote:

> }ttyE0 is configured automatically if it's the console. When it's not,
> }you need to uncomment the line for it in /etc/wscons.conf (per the
> }comment there). It may not be a bad idea to turn off the getty on
> }ttyE0 until you have the serial console set up to your satisfaction.
>
> The serial console is working just fine.  Should I just disable wscons?

Oh. I don't know. I just meant that, since you have to rebuild and
reinstall the boot blocks to change the baud rate, com port, and
handshaking, it's convenient not to have to edit /etc/ttys each time.

> }True, but you'll probably have better luck if you don't try to run a
> }getty on the unconfigured virtual terminal.
>
> The virtual terminal is no longer unconfigured, and attempting to
> change virtual terminals still causes a panic.  Doing anything else
> at the display has had no effect.

Well, it's a "new" bug, then. I have no trouble with this on 1.4.3:

console "/usr/libexec/getty Pc"         vt420   off secure
ttyE0   "/usr/libexec/getty Pc"         vt220   on secure
ttyE1   "/usr/libexec/getty Pc"         vt220   on secure
ttyE2   "/usr/libexec/getty Pc"         vt220   on secure
ttyE3   "/usr/libexec/getty Pc"         vt220   on secure
tty00   "/usr/libexec/getty std.9600"   unknown off secure
tty01   "/usr/libexec/getty vt.19200"   vt420   on secure

I'm running X on ttyE3. I did have just the getty on tty01 for a long
time, then after wedging X up really good one day, I decided to make
the serial port the console.


Frederick