Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!sgiblab!darwin.sura.net!udel!news.sprintlink.net!demon!awfulhak.demon.co.uk!awfulhak!brian From: brian@awfulhak.demon.co.uk (Brian Somers) Newsgroups: comp.os.386bsd.bugs Subject: Re: Comm strangeness. Date: 20 Dec 93 01:14:16 Organization: Coverform Ltd. Lines: 19 Message-ID: <BRIAN.93Dec20011416@awfulhak.demon.co.uk> References: <1993Dec20.015327.17390@ncsu.edu> NNTP-Posting-Host: awfulhak.demon.co.uk In-reply-to: cddukes@eos.ncsu.edu's message of Mon, 20 Dec 1993 01:53:27 GMT In article <1993Dec20.015327.17390@ncsu.edu> cddukes@eos.ncsu.edu (CHRISTOPHER D DUKES) writes: Is this standard operating procedure for *ix and modems? Is this a glitch in how the OS accesses the comm port? or Is this probably just a glitch in both software packages when they perform [deleted] -- "Very Pete Townshendish." "Who?" "Exactly." cddukes@eos.ncsu.edu cdukes@nyx.cs.du.edu pakrat@vnet.ibm.com It seems to be a preference that one of the FreeBSD people introduced. You can get rid of the problem by setting clocal (stty -f /dev/tty?? clocal) .... or is it the other way around .... Brian. -- Brian <brian@awfulhak.demon.co.uk>