--Apple-Mail-1788819587-3 Content-transfer-encoding: quoted-printable Content-type: text/plain; charset=us-ascii
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.
However, when seen through the Macintosh SystemX finder, it will have to =
be
case insensitive to maintain compatibility.
We shall see.
-jcr
--Apple-Mail-1788819587-3 Content-transfer-encoding: quoted-printable Content-type: text/enriched; charset=us-ascii
<=
flushleft><fontfamily><param>Helvetica</param><color><param>0000,0000,0000=
</param>
<italic></italic></color><italic>At 09:21 PM 4/12/00 -0400, Jonathan S. =
Shapiro wrote:</italic><color><param>0000,0000,0000</param>
<italic><color><param>0000,0000,DEB7</param>>31 characters simply won't =
do, as the hex representation of an SHA result</color></italic>
<italic><color><param>0000,0000,DEB7</param>>requires 40 characters =
*minimum*. Basically, you are telling me that there</color></italic>
<italic><color><param>0000,0000,DEB7</param>>exists no possible encoding =
under MacOs for SHA filenames. If this is so,</color></italic>
<italic><color><param>0000,0000,DEB7</param>>I'll drop MacOs =
compatibility. If I go to a base32 encoding, which *can* =
be</color></italic>
<italic><color><param>0000,0000,DEB7</param>>done compatible with a =
case-broken FS, I'll still end up needing at least 32</color></italic>
<italic><color><param>0000,0000,DEB7</param>>character =
names.</color></italic>
<italic><color><param>0000,0000,DEB7</param>></color></italic>
<italic><color><param>0000,0000,DEB7</param>>...</color></italic>
<italic><color><param>0000,0000,DEB7</param>></color></italic>
<italic><color><param>0000,0000,DEB7</param>>Is MacOS9 case insensitive? =
What about MacOsX?</color></italic>
<italic></italic></color><italic>MacOS 9 is the current version of the =
Mac OS. I don't feel bad =
about</italic><color><param>0000,0000,0000</param>
<italic></italic></color><italic>telling people to upgrade. I'm =
planning on upgrading my machine =
this</italic><color><param>0000,0000,0000</param>
<italic></italic></color><italic>weekend. =
:-)</italic><color><param>0000,0000,0000</param>
<italic></italic></color><italic>MacOS 9 continues to be case =
insensitive, IMHO the only way a file =
system</italic><color><param>0000,0000,0000</param>
<italic></italic></color><italic>should =
work.</italic><color><param>0000,0000,0000</param>
<italic></italic></color><italic>I assume in the BSD mode, MacOsX is =
case sensitive like all Unixen.
</italic>Depends on the filesystem in effect on the particular =
drive/partition. HFS filesystems are case-insensitive, UFS filesystems =
are case-sensitive. I understand that there have been several =
knock-down,drag-out fights at Apple over this.
<color><param>0000,0000,0000</param>
<italic></italic></color><italic>However, when seen through the =
Macintosh SystemX finder, it will have to =
be</italic><color><param>0000,0000,0000</param>
<italic></italic></color><italic>case insensitive to maintain =
compatibility.</italic><color><param>0000,0000,0000</param>
We shall see.
-jcr
--Apple-Mail-1788819587-3--