I'm completely with Dan on this. This is essential functionality for
enterprise customers particularly for minimisation of zones.
It is effectively what Jumpstart does today - it can take a list of
packages (it understands metaclusters too but that concept is
effectively dead with IPS) to install.
There is an existing RFE for SRV4 based Zone install to allow passing a
specific list of packages to build the zone. It could even be made to
work at one point by a little hackery (I don't believe it does anymore
and I haven't tried in several years now).
I believe the functionality belongs in 3 places. pkg(1) the tool (and
for that take the GUI too), the Automated Installer, and the distro
constructor.
These cover three different cases.
1) in the pkg(1) for scripting installs of sets of packages for whatever
reason.
2) Automated Installer: Setting up lots of near identical systems, that
aren't disk based clones and aren't zones. Where a custom distro isn't
needed.
3) Distro Constructor for more advanced uses than AI can provide and
where a custom distro is a better choice.
--
Darren J Moffat
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
