On Mon, Feb 24, 2003 at 05:35:52PM -0800, Ben Hines wrote:
> On Monday, February 24, 2003, at 03:49 PM, David Brown wrote:
> >I have only one compelling reason: HFS is not case sensitive. I have
> >one, and only one application I'm using that absolutely depends on
> >Unfortunately, until they fix it, I'm kind of stuck.
> A lot of UNIX heads seem to think they need this, when in fact they
The opencm package currently depends on case-uniqueness, and case
sensitivity. Its archive is stored in 64 subdirectories: a-z and then
A-Z. It appears to work for a while, because once it creates 'A' access
to 'a' works, but it can then later get conflicts.
It also makes it impossible to move a repository from one machine to
another, since the FS being case-sensitive wouldn't be able to find most
of the files.
Admittedly, opencm should be fixed, but since it is under development,
and this isn't all that high of a priority, it will be a while. I just
My other BIG gripe about HFS is that Apple doesn't seem very forthcoming
about a nice clean documented interface to the extra attributes. I've
found programs that use it, but no real docs on it. I get the
impression they are trying to discourage use of the extra information
(since on UFS it gets stored in a file).
I would be most happy if HFS+ had a directory attribute or flag which
would mark a tree as case sensitive.
unix-porting mailing list | email@hidden
Do not post admin requests to the list. They will be ignored.