Return to BSD News archive
Newsgroups: comp.os.386bsd.bugs Path: sserve!newshost.anu.edu.au!munnari.oz.au!bunyip.cc.uq.oz.au!harbinger.cc.monash.edu.au!yeshua.marcam.com!usc!howland.reston.ans.net!gatech!concert!inxs.concert.net!taco!cddukes From: cddukes@eos.ncsu.edu (CHRISTOPHER D DUKES) Subject: Comm strangeness. Message-ID: <1993Dec20.015327.17390@ncsu.edu> Sender: news@ncsu.edu (USENET News System) Organization: NCSU Campus Computing Date: Mon, 20 Dec 1993 01:53:27 GMT Lines: 20 I've recently installed FreeBSD, and I've encountered some strange problems when using kermit, or other comm programs with my cheap old external 2400 baud modem. If I set the modem so that the CD line is true to the modem's connection status Kermit stays locked until I press control-C and works afterwards, and minicom doesn't work at all. If I set the modem so that it has the CD line on at all times Kermit gets running with no problem and minicom works great. 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 termios() or ioctl() on the line? I've tried minicom for ioctl and termios and it doesn't work either way, but I don't know enough about either to be able to diagnose if they are doing something that they shouldn't. Any pointers would be appreciated. -- "Very Pete Townshendish." "Who?" "Exactly." cddukes@eos.ncsu.edu cdukes@nyx.cs.du.edu pakrat@vnet.ibm.com