Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!


why??? | 19 comments | Create New Account
Click here to return to the 'why???' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
why???
Authored by: Craigthulu on Oct 28, '03 07:52:56AM
Since Windows 95 it has been case sensitive. And there were extensions from third parties that allowed earlier versions do long file names and case sensitivity.

The one thing I dislike about OSX is that it is case insensitive.

I would also like to know why you think the difference between MyDocument and mydocument is "annoying and confusing"? (Other than a bad naming convention).

[ Reply to This | # ]

why???
Authored by: Alrescha on Oct 28, '03 09:31:20AM

maybe your Windows 95 is case sensitive, but mine is not. Nor is my copy of Windows 2000 ('my documents' and 'My Documents' are the same place).

I'm more annoyed by the fact that it's different from machine to machine. I've started to fix this by getting rid of the non-Mac machines... :-)

A.



[ Reply to This | # ]
why???
Authored by: vladimus on Oct 28, '03 02:53:34PM
mine is not. Nor is my copy of Windows 2000 ('my documents' and 'My Documents' are the same place)

Um, "My Documents" and "my documents" being in the same place would make your copy of Windows case-sensitive. Confusing, huh?

[ Reply to This | # ]

What does case sensitive mean?
Authored by: paulio on Oct 28, '03 03:56:19PM

Sorry, I think you missed the point.

Windows 95 does NOT have a case sensitive file system. Neither does NT, Windows 2000, Windows XP, Mac OS 9, or Mac OS X 10.1 thru 10.2.

However, all the above allow you to type in uppper and lower case in filenames. The thing is that the filesystem is NOT case sensitive.



[ Reply to This | # ]
case-aware != case-sensitive
Authored by: Anonymous on Dec 08, '03 03:40:13PM

No. FAT and FAT32 filesystems (and NTFS, for that matter) are exactly like default HFS+: case-aware, but not case-sensitive.

You cannot create two files, "FOO" and "Foo", in the same directory on any of these filesystems.

Having a case-sensitive option for HFS+ is an absolute must-have for real OS X servers.

It's also handy for those of us who like to layout CD-Rom images prior to burning. Some CDs I produce have directories like "index" in the same directory as a file named "INDEX". Have to build those on my BSD box.

No, it is not an option to change the names of these files or directories. In this case the underlying system needs to change to support the workflow, not the other way around.

[ Reply to This | # ]