cwr@pnet01.cts.com (Will Rose) (01/10/91)
Some time ago I tired of trying to remember what 1d2 meant, and patched
the 1.5.10 init to allow comments in /etc/ttys (and also got init to call
getty with the speed it read from ttys). I've just been looking at Steve
Kirkendall's revised tset, which seems a very good idea, but once again
involves additional data in /etc/ttys. Could some authority (ast? Bruce
Evans?) define a standard /etc/ttys format, that would allow more
functionality than the current version? It might be nice in 1.6...
My bet is:
# comment
nnn [SK's terminal type] # comment
# comment
[nnttyname]
etc...
The nnn, nnttyname above are lines using the current standard. Obviously,
all the comments are optional - but they make life a lot easier when you're
messing with multiple log-ons.
Comments, anyone?
Will
-----------------------------------------------------------------------
"If heaven too had passions | Will Rose
even heaven would | UUCP: {nosc ucsd hplabs!hp-sdd}!crash!pnet01!cw
grow old." - Li Ho. | ARPA: crash!pnet01!cwr@nosc.mil
| INET: cwr@pnet01.cts.com
UUCP: {nosc ucsd hplabs!hp-sdd}!crash!pnet01!cwr
ARPA: crash!pnet01!cwr@nosc.mil
INET: cwr@pnet01.cts.comTAR@MAINE.BITNET (01/12/91)
(Person asks what the 1d2 in /etc/ttys was for and so on...)
The first digit in the field tells INIT:
0 = Dead line
1 = Line to be run using login (direct)
2 = Line to be run using getty (modem, direct, or ethernet)
The second letter tells INIT what speed and parity to use.
d = 2400,N,8,1
0 = Console
The third digit tells INIT what line this is,
0 = Console
1 = tty1
2 = tty2, and so on.
NOTE: All this, plus a listing of the second-position letters and what
speed/partity they are, can be found in the INIT source code.
Hope this helps.
--Moth