#26 shfs doesn't report itself as a networked filesystem

[Anonymous]

After looking though most of the bugs listed on this
tracker, I think the major problem with shfs is that it
doesn't report itself as a networked file system to the
kernel.

The kernel's VFS layer has different ways of handeling
data, cache and input/output for networked/remote file
systems vs local file system mounts. NFS, smbfs, etc
all indicate to the kernel that they are networking
file system.

Also when most linux operating systems boot, they'll
attempt to mount everything in /etc/fstab that's local,
then start networking, and then mount remote shares
such as nfs, afs and smbfs. shfs file systems listed in
fstab attempt to mount before networking is setup which
is another indication that shfs needs to indicate to
the kernel that it is infact a networked filesystem.

Emacs and nautilus also handle networked file systems
differently when writing to them. With shfs, nautilus
will often hang when trying to move a file to a remote
mount.

I don't know very much about the kernel VFS layer so I
really have no idea to how to about doing this, but it
shouldn't be very difficult.

-Sumit
SKhanna21@tntech.edu

[Nobody/Anonymous]

Logged In: NO

Is this bug going to be fixed? I causes quite a lot of trouble.

Here is the related Gentoo bugzilla entry:
http://bugs.gentoo.org/show_bug.cgi?id=74867