Hi,
I've been reading through the AI documentation, and it's not clear to me
how one would implement the "old jumpstart" feature of derived profiles.
I'm certain I must have missed it...
Currently we have a large lab populated with a wide variety of systems
-- no two alike. We use derived profiles and a "smart" begin script to
generate the profile based on the hardware present... choosing the boot
disk (because it's the one on the particular type of HBA desired, versus
simply choosing c0t0d0 or something based on size), selecting multiple
NICs to configure, even including additional software packages based on
the HW configuration.
Needless to say our begin script is rather extensive, our rules file has
twelve lines in it and never changes, and our finish script actually
pre-configures some of the software installed via the derived profile.
How do I accomplish the same with the AI?
--
Cheers,
Jon.
{-%]
========
If you always do what you've always done, you'll always get what you've always
gotten.
- Anon.
--------
When someone asks you, "Penny for your thoughts," and you put your two cents
in, what happens to the other penny?
- G. Carlin (May 12, 1937 - June 22, 2008)
========
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jon_aimone.vcf
Type: text/x-vcard
Size: 301 bytes
Desc: not available
URL:
<http://mail.opensolaris.org/pipermail/caiman-discuss/attachments/20090128/bb17a738/attachment.vcf>
