Charles Hedrick wrote:
Thanks very much for this response. Is it practical for me to update just
> the xen components? I'm not averse to test releases on some systems, but > I'd prefer to stick with a release (2009.6 in this case) on this particular system if I can. No, you need an updated kernel too. One thing you can do is to use beadm(1M) to create one or more alternate boot environments (BE). This way you can keep 2009.06 but also experiment with the newer bits in the dev tree. NOTE: the dev tree is still at build 111 (b111), but this should change shortly. There are various ways to do this... This is what I usually do to ensure that the stock bits remained absolutely unchanged. What we'll do it to create a tree of cloned disk images.. Create a backup up os2009.06 in case you mess something up. Then, create a branch for the development release. You may have to update some packages to be able to upgrade to newer releases, so we'll do that in the branch. beadm create os2009.06-backup beadm create dev-branch beadm activate dev-branch reboot One you've rebooted, re-target (the dev-branch) from the release repo to the development repo. Then upgrade the pkg package. beadm list pkg set-authority -O http://pkg.opensolaris.org/dev opensolaris.org pkg install SUNWipkg Now lets create a build specific BE. NOTE: b116 doesn't exist in the repo as of today, but should shortly. ("pkg search entire" for a list of builds). From the dev-branch, create a b116 BE. beadm create snv116 beadm mount snv116 /mnt pkg -R /mnt refresh pkg -R /mnt install [email protected] bootadm update-archive -R /mnt beadm umount snv116 beadm activate snv116 reboot MRJ _______________________________________________ xen-discuss mailing list [email protected]
