Maurilio Longo wrote: > Alan M Wright wrote: >> [...] >> >> Feel free to raise the RFE but (my opinion) I don't think changing >> mv(1) to allow this by default is a good idea. What do you do on >> mixed-mode file systems, would mv(1) take the case-sensitive or the >> case-insensitive perpspective? Even if you add a new flag, you >> would still have caveats - perhaps better to create a new command. >> > Alan, out of curiosity, why do you have an insensitive and a mixed flavour of > zfs and not just the insensitive (preserving) one? I mean, to share it with > CIFS why was the mixed one created/needed?
Mixed-mode allows NFS and local operations to behave as expected (they see a case-sensitive file system), while allowing the CIFS service to operate in a case-insensitive way. For file sharing across local users, NFS and CIFS clients, I think this provides the "least surprise" option. For example, in mixed-mode, you wouldn't have encountered the mv(1) issue that we were discussing. Since we were adding mixed-mode, it seemed reasonable to offer a fully case-insensitive option. There may be times when it is appropriate (perhaps in a Windows/MacOS only client environment) but, for most environments, I would expect mixed-mode to provide the expected behaviour. Alan _______________________________________________ storage-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/storage-discuss
