Looks OK to me. We will want to release note information about running 
the Device Driver Untility (aka HDD) prior to running the installer - 
assuming that it actually makes it into the release. I'm guess it will.

Frank


Barbara.Lundquist at Sun.COM wrote:
> Gang,
> I think that the online help and the Getting Started should be OK for 
> the code freeze, based on review
> input I received yesterday. ****But, please skim the review summary 
> below and see if you see any items that you think
> should be handled ASAP.****
>
> I'd like to see us do some further work after the code freeze. I'll 
> followup next week. If we find errors, we could Release Note
> them.
>
> FYI, attached is the revised Getting Started. IGNORE 1st two pages.
>
> Barbara
>
> Major Changes that are already made
> -----------------------------------------------
> 1 - changed all references to prototype and to slim install
> 2 - removed references to Distribution Constructor
> 3 - Added new references to beadm utility and to using "pkg 
> image-update" as the upgrade method
> 4 - Installer sections: added new locale screen info, revised timezone 
> screen info, revised disk screen info
> 5 - Removed specifications that disk partitioning must be preset prior 
> to install
> 6 - Stated that removable media need only be plugged in prior to install
> 7 - Release is identified as OpenSolaris 2008.05 release
> 8 - Removed the Windows VMware Release Note reference, as that's been 
> fixed.
>
> Sections that could be expanded after code freeze:
> ---------------------------------------------------
> 1 - Expand instructions on how to use pfexec to change to superuser on 
> Live CD
>     Current text: "Root is set up as a role on the live CD. Therefore, 
> the only way you can become root on the Live CD is to use the pfexec 
> su command, so that RBAC can authorize the operation."
> 2 - Add more specific pointers to beadm utility.
> 3 - Add more specific pointers for IPS GUI and screencast.
> 4 - Clarify what could happen if you interrupt an installation in 
> progress.
>     Dave says: If no partitioning operations were required then this 
> won't be an issue, you just won't have an installed and bootable system.
> 5 - Do we want to say more about the default file system setup in the 
> ZFS storage pool created by the installer? I removed existing 
> specifications about swamp and /usr..., as it was incorrect.
>
> Do additional review of the following existing sections
> --------------------------------------------------------
> 1 - Recheck multibooting section
> 2 - validate the GParted process.
> 3 - Recheck existing partitioning procedure.
> 4 - Recheck default settings
> 5 - Recheck disk panel instructions
>
> Barbara
>
>
>


Reply via email to