Date: Thu, 15 Feb 96 19:46 WET From: uhclem@nemesis.lonestar.org (Frank Durda IV) To: freebsd-hackers@freebsd.org Subject: Re: An ISP's Wishlist... Message-ID: <m0tnFFp-000CqQC@nemesis.lonestar.org>
next in thread | raw e-mail | index | archive | help
[2]Most modems allow you to interrogate them AFTER the call has completed [2]to find out the cause of the failure. Nearly all modems based on [2]Rockwell chipsets do this, so do most AT&T, and Sierra chipset designs. [3]A correctly configured modem will reset on the last close because of [3]the on-to-off DTR transition. But that is not what he wanted in this situation. [2]The simplest thing would be to have something other than getty reacquire [2]the port after a disconnect, query the modem, then reset the modem and [2]exec the real getty. [3]What you propose would require significantly rearchitecting the tty [3]revocation model (specifically, to exempt init but not its children) [3]so that the DTR would not drop until the query is complete. [3]This could not be done while maintaining compliance with POSIX termios. Uh, I was trying to solve the problem for an ISP who really doesn't care about POSIX-anything. If it does what he wants and he is happy, it is compliant in a more important way. He can already do his completion polling easily with UUCP connections. For other calls, there are other ways to hold DTR (including a dummy process that holds it open) until the information is recovered. We use to do this with Apple Laserwriters so that the printer response messages would not disappear or get truncated when a file being printed ended (serial printer). There is a solution to this problem, that's all. Frank Durda IV <uhclem@nemesis.lonestar.org>|"The Knights who say "LETNi" or uhclem%nemesis@rwsystr.nkn.net | demand... A SEGMENT REGISTER!!!" ^------(this is the fastest route)|"A what?" or ...letni!rwsys!nemesis!uhclem |"LETNi! LETNi! LETNi!" - 1983
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?m0tnFFp-000CqQC>