[hylafax-users] HFAXD and Hylafax running on OSX / PowerMac

["Guy R. Loucks" <gstmgmtc@optushome.com.au>]

Ok people, it is done: now testing, from the archives:

"
To run as a daemon, I use:
/usr/local/sbin/hfaxd -i 4559

Use -i to run as a daemon instead of in inetd.  You need to specify
the port to run on, 4559 is the default.

If anyone has a better way of starting the hfaxd server, please tell
me; I got this from reading the man page and not the How To, so it
might not be the Official Best Way.

Alan"

I hang my head in shame. So the order is:

1.	The patched config file which Lee developed
2.or	Build as follows:

./configure --with-GETTY="BSD" --with-CXXFILE="-x c++"

3.	do the make, make test, make install, configure your modem etc.
4.	Make a devfs for the chrooted environmen and mount:
I created	:	mkdir  ~faxadm/dev
and 		:	mount -t devfs ~faxadm/dev /var/spool/fax/dev
5.	Start hfaxd
/usr/local/sbin/hfaxd -i 4559

Now people,

How do we go about a test script etc, I would like to build up some 
install / startup scripts, bundle this in, make use of some of Apple's 
web pages and put it up once it is tested..

Right now I am going to go an poor myself a cold brewski, and put my 
feet. up. After that I will have myself flogged. What is the current 
Hylafax release for me to download and test now, are we nearing another 
RC / release?

Cheer all,

Guy

On Thursday, November 15, 2001, at 08:41  AM, Guy R. Loucks wrote:

> Hello People,
>
> Actually, faxgetty is ok, the problem is with HFAXD, and the chrooted 
> environment. see notes below:
>
> From: "Guy R.Loucks" <loucksg@optushome.com.au>
> Date: Tue Oct 02, 2001  08:17:45  PM Australia/Sydney
> To: hylafax-devel@hylafax.org
> Subject: [hylafax-devel] Re: OS-X support Solution?!??
>
> So close:
>
> Oct  2 19:52:40 localhost HylaFAX[13096]: getpeername: Socket operation 
> on non-socket
>
> Oct  2 19:56:16 localhost HylaFAX[13105]: getpeername: Socket operation 
> on non-socket
>
> I have seen this referenced before, I think this is a pointer size 
> issue on the getsocket operation of hfaxd. I am open to suggestions. 
> The notes below worked.
>
> I created a ~faxadm/dev
> and mount -t devfs ~faxadm/dev /var/spool/fax/dev
>
> It looks now like the chrooted environment may be ok!
>
> I will update as I discover more.
>
>
> On Tuesday, October 2, 2001, at 07:29  PM, Guy R.Loucks wrote:
>
> Ok,
>
> Looks like we have a goes on OSX: I think this can be included in the 
> install script. I am testing this against the current release, and will 
> try it against the release candidate. From Apple:
>
> it doesn't say so in the man pages, but special device files can only
> exist in a devfs filesystem, and thus mknod will only create files in
> a devfs filesystem.
>
> The US guys suggested that if you mount a devfs filesystem in a
> user's environment, you can edit the device files available to the
> user without impacting what is in the /dev directory.
>
> eg
>
> mkdir ~/dev
> mount -t devfs devfs ~/dev
>
> This will provide the system defaults in a devfs filesystem in the
> ~/dev directory - any device files manually created in /dev will not
> be automatically duplicated.
>
> Note also that the ditto command can be used to copy device special
> files between devfs filesystems.
>
> I hope this helps.
>
> So I will make a ~faxadm/dev and mount it on the var/spool/fax/dev 
> directory, and we should have a production environment. If we can get 
> it into the install scripts. I will put the next release notes up on 
> the Apple OSX software downloads page.
>
> Cheers,
>
> Guy
>
>
> On Monday, October 1, 2001, at 12:51  PM, Guy R. Loucks wrote:
>
> People,
>
> Ok the conclusion of the investigation of hfaxd in OSX, we can not 
> support a chrooted environment under OSX. Actually we can support it, 
> but you can not have access to device special files, you need to make 
> the requests from the O/S supplied drivers.
>
> OSX will not all us to create a /dev/null etc. under the /var/spool/fax 
> directory etc.
>
> My thoughts, some conditional compile code around to omit the chrooted 
> environment in OSX, with huge disclaimers warning people of the 
> security implications etc.
>
> Or I welcome any other thoughts on the matter. I have placed a call 
> with Apple, although they have been so busy with OSX 10.1 (running this 
> now) I don't think I will ge an answer for a few weeks.
>
> I welcome everyones thoughts and input on a resolution to hfaxd.
>
> Cheers,
>
> Guy
>
> On Monday, September 24, 2001, at 07:57  AM, Guy R. Loucks wrote:
>
> Hello again people,
>
> My apologies for being away for so long. Some good news.
>
> I suppose give the past fortnight just about anything is good news.
>
> It looks like our little mknod problem may be more generic. I have had 
> apple duplicate the issue, and forward it as a case for investigation 
> internally. It behaves this way in 10.0 - .4, and has been tested 
> against 10.1 RC-1. I am wondering of maybe removing the chrooted 
> environment from hfaxd, and just trying it against the native OS-x 
> device special files as a test.
>
> As a reminder, the problem is making DEVICE SPECIAL files outside of 
> the /dev directory does not appear to work.
>
> Your thoughts and comments welcome.
>
> Kind regards,
>
> Guy
>
> ---
> Guy R. Loucks			|   "Everyone is a genius at least once a year.
> "These opinions and 	|    The real geniuses simply have their bright
>  ideas are my own,   		|    ideas closer together."       G.C. 
> Lichtenberg
>  what few there are."		|
> ---------------------------------------------------------------------------
>
> CAUTION: This message and any attachments contain information that is
> CONFIDENTIAL and is LEGALLY PRIVILEGED. If you are not the intended 
> recipient any use, disclosure or copying of this email message or 
> attachments is strictly prohibited. If you have received this message in
> error, please notify immediately and erase all copies of this message
> and attachments.
>
>
>
>
>
> ____________________ HylaFAX(tm) Developers Mailing 
> List ____________________
> To unsub: mail -s unsubscribe hylafax-devel-request@hylafax.org < 
> /dev/null
>
>
>
>
> ____________________ HylaFAX(tm) Developers Mailing 
> List ____________________
> To unsub: mail -s unsubscribe hylafax-devel-request@hylafax.org < 
> /dev/null
>
>
>
>
> On Saturday, November 10, 2001, at 05:00  AM, Lee Howard wrote:
>
>> At 12:38 PM 11/9/01 -0500, Michael Engelhart wrote:
>>> Hi,
>>>
>>> I'm trying to build hylafax on OS X v10.1.   I was able to get 
>>> configure
>>> to run by copying my /usr/libexec/config.guess that comes with my OS X
>>> distro and replacing the config.guess that comes with hylafax but now
>>> configure is saying it can't find the C++ standard library which OS X
>>> stores in (of all places) /usr/include/gcc/darwin/2.95.2/g++
>>>
>>> Any ideas on how to tell configure how to find the standard libraries?
>>> I'm assuming there is a switch somewhere but I'm not that familiar 
>>> with
>>> these kinds of unix build systems.
>>>
>>> Thanks for any help or if there already is an OS X build available.
>>
>> CVS HylaFAX supposedly compiles on OS X.  Not only was there an issue 
>> with
>> config.guess, but there was something that had to be tweaked in 
>> configure
>> so that g++ was used instead of whatever it picks by default.  This 
>> was the
>> patch:
>>
>> diff -Nru hylafax.orig/configure hylafax/configure
>> --- hylafax.orig/configure      Mon Jul 16 13:51:35 2001
>> +++ hylafax/configure   Tue Aug 14 14:19:46 2001
>> @@ -1256,6 +1256,7 @@
>>      case $CXX-$TARGET in
>>      xlC-*-aix*)                CXXFILE="-+";;
>>      gcc-*)             CXXFILE="-x c++";;
>> +    *-*darwin*)        CXXFILE="-x c++";;
>>      CC-*-sco3.2v5.*)   CXXFILE="+.c++";;
>>      esac
>>  fi
>> @@ -3599,6 +3600,7 @@
>>      *bsd*)     GETTY=BSD;;
>>      *-sunos*)  GETTY=BSD;;
>>      *-ultrix*) GETTY=BSD;;
>> +    *darwin*)  GETTY=BSD;;
>>      *)         GETTY=SysV;;
>>      esac
>>  fi
>>
>> However, all of this can be accomplished by running configure like 
>> this:
>>
>> ./configure --with-GETTY="BSD" --with-CXXFILE="-x c++"
>>
>> Be wary, however, that there are issues with faxgetty and OSX.  I 
>> can't be
>> more specific than that, though.  If you need to correspond with other
>> HylaFAX-OSX users, try:
>> "Guy R. Loucks" <loucksg@optushome.com.au>
>> Erick Schmidt <eschmidt@rockymountainsurety.com>
>>
>> Lee.
>>
>>
>>
>> ____________________ HylaFAX(tm) Developers Mailing 
>> List ____________________
>>  To unsub: mail -s unsubscribe hylafax-devel-request@hylafax.org < 
>> /dev/null
>>
>
>
>
> ____________________ HylaFAX(tm) Developers Mailing 
> List ____________________
> To unsub: mail -s unsubscribe hylafax-devel-request@hylafax.org < 
> /dev/null
>



____________________ HylaFAX(tm) Users Mailing List _______________________
 To unsub: mail -s unsubscribe hylafax-users-request@hylafax.org < /dev/null