Date: Sat, 21 Jun 1997 09:09:24 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: freebsd-current@FreeBSD.ORG Subject: Re: getty modem control Message-ID: <19970621090924.HW47363@uriah.heep.sax.de> In-Reply-To: <199706200815.IAA15687@veda.is>; from Adam David on Jun 20, 1997 08:15:07 %2B0000 References: <19970620073506.MK21253@uriah.heep.sax.de> <199706200815.IAA15687@veda.is>
next in thread | previous in thread | raw e-mail | index | archive | help
As Adam David wrote: > Further to the discussion > on the subject of (m)getty back in February, would it work to use DSR as RI > for those ports without RI? I'm afraid not. > AT&S1 DSR will become active after answer tone has been detected and > inactive after the carrier has been lost, i.e. becomes active after > RI and before CD (probably too late to catch caller-ID though?). I have no ideas about caller-ID (it's not supported by the Deutsche Telekom on analog lines). Well, perhaps give it a try? > The whole point was that the user only gets the features requested via > specific gettytab entries. Unless requested, they stay out of the way. I realized this. But still, you make getty far more complex by adding this, and in particular, you're pulling an entire new class of problems into getty in the end: handling the various idiosyncrasies of various modems. As long as the regular getty demands an un-broken modem, one that can remember its speed for an incoming call, and that properly resets on each DTR drop, things are simple. Once you start to talk to modems, look at mgetty for the result. mgetty wasn't always that fat, but much of the code has been added to handle any oddball modem that can be found on this planet. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19970621090924.HW47363>