| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
| |
the existing terminal types/classes that have the baudrate suffix,
but differ in that no baudrate is set/defined.
The purpose of these new types/classes is to allow them to be used
for the serial console. Currently the uart(4) driver fixates the
baudrate and the CLOCAL flag, which means that it doesn't matter
whether you give it std.<baud> or 3wire.<baud> as the terminal type
to getty and what exactly <baud> is set to. It's being overridden
by uart(4). The goal is to change uart(4) not to override these
settings.
|
|
|
|
| |
Obtained From: DragonFly BSD (commit f95025e8c9a4471edb610557263b12acd8e7fb3a)
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
| |
PR: docs/148500
Submitted by: Warren Block (wblock at wonkity dot com)
Approved by: ed@
MFC after: 1 week
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
| |
MFC after: 2 weeks
|
|
|
|
|
|
|
| |
PR: conf/90346
Submitted by: Gavin Atkinson <gavin.atkinson@ury.york.ac.uk>
Approved by: philip (mentor)
MFC after: 3 days
|
| |
|
|
|
|
|
|
|
| |
to bring it into accord with the present getty(8) code.
PR: bin/56325
MFC after: 3 days
|
|
|
|
|
| |
PR: conf/26420
Submitted by: Jon Passki <cykyc@yahoo.com>
|
|
|
|
|
|
|
| |
This does nothing if you don't have an /etc/issue file.
PR: 22331
Submitted by: Rick C. Petty <rick@kiwi-computer.com>
|
|
|
|
|
| |
PR: 18082
Submitted by: C. Stephen Gunn <csg@dustdevil.waterspout.com>
|
| |
|
| |
|
|
|
|
| |
PR: 7280
|
|
|
|
|
|
| |
PR: 6600
Reviewed by: phk
Submitted by: Josh Gilliam <josh@quick.net>
|
|
|
|
|
| |
how to force a local tty line into CLOCAL mode and Xon/Xoff flow control.
This is the preferrable way (over rc.serial).
|
|
|
|
| |
Requested-By: John Robert LoVerso <loverso@osf.org>
|
|
|
|
| |
Loose lips sink ships! Man the firewall and look alert!
|
|
|
|
| |
feature.
|
|
|
|
| |
punctuation.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
Date: Wed, 10 Nov 1993 00:51:19 GMT
Subject: typo in etc/gettytab
[editor: fix typo in comment about what things need turned off for
none crt entries]
|
|
|
|
|
|
|
|
| |
(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).
|
| |
|
|
|
|
| |
and 115.2k baud gettys.
|
|
|