Date: Mon, 18 Jun 2001 13:40:45 -0400 (EDT) From: Garrett Wollman <wollman@khavrinen.lcs.mit.edu> To: "Andrey A. Chernov" <ache@nagual.pp.ru> Cc: current@FreeBSD.ORG, FreeBSD-standards@bostonradio.org Subject: Re: Ok, try this patch. (was Re: symlink(2) [Was: Re: tcsh.cat]) Message-ID: <200106181740.NAA58004@khavrinen.lcs.mit.edu> In-Reply-To: <20010618213516.A7179@nagual.pp.ru> References: <200106180149.f5I1nma09752@earth.backplane.com> <Pine.BSF.4.21.0106181454450.6291-100000@besplex.bde.org> <200106181553.LAA56935@khavrinen.lcs.mit.edu> <20010618205944.A6595@nagual.pp.ru> <200106181722.NAA57757@khavrinen.lcs.mit.edu> <20010618213516.A7179@nagual.pp.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
<<On Mon, 18 Jun 2001 21:35:17 +0400, "Andrey A. Chernov" <ache@nagual.pp.ru> said: >> > ./foo/ .// >> > ./foo/bar .//bar >> >> No, because the ``resulting filename'' begins with a slash. > It seems resulting filename (pathname?) begins with "./" (not a slash). No, it doesn't. The ``resulting filename'' is "/" in the first case, and "/bar" in the second case. Both begin with a slash, and so are resolved relative to the root. There is no "./" involved anywhere in the process. The value of the symbolic link is not somehow inserted into the path being resolved. Once a symbolic link is encountered, pathname resolution *starts over* with the last directory searched in the old path used as the current working directory. -GAWollman To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200106181740.NAA58004>