Martin Sivak (msivak@xxxxxxxxxx) said: > > 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. > > To be exact, we have to be able to unload all network and storage drivers and instruct udev to load them again. > > Unloading just storage and network supposes we know which modules are network and storage.. that is why we currently save a list of modules loaded before loader and restores to that state (no guessing that way..). At what point do we reexamine everything that is done in driver discs in terms of what is absolutely required, versus 'what we have always done'? For example, the 'feature' of unloading all drivers to then load them in an interactive order seems to mainly be there to preserve the fallacy that storage device names are meaningful. Is that the only reason that it's required? If so, is that feature worth an entirely separate interactive infrastructure? Why does it need to be interactive, when it could theoretically be done via kickstart commands, or commandline operations? Bill, playing devil's advocate _______________________________________________ Anaconda-devel-list mailing list Anaconda-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/anaconda-devel-list
