Given that the current openSolaris installer does not allow customization
of packages, it seems the only real choice is to let it do its thing and
then modify the packages afterwards.
You could either finish the installation, reboot into the installed system,
and then start adding/removing packages, or modify the package set after
the installation program finishes, but before rebooting.
Intuitively, it seems the second option would be cleaner. The SMF manifests
won't be imported, and none of the unwanted services will have a chance to
start.
Would there be any issues in running the pkg command with the alternative
root option under the live CD after the installation but before rebooting?
How thorough is package removal? Will removing a package result in a system
identical to one in which that package was never installed in the first
place? Or will there be miscellaneous cruft left?
I was playing with removing packages after the reboot from the running
system. Removing one of the gnome packages resulted in this:
Warning - directory var/log/gdm not empty - contents preserved in
/var/pkg/lost+found/var/log/gdm-2008-05-14+19:47:45
An interesting new use of the lost+found directory convention :). I assume
in this case var/log/gdm was owned by the package being removed, and
contained files not part of the package. So it moved the files elsewhere,
and then deleted the directory.
On another note, how similar are package names between S10U5 and
openSolaris? I already have a pretty good list of packages I want installed
under S10U5, would that be roughly similar to the openSolaris equivalent?
Or would it be better to ignore that list just start from scratch?
Thanks much...
--
Paul B. Henson | (909) 979-6361 | http://www.csupomona.edu/~henson/
Operating Systems and Network Analyst | henson at csupomona.edu
California State Polytechnic University | Pomona CA 91768
