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
Look at the difference between my running BE and a `clone' I made with
beadm create osol-108_cifs
beadm list -a
BE/Dataset/Snapshot Active Mountpoint Space
Policy Created
**
opensolaris-1
**
rpool/ROOT/opensolaris-1 NR / 4.82G
static 2009-03-07 21:02
rpool/ROOT/opensolari...@2009-03-08-03:02:43 - - 183.26M
static 2009-03-07 21:02
rpool/ROOT/opensolari...@install - - 74.67M
static 2009-03-07 12:47
rpool/ROOT/opensolari...@osol-108_cifs - - 64.97M
static 2009-03-09 02:35
osol-101b
rpool/ROOT/osol-101b - - 95.53M
static 2009-03-07 12:27
**
osol-108_cifs
**
rpool/ROOT/osol-108_cifs - - 56.0K
static 2009-03-09 02:35
opensolaris-1 weighs in at 4.82G while `clone' osol-108_cifs is at
56.0k. A tiny fraction of the running BE.
But aside from confusing terminology... I'm pretty sure I'll
eventually begin to understand what is inside the various names.
What I'd like to know, now that I've got a crude but working system
going with cifs setup and working, how can I best preserve that start?
I mean all 4.82g in some way that can be reinstalled onto bare
metal overwriting opensolaris-1
Is that what is called an `image'?
Assuming I really screwup my install up the road a bit, I want a fall
back that isn't all the way back to 101b with no customizations. I'd
like to preserve all customization, installed software etc in some
format where I could reliably save it on a different machine... and if
needed clear the current install or overwrite it..
Something like people do with Ghost in windows... or `dd' on various
unixs'?
Do any of the formats I see tossed around Image, clone, snapshot have
that capability?
Put another way, do I need that capability to be able to completely
roll back to a known good state?
How is that kind of full on return to a known good state best
facilitated?
_______________________________________________
indiana-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
