On Mar 17, 2007, at 5:05 AM, Roland Mainz wrote:
[EMAIL PROTECTED] wrote:
Somehow I wish both Solaris and NFS would use a longer value for
paths... IMO it will hurt some day if multibyte locales will
become more
widespead. Short: In a multibyte locale one character may occupy
multiple bytes - which means the maxmimum number of useable
_characters_
in a path depends on the encoding+characters being used. A limit
of 1024
bytes therefore result in an effective character length limit of
around
250 characters (assuming UTF-8 encoding and lots of characters
outside
the BMP plane) which may be too small for some applications/
languages
(e.g. Hindi _may_ be affected), other operating systems seems to
be in a
better position here, e.g. Linux has a PATH_MAX of 4096.
There is not much we can do to change it,
What about writing a note that the next major version of NFS (NFSv5)
should address this problem and allow at least 1024 _characters_
(which
translates more or less to ((MB_LEN_MAX+1)*1024) _bytes_, e.g. 6144
bytes for MB_LEN_MAX==5 ... but I guess a choice of 8192 may be
better,
just to be on the safe side for the next couple of decades... :-) ) ?
NFSv3 and NFSv4 place no limits on the length of component names or
symbolic link contents. The limits are decided upon by the
client and server operating environments.
The standards are flexible and need no work from the over-the-wire
perspective.
Spencer
_______________________________________________
opensolaris-code mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/opensolaris-code
