Hi Richard. (and Hi Gavin and Alan). Why? Because I don't want to pollute version 151a with a new /bin/pkg. >From memory, I suspect that "pkg update pkg" didn't used to create a new BE. Old habits die hard.
I did actually read the upgrade release notes (http://docs.oracle.com/cd/E23824_01/html/E23811/glpgv.html#glpcn) before I started. I didn't however notice that "pkg image-update" has now been replaced by "pkg update". (Again - Why? - if the "image-update" argument is invalid, it should have said so. Why get people used to a particular syntax, then change it? Anyway, I'm trying again, but with "pkg update" instead of "pkg image-update". I won't "init 6" until I get home. I don't want my box to be circularly rebooting every minute for the next 6 hours. Cheers-Chris On Mon, Nov 28, 2011 at 12:17 PM, Richard Smith <richard.r.sm...@oracle.com> wrote: > Chris Wells wrote: >> >> Just upgraded from 151a (Solaris 11 Express), to Solaris 11 11/11 (x64), >> using all the wonderfulness that is beadm. > > Was beadm really necessary? Normally pkg creates new BEs when it needs to > while doing updates and you can tell it explicitly that a new BE is > required. > The release notes describe the procedure as: > > pkg update pkg:/package/pkg # creates new BE > reboot > pkg update --accept # creates new BE > reboot > -- Regards, Chris _______________________________________________ ug-msosug mailing list ug-msosug@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/ug-msosug
