* [email protected] ([email protected]) wrote: > > > >The point is that they don't *need* or have to be in the installer. > >They're just as beneficial and useful at firstboot, in a Visual Panel, > >or somewhere else. There is no overwhelmingly great reason to force > >them to be part of the install process. Installation should be about > >installation and the minimum amount of configuration to get the system > >going. Anything beyond that is a pollution of the process IMO. > > > Our customers want an "hands-off" install; an install which can be > customized to a point where the system reboots and nothing needs to > be done.
The graphical installer isn't going to solve this problem. The automated installer however would. > "Visual panels" do not work when you need to install 100s of systems. No, but a package which once installed as part of the automated installer that creates an smf service and method to do post-install customization would work. > The fact that you are required to configure a system after it is installed > is a bug. Any system which requires post-install configuration is broken > to a point that is not usable. That's your opinion of course, I and others pretty strongly disagree. There are things that should absolutely be asked at install time. However, install time is not the proper place to ask every possible question someone might want to configure. There's a balance to be struck. Of course there are differences between an interactive install and a 'hands-off' install. I think I've provided an answer for how to configure 'anything' post-install during an automated installation. Cheers, -- Glenn _______________________________________________ opensolaris-discuss mailing list [email protected]
