[elrepo] kmod -> driver disk

[Manuel Wolfshant]

On 01/04/2011 03:32 AM, Dag Wieers wrote:
> On Mon, 3 Jan 2011, Phil Perry wrote:
>
>> On 03/01/11 12:35, Mário Barbosa wrote:
>>
>>> Can anyone give me some quick pointers as to how to merge some of these
>>> kmod's into a driver disk to be used at install time?
>>>
>>> My personal needs/wishes involve the sk98lin and the r8192se modules,
>>> but I am looking for a general approach on how to do this for "any"
>>> combination of drivers to be used on both el5 and el6 installs.
>>
>> ELRepo packages kmods using Red Hat's Driver Update Programme framework:
>>
>> http://dup.et.redhat.com/
>>
>> As a starting point, take a look at the section entitled "Building a
>> Driver Update Disk".
>>
>> I've not personally built any driver update disks, so perhaps someone on
>> this list might have the relevant experience to assist further, or you
>> can let us know how you get on.
>>
>> As mentioned in the above article, only storage and network drivers
>> really need to be installed using driver disks during installation,
>> anything else can be installed from an optional add-on repository.
>
> Not sure if it is at all possible, but wouldn't it be nice to have a 
> single driver disk with all ELRepo drivers on it. 
That would not be really hard to do. If memory serves, theoretically all 
kmods must end in a specific folder of the DD and all PCI & Co. 
description files must be concatenated. IIRC there was a method to 
short-circuit the building of RPMS and preserve the already built ones.
Caveat is that back in the 5.2 era when I played with creating driver 
disks for realtek r8169, anaconda used to install all the kmods found on 
the DD.... even independent of the architecture ( which is why I created 
separate i386 and x86_64 disks )

> And which gets update for every update in the repository ?
That could be automated too, I guess ..