At 09:21 PM 4/12/00 -0400, Jonathan S. Shapiro wrote:
>31 characters simply won't do, as the hex representation of an SHA result
>requires 40 characters *minimum*. Basically, you are telling me that there
>exists no possible encoding under MacOs for SHA filenames. If this is so,
>I'll drop MacOs compatibility. If I go to a base32 encoding, which *can* be
>done compatible with a case-broken FS, I'll still end up needing at least 32
>character names.
>
>...
>
>Is MacOS9 case insensitive? What about MacOsX?
MacOS 9 is the current version of the Mac OS. I don't feel bad about telling people to upgrade. I'm planning on upgrading my machine this weekend. :-)
MacOS 9 continues to be case insensitive, IMHO the only way a file system should work.
I assume in the BSD mode, MacOsX is case sensitive like all Unixen. However, when seen through the Macintosh SystemX finder, it will have to be case insensitive to maintain compatibility.