Subject: Thoughts on text console
To: None <amiga-dev@NetBSD.ORG>
From: Blaz Zupan <email@example.com>
Date: 07/08/1995 23:11:14
Ok, so we have ttye0 for the custom chip text console, ttye1
for Retina Z2, ttye2 for Z3 and ttye3 for cirrus based boards.
Now what if someone produces a Cybervision or Piccolo SD64
driver, then we'll have ttye4, and so on. Now imagine a user that's
trying to boot a generic kernel with all those drivers enabled,
so that the one that fits his hardware is selected. Now are you
sure there is a line in /etc/ttys for his ttyeX? Isn't this
getting a bit confusing? Also if we add all those ttyeX device
entries to /etc/ttys the user will usually get a whole bunch
of warnings on the console that ttyeX isn't configured and then
he'll have to disable all the unused lines in /etc/ttys. Couldn't
this be somehow automated?
Wouldn't it be wiser if the default console would be always
configured as ttye0 (and it doesn't matter if the default console
is cc, rt, rh, cl or whatever). ttye1-ttye9 could be the virtual
consoles (if it happens that someone implements virtual console
support). How would we select WHAT the default console is?
Well, how do we currently select which console owns the keyboard?
Any opinions on this?
Blaz Zupan, Ljubljanska 19/b, 62000 Maribor, Slovenia
firstname.lastname@example.org, 2:380/104.40, GMIZO::BLAZ