From owner-freebsd-hackers  Mon Jul 24 12:24:33 1995
Return-Path: hackers-owner
Received: (from majordom@localhost)
          by freefall.cdrom.com (8.6.11/8.6.6) id MAA06443
          for hackers-outgoing; Mon, 24 Jul 1995 12:24:33 -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 MAA06437
          for <hackers@freebsd.org>; Mon, 24 Jul 1995 12:24:22 -0700
Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id FAA28570; Tue, 25 Jul 1995 05:20:49 +1000
Date: Tue, 25 Jul 1995 05:20:49 +1000
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199507241920.FAA28570@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 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.

>This is really my whole problem with rc.serial, which could probably
>be argued for on the basis of CTS/RTS flow control, and maybe nothing
>else.

In Linux it is used to initialize IRQs etc. for recalcitrant h/w :-).

>The default baud being 9600 is not the problem.  The modem being able
>to "magically" detect the baud which the port is set to *is* the problem.

>The only way to solve this thing is to find where the error is in the
>driver or in the getty or in the modem cable or in the modem settings
>and correct it.

This is hard to do when the person who has the problem is not part of
this discussion.

Bruce