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 would
al Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> 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 st
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
Tim Cook wrote:
Hi Gerald,
When I run :
zonemgr -a modify -n global -G nano
I get the following error(s):
zlogin: 'zlogin' not applicable to the global zone
zlogin: 'zlogin' not applicable to the global zone
Error: The wget command is required to download and install the
Blastwave pkg-get.pkg p
Tim Cook wrote:
I'm confused then if /opt is not inherited by default. This was my
scenario:
Install snv_b55. Then installed the pkg-get tool from blastwave and
installed screen, openssh, and a few other utils (all of which go into
/opt/csw/whatever. I then created my zpool tank, and then put
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 " option. No
Tim Cook wrote:
So what about /opt/csw, is there anyway to prevent the zones from
linking to it? I know you can't remove it from the inherit-pkg-dir
because it says it's invalid. It's been somewhat a pain to use pkg-get
(blastwave) with zones because of it.
I don't think I understand what you
[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 - n
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:
Learn something new every day. I didn't know that and thanks for the
clarification. Your suggestion of introducing a "whole root zone" makes
should be revisited. Not because of lazy typists but because of
incorrect assumptions folks (like me) might make.
[EMAIL PROTECTED] wrote:
FYI, you can
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 a
FYI, you can also use "create -b" (blank) so you don't have to run
remove-pkg-dir 4 times.
John Clingan
Sun Microsystems
Sent from mobile phone.
-Original Message-
From: Tim Cook <[EMAIL PROTECTED]>
Subj: [zones-discuss] New zone, sysidtool:net isn't starti
On Mon 29 Jan 2007 at 04:07PM, Tim Cook wrote:
> Help??? What did I do wrong here?
Tim,
Thanks for giving it a spin-- the usability feedback is good.
You are doing well so far-- now log into the zone on console
(zlogin -C z1) and answer the system identification questions so
the zone knows its
So I started by doing the following to create a zone. The zone resides on a
zfs pool. This is the first zone on this system:
# zonecfg -z z1
z1: No such zone configured
Use 'create' to begin configuring a new zone.
zonecfg:z1> create
zonecfg:z1> remove inherit-pkg-dir dir=/sbin
zonecfg:z1> remo
14 matches
Mail list logo
