On 01/14/10 01:39 PM, Sundar Yamunachari wrote: > Sarah, > Thank you for responding to my comments. More comments to your response. > > Sarah Jelinek wrote: ... >>> - The differences between 2 (Installation from pre-packaged media, >>> such as a CD, DVD, or USB flash memory stick) and 4 (Booting of the >>> installation environment from media such as CD, DVD, or USB flash >>> memory) are not clear. What do you mean by installation in this case? >> >> One describes the installation itself and the other simple notes what >> boot mechanisms we will provide. So, there isn't any specific >> installation method implied in the statement "1.Booting of the >> installation environment from media such as CD, DVD, or USB flash >> memory." Just how we plan to provide the booting to get to the >> installation environment > You need to boot to do the install. So I consider them together.
There isn't meant to be any requirement to specifically boot in order to install. It may be the case that implementations of an installer may have such requirements (and right now ours do), but one could imagine an installer of Solaris that uses the architecture but actually runs under some other OS such as BSD or Linux or Windows (such installers actually exist for some specialized Linux distros, in fact). Tying them together architecturally isn't necessary and actually undermines the flexibility to do those sorts of things. >>> Page 5: >>> - get_progress_estimate(): retrieves an estimate of the time >>> required to execute the checkpoint >>> My understanding of the checkpoint is that it is a milestone or >>> endpoint. How can you estimate with out a starting point? >> >> This method asks the checkpoint for its estimate on time, length, >> whatever way we are estimating progress(this hasn't been designed >> yet). The engine has to ask all registered checkpoints for this, and >> then it must create a progress total, with the milestones, for giving >> progress to the progress receivers. > The expectation is that the each checkpoint will provide the time (or > length or something) it takes to complete the tasks defined by the > checkpoint? > Yes, the checkpoint provides its own estimate, hopefully based on the parameters of the installation. This may be in some standard unit (so that it can be scaled appropriately) rather than an exact time, but we'll sort that out at design time. The point is to avoid hard-coded percentages such as are in the current GUI. Dave
