Kyle McDonald writes: > James Carlson wrote: > > Secondly, there's no fundamental requirement that every bit from the > > "snapshot" is installed on any given system. Many things are optional > > components, and it's perfectly possible for a system installed from > > "Update X" that is known to contain "Feature Y" not to have any part > > of Y installed at all. > > > Again, I aggree with you abotu determining this stuff on a running > system post-install. > > But during install, in a begin or finish script. When figuring out what > Features are available to install on the machine, it is an indicator. > > It's the only indicator I have for several things that are impossible > for me to test for any other way. For example, how can I test to see if > the Jumpstart profile processor in the release I'm running in will > accept the 'mirror' option to the filesys keyword, or if I'll have to do > the SVM operations manually in the Finish scripts?
I'm not a jumpstart guru (obviously), but is it possible to invoke "check" at that point? That'd be the right tool to validate that the proposed rules are acceptable. > I don't know how you say that the mapping s are undocumented. Each new > release of Solaris documents the packages that are removed or added, the > changes to the jumpstart keywords are also documented as being available > from some release and on, or up till some release. We've got informal documentation of some of these things, but no stability levels or official system documentation. I don't see how anyone could depend on it reliably. -- James Carlson, Solaris Networking <james.d.carlson at sun.com> Sun Microsystems / 35 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677
