Hi Karen,
On Tue, 20 Jul 2010, Karen Tung wrote:
The problem with this is that the repository does not get
initialized until boot_archive_configure, [2] which runs after
slimcd_pre_boot_archive_pkg_img_mod. This means that the
repository in the proto area really only contains the basic
schema itself and has no knowledge of ANY services.
If I remember correctly, we want to initialize the GNOME caches at this
point,
as supposed to do it in the boot archive configure step, because we want
these
initializations to carry over to the installed system too. It might also be
that
the boot archive didn't contain all the commands necessary to execute these
GNOME initialization scripts.
There appears to be at least 3 possible solutions to this:
1: Generate the GNOME caches in boot_archive_configure after
SMF is initialized
2: Move the SMF initialization code to the pre_boot_archive
finalizer
3: Don't use the proto area's repository.
What about option 4?
4: Do SMF import of all the services to a *tempoary" SMF repository, and
query against
that temporary repo to get the needed information. This temp repo should
not
be part of the image.
(4) seems rather heavyweight.
Do you foresee any problems with (2) - move the SMF
initialization to pre-boot archive creation?
Thanks,
Alok
_______________________________________________
caiman-discuss mailing list
caiman-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
