Re: symlink(2) [Was: Re: tcsh.cat]

[Matt Dillon]

: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

    This is a reasonable distinction to make.  If someone actually tried to
    open() a ""'d symlink an argument can be made to return a specific error
    rather then trying to resolve it.  I'm not sure it's worth it, though.
    It just doesn't come up that often and there are a thousand other ways you
    can hogtie yourself in the system that takes less effort.

                                        -Matt


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