Hi,

since OSOL 2008.05 one can upgrade a BE via IPS ( Image Packaging 
system), and the procedure is similiar to LU. The process has been 
improved!
And, there is a new command called beadm(1M) which has the same 
functionalities and features like LU, and it handles zfs filesystems, 
actually it implies zfs .

The command /pkg image-update/ creates a new BE copy, then upgrade all 
packages and finally activates the new BE and creates a new entry in 
GRUB menu automatically.
After a reboot the new BE is started. The old BE entry is kept in the 
GRUB menu,so one have the option to go back to the old boot environment.

For instance: (see  http://dlc.sun.com/osol/docs/content/IPS/ggfwk.html)
# pkg image-update

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.

os# beadm list
BE                 Active     Active on reboot         Mountpoint     
        Space Used
----                 ------        ---------                         
----------                     -----
opensolaris     yes         no                                 legacy 
                    57.5K
opensolaris-1  no          yes                                 -         
                    2.59G

After the upgrade one can maintain all existing  BEs with the beadm command.
So the difference is, that with pkg image-update you just execute one 
command ( instead of three:  create an ABE, upgrade it and finally 
activate it ).

The BE Utility beadm(1m) in general has the same features and 
functionalities as Live Upgrade, and it implies zfs file systems.
One can create snapshots and clones. Actually, beadm(1M) creates firstly 
a snapshot when creating a new BE. And, secondly builds the new BE from 
this snapshot. 
So you can create a new BE with beadm:
# beadm create [-a] [-e non-activeBeName | beName at snapshot] [-o 
property=value] ...[-p zpool] beName

acitvate it:
# beadm activate beName

delete a BE:
# beadm destroy [-f] beName | beName at snapshot

list al BEs:
# beadm list [-a | [-ds] [-H] [beName]

mounts BEs:
# beadm mount bename mountpoint

unmounts BEs:
# beadm unmount beName

renames BEs:
# beadm rename beName newBeName

etc.etc.

regards,
claudia hildebrandt

On 03/16/09 10:20, Michael Ramchand wrote:
> Uwe Dippel wrote:
>> [i]I thought LU was supposed to be "safe" :-(  [/i]
>>
>> Alas, that's the one thing that it is not. (Just search the archives, 
>> if in doubt.)
>> I'm not working for SUN, only summarize what I picked up on the way 
>> here:
>> LU was bought from a third party, cannot be redistributed therefore, 
>> is maintained only, and will be replaced by a new system as soon as 
>> possible; at least for OpenSolaris.
>>   
> That's not exactly true. The fact it that OpenSolaris has a completely 
> different packaging and installation system, therefore LU is simply 
> not relevant to it. There are NO redistribution issues with LU, 
> there's just no point. :-)
>
>> It works okay, if it works, and especially it does so on ZFS. We have 
>> analysed it, and found some conceptual limitations and some promises. 
>> At least, compared to all other OSes, LU is a great step into the 
>> correct direction: Upgrades should be easy, and done on a clone of 
>> the system, 'on the system', without touching the original. That 
>> would be a show-stealer. Unfortuantely, the latter (not touching the 
>> original) is far from true for LU, and that's why it cannot be "safe".
>>
>>   
> This really depends on what you consider to be the "not touching the 
> original". Other than requiring that you update the LU packages before 
> upgrade, the ONLY thing that LU will change is the record of what your 
> boot environments are which unfortunately live within the BE. It would 
> be impossible not to change it. (Think about it). The fact is that you 
> can ALWAYS recover your original boot environment. The most painful 
> thing that you'd ever need to do is re-install grub to get the system 
> to point at your old BE, and that's the worst case scenario. And 
> that's why it is "SAFE".
>> Uwe
>>   
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> install-discuss mailing list
> install-discuss at opensolaris.org
> http://mail.opensolaris.org/mailman/listinfo/install-discuss
>   

-- 
******************************************************************
Claudia Hildebrandt             
Systems Engineer                Phone: +49-30-747096761
Global Systems Engineering      Mobile:+49-171-6429689
Sun Microsystems GmbH           Fax:   +49-30-747096-868
Komturstrasse18a                mailto:claudia.hildebrandt at sun.com
12099 Berlin                    http://www.sun.de       
Germany
Blog: http://blogs.sun.com/claudia
XING-Kontakt: http://www.xing.com/go/invite/7365578.31f964
*******************************************************************
Sitz der Gesellschaft: Sun Microsystems GmbH, Sonnenallee 1, D-85551 
Kirchheim-Heimstetten
Amtsgericht Muenchen: HRB 161028
Geschaeftsfuehrer:Thomas Schroeder, Wolfgang Engels, Dr. Roland Boemer
Vorsitzender des Aufsichtsrates: Martin Haering
******************************************************************** 
NOTICE:  This email message is for the sole use of the intended
recipient(s) and may contain confidential and privileged
information.  Any unauthorized review, use, disclosure or
distribution is prohibited.  If you are not the intended
recipient, please contact the sender by reply email and destroy
all copies of the original message.



Reply via email to