"Bernhard R. Link" <brlink@xxxxxxxxxx> writes: > http://www.opengroup.org/onlinepubs/009695399/basedefs/xbd_chap03.html#tag_03_266 > > | 3.266 Pathname > | > | A character string that is used to identify a file. In the context of > | IEEE Std 1003.1-2001, a pathname consists of, at most, {PATH_MAX} bytes, > | including the terminating null byte. It has an optional beginning > | slash, followed by zero or more filenames separated by slashes. A > | pathname may optionally contain one or more trailing slashes. > | Multiple successive slashes are considered to be the same as one > | slash. Which is a bit stale, and there is an update that is crucial when discussing the issue that is the topic of this thread. Try this one instead, especially the last ", except for" which is an important clarification. http://www.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap03.html | 3.266 Pathname | | A character string that is used to identify a file. In the context of | POSIX.1-2008, a pathname may be limited to {PATH_MAX} bytes, including the | terminating null byte. It has an optional beginning <slash>, followed by | zero or more filenames separated by <slash> characters. A pathname may | optionally contain one or more trailing <slash> characters. Multiple | successive <slash> characters are considered to be the same as one | <slash>, except for the case of exactly two leading <slash> characters. And 4.12 in the same issue of POSIX says pathnames with exactly two leading slashes may be handled in an implemenation defined manner (i.e. three or more means the same thing as a single slash). Confusing ;-) -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html