:>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.


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

Reply via email to