Date: Thu, 11 Sep 1997 10:38:48 +0000 (GMT)
From: Terry Lambert <tlambert@primenet.com>
To: bde@zeta.org.au (Bruce Evans)
Cc: ache@nagual.pp.ru, bde@zeta.org.au, current@FreeBSD.ORG, nnd@itfs.nsk.su
Subject: Re: PPP - why set CLOCAL for server ('-direct' mode) ?
Message-ID: <199709111038.DAA14664@usr05.primenet.com>
In-Reply-To: <199709110740.RAA31874@godzilla.zeta.org.au> from "Bruce Evans" at Sep 11, 97 05:40:15 pm
next in thread | previous in thread | raw e-mail | index | archive | help
> >I don't think so. It is upper level control function, f.e. /etc/rc.serial > > I think so :-). As far as I'm concerned, rc.serial serves only two valid functions: to set the default port baud rate and CTS/RTS flow control state. The value of the CTS/RTS flow control state is a workaround for broken hardware (and should be worked around with more broken hardware, specifically, a broken cable). THe default should be CTS/RTS off, and it should be turened on by getty from gettytab, when the DCD goes high and the open completes. In the off state, the port should always assert CTS on its pins. The value of setting the default port baud rate is questionable: that can be accomplished in getty, either via two opens (one blocking, one not) or, as is traditional, when the DCD goes high. The value before the DCD goes high is dubious: it's only use is for fixed port-to-modem speeds, which defeat the UNIX autobaud mechanism for no good reason, and mgetty, which should be specifying that the open completes on RI instead of DCD-OFF-TO-ON transition -- in other words, yet another kludge for yet more broken hardware, and the lack of an WAITRI flag for open. Bletch. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199709111038.DAA14664>