Date: Mon, 18 Jun 2001 11:53:59 -0400 (EDT) From: Garrett Wollman <wollman@khavrinen.lcs.mit.edu> To: Bruce Evans <bde@zeta.org.au> Cc: current@FreeBSD.ORG, FreeBSD-standards@bostonradio.org Subject: Re: Ok, try this patch. (was Re: symlink(2) [Was: Re: tcsh.cat]) Message-ID: <200106181553.LAA56935@khavrinen.lcs.mit.edu> In-Reply-To: <Pine.BSF.4.21.0106181454450.6291-100000@besplex.bde.org> References: <200106180149.f5I1nma09752@earth.backplane.com> <Pine.BSF.4.21.0106181454450.6291-100000@besplex.bde.org>
next in thread | previous in thread | raw e-mail | index | archive | help
<<On Mon, 18 Jun 2001 15:40:23 +1000 (EST), Bruce Evans <bde@zeta.org.au> said: > NetBSD committed essentially this patch 4 years ago (as part of rev.1.23). > I like it, except it seems to be incompatible with POSIX.1-200x. I think I agree with your interpretation. Quoting from XBDd7, page 101, lines 3153ff: # In all other cases, the system shall prefix the remaining pathname, # if any, with the contents of the symbolic link. [...] [T]he # resolved pathname shall be the resolution of the pathname just # created. If the resulting pathname does not begin with a slash, the # predecessor of the first filename of the pathname is taken to be the # directory containing the symbolic link. So, if we have a symbolic link ``foo'' with contents ``'' (i.e., the empty string): Pathname Resolves to ./foo ./foo (i.e., the link itself), iff condition 3 on lines 3151-2 is met; otherwise [ENOENT] ./foo/ / ./foo/bar /bar -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?200106181553.LAA56935>