Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 07 Jun 1996 09:21:20 +0200 (MET DST)
From:      "Christoph P. Kukulies" <kuku@gilberto.physik.rwth-aachen.de>
To:        dwhite@resnet.uoregon.edu
Cc:        kuku@gilberto.physik.rwth-aachen.de, freebsd-questions@freefall.freebsd.org
Subject:   Re: hylafax configuration help needed
Message-ID:  <199606070721.JAA18471@gilberto.physik.rwth-aachen.de>
In-Reply-To:  <Pine.BSF.3.91.960606134139.3683B-100000@riley-net170-164.uoregon.edu>

next in thread | previous in thread | raw e-mail | index | archive | help
> On Thu, 6 Jun 1996, Christoph P. Kukulies wrote:
> 
> > I installed hylafax (v3pl0) on my home machine (2.2-current) and
> > some problems come up:
> > 
> > The modem is a noname internal modem. faxaddmodem detected it as
> > as manufacturer 'EXAR'. During the installation some childprocess
> > of faxaddmodem was hitting in between the installation dialog
> > always saying that something got 'hung with your modem - eh?'.
> > After the installation had finished that backgroundprocess was still
> > spitting this message and I killed it.
> 
> I had a similar problem.  It wouldn't detect my Supra properly.  I ended 
> up going in and configuring it manually.  :(


Did you have this background process too, always saying
"something's hung, check your modem, eh?" ?

I examined faxaddmodem a bit and found that the response I
got from my modem (0,2) was OK, the script also found it was
a class 2 modem, then it continued checking other modem features
which all seemed to be OK but still I had these nagging backgrounded
message.

Might there be still a shell (sh) problem? I havn't yet examined it
deeper what exactly happens in this script but I'd be curious if anyone
else running current and hylafax is seeing this problem.


> 
> > Now I thought the idea is to add a line 
> > ttyd1 "/usr/local/sbin/faxgetty" dialup on
> > in my /etc/ttys and so I did.
> > 
> > What's weird now is that I can't use /dev/cuaa1 for dialout anymore.
> > Kermit: Device busy. cu: /dev/cuaa1: Line in use
> > 
> > Solution ? 
> 
> I think hylafax resets the permissions on that device to r/w root only.  
> 
> Doug White                              | University of Oregon  
> Internet:  dwhite@resnet.uoregon.edu    | Residence Networking Assistant
> http://gladstone.uoregon.edu/~dwhite    | Computer Science Major
> 
> 

--Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199606070721.JAA18471>