Hi, Could anyone explain me the following issue.
My sqa36.sfbay machine had OSol snv_133 when I decided to upgrade it to snv_134 by using pkg image-update. 'pkg image-update' worked and completed successfully with the final message: ======================= A clone of opensolaris exists and has been updated and activated. On the next boot the Boot Environment opensolaris-2 will be mounted on '/'. Reboot when ready to switch to this updated BE. ========================== But after rebooting machine I typed 'uname -a' and saw andold snv_133 version again: sqa36% uname -a SunOS sqa36 5.11 snv_133 sun4u sparc SUNW,Sun-Fire-V240 At that time 'beadm list' showed: # beadm list BE Active Mountpoint Space Policy Created -- ------ ---------- ----- ------ ------- opensolaris - - 4.71M static 2010-02-25 12:00 opensolaris-1 - - 825.99M static 2010-03-04 12:24 opensolaris-2 NR / 7.62G static 2010-03-24 14:36 So I deleted an old opensolaris-1 BE: # beadm destroy opensolaris-1 and rebooted machine again. But 'uname -a' still shows snv_133. Then I tried to apply 'pkg image-update' again, but this time it says: No updates available for this image. So I'm kind of confused, what version I really have now? Thanks, Sergey _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
