'rm' removes files but 'ls' still shows them on the fs
On Tue, 5 Dec 2006, felipe1982 wrote:
Quote:
felipe@anarchy&#~> su -c 'mount -a'
Password&#
/sbin/mount.ntfs-3g&# error while loading shared libraries&# libfuse.so.2&# cannot open shared object file&# No such file or directory
Did you run 'su -c ldconfig' as I suggested in the former comment?
Quote:
Unsatisfied dependency&# ntfs-3g-20061115-1.guru.suse101@i686 requires fuse >= 2.6.0
Unsatisfied dependency&# ntfs-3g-20061115-1.guru.suse101@i686 requires libfuse.so.2
Unsatisfied dependency&# ntfs-3g-20061115-1.guru.suse101@i686 requires libfuse.so.2(FUSE_2.5)
Unsatisfied dependency&# ntfs-3g-20061115-1.guru.suse101@i686 requires libfuse.so.2(FUSE_2.2)
Unsatisfied dependency&# ntfs-3g-20061115-1.guru.suse101@i686 requires libfuse.so.2(FUSE_2.6)
Why doesn't it recognise fuse 2.6.1?
Because you mix a package manager with source installation. If ntfs-3g still
doesn't start after 'su -c ldconfig' then remove the ntfs-3g rpm and compile
it from the source.
Quote:
What else do I need to do for the computer to recognise fuse>=2.6.0?
Probably it won't recognise because you installed it from the source.
Quote:
I'd prefer to use rpms (ntfs-3g-xxxxx.rpm), but is it hopeless?
No, it's definitely not hopeless. When the packagers have time, I'm sure
they will make it.
Quote:
Is installing from source the only way out?
No, there are many dozens way to install it. But at present the NTFS-3G
developers support only installation from the source because otherwise we
couldn't spend so much time with the real NTFS development. Packaging is
very distribution specific and you also use not yet very popular utilities
like 'smart' and 'checkinstall', which apparently have some shortcomings.
