Joerg Schilling writes:
> Ienup Sung <[EMAIL PROTECTED]> wrote:
>
> > I'm afraid that might not be possible due to I'm quite sure
> > many people wouldn't like the change of the max name length.
>
> In general, programs that do not deal with this are either completely broken
> or
> do not yet follow POSIX rules to call pathconf(name, _PC_NAME_MAX)
> for a correct value.
There are at least two problems with that position:
1. MAXNAMELEN is a #define, which means that it has been compiled
into applications for _decades_; well before there was any such
thing as POSIX or pathconf().
2. Solaris is intentionally backwards-compatible. You can't break
existing applications. Returning a path component that causes an
application -- even a "non-POSIX" one -- to scribble outside of
compiled-in array bounds would be an incompatible change.
I'm not wild about the design implications of MAXPATHLEN or
MAXNAMELEN, but I think the evaluation of whether we can alter or
abolish them needs to be a bit deeper than just asking "is it POSIX?"
--
James Carlson, KISS Network <[EMAIL PROTECTED]>
Sun Microsystems / 1 Network Drive 71.232W Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677
_______________________________________________
opensolaris-discuss mailing list
[email protected]
