Peter Tribble writes: > > The > > sysid config stuff isn't consider a part of the core engine capability > > with Caiman. We consider the sysconfig stuff to be separate from the > > core engine. system configuration is something that should be available > > to users at all times, and the install system configuration is really a > > special case of the general stuff. > > I consider this to be a mistake. Configuration is a core > component of the installation process, so should be treated > as such. Making it available at other times is fine.
I don't agree. While I agree that giving the user access to configuration tools during install is a good thing (and would like to see us provide *more* access to *more* tools), I strongly disagree with the idea that install time should be a "special time." It should not be the case that there are special things that can be done when the system is installed, and that cannot be done at other times. In fact, the process of setting up these bits of configuration shouldn't be different. (E.g., setting up name services.) That's the problem that we end up with if we say that configuration is an integral part of installation. We end up with "special" bits of configuration magic there that end up being alien to the rest of the system -- users end up wondering how they can get back to the point where they can reenter or correct some information, and unless they reinstall the system, they really can't do that, because install time is special. And that's bad. Instead, it makes sense to me to say that install should be able to invoke configuration, but not that configuration is bolted to install's hip. -- James Carlson, KISS Network <james.d.carlson at sun.com> Sun Microsystems / 1 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677
