Jeff Spaleta (jspaleta@xxxxxxxxx) said:
This allows hardware probing to be done only once; the specifics of where/how kudzu is run in this setup may be tweaked slightly - the initscript may be moved. kudzu also runs without interaction now, and just does the configuration of whatever it finds.
Does this mean kudzu will remove and unconfigure whatever it doesnt find without interaction as well?
Yes. Hence, a large shaking out period.
While the addition and removal of the hardware that is present makes sense, the unconfiguration (read: data loss) of that hardware's profile does not. Is there not (or shouldn't there be) a mechanism to cache the configuration of the devices so that the customizations made to them is retained when they are plugged back in? This system would provide the benefits of both models (speed, statefulness) without the draw back of either (boot speed, digital decay) IMO.
Should the user really want the device to "reset" when it is unplugged/poweredoff at restart and then reinstalled later would be to somehow manually clear the cache. Which is a much less frequent activity i hope.
-- Michael Favia michael.favia at insitesinc.com Insites Incorporated http://michael.insitesinc.com
