[elrepo-devel] a few comment about elrepo's packages

[Farkas Levente]

On 08/29/2009 12:01 PM, Alan Bartlett wrote:
> On 29/08/2009, Phil Perry<phil at elrepo.org>  wrote:
>
> <snip>
>
>>   2. Blacklisting
>>
>>   We provide a standardised mechanism within kmodtool for blacklisting
>>   modules where needed. Alan would be able to give you an example of a
>>   modules that requires this, but I believe some of the network controller
>>   driver modules do.
>
> When either the kmod-r8101 or the kmod-r8168 package is installed, the
> Red Hat distributed 8169 module is blacklisted.
>
> The requirement, to blacklist any existing 8169 module before a 8101
> or 8168 module is loaded, is specified in the Realtek documentation.

anyway it's a good question how to handle future kernel which include 
elrepo's kmod? eg. when 5.4 comes out what happened with xfs, kvm and 
fuse kmod which will included in the upstream kernel?
solution:
1. everybody have to remove by hand old kmods before reboot with the new 
kernel.
2. as we can't expect that upstream kernel will obsolete old kmods we 
can somehow check the new kernel's kmods.

anybody has any tipp for this? eg. in my case i wouldn't like to remove 
by hand these modules on 400 servers:-( and the same is true for 8101 
and 8168 since 5.3's 8169 include the driver for these models.

-- 
   Levente                               "Si vis pacem para bellum!"