Hello, On Mon, Aug 25, 2008 at 10:31 PM, <[EMAIL PROTECTED]> wrote:
> On Sat, Aug 23, 2008 at 12:30:56PM +0300, Sergiu Ivanov wrote: > > What I wanted to say was that netfs_S_dir_lookup does not give the > > client retry notifications in case it encounters a symlink (except for > > the special case when the path is absolute), and symlinks are > > translators. Probably, we shouldn't return retry notifications either > > in case we encounter translators... > > Ah, I think I see now what you mean. It's not really comparable, though. > "Normal" filesystem translators actually implement the filesystem that > stores the symlink -- while the proxy only exposes the underlying > filesystem. > > Note that the symlink translator exsists for the sake of filesystems > that do not know about symlinks (fatfs for example), or to allow setting > them as active translators on a readonly filesystem. In normal cases > (like ext2), the symlinks are handled specially by the FS server instead. > > If you look up a symlink on a file system that doesn't natively suppport > symlinks, it will handle it like any other active translator, i.e. it > should give you a retry notification. > Ah, I see... I wasn't aware of this thing. Thanks a lot for the explanation! scolobb
