We don't have sparse zones in 2009.06
Hey db, if you don't have sparse root zones in OpenSolaris 2009.06, then what
do you call the sparse root zone I made in OpenSolaris 2008.11 by following
this tutorial:
http://houdini68.blogspot.com/2009/03/sparse-zones-cloning-and-zfs.html
The end
We don't have sparse zones in 2009.06
Hey Dan, if you don't have sparse root zones in OpenSolaris 2009.06, then what
do you call the sparse root zone I made in OpenSolaris 2008.11 by following
this tutorial:
http://houdini68.blogspot.com/2009/03/sparse-zones-cloning-and-zfs.html
The end
Ok, I read through everything that was posted again and it all makes sense now.
Sorry for being obnoxious, but obviously a lot of us sparse root zone users are
a little confused by how things work now in Indiana / Solaris 11 I don't
get why we can't somehow just use ZFS cloning and beadm
I'm not an expert on this, but I believe the non-global zones will update
themselves as long as you detach them before you do the pkg image-update.
Here is a link that shows how to do it using OpenSolaris 2008.11:
http://blogs.sun.com/jerrysblog/entry/updating_zones_on_opensolaris_2008
That
In OpenSolaris 2008.11 I used the /home directory for user home directories
instead of /export/home.
Don't know if that helps.
--
This message posted from opensolaris.org
___
zones-discuss mailing list
zones-discuss@opensolaris.org
What I meant to say was that my OpenSolaris 2008.11 ipkg zones use /home for
user directories instead of /export/home.
I think it maybe has something to do with the automounter not being set up
automatically in the zones? I know in the global zone in 2008.11, the /home
directory is off limits
One thing I've found to be true though: either a machine is all zoned, or not.
It gets horribly confusing to have real activity in the global zone,
where you can half see the non-global zones, so if you have zones
on a machine then it's easier to run nothing in the global zone and
just use
Did any of you guys go here:
http://sunsolve.sun.com
or try opening up a sunsolve support ticket? If you did, what did they say to
do to fix the problem?
--
This message posted from opensolaris.org
___
zones-discuss mailing list
Instead of a separate distro, perhaps it would be simpler for
everybody if there was a no-GUI server installation option that
simply doesn't install the GUI tools. Would that meet your needs?
Thanks for the quick response Jeff!
We also already did have a discussion about having a minimal
I know some of you guys are chuckling at my statements thinking well, maybe
his postfix and apache and BIND / named servers don't have a windowing
environment, but Oracle needs X-windows. Well, actually it's possible to
install Oracle without using X-windows on Red Hat Enterprise Linux (see
Rats. This post was supposed to be below my other two older posts in the forum,
not above them. My bad.
--
This message posted from opensolaris.org
___
zones-discuss mailing list
zones-discuss@opensolaris.org
But this is fairly far from the Zones-discuss topic.
I respectfully disagree, I think this is part of the Zones-discuss topic.
The whole reason people want a minimal OpenSolaris install is to have a global
zone with nothing running in it (except for maybe an SSH server and an internal
I hate to crash the party. But it looks like Linux already makes it possible to
run an NFS server inside of a Linux OpenVZ zone / container with most of the
same advantages that you would get from a Solaris non-global zone NFS server
implementation. For those of of you who aren't familiar with
Since a lot of people here said they weren't uber-skilled programmers. An easy
and quick way to put a band aid on the wound might be to port a working UNFS3
implementation to non-global zones:
http://unfs3.sourceforge.net/
You could create a compatibility layer for UNFS3 where the
I found this thread at forums.sun.com :
http://forums.sun.com/thread.jspa?threadID=5333685
Looks like some ambitious Solaris sysadmins have already been running UNFS3 in
Solaris Zones!
--
This message posted from opensolaris.org
___
zones-discuss
Bernd, did you detach the zones before doing the pkg image-update?
See the following links:
http://blogs.sun.com/jerrysblog/entry/updating_zones_on_opensolaris_2008
http://opensolaris.org/jive/thread.jspa?threadID=119288tstart=0
--
This message posted from opensolaris.org
After detaching the zone and reattaching it like it's described in the
docs the zone works again. Thanks.
I'm glad it worked.
Hals und Beinbruch!
--
This message posted from opensolaris.org
___
zones-discuss mailing list
Ok, now I'm hitting this bug too:
r...@solarisunix:~# zoneadm -z testzone3 install
A ZFS file system has been created for this zone.
Publisher: Using opensolaris.org (http://pkg.opensolaris.org/dev/ ).
Image: Preparing at /export/zones/testzone3/root.
Cache: Using
Ok, so the data that I need is definitely out there on the internet somewhere
in the repository:
r...@solarisunix:~# pkg search -r entire | grep 127
description setentire pkg:/ent...@0.5.11-0.127
pkg.summary setentire pkg:/ent...@0.5.11-0.127
pkg.fmri
My bad, sorry for the typo, the data I need to get somehow to install into the
zone is here:
r...@solarisunix:~# pkg search -r entire | grep 129
description setentire pkg:/ent...@0.5.11-0.129
pkg.summary setentire pkg:/ent...@0.5.11-0.129
pkg.fmriset
Does anybody know if this might be related to this bug?
http://defect.opensolaris.org/bz/show_bug.cgi?id=13683
--
This message posted from opensolaris.org
___
zones-discuss mailing list
zones-discuss@opensolaris.org
This is the output for my pkg authority if it helps anyone with this:
r...@solarisunix:~# pkg authority
PUBLISHER TYPE STATUS URI
opensolaris.org (preferred) origin online
http://pkg.opensolaris.org/dev/
r...@solarisunix:~# uname -a
SunOS
I've been googling on this for over 10 hours so far, but still no luck, so far
the best hint I found was this link:
http://uros.opensolaris.rs/2010/01/05/updating-opensolaris-to-arbitrary-build-version/
on updating to a specific version. I tried a variation of the command that UROS
was using
Since no one in the opensolaris community seems to be willing to help
troubleshoot this issue, I guess I'm just going to have to try to brute force
this by trying every possible combination of zoneadm -z testzone install with
different flags and options pointing to the package that I know
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
Here is the bug and the fix, if anyone wants it or finds it useful when they
google this error message and arrive at the end of this thread:
http://defect.opensolaris.org/bz/show_bug.cgi?id=13493
--
This message posted from opensolaris.org
___
These links might help to add a little bit more to the explanation (this is my
collection of all time favorite OpenSolaris zones related links here):
http://blogs.sun.com/jerrysblog/entry/updating_zones_on_opensolaris_2008
http://blogs.sun.com/jerrysblog/entry/zones_on_opensolaris_2008_11
Also, another important caveat / missing piece that I noticed is missing from
all of the OpenSolaris Indiana Sun blogs and documentation I've looked at so
far: to do resource caps on CPU and RAM memory in OpenSolaris I think you need
to install the SUNWrcap package first like this:
# pkg
31 matches
Mail list logo
