Olaf Mueller wrote:
Hello,
seems to me that kmod-fuse, the new replacement for dkms-fuse, needs a
lot of additional kernels to have installed? Is it really necessairy to
have 3 kernels installed?
Here is the output of my last 'yum update' call.
============================================================================
Package Arch Version Repository
Size
============================================================================
Installing:
kmod-fuse i686 2.7.4-1.el5.rf rpmforge
26 k
replacing dkms-fuse.noarch 2.7.4-1.nodist.rf
kmod-fuse-PAE i686 2.7.4-1.el5.rf rpmforge
26 k
replacing dkms-fuse.noarch 2.7.4-1.nodist.rf
kmod-fuse-xen i686 2.7.4-1.el5.rf rpmforge
26 k
replacing dkms-fuse.noarch 2.7.4-1.nodist.rf
Updating:
clamav i386 0.95.1-3.el5.rf rpmforge
2.7 M
clamav-db i386 0.95.1-3.el5.rf rpmforge
20 M
clamav-devel i386 0.95.1-3.el5.rf rpmforge
6.4 k
clamav-milter i386 0.95.1-3.el5.rf rpmforge
88 k
clamd i386 0.95.1-3.el5.rf rpmforge
235 k
Installing for dependencies:
kernel-PAE i686 2.6.18-128.1.6.el5 updates
15 M
kernel-xen i686 2.6.18-128.1.6.el5 updates
16 M
I use apt, and when asking for a full update it also offered to install
kernel-xen (though not kernel-PAE) for kmod-fuse, although I use the
plain kernel.
But if you ask apt to simply install kmod-fuse, it removes dkms-fuse and
doesn't ask for the xen kernel.
I guess yum will behave similarly, ie if you "yum install kmod-fuse" it
shouldn't pull in kernel-PAE and kernel-xen (of course these are not
necessary if you have the regular kernel).
Not sure if this can be fixed, I suspect it's an artefact of the dep
resolution in yum/apt (?)
_______________________________________________
users mailing list
[email protected]
http://lists.rpmforge.net/mailman/listinfo/users
