[elrepo] RFP: mISDN and Dahdi ...

[Alan Bartlett]

2010/1/12 Clinton Lee Taylor <clintonlee.taylor at gmail.com>:

>> I really would not like to comment about broken symlinks for other
>> kmod packages in relation to older, removed, kernels. In general, if
>> everything is working I will go as far as saying that it is "not bad"
>> -- but then again, to a perfectionist, it is "not good". Assuming
>> those other packages do not originate from ELRepo, things seem to be
>> as I would expect.

>  All my kmods are from ELRepo, seeing that you guys have put
> everything that I need in once place, thanks!
> I see that some kmods extra are stored in differance paths, but
> nothing of the symlinks are broken, it seems that folder are kept for
> the extras, even if that kernel is remove, so not the end of the
> world.

Ah, ha. I understand. So everything is correct and nothing is broken.
As long as you have the /lib/modules/<kversion>/extra/ directory,
regardless of whether you have kernel-<kversion> installed or not,
then that *is* correct and I can revise my above comment by deleting
the "not good" & substituting "good" for the "not bad". :-)

Expanding that a little further, as the kmod packages from ELRepo are
kernel independent, kABI tracking then you only need to have a kernel
installed that agrees with the published Red Hat kernel ABI for the
kmod package to be viable. In every case you will have a
/lib/modules/<build-kversion>/extra/foo/foo.ko file and any number
(from zero upwards) of /lib/modules/<installed-kversion>/weak-updates/
based symlinks back to the extra/foo/foo.ko file.

Alan.