Hi Alok.
Here are my comments for the DC-Redesign doc, submitted today with your
approval. I reviewed the version I pulled at 11:34 AM PST today.
3.5: In general what is the difference between checkpoint name and
mod_name? I thought at first that "checkpoint name" was what gets
listed by distro_const -l. However, parse-manifest and target-setup
have checkpoint names but don't get listed by distro_const -l. Please
clarify what mod_name and checkpoint_name is in the document.
3.5.4: How come text-installer doesn't have its own prePkgImageMod? Is
all of its prePkgImgMod processing common to the other kinds of images?
Would there be a need, for debugging perhaps, for splitting out the
common processing from the image-specific processing?
3.5.6: Same basic question as 3.5.4.
3.7: The doc says that "CUD doesn't have a concept of finalizer scripts
but instead has a concept of checkpoints." so it is not clear whether
user-supplied checkpoints can be placed anywhere among the pre-defined
checkpoints. With finalizer scripts, one just edited the manifest to
include the user-defined script whereever it was supposed to go relative
to other scripts. Does the mechanism which implements pre-defined
checkpoints list them in the manifest the same way, allowing users to
put their custom scripts where they want (like they can now), or are
there restrictions on where custom scripts can be executed? Can
multiple user-defined scripts be specified? (E.G. If someone wanted to
add something right after populating the pkg-image area, and then do
something later to the boot-archive, is this possible?) Please clarify
this in the doc.
3.10: Currently DC has a simple log that displays only error messages,
and a detailed log that displays error and informational messages. The
DC-Redesign doc talks of a simple log that contains error and
informational messages, and a detail log that contains debug information.
- I see a need to have a log with just error messages. This is useful
if, for example, someone wants to batch a DC job. Do we expect users to
tee the output of DC to a logfile for this?
- What does "debug information" refer to? How does it differ from
informational messages?
The second paragraph is incomplete. Maybe a cut and paste error?
Here are a few grammatical corrections I found as well:
1.2.7: first sentence: The CUD Error Service is used to store and
retrieve errors.
3.1 Fourth PP: If DC is being resumed... it ensures that the build...
creating datasets are cleared.
3.5.9 First PP: ...finalizer script to be a checkpoint...
3.14: ... individual DC checkpoints as well...
Thanks,
Jack
_______________________________________________
caiman-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
