This is the mail archive of the
libc-alpha@sources.redhat.com
mailing list for the glibc project.
Re: [patch] manual/conf.texi, sync _POSIX_PATH_MAX with header value
- To: GNU C Library <libc-alpha at sourceware dot cygnus dot com>
- Subject: Re: [patch] manual/conf.texi, sync _POSIX_PATH_MAX with header value
- From: Mark Brown <broonie at sirena dot org dot uk>
- Date: Tue, 9 Jan 2001 17:16:41 +0000
- References: <20010108194024.A10073@visi.net>
On Mon, Jan 08, 2001 at 07:40:24PM -0500, Ben Collins wrote:
> @comment POSIX.1
> @item _POSIX_PATH_MAX
> The most restrictive limit permitted by POSIX for the maximum number of
> -bytes in a file name. The value of this constant is @code{255}.
> +bytes in a file name. POSIX defines this to be no less than 255. In
> +the GNU C library, the value of this constant is @code{256}.
What prompted this patch was a bug report from me complaining that POSIX
(or at least, SUS2) requires that _POSIX_PATH_MAX be exactly 255. The
relevant ChangeLog entry that Ben dug out was:
| 2000-04-30 Andreas Jaeger <aj@suse.de>
|
| * posix/bits/posix1_lim.h (_POSIX_PATH_MAX): Increase to 256 in
| accordance with Austin Draft.
which seems to indicate that this has been done in order to conform to
an upcoming version of the standard, which isn't what the above patch
says. I'm somewhat mystified as to why such a change would be made,
though.
--
Mark Brown mailto:broonie@tardis.ed.ac.uk (Trying to avoid grumpiness)
http://www.tardis.ed.ac.uk/~broonie/
EUFS http://www.eusa.ed.ac.uk/societies/filmsoc/