Dave, Thank you for your feedback. Comments are inline. I will update the document to reflect these suggestions.
On Wed, Aug 4, 2010 at 11:48 AM, Dave Miner <[email protected]> wrote: > On 08/ 3/10 01:37 PM, Andrew Gracey wrote: > >> Hi, >> >> We have attached the first draft of the design document here >> < >> http://hub.opensolaris.org/bin/view/Project+caiman/Network+Text+Installer >> >. >> >> We would like feedback by August 10th. >> >> > Good start, some comments and questions. General comment is that it's > helpful in commenting to have sections (and pages) numbered. Less of an > issue in short documents, but still would be nice. > Done > > Purpose, last sentence: AI allows for setting up each install with unique > configuration, the issue you're solving here is interactive configuration of > a network-booted installation. > > Requirements: #5 says that installadm is to be updated, but the Use Cases > indicate no changes to installadm. > I clarified that the changes are not visible to the user. That said, I like your solution proposed below so we might just remove this section altogether. > > Solution, Server: > - Please be specific about the name of the finalizer script that is being > modified > We were not sure which one we needed to modify but we will update that. > - Specifics about the package list would be useful to record > We can add that, I wasn't sure if that would go in the design document or the user documentation. > - Why does installadm need to manipulate the GRUB menu for interactive > choices? Shouldn't these be included in the menu by the construction > process? But, see later comment on client use case section. > Since we were missing the now obvious solution we needed a way to add a third choice. The menu created during construction is used when booting from media and not from net. Installadm creates it's own GRUB menu for network-booting. Since media booting this image is out of the scope of our project we do not need to modify the menu created by DC. > > Solution, Client: > - the "OK prompt" is properly known as the OBP (OpenBoot PROM) firmware > Thanks "OK prompt" seemed odd but I wasn't sure . - AI and text installer are not "SMF scripts" but perhaps "executed by SMF > services" > Thanks again - Can you elaborate on why we need to download a second copy of the boot > archive? Is there not a relatively straightforward solution to this that > wouldn't involve the extra tens of MB of re-transfer? > There are two boot archives in the image, one for x86 and one for x64. Only one boot archive is downloaded while booting the AI image but we need both to install using text. - Why is modifying the text installer preferable to creating symlinks to > needed files? > Symlinks seemed like a bad solution that we used to make it work for class. Do you think it is a good solution? > - There isn't a better way to communicate to the GRUB menu ICT than > deleting one of the files, which are generally assumed to be persistent by > the existing design? > We would imagine that there is but couldn't come up with one. We were thinking that we would have to change the script to require an extra argument specifying whether the installed system had graphics or not. > > Use Cases: > In general, use cases should be much more specific about the goal or task, > the inputs from the user, and the resulting actions. The Examples in > http://hub.opensolaris.org/bin/view/Project+caiman/AI+Image+Management are > closer to what we'd consider real use cases. > We are new to this, thanks for the example > > Use Cases, Client: Have you considered another alternative, which is that > when the default menu item in GRUB is selected, or the default mode from > SPARC when "boot net:dhcp" (no "- install") is used, the existing > text-mode-menu is brought up? Is there an advantage to the approach > proposed? > There is no advantage to the our approach except that we didn't think to make it that simple. The only problem that I can think of is that you would not know if the image you are booting from has the text-install packages or not until you boot. > > Dave > > > _______________________________________________ > caiman-discuss mailing list > [email protected] > http://mail.opensolaris.org/mailman/listinfo/caiman-discuss >
_______________________________________________ caiman-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
