local.9600. Whilst the actual binary termios(4) definitions and preceeding
comments for local.9600 indicate that parity is disabled, getty(8)
internally simulates parity based on the presence or absence of the 'np'
flag.
PR: conf/76226
Submitted by: peter
Approved by: grog (co-mentor)
MFC after: 1 month
By misinterpreting some data, I thought that getty wouldn't apply any
baud rate to the syscons devices, but it uses the default entry instead.
This means that the baud rate is set to 1200. This isn't too bad, except
when using canonical mode. Make it use 9600 baud by default.
MFC after: 1 week
Devices that don't implement param() (which means they don't support
hardware parameters such as flow control, baud rate) hardcode the baud
rate to TTYDEF_SPEED. This means the buffer size cannot be configured,
which is a little inconvenient when using canonical mode with big lines
of input, etc.
Make it adjustable, but do clamp it between B50 and B115200 to prevent
awkward buffer sizes. Remove the baud rate assignment from
/etc/gettytab. Trust the kernel to fill in a proper value.
Reported by: Mikolaj Golub <to my trociny gmail com>
MFC after: 1 month
Add the `lc' option to default. Having getty understand the issues of
CAPS-only terminals is a nop these days, but `lc' avoids hassles for
people with CAPS-only user names.
Suggested by: Don Yuniskis
weekly:
Modify the call to makewhatis, now that our makewhatis can take the
entire ${MANPATH} as a single argument.
(see changes to getty which this patch is part of)
Basically, a few of the tty flags were changed to work better with
'CRT's, and the flags are better documented (documentation from Bruce
Evans).
