maurilio longo wrote: >> Maurilio Longo wrote: >>> Alan M Wright wrote: >>>> Nicolas Williams wrote: >>>>> On Wed, Mar 05, 2008 at 03:09:22PM -0800, Alan M Wright wrote: >>>>>> Nicolas Williams wrote: >>>>>>> Should a CR be filed against mv(1) here? Or an RFE for an option to it >>>>>>> that obviates the identical file check, at least on case-insensitive >>>>>>> file systems? >>>>>> Fromm an mv perspective this is indistinguishable from >>>>>> having multiple links to a file. >>>>> nit: not if the link count is 1 :) >>>> So ... it would be unfortunate if the thing you wanted >>>> to rename was a directory. >>>> >>> Maybe I'm making the whole thing easier than it is, but could mv test for >>> the >>> case sensitivness of the underlaying filesystem and if it insensitive (which >>> on solaris can be) do a case sensitive comparison of its parameters ( foo >>> and >>> Foo ) and if they are different, while pointing to the same inode, change >>> them? >>> >>> This should solve the case even if it is the name of a directory. >> Without a new command line option, that's not a good idea because >> mv would behave differently dependent on the underlying file system >> and scripts that rely on the mv exit status could break. >> > > A script or program that relies upon a case sensitive filesystem could face > bigger > problems than mv not changing a file name. > I think that now that zfs can have a case insensitive mode all the programs > which > can be executed on such a filesystem need to be aware of this fact.
Mixed-mode was intended to deal with such issues. Mixed-mode allows application specific behavior, i.e. mv(1) will perform case-sensitive operations and the CIFS service will perform case-insensitive operations. On a mixed-mode file system, 'mv foo Foo' will change the on-disk name. >> If the file system is case-insensitive, why do you care about the >> on-disk case? And if you do care, it's easy to change it. > > I care because mylasttriptoeurope.doc is uglier than MyLastTripToEurope.doc > (at least for me :)). No problem -> mixed-mode. > But mv is not my real concern, it was just an example, I was looking for a way > to use samba (not Sun's CIFS server) on such a filesystem to overcome the way > samba emulates case-insensitiveness on a case-sensitive filesystem. > > From a windows pc, a samba share upon such a filesystem works wonderfully, > but you cannot change the case of a filename, this fact started this thread > for me. > > So, while I'm aware that it is samba which should be changed to use such a > kind > of filesystem (maybe it was already changed to work on mac os x), samba is just > a program, like mv, which needs to be made aware that it is running on a case > insensitive filesystem. Not necessarily, some commands are subject to POSIX requirements. Alan _______________________________________________ storage-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/storage-discuss
