Roland Mainz <[EMAIL PROTECTED]> wrote:
> [EMAIL PROTECTED] wrote:
> >
> > >[...]
> > >> Note that you cannot create such links in Solaris.
> > >
> > >Will NFS also enforce PATH_MAX on the value filled in by readlink()?
> > >Otherwise, even if one couldn't create such a link on Solaris, one might
> > >still be able to see one.
> >
> > NFS_MAXPATHLEN is the maximum lenght it wants (1024)
>
> 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.
PATH_MAX isnotthe problem as Solaris supports openat() since ~ 6.5 years.
The real problem with Solaris is that is only NAME_MAX to be 255 while I
already need 330 in order to fully support JOLIET in hsfs.
I did already propose to change the lookuppn() interface to allow NAME_MAX to be
as big as PATH_MAX. I hope there is a chance to get this done.
Jörg
--
EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin
[EMAIL PROTECTED] (uni)
[EMAIL PROTECTED] (work) Blog: http://schily.blogspot.com/
URL: http://cdrecord.berlios.de/old/private/ ftp://ftp.berlios.de/pub/schily
_______________________________________________
opensolaris-code mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/opensolaris-code
