By user9148476 on Mar 05, 2010
The rest of this should be old-hat to folks that have done image-updates before. The actual upgrade:
$ pfexec pkg uninstall entire PHASE ACTIONS Removal Phase 54/54 PHASE ITEMS Reading Existing Index 8/8 Indexing Packages 1/1So far so good...
$ pfexec pkg image-update --be-name on-nightly DOWNLOAD PKGS FILES XFER (MB) Completed 224/224 3251/3251 105.8/105.8 PHASE ACTIONS Removal Phase 1639/1639 Install Phase 1845/1845 Update Phase 7060/7060 PHASE ITEMS Reading Existing Index 8/8 Indexing Packages 224/224 Indexing Packages 224/224 Optimizing Index... PHASE ITEMS Indexing Packages 791/791 A clone of opensolaris_133 exists and has been updated and activated. On the next boot the Boot Environment on-nightly will be mounted on '/'. Reboot when ready to switch to this updated BE.And after the reboot, am I running the bits from my workspace?
$ uname -v onnv-ipsGiven when I cloned the gates, I'm running an snv_135 base, plus a few pushes. When build 136 rolls around, I plan to return to updating from the development repository and keep all the consolidations up to date.