beadm vs liveupgrade
Hi,
I'm trying to read and exercice around beadm and 'pkg update' in local and global zones.
Previously, in Solaris 10 with liveupgrade, after the 'luactivate' stage, when rebooting, there was a file syncing stage. The file /etc/lu/synclist defined what to do (APPEND/OVERWRITE) with diverging files.
I've the feeling that this is gone with beadm?!
Is this really gone. This would mean that all user data should be put in a 'shared' file system common to both BE.
This also means that /var/adm/messages will miss some entries that hapened between new BE creation and actual reboot to this new BE.
I'm trying to read and exercice around beadm and 'pkg update' in local and global zones.
Previously, in Solaris 10 with liveupgrade, after the 'luactivate' stage, when rebooting, there was a file syncing stage. The file /etc/lu/synclist defined what to do (APPEND/OVERWRITE) with diverging files.
I've the feeling that this is gone with beadm?!
Is this really gone. This would mean that all user data should be put in a 'shared' file system common to both BE.
This also means that /var/adm/messages will miss some entries that hapened between new BE creation and actual reboot to this new BE.
0