Not likely to be a common problem for most I know, but a lesson in how file permissions can restrict the execution of things under OSX nonetheless. Depending on what the group has to say, it may also prove useful to those who like to partition their HD and give common names to their volumes.
Volumes under OS X can either be mounted as 'respecting (UNIX) privileges' or 'ignoring privileges'. So HFS+ volumes that don't have appropriate Unix privileges set up are mounted as 'ignoring privileges' whereas a drive set up from OS X would probably be mounted as 'respecting privileges'.
There do seem to be problems under OS X with filenames, and there have been reports of problems with volumes named "Applications" (or "Users") reported on Macintouch (for example, if you have brackets in the Eudora filename, you can't make it the default mail handler application). There are problems reported by people who have spaces or asterisks in their passwords.
This is most probably because the Unix underpinnings of OS X still have to come to terms with the fact that users might want to put spaces, punctuation or other things into their file names or other things. And also because Unix relies on pathnames, rather than Mac OS's volume ID's and FSSpecs. That's what you get when Apple attempts to replace the Mac 's 1980-2000 based technologies with Unix's 1960's based technology (or if you prefer, 'merge' the 1960's Unix with the 1980's Mac technologies).
Of course which technologies wind up winning remains to be seen. This will also probably wind up determining how usable Mac OS X becomes.
Have fun, Shay -- =========================== Shay Telfer ================================ Perth, Western Australia Technomancer Sponsor WA's Solar Car Opinions for hire [POQ] Sungroper [EMAIL PROTECTED] fnord <http://sungroper.asn.au/>
