https://bugzilla.novell.com/show_bug.cgi?id=285101#c24
--- Comment #24 from Bernhard Kaindl
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.