The boot environments are cumulative (at a block level - so they're very
efficient). And they are for your own protection, so there's no point in
overwriting the current.
You use beadm to manage them. Below you can see the four I have on my
machine (and they've definitely saved my ass on more then one occasion):
bleon...@opensolaris:~/Documents/lab3$ beadm list
BE Active Mountpoint Space
Policy Created
-- ------ ---------- -----
------ -------
opensolaris-SUNWipkg-brand_0.5.11-0.111 NR / 6.61G
static 2010-07-26 10:49
opensolaris-conky1.5.1-0.111 - - 21.52M
static 2010-04-27 14:37
opensolaris-virtualbox3.1.8-0.101 - - 15.18M
static 2010-05-19 12:50
opensolaris-virtualbox_3.1.6-0.101 - - 45.23M
static 2010-03-31 11:49
You can see the 3 older boot environments are hardly taking up any space.
Regards,
Brian
Peter Steiner wrote:
When I start an update of my system a popup appears prompting me for a (new)
name for the next boot environment.
By default it is "opensolaris-2".
"Boot environment" seems to me something like a restore point of the system.
How can I tell OpenSolaris: Overwrite the existing last boot environment
"opensolaris-1" instead of creating a new one?
How can I delete older existing "boot envirnments"?
Are these boot environments cumulative or full backups?
Peter
--
W Brian Leonard
Principal Product Manager
860.206.6093
http://blogs.sun.com/observatory
_______________________________________________
opensolaris-help mailing list
opensolaris-help@opensolaris.org
