Date: Sun, 17 Jun 2001 23:14:19 +0400 From: "Andrey A. Chernov" <ache@nagual.pp.ru> To: Jordan Hubbard <jkh@osd.bsdi.com> Cc: bde@zeta.org.au, imp@harmony.village.org, steveo@eircom.net, david@catwhisker.org, current@FreeBSD.ORG Subject: Re: symlink(2) [Was: Re: tcsh.cat] Message-ID: <20010617231418.A60728@nagual.pp.ru> In-Reply-To: <20010617113141A.jkh@osd.bsdi.com>; from jkh@osd.bsdi.com on Sun, Jun 17, 2001 at 11:31:41AM -0700 References: <200106170518.f5H5I6V44586@harmony.village.org> <Pine.BSF.4.21.0106172154520.582-100000@besplex.bde.org> <20010617113141A.jkh@osd.bsdi.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Jun 17, 2001 at 11:31:41 -0700, Jordan Hubbard wrote: > It seems your argument to disallow null symlinks got somehow taken > as an argument to disallow all "invalid" symlinks then. To say it more clear: now I even not against ""-symlinks making ability, such strings are valid per POSIX after all, as already noticed in this discussion. I am against _resolving_ them to illegal "" name (and to "." in pathnames) which cause all errors that Bruce describe. -- Andrey A. Chernov http://ache.pp.ru/ 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?20010617231418.A60728>