Hi Narendra, > I have one basic question and a suggestion. > Is there any hard dependency between "System Identification" and > "Solaris Install"? > What I mean is, is it very much necessary that, "Sysid" should come > befor installation starts? yes, some of it has to come before install starts. But, not all of it. > > Will it not be a good idea to push "sysid" ( I mean system > configuration) to the post-install phase. As much as we can, yes, we are going to do this. > When the installation starts, try to guess or ask very few "Very much > necessary" questions (it will be very good if nothing is asked) and > then jump to installer part. Exactly what we are planning. > And after the installation is over, when the root user logs in for the > first time, provide him a screen, where the current configuration is > presented. > Here, the root user can accept the existing configuration or change > the values in the same screen and then press the accept button. > Also, give him an option to create more users. > All these things are done in a single screen. > This are the plans we have now. The current mockup doesn't show this but it will as we work through this. > This will help in reducing the number of screen presented during > installation. So, install will become faster. > And we will not end up asking "configuration questions" and trash > them, if the user selects "Upgrade" instead of "Initial Install". > Exactly. It is unnecessary to ask for configuration if the user chooses upgrade. > Hope this makes some sense. It does, and is perfectly aligned with what we are planning.
Thanks for reviewing this. sarah **** > > Regards, > Narendra > > On 12/6/06, *David Bustos* <David.Bustos at sun.com > <mailto:David.Bustos at sun.com>> wrote: > > Quoth Sarah Jelinek on Wed, Nov 08, 2006 at 01:21:48PM -0700: > > We have completed the first draft of the Caiman install project > > architecture document and have posted it for review. > > > > You can get it: > > http://www.opensolaris.org/os/community/install/caiman_arch.pdf > > Page 9: > - What do you mean when you say that the "Software selection > service > ... [verifies] the consistency of the software selection"? Why > would the GUI allow the user to choose inconsistent software? Or > shouldn't the GUI allow another functional unit to keep the user > from choosing inconsistent software? > > - What do you mean by "[The] Essential System Configuration > service is > called to set system settings such as time zone and locale."? > I presume you mean gathering settings to be transferred to the > newly > installed system during the "Configuration Phase", in which case > I think you should reword this sentence to clarify. Though it > seems > that locale is something that should be used by the installer > itself. > > 3. Channel Service, page 18: > - What does "During an interactive installation, provide the ability > to provide of streaming data." mean? How is this different > from the > logging service? What is being channeled, and between what? > > 4. Customization Service, page 19: > 4.2 Requirements, item 4: Is this a finish script? > > 4.2 Requirements, item 6: Do you mean that this component will log? > If not, shouldn't logging be left to the logging service? > > 5. Driver Verification Service, page 20: > 5.2 Requirements, item 5: Isn't querying repositories for the latest > versions of the driver a duplication of what the ITU Service does? > > 5.2 Requirements, item 6: You mean provide information on devices > missing drivers, right? > > 7. GUI Service, page 23 > 7.1 Purpose: "Will determine system configuration data automatically > if possible."? How is the GUI qualified to do that? > > 9. Jumpstart Profile Service, page 25 > 9.2 Requirements, item 1: How will you "provide automated > detection of > jumpstart installation request."? Is this just a timeout of > a prompt? > > 9.2 Requirements, item 7: What is a remote software update? > > 9.2 Requirements, item 9: Can you provide motivation for "support to > upgrade from a partial repository."? > > 10. Logging Service, page 27 > 10.2 Requirements, item 4: Do you anticipate that the logging > service > will have a lot of bugs? > > 10.2 Requirements, item 6: Will all installation applications be > able > to display the logs? > > 10.2 Requirements, item 14: You mean "other processes are still > executing", right? > > 10.3 Non-Requirements, item 1: I think log messages are typically > exempt from localization. Are you planning otherwise? > > 11. Metadata Service, page 29 > - The metadata service is not mentioned in the Introduction, > though it > does appear in the diagrams. Why is that? > > 11.1. Purpose > - Can you give some examples of the metadata you will be storing? > > - What is "CSN format"? > > - What is "Software Update manager"? > > 12. Patching Service, page 30 > 12.2. Requirements, item 4: This ability seems similar to one of the > ITU Service. And the Software Repository Service. Should > they be > factored together? > > 13. Post-Install Service, page 31 > 13.2. Requirements, item 1: What are "default post-install actions"? > > > David > _______________________________________________ > install-discuss mailing list > install-discuss at opensolaris.org > <mailto:install-discuss at opensolaris.org> > http://opensolaris.org/mailman/listinfo/install-discuss > > > > > -- > Warm Regards, > Narendra > > Visit my blogs at: > http://ssnarendrakumar.blogspot.com/ > http://blogs.sun.com/roller/page/ssnkumar > ___ ___ __ _ > / __/ / __/ / | / / > _\ \ _ \ \ / /| |/ / > \___/ \___/ /_/ |__/
