https://bugzilla.novell.com/show_bug.cgi?id=285101#c24 --- Comment #24 from Bernhard Kaindl <bk@novell.com> 2007-07-30 10:36:14 MST --- One further point which I need to give in addition view about if admins really want to allow users to mount filesystems if fuse is installed: openSUSE contains about 290 software packages which install boot scripts and say if each of them only needs only 100ms at boot, your boot would still take 29 seconds longer as it would need to be. Also the boot messages get too crowed if all of them output a line of text. Therefore, I can very well imagine that we do not want to start anything what is not needed, otherwise it gets way out of hand (and do not think that fuse is a similar basic service as printing). Personal note on how I noticed this: There were days (some time ago) where I could select "install everything" in YaST and the booting took ages with lots of stuff started!!! So every little bit counts IMHO. Another argument may be: Once you start making exceptions to the rule to only start what is actually needed, you open the gates... You discarded (that's how I understand it) the possibilities which I described to only start fuse when it's needed, by saying
This is wrong. In the (not so) long run we want to get rid of suid fusermount. The unprivileged mount patches are already in -mm, so 2.6.24 is not unrealistic.
and
No, I think there's no problem with unconditionally loading the module if the fuse package is installed. If the user doesn't want this, then (s)he should remove the package.
The _real_ bug in this case was a wrong dependency on fuse, but that has been resolved, so I think this is not an issue any more.
As of this moment you are wrong, the current compiz still includes this file: ldd /usr/lib64/compiz/libfs.so libfuse.so.2 => /lib64/libfuse.so.2 (0x00002b5e49bc8000) http://compiz.org/Compiz_0.5 Fs plugin: FUSE plugin that maps compiz options to a file-system and allow efficient manipulation of options by reading and writing files. I talked with our compiz maintainer: It would be the next thing on his list, and it's really not used anywhere yet, so it would not be a problem to not install it but OTOH, it would be the only plugin which is splitted into a separate package (compiz has LOTS of plugins) and if libfuse would be in its own package, it would totally not make sense to split it into a separate package, just for this single file. As ntfs-3g (unless I link it statically) need libfuse and long as it is used with root privileges, it does not need fusermount installed or fuse started in any way, we could solve this by splitting off fuse to: * libfuse2 - contains libfuse (is installed when ntfs-3g is installed) * fuse2 - contains fusermount, mount.fuse, the rc script and docs and possibly separate ulockmgr packages. Regarding that: As far as I can see, none of the openSUSE-included rpms which use fuse (checked curlftpfs encfs fuseiso fusepod fusesmb gphotofs obexfs sshfs wdfs and compiz) use libulockmgr, so I guess that it does not make huge sense to ship it? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.