Bug#927221: Comparisons to Other Distros
Ron Lovell
ron163264 at gmail.com
Wed Apr 17 03:14:51 BST 2019
Wow, that was quick.
As a sanity check, I took a look at my Arch Linux and openSUSE Tumbleweed
installations. Each has both fuse[2] and fuse3 installed, each has the
corresponding library installed.
For Arch, a fuse-common pkg supplies /usr/bin/mount.fuse, which happens to
be dyn linked to libfuse 3 (per ldd(1)). Pkg fuse2 supplies
/usr/bin/fusermount, not dyn linked to libfuse per ldd. Pkg fuse3 supplies
/usr/bin/fusermount3, again not linked.
gvfsd-fuse requires fuse2 and is linked to libfuse 2. sshfs requires fuse3
and is linked to libfuse 3.
For Tumbleweed, pkg fuse supplies /usr/sbin/mount.fuse, not linked to
libfuse per ldd. Pkg fuse3 supplies /usr/sbin/mount.fuse which links to
libfuse 3. Pkg fuse supplies /usr/bin/fusermount, not linked. Pkg fuse3
supplies /usr/bin/fusermount3, not linked.
On both systems I was able to use the fuse2 fusermount to unmount an sshfs
(fuse3) mount, but that doesn't mean much.
So I'm a wee bit worried that not having BOTH fuse and fuse co-installed
might uncover problems in Debian. Time for lots of testing when the bits
are available. I'll try to help out there.
--
James Ronald Lovell <ron163264 at gmail.com>
Huntsville, AL, USA
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/pkg-gnome-maintainers/attachments/20190416/94612e15/attachment.html>
More information about the pkg-gnome-maintainers
mailing list