Re: sshfs and permissions of /dev/fuse
On Sat, Feb 23, 2008 at 11:02:53 -0800, Amit Uttamchandani wrote:
> >
> > Do you have "fuse-utils" installed? /dev/fuse is meant to be created with
> > ownership root:fuse, so the fuse group has to exist on your system. If I
> > remember correctly, this group is created by the post-installation script of
> > fuse-utils.
> >
> > You can check if your system has the fuse group:
> >
> > $ grep fuse /etc/group
> > fuse:x:115:
> >
>
> Thank you for replying.
>
> Yes my system does have the fuse group. Running the above command I get
>
> fuse:x:111:amit
That should be OK, I think.
> I added my username 'amit' to that group as per instructions in the
> previous post in the thread. I guess I am unsure as to how to properly
> use fuse+sshfs. Here are some notes that might of interest:
>
> * Install of fuse-utils, sshfs was successful.
>
> * The only error message I got was using module-assistant to install
> the fuse kernel module. I guess it wasn't really necessary to install
> the kernel module fuse since it looks like the debian etch kernel
> already has it?
The 2.6.18 images have fuse.ko included. However, we should make sure
that your experiment with module-assistant has not left behind an
additional - possibly broken - fuse module. Run
find /lib/modules/$(uname -r) -name fuse.ko
and verify that it only lists one file:
/lib/modules/<YOUR_KERNEL_VERSION>/kernel/fs/fuse/fuse.ko
> * I create a directory in my home folder called 'mnt_ssh'
>
> * I run the command sshfs <myusername>@<host> mnt_ssh
> - I get this error: fusermount: failed to open /dev/fuse: No such file or directory.
>
> * I try to run the above command with sudo and I get the same error.
>
> * Sure enough /dev/fuse does not exist.
>
> * Now here comes the interesting part. At one point, after I rebooted
> I decided to just check on /dev/fuse and it did exist! So I guess
> udev created it but I'm not sure what I did to get it created.
>
> I am sure I am missing something quite simple here.
Try "modprobe -v fuse" (unload the module first if it is already
loaded). This should create /dev/fuse or give you an error message. For
comparison, here is what happens on my system (I remove the module first
to illustrate how the device node is created):
# ls -l /dev/fuse
crw-rw---- 1 root fuse 10, 229 2008-02-23 20:16 /dev/fuse
# modprobe -r fuse
# ls -l /dev/fuse
ls: cannot access /dev/fuse: No such file or directory
# modprobe -v fuse
insmod /lib/modules/2.6.24-flo/kernel/fs/fuse/fuse.ko
# ls -l /dev/fuse
crw-rw---- 1 root fuse 10, 229 2008-02-23 20:17 /dev/fuse
Another thing to check is fusectl:
$ mount | grep fuse
fusectl on /sys/fs/fuse/connections type fusectl (rw)
If that is missing for you, try to run
invoke-rc.d fuse start
or
invoke-rc.d fuse restart
--
Regards, | http://users.icfo.es/Florian.Kulzer
Florian |
Reply to: