On Sat, 2003-11-15 at 15:43, Christopher Faylor wrote: > Yes, I've already (obviously?) been to SUSv3. I wasn't talking about > standards. I was talking about common practice. > > If you have a common practice web site that you want to show me then > that might be a convincing argument. Otherwise, I'll have to fall back > on my personal UNIX experience.
http://zebra.fh-weingarten.de/~maxi/html/mplayer-dev-eng/2003-04/msg00600.html Part of a thread on this in another project. Seems like the hurd follows the no-PATH_MAX, use pathconf() always approach. Which means that everything thats portable to the hurd, will Do The Right Thing, if we eliminate the PATH_MAX and MAXPATHLEN defines. In my digging, I found that PATH_MAX, if defined, MUST be the largest path length possible. Presumably thats so that programs with static buffers won't run into trouble. Either way(increase PATH_MAX or remove it), to support longer paths, we'll need to make the change and transition to it. So, as I see it the question for you is : which route do you prefer? Rob -- GPG key available at: <http://www.robertcollins.net/keys.txt>.
signature.asc
Description: This is a digitally signed message part