In message <[EMAIL PROTECTED]> on Thu, Apr 29, 2004 at 12:10:52PM +0800, Craig Ringer wrote: > On Thu, 2004-04-29 at 11:48, Mark Secker wrote: > > CD /volumes/<name of mounted ipod image> > > CP -R iPod_Control /Volumes/<name of reset iPod> > Perhaps tcsh under OSX does things differently, but on most systems > commands are case sensitive,
This is actually a very interesting scenario. The short of it is: 'CD' should /not/ work, while 'CP' /should/. Reasons as follows: For CP, the behaviour will be highly sensitive to how your shell performs in a situation that its author had not anticipated: namely, that of a case-insensitive filesystem. 'CP' /should/, by rights, work under Mac OS X machines with HFS+ filesystems because 'CP' is a valid match for any files that is named 'cp'. /However/, most shells use a 'hashing' mechanism to avoid trawling through the entire contents of $PATH every time you issue a command. In these circumstances, the behaviour can vary. But, 'CP' /should/ really work. For CD, the situation is entirely different. 'cd' is not the name of a programme on your disk, it is the name of your shell's 'built-in' command. Since built-in commands are not stored on the filesystem, they are not case-insensitive like HFS+ is (unless the shell author has anticipate the need -- unlikely for UNIX shells). Therefore, 'CD' will probably fail.
