Peter Tribble wrote: > On Tue, May 26, 2009 at 10:04 PM, Shawn Walker <swalker at opensolaris.org> > wrote: >> My problem with that is you could use that logic to justify any >> configuration changes a person might need to make during install. > > Not any; just those necessary to make the system come up correctly > on the network in a state that means you can connect to it or manage it > remotely.
Which may or may not even be possible at the time of installation. To you network setup is important, to another person, X configuration is important. >> It also complicates the install process from both a technical and user >> perspective. > > It shouldn't be complicated at all. From a user (enterprise user) perspective, > the uncomplicated route is single pass through all the questions up front. But that also causes duplication of all of the various network configuration programs / applications that are provided for the user after the system has started. >> I understand why you desire it to be part of the install process, but I tend >> to agree with the original philosophy behind caiman that tends towards >> configuration-less install. > > I wouldn't use it myself either way, but having seen how other people get > systems installed and configured, it seems to me that having the configuration > questions asked up front would be what's expected. Although I'm shocked > at how manually intensive some of those processes are. The point being that > you have to fit in with how users (customers!) work, rather than dictating to > them. There's a give and take to that though. If you give users exactly what they ask for, you'll often end up with a poorly designed and implemented system. Or even though you implement something exactly how it was asked for, they'll come back and say "that isn't what I asked for!" :) Sometimes users must adapt as well as the system. -- Shawn Walker
