Dennis Clarke wrote: > OKay, so I have been sending emails all day to you guys in which I was > trying to figure out what to do and how to do it and why was I doing > this anyways ? :-) > > well here is the good news my friends ... earlier today I upgrade the > SUNWipkg software to the absolute latest and greatest and I did that > blindly without thinking too much. > > That went smoothly like so : > > -bash-3.2# pkg version > d974bb176266 > -bash-3.2# pkg install -v [EMAIL PROTECTED]:20080620T101740Z > Before evaluation: > UNEVALUATED: > +pkg:/[EMAIL PROTECTED],5.11-0.91:20080620T101740Z > > After evaluation: > pkg:/[EMAIL PROTECTED],5.11-0.86:20080426T174940Z -> > pkg:/[EMAIL PROTECTED],5.11-0.91:20080620T101740Z > None > DOWNLOAD PKGS FILES XFER (MB) > Completed 1/1 100/100 0.89/0.89 > > PHASE ACTIONS > Removal Phase 2/2 > Update Phase 92/92 > Install Phase 11/11 > -bash-3.2# pkg version > 0ae5e72ba7ee > > Now maybe I wasn't supposed to do that and I should have just stuck > with something related to snv_86 or something like that. I really > don't know .. I just wanted to do what a John Doe average user would > do. Grab the latest and then upgrade to that. > > Seems to work fine for me. What were other people talking about ? I > don't see a problem and .. I couldn't find one. > > I then decided to just update the whole shooting match with this sort > of thing : > > -bash-3.2# pkg image-update -v > Before evaluation: > UNEVALUATED: > +pkg:/[EMAIL PROTECTED],5.11-0.91:20080613T174525Z > +pkg:/[EMAIL PROTECTED],5.11-0.91:20080616T184243Z > +pkg:/[EMAIL PROTECTED],5.11-0.91:20080613T182134Z > +pkg:/[EMAIL PROTECTED],5.11-0.91:20080613T182617Z > > After evaluation: > pkg:/[EMAIL PROTECTED],5.11-0.86:20080426T175140Z -> > pkg:/[EMAIL PROTECTED],5.11-0.91:20080613T174525Z > . > . > . > None -> pkg:/[EMAIL PROTECTED],5.11-0.91:20080613T180217Z > None -> pkg:/[EMAIL PROTECTED],5.11-0.91:20080613T182501Z > None -> pkg:/[EMAIL PROTECTED],5.11-0.91:20080613T174340Z > None -> pkg:/[EMAIL PROTECTED],5.11-0.91:20080613T182505Z > None > DOWNLOAD PKGS FILES XFER (MB) > Completed 557/557 15551/15551 1334.65/1334.65 > > PHASE ACTIONS > Removal Phase 3207/3207 > Update Phase 14966/14966 > Install Phase 6234/6234 > Jul 2 04:01:27 aequitas pseudo: pseudo-device: lofi0 > Jul 2 04:01:27 aequitas genunix: lofi0 is /pseudo/[EMAIL PROTECTED] > A clone of opensolaris exists and has been updated and activated. On > next boot the Boot Environment opensolaris-1 will be mounted on '/'. > Reboot when ready to switch to this updated BE. > -bash-3.2# beadm list > > BE Active Active on Mountpoint Space > Name reboot Used > ---- ------ --------- ---------- ----- > opensolaris-1 no yes - 5.29G > opensolaris yes no legacy 3.50M > -bash-3.2# > > So there you have it ... it did exactly what it should and I didn't > see a single problem. > No network lag or timeouts or anything like that. > > see details at : > http://www.blastwave.org/dclarke/OpenSolaris/image-update-woohoo.txt > > so gee ... now what ? reboot I guess ? > > Before I do that .. is there anything new in the GRUB config for me to > look at? I have this machine set to run with a serial console and I > hope that is retained. > Since you are upgrading from 2008.05 to build 91 you need to do the following.
> Instructions to update OpenSolaris 2008.05 to build 89 or later > ================================================================ > > The command "pkg image-update" can be used to update an OpenSolaris > 2008.05 system to build 89 or later. However due to changes in the > GRUB boot system, one must manually update the Master Boot Record (MBR) > to include these latest changes. > > When "pkg image-update" completes successfully, it will print a message > of the form > > A clone of opensolaris exists and has been updated and > activated. On next boot the Boot Environment opensolaris-1 will > be mounted on '/'. Reboot when ready to switch to this updated > BE. > > The name of the newly created clone can also be seen by looking for the > "Active on reboot" entry in the output of the "beadm list" command > > $ beadm list > BE Active Active on Mountpoint Space > Name reboot Used > ---- ------ --------- ---------- ----- > opensolaris-1 no yes - 17.06M > opensolaris yes no - 33.92M > > First, mount the clone under the /mnt directory > > $ pfexec mount -F zfs rpool/ROOT/opensolaris-1 /mnt > > Next, update the GRUB configuration on your ZFS boot device(s) using > > $ pfexec /mnt/boot/solaris/bin/update_grub -R /mnt > > When you're ready to boot into the updated boot environment, you can > reboot(1M) or init(1M) as usual. > _______________________________________________ indiana-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
