[OpenAFS-devel] OpenAFS and HFS+ (Case-Sensitive, Journaled)

[emoy@apple.com]

There really isn't anything that special about the coding.  The  
original coding used 64 characters, including A-Z and a-z.  The  
"special" coding just uses other punctuation characters instead of  
upper case letters.  When I made the change, I figured users on other  
platforms would be used to the original coding, so I just special  
cased the DARWIN case to use the "special" encoding.

The "special" coding should work fine on either a case sensitive or  
insensitive filesystem.  The only difference is if you actually have  
to type the paths (which is rarely needed), you may need to shell  
escape some of the characters in the "special" coding.
------------------------------------------------------------------------ 
--
Edward Moy
Apple

(This message is from me as a reader of this list, and not a statement
from Apple.)

On Jul 13, 2006, at 8:46 PM, Jon Allen Boone wrote:

> Folks,
>
>   I've seen various messages in the archives discussing that the  
> namei fileserver probably does not work with HFS+ and that special  
> "coding" was done to support having the cache files on HFS+ in case- 
> preserving mode.  I haven't been able to discern whether or not  
> these issues were specific to HFS+ in case-preserving mode or if  
> they still apply when HFS+ is configured in Case-Sensitive mode.
>
>   I have 5 OpenAFS clients / 1 server running now with the  
> following setups:
>
>   1 server using UFS partitions for /vicepxx
>   1 client using HFS+ Case-preserving for cache files in /var/db/ 
> openafs/cache
>   4 clients using HFS+ Case-sensitive for cache files in /var/db/ 
> openafs/cache
>
>   Is the special coding I've seen reference to a conscientious  
> attempt to keep cache files from being identical modulo case?
>
>   Is there some reason why I should fear using HFS+ Case-sensitive  
> fs on the server?
>
> --jon
>
> _______________________________________________
> OpenAFS-devel mailing list
> OpenAFS-devel@openafs.org
> https://lists.openafs.org/mailman/listinfo/openafs-devel