From owner-freebsd-hackers  Sun Jul 23 17:37:02 1995
Return-Path: hackers-owner
Received: (from majordom@localhost)
          by freefall.cdrom.com (8.6.11/8.6.6) id RAA21351
          for hackers-outgoing; Sun, 23 Jul 1995 17:37:02 -0700
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.34])
          by freefall.cdrom.com (8.6.11/8.6.6) with ESMTP id RAA21345
          for <hackers@freebsd.org>; Sun, 23 Jul 1995 17:36:57 -0700
Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id KAA27257; Mon, 24 Jul 1995 10:33:11 +1000
Date: Mon, 24 Jul 1995 10:33:11 +1000
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199507240033.KAA27257@godzilla.zeta.org.au>
To: bde@zeta.org.au, terry@cs.weber.edu
Subject: Re: dial up at > 9600 baud
Cc: ache@astral.msk.su, hackers@freebsd.org, harry@hgac.com,
        jkh@violet.berkeley.edu
Sender: hackers-owner@freebsd.org
Precedence: bulk

>> It's not nice to have to specify the speed in more than one place, but
>> I regard that as a bug in getty or gettytab.  getty thinks it owns the
>> ...

>The port state information for incoming and outgoing communications
>on a given port should be maintained *seperately* for the tty devices
>accessing the port.  Then this wouldn't be a problem.

It is maintained separately.  Read the man page.  We're talking about
the problem that changes to the defaults for initial state can be
specified in either /etc/rc.serial or in /etc/gettytab, and it must be
specified in /etc/gettytab because getty doesn't trust the defaults and
it may want to autobaud, and setting it in /etc/rc.serial might fix the
original problem.

Bruce