On Fri, Mar 11, 2005 at 01:48:30PM -0800, gary ng wrote:
> While the dependency has changed back to fuse-utils
> 1.3-1, the calling parameter in mount.gmailfs seems to
> be changed to the newer version so it gives a unknown
> option with fuse-util 1.3-1(fusermount).
Works fine for me, with fuse-utils 1.3.-1: in 0.3-7, I have
specifically reverted my patch to mount.gmailfs so it works with
fusermount 1.3:
========================================================================
~/test # dpkg -l fuse-utils | G ii
ii fuse-utils 1.3-1 Filesystem in USErspace (utilities)
~/test # dpkg -l gmailfs | G ii
ii gmailfs 0.3-7 Use your GMail account as a filesystem
~/test # sudo which fusermount
/usr/bin/fusermount
~/test # sudo fusermount -h
fusermount: [options] mountpoint [program [args ...]]
Options:
-h print help
-u unmount
-p check default permissions on files
-c cache in kernel space if possible
-x allow other users to access the files (only for root)
-n name add 'name' as the filesystem name to mtab
-l issue large reads
-q quiet: don't complain if unmount fails
~/test # G fusermount /sbin/mount.gmailfs
os.system("fusermount -n gmailfs -l -c -x '%s' '%s' '%s' '%s'" %
(mountpoint, pyfile, mountpoint, odata) )
~/test # s mount.gmailfs none /mnt -o username=xxxx,password=xxxx,fsname=xxxx
gmailfs.py:Gmailfs:mountpoint: '/mnt'
gmailfs.py:Gmailfs:unnamed mount options: []
gmailfs.py:Gmailfs:named mount options: {'username': 'xxxx', 'password':
'xxxx', 'fsname': 'xxxx'}
INFO:gmailfs:Connected to gmail
========================================================================
So my take on your problem is that you have the 2.x fusermount
somewhere in your PATH (/usr/local/bin/ comes to mind), that takes
precedence over the fusermount provided by fuse-utils 1.3-1;
fusermount 2.x doesn't want all those options, for instance -n is now
deprecated.
In any case, the fusermount call in mount.gmailfs is definitely a
valid call to fusermount 1.3, as shown above in the "fusermount -v"
output.
> I believe this bug should be re-opened or a new one
> assigned. Basically, the current gmailfs needs the
> newer fuse-utils, just blindly changes the dependency
> back is plain wrong.
May I suggest you throroughly test your setup before you judge others'
work ?
Let me know if you still can't get gmailfs 0.3-7 to work on sarge,
with the indications I gave above.
Cheers,
--Seb
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
