From owner-freebsd-hackers Thu Feb 15 10:13:11 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id KAA13145 for hackers-outgoing; Thu, 15 Feb 1996 10:13:11 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id KAA13140 for ; Thu, 15 Feb 1996 10:13:09 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id LAA02589; Thu, 15 Feb 1996 11:11:04 -0700 From: Terry Lambert Message-Id: <199602151811.LAA02589@phaeton.artisoft.com> Subject: Re: An ISP's Wishlist... To: uhclem@nemesis.lonestar.org (Frank Durda IV) Date: Thu, 15 Feb 1996 11:11:03 -0700 (MST) Cc: freebsd-hackers@FreeBSD.org In-Reply-To: from "Frank Durda IV" at Feb 14, 96 10:10:00 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.org Precedence: bulk > Most modems allow you to interrogate them AFTER the call has completed > to find out the cause of the failure. Nearly all modems based on > Rockwell chipsets do this, so do most AT&T, and Sierra chipset designs. A correctly configured modem will reset on the last close because of the on-to-off DTR transition. > The simplest thing would be to have something other than getty reacquire > the port after a disconnect, query the modem, then reset the modem and > exec the real getty. What you propose would require significantly rearchitecting the tty revocation model (specifically, to exempt init but not its children) so that the DTR would not drop until the query is complete. This could not be done while maintaining compliance with POSIX termios. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.