On Sep 1, 2006, at 10:52 AM, Sarah Jelinek wrote: > Chris wrote: >> On Fri, 1 Sep 2006, Dave Miner wrote: >> >> >>> Ultimately, this part of the discussion is trying to solve the wrong >>> problem up front: note your assumption, "given the number of >>> questions >>> we have". The primary problem in the graphical install is the >>> amount >>> and complexity of input required to achieve a working install; >>> reducing >>> that will change the set of problems that the UI design needs to >>> solve >>> and probably send this discussion into very different (and far more >>> interesting) territory. Mike's mail, and Frank's response, are >>> pretty >>> reflective of the kind of basic understanding of the tasks and users >>> that we have to arrive at in order to generate a design that will >>> stand >>> up in the market vs. the competition. >>> >> >> One thing that stands out, especially from Mike's collection of >> screenshots is how many screens are devoted to the initial system >> identification compared to the install itself. And I would guess >> that a >> few first time users will probably wonder why they are entering >> the same >> information twice. >> >> > I assume you are talking about Solaris installer? If so, I agree. > It is silly to ask so many unnecessary questions and more than > once. This is one of the areas where we can and should reduce the > number of questions. It struck me as well that the other installers > don't ask these questions and don't need to ask them to achieve > installation.
I completely agree. The questions should represent the minimal set of questions necessary to accomplish a successful configuration in the user's environment. After all, why ask the question if the machine will not use that information? >> I know it's important to have the identification process, but >> maybe it >> would be nice to give users the option of taking the sysid >> settings of the >> install host, and pass them onto the installed image. >> > 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. 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. It's simple enough that an average joe could use it, yet complex enough that customized configurations (by subnet, for example) could be created. >> [ the remainder deleted for brevity ] >> >> > > _______________________________________________ > install-discuss mailing list > install-discuss at opensolaris.org > http://opensolaris.org/mailman/listinfo/install-discuss ----- Gregory Shaw Programmer, SysAdmin fmSoft, Inc. Network Planner shaw at fmsoft.com And homebrewer... Prayer belongs in schools like facts belong in organized religion. Superintendant Chalmers - "The Simpsons" -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.opensolaris.org/pipermail/install-discuss/attachments/20060901/7a349853/attachment.html>
