Jack Schwartz wrote: > Hi Peter. > > On 08/16/09 15:35, Peter Tribble wrote: >> On Thu, Aug 13, 2009 at 11:17 PM, Jack Schwartz<Jack.A.Schwartz at sun.com> >> wrote: >> >>> Hi Peter. >>> >>> Thanks for your review. Comments inline... >>> >> >> I must be being dense. I understand even less how this might work than >> I did before... >> >> >>>> 3.3 Why add specific support to AI? I would have thought that adding >>>> additional drivers to the installed image was no different to adding any >>>> other package. >>>> >>> You are correct in that the mechanics of adding an additional driver to the >>> installed image is the same as adding any other package to that image. (In >>> fact, updates to the DDU for doing manual installs of packages will be shim >>> layers which call pkg or pkgadd to do the real work.) >>> >> >> Thinking about this more: why would I have to explicitly specify that a >> driver >> identified as being required by a piece of hardware in my system be >> installed? Why wouldn't the installer just install all necessary drivers >> (unless >> explicitly told to ignore them, of course)? >> > I agree it would be nice to install all drivers which a system needs > automatically. (This is <searchall> in the AI manifest.) If we do > this we need to make sure it plays well with use cases where the user > explicitly specifies certain drivers to install. > > I will change the functional specification to include that the AI > manifest template have searchall listed. This way, if the user does > nothing, drivers will be automatically searched. The user is also > free to take the searchall out, or to add requests for explicit > drivers in addition. >> >>> So why is this needed? Special drivers have to be added to the installed >>> image so they are available to aid in the installation itself. One needs to >>> add the special driver for a legacy raid card before the disks of that card >>> can be used as a target for the install. That driver won't be available >>> soon enough if its package is merely listed as one of the packages to >>> install. >>> >> >> But, if I'm running AI, then I'm booting an AI image. I would expect that >> to have all the "official" drivers in it already by default. All the >> drivers that >> DU knows about and you're proposing to allow automatic installation of >> will already be present - or should be. >> This really boils down to how one can provide drivers needed at boot time. In case of AI, one could simply update the AI image on the server to include the driver. That's certainly an interesting idea worth exploring.
-Sanjay > _______________________________________________ > caiman-discuss mailing list. > caiman-discuss at opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/caiman-discuss >
