Hello, Yes, the new driverdisc contains only RPM files. The modules (.ko files) are then automatically extracted from those rpms during driver disc loading. After the extraction, depmod is run to regenerate the dependency and pci table files. The RPMs which should be considered for automatic DD extraction have to have correct Provide: "flag" as is also mentionedd in the docs. -- Martin Sivák msivak@xxxxxxxxxx Red Hat Czech Anaconda team / Brno, CZ ----- "Prudhvi Tella" <Prudhvi_Tella@xxxxxxxx> wrote: > Does the new driver disk contain only RPMs, like below? > > 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 > | /... - any other architecture the DD provides drivers for > > > Or can we also put put the required files like before? > > DDv3 structure > -------------- > / > |rhdd3 - DD marker, contains the DD's description string > |modinfo > |modules.alias > |modules.cgz > |modules.dep > |pcitable > /rpms > | /i386 - contains RPMs for this arch and acts as Yum repo > | /i586 > | /x86_64 > | /ppc > | /... - any other architecture the DD provides drivers for > > > Could anyone please clarify the new format or give an example? > > Thanks > > _______________________________________________ > Anaconda-devel-list mailing list > Anaconda-devel-list@xxxxxxxxxx > https://www.redhat.com/mailman/listinfo/anaconda-devel-list _______________________________________________ Anaconda-devel-list mailing list Anaconda-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/anaconda-devel-list
