Date: Sat, 16 Jun 2001 11:45:33 -0700 (PDT) From: Matt Dillon <dillon@earth.backplane.com> To: Poul-Henning Kamp <phk@critter.freebsd.dk> Cc: Jordan Hubbard <jkh@osd.bsdi.com>, bde@zeta.org.au, steveo@eircom.net, david@catwhisker.org, current@FreeBSD.ORG Subject: Re: symlink(2) [Was: Re: tcsh.cat] Message-ID: <200106161845.f5GIjXl01077@earth.backplane.com> References: <89423.992715599@critter>
next in thread | previous in thread | raw e-mail | index | archive | help
:...
:>
:>True. It would break phk's malloc debugging features to disable this,
:>for example.
:
:Not only that, but considerning that a symlink can point into a
:different filesystem even in normal use, there is no simple way to
:validate the valididty of the name.
... or be associated with a chroot situation and simply not resolve
when accessed outside of the chroot. At BEST we had symlinks on the
server that crossed NFS boundries on the client, for example. From
the server's point of view they went off into empty space.
Or a thousand other things.
We should let this this thread die now. I think it's fairly clear
that symlinks should not be messed with. cp's handling of symlinks
is another, unrelated matter.
-Matt
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?200106161845.f5GIjXl01077>