|
From: Mike Young
[mailto:myoung@xxxxxxxxxxxxxxxxxxx] Hi,First of all, I apologize re-opening such an old thread. But while I have found some clarifications on the file system layout for the ddv3 drivers, along with some patches, I have been unable to actually find any real documentation on how to create a ddv3 driver. For example, I see the structure is as follows:> DDv3 structure> --------------> /> |rhdd3 - DD marker, contains the DD's description string> /rpms> | /i386 - contains RPMs for this arch and acts as Yum repo> | /i586> | /x86_64> | /ppc> | /...But what I don't see is what else it might be looking for. Do I still package these folders into a .iso package?If there's some documentation on this procedure, I'd really appreciate a link to it. The search terms I'm using must be too generic and the only thing that reports anything substantive is ddv3. Unfortunately, everything leads back to this thread.Thanks!MikeThere’s been a bit of
discussion of this over on kickstart-list recently J
The best way to create driver disks is using ddiskit. Beware which distro
you’re using, though. RHEL 5.1 Release Notes state that Anaconda
now supports the v3 rpm format, but the Anacondas of CentOS 5.6 and 5.7 do not
contain the necessary code. I needed a JMicron(R) JMC250 PCI-E
Ethernet Adapter. After fighting the Big Snake for several days, I gave
up, put the kmod-jme rpm from ELRepo
into my main repository and installed it via kickstart. I don’t
configure networking until first boot, so I could get away with that. Moray. “To err is human; to purr,
feline.” |
_______________________________________________ Anaconda-devel-list mailing list Anaconda-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/anaconda-devel-list
