I'm just at a point here were I've brought up a new machine running near
-current and wanted to have it on serial console, but with wscons too,
and since there's not been any activity on this PR for over a year I
thought I'd give it an update....

[ On Thursday, May 18, 2000 at 13:22:39 (-0400), John Hawkinson wrote: ]
> Subject: Re: kern/10129: wscons loses when console is serial 
>
> In message <200005181414.QAA0000011175@zel459.zel.kfa-juelich.de>, Matthias Dro
> chner writes:
> >
> >jhawk@mit.edu said:
> >>  Output to /dev/ttyE* is displayed, however no input can be read.
> >> Keystrokes can be read from /dev/wskbd0, however. 
> >
> >The assignment of keyboards to displays is not done automatically
> >anymore unless the device is used as system console.
> >It has to be done later, by "wsconscfg -k", or -easier-
> >by uncommenting the "keyboard" line in /etc/wscons.conf.
> 
> Indeed, this does the trick.
> 
> Can you speak to why this is this way? Is there some reason that
> "keyboard" is not uncommented by default? It seems to me that the
> handing of output and input devices should be handled similarly, and
> the current state violates the principal of least confusion.
> 
> I would say, at a bare minimum, this needs a doc/CHANGES
> entry, since it was not this way in 1.4.


Not only that but it also causes anyone with any PC experience to
believe that the system is totally hung!  :-)


Personally I'd like to see the pckbd configured automatically all the
time, regardless of where the console is.  For the same reasons it makes
sense to auto-configure screen 0 all the time too.

-- 
							Greg A. Woods

+1 416 218-0098      VE3TCP      <gwoods@acm.org>     <woods@robohack.ca>
Planix, Inc. <woods@planix.com>;   Secrets of the Weird <woods@weird.com>