Return to BSD News archive
Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!msunews!agate!newsxfer.itd.umich.edu!zip.eecs.umich.edu!panix!cmcl2!newsserv.cs.sunysb.edu!starkhome.cs.sunysb.edu!localhost!gene From: gene@starkhome.cs.sunysb.edu (Gene Stark) Newsgroups: comp.os.386bsd.questions Subject: Re: Sharing a modem between FlexFAX and Kermit? Date: 21 Jan 95 17:24:48 Organization: Gene Stark's home system Lines: 21 Message-ID: <GENE.95Jan21172448@starkhome.cs.sunysb.edu> References: <kientzleD2M43C.8D6@netcom.com> NNTP-Posting-Host: localhost.cs.sunysb.edu In-reply-to: kientzle@netcom.com's message of Wed, 18 Jan 1995 17:47:36 GMT In article <kientzleD2M43C.8D6@netcom.com> kientzle@netcom.com writes: The FlexFAX docs claim it can share a serial port with other programs, but I've had no luck. I've tried setting FlexFAX to use /dev/tty01 (minor mode 1) and Kermit to use /dev/cua01 (minor mode 129), but Kermit keeps claiming that it can't get access to the port. When I run Kermit as root, it claims `device busy.' Can anyone point me to the magic incantation that makes this work? For the record, FreeBSD 2.0 from the Walnut Creek CD-ROM dist. I used the precompiled Kermit binary and compiled FlexFAX from the `ports' directory. When a program uses the uucp locking protocol to lock the device that flexfax has open (/dev/tty01), then flexfax close the device and gets out of the way until such time as the lock is removed or the process that created the lock has died. Make sure that kermit is creating the proper lock files. - Gene Stark