On Sun, Mar 24, 2019 at 1:02 PM Dale <rdalek1...@gmail.com> wrote: > > Rich Freeman wrote: > > > > Suppose you have an Acme model 1234 network card. You've previously > > answered Yes to enabling its driver, and No to enabling the Acme model > > 2345 card. > > > > Now a new option comes along to show/hide all the Acme cards. That is > > a new option, so it has no existing value as far as the config > > database design goes. If you answer No, then you disable your model > > 1234 card (without even being asked, because that isn't a new option). > > If you answer yes then effectively your previous choices remain in > > effect (model 1234 remains enabled, and model 2345 remains disabled). > > > > One would think it should ask if you want any ACME drivers first. If > you say yes then ask which ones you want. If you answer no then disable > them all and move to the Better-than-nothing drivers next in the list, > assuming the are alphabetical.
This is exactly what it is doing. There is a new question about whether you want any ACME drivers. It defaults to Yes. If you answer Yes then it prompts you for each individual driver, though it will skip those prompts since you've already answered them. If you answer No then it will set all the individual drivers to No (including the ones you previously set to Yes), and not prompt you further. > Once you get past that driver, nothing > else should disable the drivers you wanted. But the drivers you wanted WERE Acme drivers, so if you answered No to that question why would it prompt for those? You can see how defaulting to No on these sorts of questions can be more dangerous, because it can cause you to reverse decisions you previously made, while defaulting to Yes on the big questions (that don't actually build anything), and defaulting to No on the little questions (which do build things) has the result that if you accept all the defaults you keep the same kernel build you had before. If you answer Yes to whether you want ACME drivers it won't actually build any drivers - you have to enable those individually, and those questions presumably still default to No. -- Rich