On 6/21/06, Lori Alt <[EMAIL PROTECTED]> wrote:
I checked into this and got some information from
the install group. What I learned is this: the
process of creating a flash archive is just a matter
of using cpio/pax to make a copy of the contents
of an installed system. A flash archive doesn't
contain any information about the configuration (i.e.
storage partitioning) of a system. It's more like a
'super-package' which contains all of the system
software plus some customizations. When you install
a flash archive, you need to have already created the
storage to hold the archive contents. That's done with
the standard Solaris install software (same as a regular
initial install, upgrade, jumpstart, or liveupgrade).
But the distributed Solaris install software is not
yet zfs-aware.
So the answer to your question is that you can create a
flash archive from this system with zfs filesystems, but
until the install software is zfs-aware, you can't use
the archive to create a system with zfs pools and datasets.
Full support for zfs in flash archives will come with
the rest of the zfs installation/boot support.
But flash archives come with multiple sections. From flash_archive(4)
on Solaris 9:
The flash archive is laid out in the following sections:
o archive cookie
o archive identification
o manifest (for differential archives only)
o predeployment
o postdeployment
o reboot
o summary
o user-defined (optional)
o archive files
It seems as though if suitably motivated, additional information about
the desired configuration could be stored in one of the above
sections, either directly or as a result of scripts (e.g. derived
profiles in jumpstart).
Mike
--
Mike Gerdts
http://mgerdts.blogspot.com/
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
