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

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Reply via email to