Thanks. Actually, you reached the point. My concern is because the latest copy containts all data (look the size):
richter at opensolaris:~$ beadm list BE Active Mountpoint Space Policy Created -- ------ ---------- ----- ------ ------- opensolaris-2 - - 13.36M static 2008-10-15 02:54 opensolaris-3 - - 40.78M static 2008-10-24 10:16 opensolaris-4 N / 47.44M static 2008-11-04 01:26 opensolaris-5 R - 23.34G static 2008-11-10 02:49 But then, being a brave man, I did: richter at opensolaris:~$ pfexec beadm destroy opensolaris-5 Are you sure you want to destroy opensolaris-5? This action cannot be undone(y/[n]): y The BE that was just destroyed was the 'active on boot' BE. opensolaris-4 is now the 'active on boot' BE. Use 'beadm activate' to change it. richter at opensolaris:~$ beadm list BE Active Mountpoint Space Policy Created -- ------ ---------- ----- ------ ------- opensolaris-2 - - 13.36M static 2008-10-15 02:54 opensolaris-3 - - 40.78M static 2008-10-24 10:16 opensolaris-4 NR / 19.54G static 2008-11-04 01:26 I suppose to be safe, and everything should be ok on next book. At least, I hope. Thanks, Edson. -- This message posted from opensolaris.org
