Harry Putnam wrote:
I've been installing and tinkering for a while now and admit to being
somewhat confused by some of the terminology.
Image, BE, snapshot, clone appear in many places.
When I make a new BE from the running BE it is said to be a clone.
(From man beadm)
beadm create [-a] [-d description]
[-e non-activeBeName | ben...@snapshot]
[-o property=value] ... [-p zpool] beName
Creates a new boot environment named beName. If the
-e option is not provided, the new boot environment will
be created as a clone of the currently running boot
environment. If the -d option is provided then the
description is also used as the title for the BE's
entry in the GRUB menu. If the -d option is not provided,
beName will be used as the title.
But when I see `beadm list -a'... the size is massively different.
So.. it can't be a clone... isn't a clone supposed to be a duplicate
in every detail? Like in science fiction stories where a human is
cloned but some tiny dna difference leads to a monster who isn't a
clone anymore. hehe
But this is a ZFS clone - which does copy on write - so until you change
something, there's no disk space overhead ;-).
Put another way, do I need that capability to be able to completely
roll back to a known good state?
Create a clone of the current environment and never touch it.
- Bart
--
Bart Smaalders Solaris Kernel Performance
[email protected] http://blogs.sun.com/barts
"You will contribute more with mercurial than with thunderbird."
_______________________________________________
indiana-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
