On 07/27/10 01:37 AM, Gary Pennington wrote:
On Mon, Jul 26, 2010 at 11:48:24PM -0700, Sunay Tripathi wrote:
On 07/26/10 11:37 PM, Gary Pennington wrote:
On Mon, Jul 26, 2010 at 10:54:24PM -0700, Sunay Tripathi wrote:
Guys,

I think we had discussed allowing a ipkg brand zone to be installed
without a network i.e. going to a repo if I already have a installed
system running. Can someone tell the correct options? I am trying
the -d option but that fails ...
# zoneadm -z test install -d /
pkg list: no packages matching 'entire' installed
you must specify -u (sys-unconfig) or -p (preserve identity).
brand-specific usage:
         install {-a archive|-d path} {-p|-u} [-s|-v]


I surmise that your test system no longer has the 'entire' package,
probably
because you have used onu on it. The procedure for creating the zone
depends on locating the 'entire' package, so it is failing because it can't
locate it. (onu removes the entire package.)

You could re-install 'entire'...

Kinda hard since I can only use external repositories. I compiled
one of the newer builds and thats what I am running so can't install
entire from b134. Is there a workaround or its just not possible
to create a zone?


I'm not aware of a straightforward workaround.

You might be able to setup a repository using your built packages and
then install the "on-nightly" incorporation and hack up the zone install
scripts to use "on-nightly" in place of "entire". I haven't tried
doing this, but it *should/could* work...

Yes, I see it. I think it should be straight forward (at least for me).
I did another work around which didn't require hacking the zone
install scripts. Basically, I setup a pkg.depotd on the build
packages and made it the primary while still keeping the
opensolaris.org. The zone install still complained about 'entire'
but it at least managed to finish install and the zone did come up.

for others on the list ...

So for people wondering how to go forward after an onu (mostly
applies to people outside of Sun), if you are were running build134
and wanted to go to a recent build, just build the workspace and
run a pkg.depotd (/usr/lib/pkg.depotd -d ws/packages/i386/nightly-nd/repo.redist -p 5000); pkg unistall redistributable;
pkg uninstall entire; pkg install redistributable (at this point
you are runnign what you built but can't add entire back unless
you are inside Sun). You also need to have your pkg publisher
something like
PUBLISHER                             TYPE     STATUS   URI
on-nightly (preferred) origin online http://192.168.1.9:5000/ opensolaris.org origin online http://pkg.opensolaris.org/dev/


At this point, you should be able to create zone on a newer
build that you are running. There was a mention of creating the
zone before you do the onu i.e. on b134 but I did had some
running zones on b134 which became unhappy when I went to
higher build (init dumping core constantly). Doing a
zoneadm detach followed by zoneadm attach -u failed again
due to entire not being there.

Cheers,
Sunay





This kind of problem makes me wonder if (in the future) we need an
enhancement which allows a user to specify exactly which packages/
incorporations should be installed into a zone, rather than just assuming
it
will be entire. Something like

zoneadm -z test install -d / -t MyOwnIncorporation,MyOtherIncorporation

(-t for 'target packge', I can't suggest -p because it is already used.)

That would be nice. BTW, if -d / is specified, you could look into
/var/pkg and pretty much get all the packages already installed in gz
and just use that. I don't know enough of pkg internal structure but
there must be a catalog (of installed packages) somewhere which
should all be available in /var/pkg/*

I just noticed
"Bug 14684 -  zone attach incorporation logic needs enhancement"
as well. How were you planning on fixing it?


This has been fixed. See the CR:

http://defect.opensolaris.org/bz/show_bug.cgi?id=14684


It would, of course, be the user's responsibilty to make sure that this
list of packages resulted in a bootable zone (although we could also
process the list to guarantee it was a useful/bootable zone.).

Can't find the ipkg manpage also. BTW, it would be good to allow
a equivalent of native zone to be created without much fuss :) and
perhaps the default should be along those lines (instead of
needing a repo).


man ipkg(5)

Ah.. For a change Dr. google doesn't have the answer but the manpage
is on the system :)

Cheers,
Sunay


_______________________________________________
zones-discuss mailing list
zones-discuss@opensolaris.org

Reply via email to