fusermount requires fuse module kernel to be loaded, isn't done automagically

[Patrick McFarland]

Currently, the fuse-utils package is correctly setup to allow the admin of the machine to add users to the fuse user group so users can run fusermount on their own without needing to be root. However, fusermount requires the fuse kernel module to be loaded, which they can't do.

The admin, of course, can add the module to /etc/modules to be automatically loaded on boot, but requiring users of Ubuntu to edit core config files is The Wrong Thing To Do (tm).

fusermount need to modprobe fuse on command execute (if fuse isn't already loaded)

[Hervé Fache (rvfh)]

Loading a module is not trivial. Kernel stuff is better done automatically.

[Patrick McFarland (diablod3)]

Are you agreeing th

[Patrick McFarland (diablod3)]

Launchpad needs the ability to edit or delete comments, damnit.

...

So, are you agreeing or disagreeing that fuse needs more automagic for the modules?

[Hervé Fache (rvfh)]

I agree. Sorry if I was not clear.

2006/4/7, Patrick McFarland <email address hidden>:
> Launchpad needs the ability to edit or delete comments, damnit.
>
> ...
>
> So, are you agreeing or disagreeing that fuse needs more automagic for the modules?
> --
> fusermount requires fuse module kernel to be loaded, isn't done automagically
> https://launchpad.net/malone/bugs/1860
>

--
In a world without walls and fences, who needs Windows and Gates?

[Patrick McFarland (diablod3)]

On Saturday 08 April 2006 09:49, Hervé Fache wrote:
> I agree. Sorry if I was not clear.

If you meant to reply on the bug report itself, you can't reply via email. At
least, not yet.

> 2006/4/7, Patrick McFarland <email address hidden>:
> > Launchpad needs the ability to edit or delete comments, damnit.
> >
> > ...
> >
> > So, are you agreeing or disagreeing that fuse needs more automagic for
> > the modules? --
> > fusermount requires fuse module kernel to be loaded, isn't done
> > automagically https://launchpad.net/malone/bugs/1860
>
> --
> In a world without walls and fences, who needs Windows and Gates?

--
Patrick "Diablo-D3" McFarland || <email address hidden>
"Computer games don't affect kids; I mean if Pac-Man affected us as kids,
we'd all be running around in darkened rooms, munching magic pills and
listening to repetitive electronic music." -- Kristian Wilson, Nintendo,
Inc, 1989

[Hervé Fache (rvfh)]

Oooops sorry! Will post in launchpad.

2006/4/8, Patrick McFarland <email address hidden>:
> On Saturday 08 April 2006 09:49, Hervé Fache wrote:
> > I agree. Sorry if I was not clear.
>
> If you meant to reply on the bug report itself, you can't reply via email. At
> least, not yet.
>
> > 2006/4/7, Patrick McFarland <email address hidden>:
> > > Launchpad needs the ability to edit or delete comments, damnit.
> > >
> > > ...
> > >
> > > So, are you agreeing or disagreeing that fuse needs more automagic for
> > > the modules? --
> > > fusermount requires fuse module kernel to be loaded, isn't done
> > > automagically https://launchpad.net/malone/bugs/1860
> >
> > --
> > In a world without walls and fences, who needs Windows and Gates?
>
> --
> Patrick "Diablo-D3" McFarland || <email address hidden>
> "Computer games don't affect kids; I mean if Pac-Man affected us as kids,
> we'd all be running around in darkened rooms, munching magic pills and
> listening to repetitive electronic music." -- Kristian Wilson, Nintendo,
> Inc, 1989
>
> --
> fusermount requires fuse module kernel to be loaded, isn't done automagically
> https://launchpad.net/malone/bugs/1860
>

--
In a world without walls and fences, who needs Windows and Gates?

[Hervé Fache (rvfh)]

Hmmm. it seems that replying by e-mail worked, according to what I see here. But how far can we trust what we see to be reality?

Anyways, I agree that when a user tries to mount a FUSE-based filesystem, the kernel module should be loaded automatically. Of course, we could force-load it at startup for everybody for now.

[Patrick McFarland (diablod3)]

Oh hey! We _can_ reply by email and have it work! Thats a new one! ... I do _not_ like this feature whatsoever.

Anyhow, I dont know why the module just isnt loaded at startup using, say, an init.d script like lsm-realtime does and whatnot.

[Hervé Fache (rvfh)]

There might be a good reason: if the module is loaded and fuse-utils
is not installed, udev won't have any rule for the module and will
create /dev/fuse with mode 660 and owner root.root, meaning that the
fuse tools will fail.

Mount at startup might be ok, but after checking for a udev rule
(feels ugly, doesn't it?). Best would be for fusermount to trigger the
insertion somehow.

2006/4/9, Patrick McFarland <email address hidden>:
> Oh hey! We _can_ reply by email and have it work! Thats a new one! ... I do _not_ like this feature whatsoever.
>
> Anyhow, I dont know why the module just isnt loaded at startup using, say, an init.d script like lsm-realtime does and whatnot.
> --
> fusermount requires fuse module kernel to be loaded, isn't done automagically
> https://launchpad.net/malone/bugs/1860
>

--
In a world without walls and fences, who needs Windows and Gates?

[Patrick McFarland (diablod3)]

Well, we need fuse-utils to be installed then. It just seems silly to not do
it the same way lsm-realtime does it. Its obviously the best solution, and it
requires less hacking of fusermount.

[Alex Muntada (alex.muntada)]

Have just installed sshfs (which requires fuse-utils) on a Dapper host and on an Edgy laptop, so I could mount a directory from host to the laptop through sshfs.

Tried a few times and it didn't work because I needed to add myself to fuse group, so I did that. Then, tried again and fusermount said that I had no permission for /dev/fuse, which was owned by root:root. So I chgrp fuse /dev/fuse and (alas!) it works wonders.

In both cases (Dapper and Edgy) the fuse module got loaded automatically (I did not perform any modprobe) but Edgy got the wrong permissions to /dev/fuse (Dapper got it right).

Do you think thas this is related to the issue you're describing here or it's a bug on Edgy?

Thanks!

[Patrick McFarland (diablod3)]

I thought I unsubscribed from this bug. I'm no longer running Ubuntu, I've gone back to Debian.

[kripken (kripkenstein)]

>> In both cases (Dapper and Edgy) the fuse module got loaded automatically (I did not perform any modprobe) but Edgy got the wrong permissions to /dev/fuse (Dapper got it right).

I am also on Edgy, and I experience the exact same issue: the fuse module was loaded automatically, but even users in the 'fuse' group don't have permissions to /dev/fuse.

[Oliver Grawert (ogra)]

do you have the udev rules file in place ?
(ls /etc/udev/rules.d/|grep fuse )

[kripken (kripkenstein)]

// do you have the udev rules file in place ?
// (ls /etc/udev/rules.d/|grep fuse )

The output from that command gets me this:

45-fuse.rules

[Jonppe (jaalto-hotmail)]

I'm using edgy as well and had the same problem.
Rules existed. I was in fuse group and fuse was the group in /dev/fuse.

Still I got permission denied error.

Anyway, I had just installed ssftp and obligatory packages, so I decided to use the magical trick;
reboot. Now everything works perfectly.

[Mark Reitblatt (mark-reitblatt)]

This is working fine in Feisty (reboot needed for permissions to take root), so I'm closing.