bin/56325: Incorrect information in /etc/gettytab
Yar Tikhiy
yar at freebsd.org
Tue Sep 9 07:40:20 PDT 2003
The following reply was made to PR bin/56325; it has been noted by GNATS.
From: Yar Tikhiy <yar at freebsd.org>
To: Mats Peterson <mats at snowbee.dyns.cx>
Cc: bde at zeta.org.au, FreeBSD-gnats-submit at freebsd.org
Subject: Re: bin/56325: Incorrect information in /etc/gettytab
Date: Tue, 9 Sep 2003 18:34:32 +0400
On Tue, Sep 09, 2003 at 01:12:56PM +0200, Mats Peterson wrote:
>
> It's still nice if it's there for a reason, though. EVEN if most people
> use no parity nowadays. I had to look at the source to find out why it
> didn't work as expected. I guess not everyone is too keen on doing that...
I'm not speaking of removing the parity capabilities completely.
However, I'd rather drop most double combinations of them because
I can hardly see how serial/terminal hardware would do "-parenb
inpck" (np:ep:), leave alone "-parenb inpck parodd" (np:op:). Bruce
simply documented the present state of getty code when he wrote the
comment in gettytab 9 years ago. I believe it's high time to revise
it. Perhaps the only combination that makes sense is np:ap: which
used to set istrip without turning on parity stuff.
--
Yar
More information about the freebsd-bugs
mailing list