On Wed, 16 Jul 2003, Ken Yap wrote:
> >The case I am making is that normally you don't export your root
> >file system from the server. Just like tftp where normally all that
> >is exported is /tftpboot. With nfs usually it is some subset of
> >the filesystem that is exported. Which is why I think handling absolute
> >paths in a way that gives a reasonable error message is much
> >preferable.
symlinks are a big problem no matter what you do. I can make a symlink to
another file system easily:
../../../../../../../somewhere_else/file
It can be the same as
/somewhere_file/file
This is a perfectly valid relative link that can go somewhere else.
I guess I don't see the problem with absolute links that relative links
really solves. Either way, if you talk to a server, and it can't resolve
the link, you'll get an error.
And let us not forget things like:
foo -> foo
A perfectly useless symlink, but relative and hence acceptable.
I'm not convinced that ruling out abs symlinks is really going to help you
much.
ron
|