Hi Sue, Thanks for your response. A few comments in-line.
Sue Sohn wrote: >> General comments: >> -------------------------------- >> >> There's no mention about the following in the spec, I think it is >> important to discuss the following topics somewhere in the spec: >> >> * How will the text installer get started? From selecting the >> appropriate >> entry in the GRUB menu? Is there any other way people can start the >> text installer? Is there an option to just boot into a shell prompt, >> and then, run >> the text installer? > > For x86, there will be grub menu entries (default for server images, > non-default for livecd). For sparc, not sure Alok has finalized this > yet, but it may be that booting the physical media will directly bring > up the text installer. It will also be possible to start the text > installer from the command line, as this capability will be provided > to allow the user to restart the install. Thanks for clarifying. I don't find this info anywhere in the spec. I think it would be useful to add it somewhere. > >> * There should be more extensive discussion on how error >> cases will be handled. For example, >> What kind of errors will occur during the installation process, and what >> will be the result of those errors? Perhaps users will be given the >> opportunity >> to fix the error, or the installer will just exit or something like >> that. If the >> installer existed because of certain errors, people can probably look >> at the >> install log to figure what's wrong. Will they be allow to fix the >> error and restart >> the installation or they can't for whatever reason.. > > I expect that the reporting and recovery from errors will be similar > to what happens for the gui installer. If an error occurs and the user > fixes the underlying problem, it will be possible to restart the > installer manually. The user will be instructed how to do so. We will > add a separate section in the spec to make this clearer. OK > >> * Can users quit the installation process in the middle of an >> install? What will >> happen if they do that. > > By "middle of an install", I assume you mean once the actual > installation has started (one can quit out of intermediate screens). > The gui doesn't allow the user to quit in the middle so we were > intending to follow the same model. It might be worthwhile for someone > to investigate whether the installation can be interrupted without > significant adverse affects - Keith filed 10003. Yes, I meant once the installation is started. The GUI installer is slightly different in the sense that since it is just one of the application running on the desktop, you can still open other windows and look at other stuff, kill the installation(not cleanly of course) or even shutdown the machine without the installation finishing. So, I was just prompting to see what the user experience will be once the installation is started. If the user really want to quit, and they don't care about the installation finishing or not, what are their options? > >> Specific comments: >> -------------------------------- >> >> Section 1.2: >> - "Boots/Installs from physical media" >> Since IPS based install will be implemented in subsequent phases, and >> this >> functional spec covers those too. Would it be more appropriate to >> mention >> that install from network will also be supported? > > Section 1.2 is meant to cover the scope of the initial phase. The > phased work is covered in 2.4. We will move the phased work section so > that it follows section 1.2, to make it easier to see the connection. OK > >> Section 1.4: >> - I think there will be a need to modify some of the >> DC finalizer scripts to generate the type of images you need. >> Do you need to add that as one of the dependencies? Or do you consider >> that as part of the text installer work? > > We consider that as part of the text installer work. We will add it as > a deliverable. OK > >> Section 2.4: >> - I thought "IPS based installation" and "software pkg grouping >> installation" >> are the same, in the sense that they are all installing from IPS. >> Unless you mean >> people will be able to choose individual packages to install from IPS >> when you say "IPS based installation". > > Sofware pkg grouping does require IPS based installation, but IPS > based installation doesn't require software pkg grouping. For > instance, AI uses IPS to install but doesn't use pkg grouping. You mean choosing individual packages from IPS? > >> Section 3.4.7: >> - "It is TBD whether the text installer should reconfigure the microroot >> env after installation." >> >> What does this mean? > > This was referring to setting up networking in the microroot to use > the values provided by the user (it was cryptic because I forgot to > update it prior to posting). This would need to be done during early > installation if we were doing the install from IPS, but not > necessarily important to do it otherwise. I suppose this is important when installing from IPS is supported, since the machine might not be able to use DHCP for whatever reason, and static IP address setup is required to contact the IPS server. For supporting cpio-based install, it is not really necessary. --Karen > >> Section 4: >> - Since the text installer binary and help files will be bundled in >> the images, I don't think >> you need to list it separately. If you want to list them, I think it >> is more clear to list them >> and then, say that they will be part of the images, since they can't >> be use "alone". > > We will remove the binary from the list. I'm going to leave the help > files as a deliverable, because they are something we need to deliver > for translation to the g11n folks. > > Thanks for your comments! > Sue >
