Re: HID stuff broken.

[James S. <jsi...@tr...>]

> Umm, I think I have just one keyboard. But at the time of the error
> message the keyboard probably wasn't connected, being USB and with my
> bad USB active extension cable, which needs to be unplugged and
> replugged after each boot to detect the devices on it.
> 
> So it's one-display-no-keyboard case. It works fine with 2.4.14-ruby.

Hm. This must be due to my VT creation changes. A tty is registered when
it detects a keyboard and their is a VT display with no keyboard attached. 

   I just realized their is the other issue I have to fix. That is the
/dev/console redirect thing. Right now this is really broken. For example
for the LP console their is no tty related to it. So if you attempt to
open /dev/console for a LP console it bombs. So I have been working on a
/dev/console that registers it own TTY that wraps aroung the struct
console functions. This will solve alot of problems.
   At present this affects the situation where you have no keyboard plugged 
in at boot time but after boot time you plug it in. Now the console stuff
can exist without a TTY. I reworked the code that way. Unfortunely the
other way around doesn't quite work yet. I'm working on the new /dev/console
TTY driver today. This way their will be no keyboard problems in the
future. /dev/console will be such that it doesn't matter if you have no
way to bring input in (i.e no keyboard). As for /dev/ttyX this will not be
the case.