Date: Sun, 17 Jun 2001 17:42:37 +0400 From: "Andrey A. Chernov" <ache@nagual.pp.ru> To: Bruce Evans <bde@zeta.org.au> Cc: Warner Losh <imp@harmony.village.org>, "Steve O'Hara-Smith" <steveo@eircom.net>, David Wolfskill <david@catwhisker.org>, current@FreeBSD.ORG Subject: Re: symlink(2) [Was: Re: tcsh.cat] Message-ID: <20010617174235.A49454@nagual.pp.ru> In-Reply-To: <Pine.BSF.4.21.0106172154520.582-100000@besplex.bde.org>; from bde@zeta.org.au on Sun, Jun 17, 2001 at 11:02:50PM %2B1000 References: <200106170518.f5H5I6V44586@harmony.village.org> <Pine.BSF.4.21.0106172154520.582-100000@besplex.bde.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Jun 17, 2001 at 23:02:50 +1000, Bruce Evans wrote: > > So disallowing null symlinks would actually unbreak /etc/malloc.conf. > > Further debugging shows that the main bug is in the kernel. > stat(2) on a null symlink bogusly succeeds and classifies the symlink > as a directory. ln(1) just believes this so it rewrites > "ln -fs aj /etc/malloc.conf" to "ln -fs aj /etc/malloc.conf/aj". > The kernel then resolves /etc/malloc.conf/aj to /aj. And this should be fixed, as I say from the very beginning. (strangely, most people here mistreat null symlinks we discuss as non-null symlinks with non-existen targets) -- 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?20010617174235.A49454>