Hi again, On Mon, May 14, 2007 at 11:43:01AM +0200, Dag Wieers wrote: > > [on kmdls]
> True. But that HOWTO will only work for a specific kernel. This can lead > to bitrot very quickly. > > Also, you depend on the availability of that specific kernel module for > that specific kernel, which isn't guaranteed for older kernels or fairly > new kernels. ATrpms builds for all RHEL5 kernels (at least as long as the disk space permits it :) > As a result, you may end up without support for NTFS and FUSE after > upgrading your kernel. dkms doesn't have that problem. (it might, but less > likely) kmdls have a yum-plugin-kmdl which pulls in the kmdls for newer (and older) kernels, but it's true, there is a time span of a couple of hours to a day where there will be a kernel update in RHEL5 and where I won't have noticed yet to kick in kmdl rebuilds. Even if fully automated kmdls can only be built once the builders actually get hold of the new kernel bits :) The upcoming generation of kmdls won't even need the yum-plugin-kmdl to track the latest kernel, e.g. apt and smart will work as well (but not on RHEL5 itself due to absence of metadata, CentOS/SL/Fedora will work fine, though). -- Axel.Thimm at ATrpms.net
pgpxPj5kzfcQO.pgp
Description: PGP signature
_______________________________________________ rhelv5-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/rhelv5-list
