Hi, yes this structure describes the layout of data in some container. We do not really care much if it is .iso, fat, ext3, cpio or squashfs if we can mount it. If you want to use the automatic detection (dlabel) you have to use container which supports labels. And that's it. Nothing complicated regarding modules.cgz or modules-info like in rhel5 format. You just package the modules as rpms and create a repository for them on some media and using the described structure. Martin ----- Original Message ----- > > > 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! > Mike > > _______________________________________________ > 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
