-.I login.
-For normal lines, the character is `0';
-other characters can be used, for example, with hard-wired terminals
-where speed recognition is unnecessary or which have special characteristics.
-.RI ( Getty
-will have to be fixed in such cases.)
-The remainder of the line is the terminal's entry in the device directory, /dev.
+.IR login (1).
+It can be, however, any desired command, for example
+the start up for a window system terminal emulator or some other
+daemon process, and can contain multiple words if quoted.
+.PP
+The third field is the type of terminal usually connected to that
+tty line, normally the one found in the
+.IR termcap (5)
+data base file.
+The environmental variable ``TERM'' is initialized with the value by
+either
+.IR getty (8)
+or
+.IR login (1).
+.PP
+The remaining fields set flags in the
+.I ty_status
+entry (see
+.IR getttyent (3))
+or specify a window system process that
+.IR init (8)
+will maintain for the terminal line.
+.PP
+As flag values, the strings ``on'' and ``off'' specify that
+.I init
+should (should not) execute the command given in the second field,
+while ``secure'' (if ``on'' is also specified) allows users with a
+uid of 0 to login on
+this line.
+These flag fields should not be quoted.
+.PP
+The string ``window='' may be followed by a quoted command
+string which
+.I init
+will execute
+.B before
+starting the command specified by the second field.
+.SH EXAMPLES
+.nf
+# root login on console at 1200 baud
+console "/usr/libexec/getty std.1200" vt100 on secure
+# dialup at 1200 baud, no root logins
+ttyd0 "/usr/libexec/getty d1200" dialup on # 555-1234
+# Mike's terminal: hp2621
+ttyh0 "/usr/libexec/getty std.9600" hp2621-nl on # 457 Evans
+# John's terminal: vt100
+ttyh1 "/usr/libexec/getty std.9600" vt100 on # 459 Evans
+# terminal emulate/window system
+ttyv0 "/usr/new/xterm -L :0" vs100 on window="/usr/new/Xvs100 0"
+# Network pseudo ttys -- don't enable getty
+ttyp0 none network
+ttyp1 none network off
+.fi