From owner-freebsd-current Thu Jun 19 22:51:01 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id WAA13102 for current-outgoing; Thu, 19 Jun 1997 22:51:01 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id WAA13096 for ; Thu, 19 Jun 1997 22:50:39 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id HAA24629; Fri, 20 Jun 1997 07:50:34 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id HAA04997; Fri, 20 Jun 1997 07:35:06 +0200 (MET DST) Message-ID: <19970620073506.MK21253@uriah.heep.sax.de> Date: Fri, 20 Jun 1997 07:35:06 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: freebsd-current@FreeBSD.ORG Cc: adam@veda.is (Adam David) Subject: Re: getty modem control References: <199706192354.XAA12656@veda.is> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199706192354.XAA12656@veda.is>; from Adam David on Jun 19, 1997 23:54:15 +0000 Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Adam David wrote: > 1. Would anyone be terribly upset if I added modem string grabbing support > to getty? This would be useful for logging caller ID and connect speed. Yep, i'm very reluctant to such things in the regular getty. The reason for this reluctance is that you gotta abuse the inbound port. Normally, the inbound port is supposed to block inside open(2) until carrier arrives. I understand that your intended changes would break this (as well as David Nugent's changes broke this, see below). If you need mgetty, better use mgetty. There's no use to invent a second all-singing all-dancing getty, i'd be more happy to keep the standard getty reasonably small, more targeted towards regular needs and non-broken modems. > 2. I've been trying to use the modem init stuff on FreeBSD 2.2.2 getty. > DTR lights up but there is no flicker on TXD. After this attempt I can > no longer access /dev/ttyd0 or /dev/cua00, 'cu' refuses to open the port > (no light on DTR) because "Line in use". That's already one of the problems i've been afraid when i've been objecting against _any_ modem initialization handling back when David Nugent added it. Fixing all the related programs to chatting with a modem will become an endless mess. I really don't think this should go into a regular getty, or after some time, we'll end up with yet another mgetty. This is silly, will bloat the regular getty, and is nothing but a duplication of (Gert Doering's in this case) efforts. Non-broken modems do work with a lightweight getty. Broken modems (and i figure the entire class of modems that is allowed in Australia belongs into this class) requires special hacks which should IMHO be left to special programs. If you don't agree on this, please agree on forking off the old (pre-David N) getty as ``getty-light'', so i could continue to use this version then. I refuse to use broken modems anyway, and i don't need the creeping featurism. (Not meant as a personal offense, but as a general statement.) -- 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. ;-)