From owner-freebsd-hackers Mon Jul 24 11:34:40 1995 Return-Path: hackers-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.11/8.6.6) id LAA03943 for hackers-outgoing; Mon, 24 Jul 1995 11:34:40 -0700 Received: from cs.weber.edu (cs.weber.edu [137.190.16.16]) by freefall.cdrom.com (8.6.11/8.6.6) with SMTP id LAA03920 for ; Mon, 24 Jul 1995 11:34:37 -0700 Received: by cs.weber.edu (4.1/SMI-4.1.1) id AA07622; Mon, 24 Jul 95 12:27:09 MDT From: terry@cs.weber.edu (Terry Lambert) Message-Id: <9507241827.AA07622@cs.weber.edu> Subject: Re: dial up at > 9600 baud To: bde@zeta.org.au (Bruce Evans) Date: Mon, 24 Jul 95 12:27:09 MDT Cc: bde@zeta.org.au, ache@astral.msk.su, hackers@freebsd.org, harry@hgac.com, jkh@violet.berkeley.edu In-Reply-To: <199507240033.KAA27257@godzilla.zeta.org.au> from "Bruce Evans" at Jul 24, 95 10:33:11 am X-Mailer: ELM [version 2.4dev PL52] 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. 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. It should be irrelevant what the new port speed is if the modem can't detect it. The current discussion is predicated on the modem being somehow able to detect it. 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. That way the modem can no longer detect the speed and the problem is eliminated. Doing the bogus getty changes is not the soloution. Terry Lambert terry@cs.weber.edu --- Any opinions in this posting are my own and not those of my present or previous employers.