Re: [RFC] fhandle implementation.
On Friday June 16, [EMAIL PROTECTED] wrote: > > On Fri, 16 Jun 2000, Neil Brown wrote: > > > knfsd can get answers to such questions as: > > > > > >- can you support NFSD_FH_LOCATABLE > > >- is file name comparison case insensitive (will be needed for NFSv4) > > Sorry, but does it mean that NFSv4 passes (by standard definition) > filenames only in UTF8 (or another Unicode encoding)? Check out draft-ietf-nfsv4-06.txt on your local IETF mirror, but yes, NFSv4 uses UTF8 for all file names (and owner and owner_group). It also defines two per-filesystem attributes: case_insensitive 16 booleanREAD Are filename comparisons on this file system case insensitive? case_preserving17 booleanREAD Is filename case on this file system preserved? though I am not certain that UTF8 has a well defined concept of case - there was some discussion about this on nfsv4-wg mailing list a while back, but I didn't pay very close attention. NeilBrown
Re: [RFC] fhandle implementation.
> On Fri, 16 Jun 2000, Neil Brown wrote: > > knfsd can get answers to such questions as: > > > >- can you support NFSD_FH_LOCATABLE > >- is file name comparison case insensitive (will be needed for NFSv4) Sorry, but does it mean that NFSv4 passes (by standard definition) filenames only in UTF8 (or another Unicode encoding)? Or means this that both client and server must use same codepage? And how is resolved if there are two names in underlying exported directory which match except for case? Netware uses huge and complicated code to generate unique names and stores these names in their own namespaces (NFS = 255 chars, case sensitive; LONG = 255 chars, case insensitive; MAC = 31 chars, case ??; DOS = 14 chars, uppercase; FTAM = 254 chars, lowercase only; of course each namespace has different set of reserved characters, "*" from NFS is translated as "STRANGE" to other namespaces... do we really want this) :-( Thanks, Petr Vandrovec [EMAIL PROTECTED]
