From owner-freebsd-bugs@FreeBSD.ORG Tue Sep 9 07:40:20 2003 Return-Path: Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 47CA516A4BF for ; Tue, 9 Sep 2003 07:40:20 -0700 (PDT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id CA31243F85 for ; Tue, 9 Sep 2003 07:40:19 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.12.9/8.12.9) with ESMTP id h89EeJUp050944 for ; Tue, 9 Sep 2003 07:40:19 -0700 (PDT) (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.12.9/8.12.9/Submit) id h89EeJe5050943; Tue, 9 Sep 2003 07:40:19 -0700 (PDT) Date: Tue, 9 Sep 2003 07:40:19 -0700 (PDT) Message-Id: <200309091440.h89EeJe5050943@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org From: Yar Tikhiy Subject: Re: bin/56325: Incorrect information in /etc/gettytab X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Yar Tikhiy List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Sep 2003 14:40:20 -0000 The following reply was made to PR bin/56325; it has been noted by GNATS. From: Yar Tikhiy To: Mats Peterson Cc: bde@zeta.org.au, FreeBSD-gnats-submit@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