[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... :-) ) ? :-) > but there are quite a few > things that make this less of an issue: many standards are stretching > the boundaries of pathnames which can be returned and used beyond > PATH_MAX. Yes, but that doesn't really help if the primary interfaces like the shells have hardcoded limits (AFAIK /usr/bin/sh and ksh88 have this problem, ksh93 no longer uses |PATH_MAX| except in the case of |readlink()|). AFAIK PATH_MAX can be handled per filesystem (e.g $ getconf PATH_MAX /tmp #), right ? ---- Bye, Roland -- __ . . __ (o.\ \/ /.o) [EMAIL PROTECTED] \__\/\/__/ MPEG specialist, C&&JAVA&&Sun&&Unix programmer /O /==\ O\ TEL +49 641 7950090 (;O/ \/ \O;) _______________________________________________ opensolaris-code mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/opensolaris-code
