Complete.Org: Mailing Lists: Archives: gopher: February 2002:
[gopher] Re: UMN Gopher on Mac OSX

[gopher] Re: UMN Gopher on Mac OSX

[Top] [All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index] [Thread Index]
To: gopher@xxxxxxxxxxxx
Subject: [gopher] Re: UMN Gopher on Mac OSX
From: Robert Hahn <rhahn@xxxxxxxxxx>
Date: Tue, 12 Feb 2002 14:22:06 -0500
Reply-to: gopher@xxxxxxxxxxxx

If anyone has the resources (I don't at the moment) I would also be 
interested in knowing whether gopher 3.0.2 compiles on OS X without 
changes if the drive format is UFS.

I read some Apple knowledge base articles about UFS, and while they 
don't address the performance problems I mentioned earlier today, 
they *did* say that while they recommend I use HFS+ for "the 
Macintosh experience", if I was planning on doing any Unix 
development, that I should probably opt to format my drive as UFS. 
Interesting. This isn't an option with my home setup at this time, 
but when I get my computer upgraded here at work (and you can bet 
I'll be using OS X when that happens), perhaps I'll explore that...

thanks again to those who have contributed to this porting work.


>Thanks for the info David.  I'm finally downloading the dev tools to
>my PowerBook myself.  (Yes, I know I promised this awhile back,
>What I'm curious about is whether the compilers included with fink
>(, which I also have not installed) exhibit similar
>behavior, or if this is unique to the Apple tools.  If fink behaves
>differently, then perhaps we can say that "compilation on Darwin is
>supported only with fink."  Another possibility is to investigate
>whether gcc supports options to tell it "be case-sensitive, please"
>and whether there is a difference when running on HFS vs. UFS
>partitions.  I intend to investigate all but the fink question
>-- John

Robert Hahn,
Quarry Integrated Communications
(519)743-4300 x2235

[Prev in Thread] Current Thread [Next in Thread]