> docs/driverdisc.txt | 125 +++++++++++++++++++++++++++++++++++++++++++++++++++ > 1 files changed, 125 insertions(+), 0 deletions(-) > create mode 100644 docs/driverdisc.txt Overall, this could use some minor proofreading/editing, but I wouldn't hold up merging the patches because of that. Thanks for adding this documentation. We may want to investigate putting this on the wiki and fetching it at package build time, like we do with kickstart and options. Seems like eventually, someone's going to want this information broken out of the package anyway. > +What can be updated using DDs? > +------------------------------ > + > +We also plan to support anaconda's updates.img placement on the DriverDisc to > +update stage2 behaviour of anaconda. I'm still not sold on this, so we shouldn't promise it just yet. > +Initrd overlay driverdisc image > +------------------------------- > + > +We have designed another possible way of providing updates in network boot > +environments. It is possible to update all modules this way, so if special > +storage module (which gets used early) needs to be updated, this is the > +preffered way. > + > +This kind of driverdisc image is applied over the standard initrd and so has > +to respect some rules. > + > +- All updated modules belong to /lib/modules/<kernel version>/.. according to > + their usual location > +- All new modules belong to /tmp/DD/lib/modules > +- All new firmware files belong to /tmp/DD/lib/firmware > +- The rpm repo with updated packages belongs to /tmp/DD-initrd/ > +- The (empty) trigger file /.rundepmod must be present Really? I didn't know we could do this. - Chris _______________________________________________ Anaconda-devel-list mailing list Anaconda-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/anaconda-devel-list
