Bug 223663

Summary:	fuse package requires additional configuration (by root) to work.
Product:	[openSUSE] openSUSE 10.3	Reporter:	Jarl Friis <jarl>
Component:	Installation	Assignee:	Forgotten User sLJ7K2dvxj <forgotten_sLJ7K2dvxj>
Status:	VERIFIED FIXED	QA Contact:	Jiri Srain <jsrain>
Severity:	Enhancement
Priority:	P5 - None	CC:	andreas.hanke
Version:	unspecified
Target Milestone:	---
Hardware:	All
OS:	SUSE Other
Whiteboard:
Found By:	Customer	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Jarl Friis 2006-11-24 18:52:30 UTC

As described in bug 222899, it requires root activity to use sshfs (and other fuse file systems)

This is really awkward. Since a sysadmin when installing the fuse package, would probably expect that this by itself will enable users to use fuse File systems (such as sshfs). However additional root activity is required, namely modifying /etc/sysconfig/kernel

My suggestion for enhancement is simply to incorporate this modification of the /etc/sysconfig/kernel into the RPM scripts executed when installing the fuse package.

Comment 1 Andreas Hanke 2006-11-25 04:37:10 UTC

I disagree. The suggestion is far too simple because there are other filesystems (like ntfs-3g) which can load the fuse module on demand. Loading it uncondionally would be bloat for users of these file systems.

I'd prefer enhancing sshfs to behave like ntfs-3g, so that it can load the module as-needed _without_ messing around in /etc/sysconfig/kernel (which is inappropriate anyway because just because I have fuse installed, doesn't mean I want it to be loaded unconditionally - it should be loaded when it's going to be used).

Comment 2 Jarl Friis 2006-11-26 20:00:00 UTC

(In reply to comment #1)
> I disagree. The suggestion is far too simple because there are other
> filesystems (like ntfs-3g) which can load the fuse module on demand. Loading it
> uncondionally would be bloat for users of these file systems.

I didn't think of that. If so, I agree with you, that this is the right way it should be done.

> I'd prefer enhancing sshfs to behave like ntfs-3g,

Sounds like the right way to solve this bug. So the bug is still the bug, but my proposal for solving this bug is not optimal, your suggestion for solving this bug is much better.

Since enhancing sshfs may take longer than my suggestion for fix, I'd say that my suggestion may still be consdered a good workaround (to improve end-user experience) until sshfs has been enhanced as you describe.

Comment 3 Takashi Iwai 2006-11-29 10:34:39 UTC

You cannot create /dev/* files without a root permission.  The solution of ntfs-3g won't work.

Comment 4 Forgotten User sLJ7K2dvxj 2007-02-05 18:44:38 UTC

Since version 2.6.0 the upstream package (and other distros) use an init script
to load the module and mount the control filesystem.

Does anybody see a problem with this solution?

Comment 5 Forgotten User sLJ7K2dvxj 2007-02-07 15:51:22 UTC

Fixed in 2.6.3-2 as per previous comment.

Comment 6 Jarl Friis 2007-08-12 09:30:11 UTC

(In reply to comment #4 from Miklos Szeredi)
> 
> Does anybody see a problem with this solution?

I don't see a problem with that, I consider it similar to my initial suggestion, but mind comment#1 by Andreas Hanke, saying
"Loading it uncondionally would be bloat for users of these file systems."

Comment 7 Jarl Friis 2007-10-23 09:44:03 UTC

I have not investigated the final technical solution, but the overall (summary) problem is no longer a problem in 10.3 final, hence marking bug as verified.