From owner-freebsd-hackers Sat Dec 7 21:00:49 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id VAA25729 for hackers-outgoing; Sat, 7 Dec 1996 21:00:49 -0800 (PST) Received: from nike.efn.org (resnet.uoregon.edu [128.223.170.28]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id VAA25724 for ; Sat, 7 Dec 1996 21:00:43 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by nike.efn.org (8.8.3/8.8.3) with SMTP id TAA05784; Sat, 7 Dec 1996 19:13:56 -0800 (PST) Date: Sat, 7 Dec 1996 19:13:55 -0800 (PST) From: John-Mark Gurney X-Sender: jmg@nike Reply-To: John-Mark Gurney To: Joerg Wunsch cc: FreeBSD hackers Subject: Re: possible bug in comconsole code... In-Reply-To: <199612071921.UAA21995@uriah.heep.sax.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Sat, 7 Dec 1996, J Wunsch wrote: > As John-Mark Gurney wrote: > > > I tried some basic stuff like "echo blah > /dev/cuaa0" which just returned > > a single "b"... then I thought that the port might be closing before the > > data was sent... so a "(echo blah;sleep 1)> /dev/cuaa0" got the whole > > thing sent out... > > It's perhaps possible that your terminal is sensible against modem > control signals? Though i've been using comconsole in a similar well... I'm using tip running on another FreeBSD box... but now it is now a little pointless... I'm now restricting logins to the comconsole as it's attached to my main server now... > environment, and only noticed that the output drops at the time the > sio devices are being probed. (Even this doesn't happen with a > modem-control insensitive terminal however.) hmmm... is tip sensitive to it? thanks for the advice though... ttyl.. John-Mark gurney_j@efn.org http://resnet.uoregon.edu/~gurney_j/ Modem/FAX: (541) 683-6954 (FreeBSD Box) Live in Peace, destroy Micro$oft, support free software, run FreeBSD (unix)