On Wed, 2 May 2012 13:06:20 +0000
Steve Traylen wrote:
Hi Steven,
> Probably no clean way of doing this. With 5.3 fuse is part of the
> main kernel so the extra package is no longer needed.
ok, so I should remove kernel-module-fuse.
But then it removes cvmfs too:
Removing:
kernel-module-fuse-2.6.18-128.7.1.el5 x86_64 5:2.6.3-1.sl5 installed 804 k
Removing for dependencies:
cvmfs x86_64 2.0.7-1 installed 11 M
cvmfs-init-scripts noarch 1.0.15-1 installed 1.4 k
fuse x86_64 5:2.6.3-1.SL installed 207 k
> Try updating fuse first since the newer fuse will then not depend
> upon "kernel-module-fuse"
My systems don't see new fuse package, so fuse-2.6.3-1.SL.x86_64 seems
last version to me:
# yum update fuse
Loaded plugins: kernel-module, priorities, protectbase
[...]
No Packages marked for Update
I've downloades 2.7.3 and tried to install it locally:
# yum localinstall fuse-2.7.4-8.el5.x86_64.rpm
Loaded plugins: kernel-module, priorities, protectbase
Setting up Local Package Process
Examining fuse-2.7.4-8.el5.x86_64.rpm: fuse-2.7.4-8.el5.x86_64
fuse-2.7.4-8.el5.x86_64.rpm: does not update installed package.
Nothing to do
Does it make sense?
> Also update to 2.0.11 for CvmFS but I don't think this is anything to
> do particularly with cvmfs, this is a fuse only problem.
I can't do that cause we have not tested new cvmfs releases.
> Hard to be precise though since SL and SLC differ on how they added
> fuse when fuse was not part of RHEL.
We're running SL, not SLC.
what versions of fuse/kernel and cvmfs do you have installed?
Cheers,
Arnau
|