|
From: <ke...@et...> - 2003-07-15 16:35:58
|
>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. I think handling the absolute path in the normal way will give you the error message you want anyway. It will fail when an open of the new pathname is attempted. You don't have to craft an error message for the case where the link starts with /. Security is unchanged. And someone might possibly have a use for it if they understand where the root of is when viewed from the client (like in LTSP, which has dangling symlinks when viewed from the server). ln -s /foo bar does work even if /foo doesn't currently exist. |
