After a little research, I'm wondering if this is an issue (although
maybe not a bug?) with mount, and not fuse. From 'man mount':
When the proc filesystem is mounted (say at /proc), the files
/etc/mtab and /proc/mounts have very similar contents. The
former has somewhat more information, such as the mount options
used, but is not necessarily up-to-date (cf. the -n option
below). It is possible to replace /etc/mtab by a symbolic link
to /proc/mounts, and especially when you have very large
numbers of mounts things will be much faster with that symlink,
but some information is lost that way, and in particular
working with the loop device will be less convenient, and using
the "user" option will fail.
The last line says that with /etc/mtab as a symlink to /proc/mounts,
the "user" option will fail. I assume that fuse mounts have an
implict "user" option? The strange thing is that 'mount' works fine,
while it is 'umount' that fails. I have confirmed this same behavior
with a normal filesystem, ie. a local ext3 filesystem specified with
the "user" option in /etc/fstab is mountable but not unmountable by a
regular user when /etc/mtab is a symlink to /proc/partitions.
I clearly don't understand what all the issues here are, but I thought
I would at least point this out.
jamie.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
