Hylafax Mailing List Archives
|
[Date Prev][Date Next][Thread Prev][Thread Next]
[Date Index]
[Thread Index]
[hylafax-users] OS-X support Solution?!??
Sorry if this is a duplicate, I have not seen any activity on the devel
group in a while, are people still using this?
I think I am close to making progress on the OSX port for hfaxd... I
welcome comments on the transcripts below.
Regards,
Guy
Begin forwarded message:
> 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
>
____________________ HylaFAX(tm) Users Mailing List _______________________
To unsub: mail -s unsubscribe hylafax-users-request@hylafax.org < /dev/null