On Tue, 2011-11-22 at 10:10 -0500, Martin Sivak wrote: > Hi, > > > Driver disks may require an interactive element, but can't that just > > be > > another screen in anaconda proper? We're already going to have > > network > > bring up UI there (as well as cmdline handling in dracut), as well as > > language and keyboard. It seems to me that we could just toss in > > another screen at an appropriate place in the UI. Note - likely not > > an > > F17 thing. > > This has to be done before we initialize network and all of storage. Or we need to be able to re-initialize after loading the driver disk. I'm pretty sure that's easy to handle for network drivers.. not sure about storage, but I don't think it's impossible. > So with install/network sources being handled by dracut, DDs have to > go into dracut too.. I'm not sure about this. Here's my reasoning (forgive the formality but I'm trying to think through the logic myself): 1) DD support needs to be in dracut if (and only if) there are supported install cases where dracut must load a driver disk before it will be able to load install.img. 2) We need a driver disk before loading install.img if (and only if) there are devices that can hold/fetch the DD, but not install.img. Therefore: We only need DD support in dracut if there are supported devices that can hold/fetch a DD but not install.img. Floppies and Zip drives are the only things that come to mind that meet this condition, but I'm not sure if we support them. Are there any others? -w _______________________________________________ Anaconda-devel-list mailing list Anaconda-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/anaconda-devel-list
