Hi Sue, A few small comments...
> As an "interactive" installer, observability for the text installer will be > similar to that of the GUI installer: A percentage-based progress bar, with > information on the current installation piece in progress. Any error > conditions > detected will be presented to the user at an appropriate time. Additionally, > the installation log will be available in the same location as it is for the > GUI installer. This location will be provided to the user when the installer > exits. > Should we also include the observability that is built in to the user selection pages, for fdisk and vtoc management? We do some error checking, basic size, display of existing partitions, slices, and warning them of overwriting existing data. Section 3.4.5: > User is informed that if additional, more advanced partition management is > required, it must be done using an external tool, such as parted. > Is this expected to a standard message displayed on this screen, or based on some user action? > The following parameters will be auto-discovered and presented to the user. > The user can then confirm the discovered values, or override them. > * IP Address (not auto-discovered) > * Netmask > * Default Gateway > Are we not worrying about nameservice discovery? Do we give them the option to add nameservice data or are we skipping this altogether? thanks, sarah > I have updated the functional specification for the Text Installer > based on the feedback and comments received and meeting discussions > last week. It is posted at: > > http://www.opensolaris.org/os/project/caiman/TextInstallerProject/text_install_spec_v2.txt > > > > If you have further feedback, please provide it by Wednesday, July 29, > at 5pm > Pacific. > > Thanks, > Sue > _______________________________________________ > caiman-discuss mailing list > caiman-discuss at opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
