Gregory Shaw wrote: >>> >> This is something we are thinking about and working on. The flow of >> control in our existing GUI, specifically the sysid questions for >> installation is clearly broken. We don't need to ask so many questions >> for Solaris installation. A lot of it can be gleaned from the existing >> system or from the network. > > I'd like to see this go one step farther: Load the sysid and > configuration information into a centrally available repository that > could be queried instead of asking questions.
Isn't this possible, to some degree, today? http://docs.sun.com/app/docs/doc/817-5504/6mkv4nh2i?a=view Chapter 6 Preconfiguring System Configuration Information (Tasks) This chapter describes how to preconfigure system information. Preconfiguration can help you to avoid being prompted for this information when you install the Solaris OS. > > The current jumpstart can be automated with start and end scripts, but > that's a very complex solution. If a central repository for information > were available, it would be possible to boot a CD (or across the net), > type in a URL for the configuration information, and stand back as the > system installs itself. Some things, such as JET <http://www.sun.com/bigadmin/content/jet/index.html>, ease the complexity. While it is not for everyone, some do find JET quite useful. And you can specify a sysidcfg file via url at boot time although it is not documented very well, or at least I can't find it. SPARC <http://docs.sun.com/app/docs/doc/817-5506/6mkv6ki9g?a=view> X86 <http://docs.sun.com/app/docs/doc/817-5506/6mkv6ki9q?a=view> Matt
