]
Sent: Wednesday, January 31, 2007 4:46 PM
To: Jerry Jelinek
Cc: Tim Cook; [EMAIL PROTECTED]; John Clingan;
zones-discuss@opensolaris.org
Subject: Re: [zones-discuss] New zone, sysidtool:net isn't starting
I recommend that you restrict blastwave bits to the non-global zone.
That way you
Blastwave is fine for installing in the global zone. However, this
implies that packages added or updated in the global zone would get
applied to ALL non-global zones as well. The only issue comes
when say you want to install just mysql in one zone and apache2 in
another zone. For this you
I recommend that you restrict blastwave bits to the non-global zone.
That way you cannot end up with package conflicts between the global
zone and non-global zones or between non-global zones.
I have made installing Blastwave packages really easy for you via
the zonemgr with the -G blastwave_pkg
Tim Cook wrote:
So essentially at this time blastwave is just a *bad idea* for global
zones. Is something like sunfreeware ok then? I assume the -G option
should work with those packages?
I don't know a lot of the details of blastwave and how
many different options it gives you.
However, in
[EMAIL PROTECTED] wrote:
FYI, you can also use create -b (blank) so you don't have to run
remove-pkg-dir 4 times.
Actually, the documented way to create a whole-root zone *is* to remove
the default inherit-pkg-dir resources. The reason for this is create
-b says to use a blank template -
FYI, you can also use create -b (blank) so you don't have to run
remove-pkg-dir 4 times.
Actually, the documented way to create a whole-root zone *is* to remove
the default inherit-pkg-dir resources. The reason for this is create
-b says to use a blank template - namely, no properties set and
When using the zone manager you just tack on a -t w to
zonemgr to create a whole root zone. The default is a
sparse zone or if you want to specify it from the command
line its -t s.
http://opensolaris.org/os/project/zonemgr/
Brad
On Mon, 2007-01-29 at 16:50 -0800, [EMAIL PROTECTED] wrote:
