The scenario is that you do a zfs recv of a root pool snapshot to a spare disk, and it happens to have the same beName as (say) the booted root pool. It could even be a copy of it.
Currently, AFAIK (have not dared try this), beadm list will simply list the two identical names, but there would be no method to, e.g., activate the second BE, or even rename it. Is this a real problem? There's a "-p" flag on create, but not on any of the other commands, so it suggests that pkg -R might actually allow --be-name to be set to an existing beName and then fail in some horribly obscure way. Thanks -- Frank _______________________________________________ indiana-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
