Date: Mon, 18 Jun 2001 13:54:27 -0400 (EDT) From: Garrett Wollman <wollman@khavrinen.lcs.mit.edu> To: Matt Dillon <dillon@earth.backplane.com> Cc: current@FreeBSD.ORG, FreeBSD-standards@bostonradio.org Subject: Re: Ok, try this patch. (was Re: symlink(2) [Was: Re: tcsh.cat]) Message-ID: <200106181754.NAA58174@khavrinen.lcs.mit.edu> In-Reply-To: <200106181746.f5IHkRE16410@earth.backplane.com> 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> <200106181740.NAA58004@khavrinen.lcs.mit.edu> <200106181746.f5IHkRE16410@earth.backplane.com>
next in thread | previous in thread | raw e-mail | index | archive | help
<<On Mon, 18 Jun 2001 10:46:27 -0700 (PDT), Matt Dillon <dillon@earth.backplane.com> said: > In anycase, I can't imagine that POSIX actually intended null > symlinks to act in any particular way The standard specifies precisely how pathname resolution is supposed to behave. FreeBSD should conform to the standard, even if some of the consequences are somewhat unexpected. (At least the semantics are consistent!) -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?200106181754.NAA58174>