Alok Aggarwal wrote: > > On Wed, 24 Jun 2009, Peter Tribble wrote: > >> On Wed, Jun 24, 2009 at 8:24 PM, Alok Aggarwal<Alok.Aggarwal at sun.com> >> wrote: >>> >>> On Tue, 23 Jun 2009, William D. Hathaway wrote: >>> >>>> Section 5.7 Invoking AI on Client Systems >>>> x86 - I understand the need to avoid accidentally installing due to >>>> boot >>>> order confusion issues, but will there be a way this can be totally >>>> hands >>>> off if desired? The wording about this wasn't clear to me. >>> >>> Yes, the user interaction can be automated via, say, >>> an expect script such that the install is hands off. >>> Infact scriptability was one of the main considerations >>> while doing the research in this area. >> >> I anticipated this working the same way that it does with jumpstart at >> the >> moment - namely being able to edit the client's menu.lst file to add the >> install boot argument. (That's how I make x86 jumpstart completely >> hands-off.) >> >> Even better would be to have both the install and non-install entries >> in the >> grub menu all the time, and have a way on the server to set which one was >> the default. > > We considered providing this choice as part of the grub > menu. It turns out that that's not very scriptable which > is why we didn't want to go down that route. >
I think this is a fairly unconvincing justification. For sites that know what default they'd like to have, this should be expressable via the menu.lst, creation of which is completely scriptable on the server side, of course. Requiring use of expect is comparatively quite difficult, IMHO. Dave
