Return to BSD News archive
Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!msunews!uwm.edu!cs.utexas.edu!swrinde!pipex!peernews.demon.co.uk!demon!awfulhak.demon.co.uk!awfulhak.demon.co.uk!not-for-mail From: brian@awfulhak.demon.co.uk (Brian Somers) Newsgroups: comp.os.386bsd.questions Subject: Re: Sharing a modem between FlexFAX and Kermit? Date: 6 Feb 1995 03:17:31 -0000 Organization: None Lines: 35 Message-ID: <3h44cb$7e@awfulhak.demon.co.uk> References: <kientzleD2M43C.8D6@netcom.com> <GENE.95Jan21172448@starkhome.cs.sunysb.edu> NNTP-Posting-Host: awfulhak.demon.co.uk X-Newsreader: TIN [version 1.2 PL2] Gene Stark (gene@starkhome.cs.sunysb.edu) wrote: : 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 This is true, you're also better off using /dev/cua01 rather than tty01. For some reason kermit hangs getting at tty01, but not at cua01. Isn't it a pitty that slattach doesn't use UUCP locking.. I've had to resort to pppd to get outgoing net connections up while faxd is running. -- Brian <brian@awfulhak.demon.co.uk> Don't _EVER_ lose your sense of humour....