Try running:
pfexec zoneadm -z zonename install -P
publisher=http://pkg.opensolaris.org/release
On build 131 having same issue with Sanity check.
Reverting to release looks to be working. I'll have
to change publisher to dev once it's installed but
at least it's installing.
Take that
So looks like the system is trying to install the incorrect version of the
entire package:
ent...@0.5.11,5.11-0.131:20100121T042929Z
But the version available in the dev release is:
ent...@0.5.11,5.11-0.131:20100115T044400Z
The text install image has a later *entire* package so how do I get
Jerry Jelinek wrote:
usr/src/lib/brand/native/zone/sw_support.c
1115
1116 } else if (strcmp(buf, SUNW_PKG_ALL_ZONES) ==
0) {
1117 infop-zpi_all_zones = B_TRUE;
1118
My thought is that if the package name is SUNWsolnm,
infop-zpi_all_zones
I looked into this a little when I hit it, and basically it's a
limitation of the opensolaris pkg commands.
I'm going for memory here, but I think the list function returns only
the lastest version from the repository, and refuses to find anything
else regardless of arguments, while the
Tristan Ball wrote:
I looked into this a little when I hit it, and basically it's a
limitation of the opensolaris pkg commands.
I'm going for memory here, but I think the list function returns only
the lastest version from the repository, and refuses to find anything
else regardless of
CarlsonJ, I'm afraid that the unfortunate subject line of these e-mails has
deceived you and others as to what the real problem here is. No one here is
really trying to install an snv_version in a non-global zone that is different
from the snv_version in the global zone (anyone who has more
However the shell scripts used to create a zone rely on the pkg list
function when searching for entire...
If you're keen, patching the scripts to use a search rather than list
might be a feasible way to allow the zone commands to install a
specified release, rather than the lastest.
Where
NOTE: In my opinion, Indiana snv_129 is an exceptionally outstanding release
and is pretty much the best OpenSolaris build released so far except for this
one minor glitch with zone creation that didn't start to happen until snv_130
and snv_131 came out in the /dev repository.
PROBLEM:
ZONES
I reposted a summary of the issue with a different subject line so that people
won't get confused anymore.
--
This message posted from opensolaris.org
___
zones-discuss mailing list
zones-discuss@opensolaris.org
more details
SunOS opensolaris 5.11 snv_111b i86pc i386 i86pc
Linux zone
#
zonename: centos2
zonepath: /export/home/centos2
brand: lx
autoboot: true
bootargs:
pool:
limitpriv: default,net_rawaccess,proc_owner,sys_config,file_dac_read
scheduling-class:
ip-type: shared
hostid:
net:
address:
10 matches
Mail list logo
