Sundar Yamunachari wrote: > Ethan Quach wrote: >> 1.2 Use cases >> >> #6 - Can you elaborate a bit on how you see this use case as >> being related to system configuration? > No. It is not related to system configuration. The process of > upgrading to the correct zpool version is similar to the system > configuration setup and it is run on the first reboot after > installation. Evan suggested this use case.
Can you please remove it then, if it doesn't belong here. >> >> #7 - If this use case falls outside the installer, why are we >> mentioning it here? > The process is similar to use case 2 and I want to capture that use case. Is your intent to capture that the user experience in these use cases should be the same? >> >> >> 1.3 - Are you defining these as the "minimum" set of system >> configuration parameters that's expected to have been gathered, >> one way or another, during the installation process? If so, I >> don't think the networking parameters should really be on this >> list. We have nwam for this don't we? > These are minimum parameters needed for a useful system after > installation. The user provided these parameters in the profile. We > need support for setting up these parameters in the SMF. For example, > the user could specify static IP for the system. The use of "minimum" is what doesn't fit here, at least not to describe the networking portions anyway. Static IP *could* be provided, but it is not required for a usable system after installation. It seems to me the list you're trying to identify here are the system configuration parameters that a user would want to set up at installation time, and thus is dictating what you view as the minimal list of things that need to be supported by whatever this mechanism does. >> >> #2 - Last sentence. Why is this a requirement for us? > This is for providing feedback to the user before reboot. But since #3 is a requirement, what use is this really? thanks, -ethan
