|
David. Now that I have a bunch of boot environments : opensolaris opensolaris-1 opensolaris-2 opensolaris-3 How do I clean up the mess? Can I remove, say, opensolaris and opensolaris-1 (free up some space and make GRUB look nicer)? What's the process so that I don't miss bits and parts? Thanks, Gilles. [EMAIL PROTECTED] wrote: Enclosed below are revised instructions for using "pkg image-update" to update to the latest OpenSolaris development builds via http://pkg.opensolaris.org/For more information on this command and the Image Packaging System (IPS) technology, refer to the pkg(1), beadm(1M) and pkg(5) manual pages and the following documents Getting Started With the Image Packaging System http://dlc.sun.com/osol/docs/content/IPS/ggcph.html Upgrading and Managing Your Boot Environments http://dlc.sun.com/osol/docs/content/IPS/snap3.html General instructions for updating to the latest OpenSolaris development build ============================================================================= 1) Before using the "image-update" subcommand, it is recommended that the latest available version of the IPS software be installed for your current boot environment (BE) $ BUILD=`uname -v | sed s/snv_//` $ pfexec pkg refresh $ pfexec pkg install [EMAIL PROTECTED] $ pfexec pkg install [EMAIL PROTECTED] 2) Verify the build of OpenSolaris in the current BE $ echo $BUILD 3) If you are running build 93 or greater, you can use "image-update" directly as follows $ pfexec pkg image-update At this point, you can boot into the updated BE using reboot(1M) or init(1M) as usual. 4) If you are using a build prior to 93, it is recommended one apply the update directly to an alternate BE in order to work-around 2387 libbe.so:beCopy() frees nvlist variables before using them http://defect.opensolaris.org/bz/show_bug.cgi?id=2387 First, display the list of the existing BEs on the system $ beadm list BE Active Active on Mountpoint Space Name reboot Used ---- ------ --------- ---------- ----- opensolaris no no - 3.92G opensolaris-1 yes yes - 17.06M Next, choose the name of a new BE - if the most recent created BE is of the form "opensolaris-<N>" where <N> is an integer, then a suitable choice for the new BE is "opensolaris-<N+1>". In the above example, the new BE would be "opensolaris-2". Finally, execute the following sequence of commands to create, mount and update the new BE $ pfexec beadm create opensolaris-<N+1> $ mkdir /tmp/mnt$$ $ pfexec beadm mount opensolaris-<N+1> /tmp/mnt$$ $ pfexec pkg -R /tmp/mnt$$ image-update 5) If you are running build 86, the following step is required in order to work-around 1979 libbe: be_activate needs to run installgrub http://defect.opensolaris.org/bz/show_bug.cgi?id=1979 >>>>>>>>>> IMPORTANT <<<<<<<<<< Due to changes in the GRUB boot system, one must manually update the Master Boot Record (MBR) to include these latest changes. Failure to follow these instructions when updating from 2008.05 (build 86) to a later build will result in a system that does not boot by default and instead the original BE must be manually selected. Update the GRUB configuration on your ZFS boot device(s) using $ pfexec /tmp/mnt$$/boot/solaris/bin/update_grub -R /tmp/mnt$$ 6) Unmount and activate the newly created BE $ pfexec beadm unmount opensolaris-<N+1> $ pfexec beadm activate opensolaris-<N+1> At this point, you can boot into the updated BE using reboot(1M) or init(1M) as usual. _______________________________________________ indiana-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/indiana-discuss --
|
_______________________________________________ indiana-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
