On Sat, Feb 23, 2008 at 02:14:46 +0100, Vincent Lefevre wrote:
On 2008-02-22 18:57:31 +0100, Florian Kulzer wrote:
Do you have fuse-utils installed?
Since sshfs depends on fuse-utils, I suppose that Amit has fuse-utils
installed.
What I meant was: Did fuse-utils install successfully or did
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:
$
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
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:
On Sat, Feb 23, 2008 at 14:03:53 -0800, Amit Uttamchandani wrote:
[...]
Try modprobe -v fuse (unload the module first if it is already
loaded). This should create /dev/fuse or give you an error message.
[...]
Ok that worked. I was able to load the fuse module and running ls -l
lists
On Sat, 23 Feb 2008 23:52:15 +0100
Florian Kulzer [EMAIL PROTECTED] wrote:
Don't worry about this, the fuse initscript does not exist in Etch. (I
forgot to check that before I sent my previous message. I run Sid.)
Can you use sshfs after you modprobe the fuse module? If so then you can
On Thu, Feb 21, 2008 at 21:46:59 -0800, Amit Uttamchandani wrote:
On Wed, 20 Feb 2008 21:42:18 +0100 Vincent Lefevre wrote:
On 2008-02-19 01:02:39 -0800, Amit Uttamchandani wrote:
I recently installed sshfs on this etch system using aptitude
install sshfs. I am having the same problem
On 2008-02-22 18:57:31 +0100, Florian Kulzer wrote:
Do you have fuse-utils installed?
Since sshfs depends on fuse-utils, I suppose that Amit has fuse-utils
installed.
--
Vincent Lefèvre [EMAIL PROTECTED] - Web: http://www.vinc17.org/
100% accessible validated (X)HTML - Blog:
have you add the user into fuse group?
Vincent Lefevre [EMAIL PROTECTED] wrote: On 2008-02-22 18:57:31 +0100,
Florian Kulzer wrote:
Do you have fuse-utils installed?
Since sshfs depends on fuse-utils, I suppose that Amit has fuse-utils
installed.
--
Vincent Lefèvre - Web:
100% accessible
On Wed, 20 Feb 2008 21:42:18 +0100
Vincent Lefevre [EMAIL PROTECTED] wrote:
On 2008-02-19 01:02:39 -0800, Amit Uttamchandani wrote:
I recently installed sshfs on this etch system using aptitude
install sshfs. I am having the same problem you listed above.
However, I can't seem to find
On 2008-02-19 01:02:39 -0800, Amit Uttamchandani wrote:
I recently installed sshfs on this etch system using aptitude
install sshfs. I am having the same problem you listed above.
However, I can't seem to find /dev/fuse.
[EMAIL PROTECTED]:~$ ls -l /dev/fuse
ls: /dev/fuse: No such file or
On Thu, 14 Feb 2008 16:37:09 +0100
Vincent Lefevre [EMAIL PROTECTED] wrote:
I've installed fuse with module-assistant auto-install fuse.
Then, after loading the fuse module, I've tried sshfs, but I get
the following error:
fuse: failed to open /dev/fuse: Permission denied
Here /dev/fuse
On 2008-02-15 09:19:25 +0800, hhding wrote:
permission is right
you should add you to group fuse
OK, I've reported a bug against the sshfs documentation:
According to the sshfs documentation:
quote from /usr/share/doc/sshfs/README
Once sshfs is installed
should be added to group fuse also to be able to use sshfs?
(But isn't that a security problem because it gives the user
permissions for whole fuse, not just sshfs?)
* Bad /dev/fuse permissions (if there is no security concern with
fuse)?
* Bad /usr/bin/sshfs permissions? (i.e
the problem?
* Incomplete sshfs documentation which should say that the user
should be added to group fuse also to be able to use sshfs?
(But isn't that a security problem because it gives the user
permissions for whole fuse, not just sshfs?)
* Bad /dev/fuse permissions
the problem?
* Incomplete sshfs documentation which should say that the user
should be added to group fuse also to be able to use sshfs?
(But isn't that a security problem because it gives the user
permissions for whole fuse, not just sshfs?)
* Bad /dev/fuse permissions
16 matches
Mail list logo