Most users/developers are not affected by this flag day.  If you use onu
or pkg image-update in a typical way, and use http://ipkg.sfbay/dev as
the origin/URI for your opensolaris.org publisher, you may ignore the
rest of this mail.  If not, read on...

With my push of

changeset:   13013:3c7681e3e323
tag:         tip
user:        Glenn Lagasse <glenn.laga...@oracle.com>
date:        Wed Aug 04 12:28:19 2010 -0700
description:
        PSARC 2010/059 SNAP BE Management
        6964804 SNAP BE management into ON
        6971379 libbe should capture and give useful error when
installgrub or ict.py fails.
        6971390 beadm does not support labeled brand zones
        6971394 BEADM_ERR_BE_DOES_NOT_EXIST has an extra space
        6971397 libbe error messages need internationalization
        6971402 Remove be_get_last_zone_be_callback
        6971409 be_create_menu returns errors from both be_errno_t and
errno sets

The effect of this integration is such that the install/beadm package
which was previously delivered from the Install consolidation
slim_source repository is now moved into ON.  As such, this
cross-consolidation change will require some care be taken when
upgrading across it in situations where you don't use ipkg.sfbay/dev as
the origin/URI for your opensolaris.org publisher.

Before you can successfully update your machine to a nightly image which
contains these changes you must first do one of the following:

a) Set your origin/URI for opensolaris.org to http://ipkg.sfbay/dev

or

b) build the slim_source repository and install two packages from that
build area into a new BE (see more details below)

If you have access to http://ipkg.sfbay/dev then I highly recommend
option (a).  Once you've set your origin/URI for opensolaris.org to
http://ipkg.sfbay/dev you can simply upgrade via ONU or image-update as
you normally would.

If you do not have access to http://ipkg.sfbay/dev (External Developers)
then you'll have to use option (b).  The details for that are as
follows:

1) Build the slim_source repository.  You can fetch a copy of it via:

hg clone ssh://a...@hg.opensolaris.org/hg/caiman/slim_source

Once you have a local copy of the source, you need to build it.  You can
follow the instructions outlined in usr/src/README to accomplish that.
Once built, you're ready to create a new BE and upgrade the relevant
packages in it to the ones that you just built.  We'll presume that
you're running on a BE at build 134, and that you've got a copy of the
slim_source repository at /home/username/slim_source:

pfexec beadm create newBE
pfexec beadm mount newBE /mnt
pfexec /usr/lib/pkg.depotd -d 
/home/username/slim_source/packages/i386/nightly-nd -p 20000
pfexec pkg -R /mnt set-publisher -P -g http://localhost:20000/ install-nightly
pfexec pkg -R /mnt set-publisher --non-sticky opensolaris.org
pfexec pkg -R /mnt uninstall entire
pfexec pkg -R /mnt install 
pkg://install-nightly/consolidation/install/install-incorporation 
pkg://install-nightly/install/beadm
pfexec pkg -R /mnt set-publisher --non-sticky install-nightly
pfexec beadm unmount newBE

You've now created a new BE that has the slim_source required changes to
navigate this flag day.  When you're ready, you can activate the new BE
and reboot into it:

pfexec beadm activate newBE
pfexec init 6

Now, you're ready to move on to the ON portion of the flag day.  You'll
need to start up your install-nightly repository:

pfexec /usr/lib/pkg.depotd -d 
/home/username/slim_source/packages/i386/nightly-nd -p 20000

And now you can build the ON gate that contains this changeset as you
normally would and use ONU as normal to upgrade to those bits.

Questions related to this integration should be sent to the project team
via our discussion list: caiman-disc...@opensolaris.org

Bugs/RFEs:

For issues related to beadm(1M), please file them under
solaris/utility/beadm either in bugster internally at Oracle or
bugs.opensolaris.org externally

For issues related to libbe, please file them under
solaris/library/libbe either in bugster internally at Oracle or
bugs.opensolaris.org externally

-- 
Glenn
_______________________________________________
on-discuss mailing list
on-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/on-discuss

Reply via email to