According to Herbert Xu on 8/31/2009 6:18 AM:
> On Tue, Jul 14, 2009 at 09:39:03PM +0000, Eric Blake wrote:
>> Furthermore, POSIX requires that if the element in CDPATH ends in slash, that
>> no additional slashes are added while forming the candidate curpath. In light
>> of the fact that //home need not be the same directory as /home (and indeed, on
>> cygwin, they are distinct entities), this is also a bug:
>
> Can you quote where POSIX says this?
Which version of POSIX are you looking at? POSIX 2008 added quite a few
clarifications about the handling of // that were not listed in POSIX 2001.
http://www.opengroup.org/onlinepubs/9699919799/utilities/cd.html
"5. Starting with the first pathname in the <colon>-separated pathnames of
CDPATH (see the ENVIRONMENT VARIABLES section) if the pathname is
non-null, test if the concatenation of that pathname, a <slash> character
if that pathname did not end with a <slash> character, and the directory
operand names a directory."...
In other words, if CDPATH is "/", then you should not append any
additional <slash> characters, such that you end up checking for the
existence of "/foo", not "//foo".
--
Don't work too hard, make some time for fun as well!
Eric Blake ebb9@xxxxxxx
--
To unsubscribe from this list: send the line "unsubscribe dash" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
[LARTC]
[Bugtraq]
[Yosemite Forum]
[Photo]