One more comment for the man page, the table needs the addition of gen-slim-count.
So the bottom of the table looks like this: post-mod X Post bootroot image area modification gen-slim-cont Generate Slim CD image content list iso ISO image creation usb USB image creation Jean Barbara.Lundquist at Sun.COM wrote: > Install gang, > > The distribution constructor docs are available for review. See > * DistroConst.pdf > * distro_const(1M) > at: > http://www.opensolaris.org/os/project/caiman/files/ > > The primary review of these docs should be done by 3/17, although I'll > extent review a second week as needed. > > Tomorrow during install team meetings, I'll bring up the following > review questions. I hope we can assign contacts for me tomorrow to > help me with the various questions below and any others that come up > over the next week. > > Barbara > > Introduction to DC Topic > > -------------------------------- > > 1 - I added a note near the start and in sys req section mentioning > SPARC AI option. Do we need to say more about that in DC doc, other > than pointing to AI doc? > > 2 - I did alot of writer edits for greater clarity. Topic needs a > technical proofread. > > > SETUP DC Topic > --------------- > > 1 - We need to clarify where to get the images from, will it just be > opensolaris.com for > both x86 and SPARC AI images? > > > 2 - How much detail should we provide for network access in sys req? > Should we just point to this > topic in the AI docs, where we plan to cover it more in detail? > > > 3 - Have I listed any internal files by mistake? > > 4 - Have any of the system requirements changed? > > > Using DC Topic > -------------- > 1 - I did alot of writer edits for greater clarity, Topic needs a > technical proofread. > > 2 - In manifest, is the checkpoint option for "resume from=" still a > number, not a text value? > > 3 - Have we sufficiently answered this question: "How do I > replace/modify/remove specific packages in my distribution without > having to pull all the packages each time I make a change?" > > 4 - Do we need to expand the explanation of the > pkg_repo_addl_authority element of the manifest in order to explain > how to point to repos outside the main Sun repos? Add some examples of > outside-Sun repositories? > > > > (#5 - #10 are SPARC questions) > 5 - What IPS repository should be specified in the manifest file in > order to get SPARC packages from a repository? > 6 - We need to expand the section that describes editing the > repository. We should add some > real-world examples of the various repositories and when they would be > used. > > 7 - How do we need to edit the finalizer scripts section of manifest > file to describe SPARC specifications? > Currently, that section mentions a grub_setup script for > initialization of grub menu... > > 8 - Are there SPARC-specific scripts that are now included in the > default finalizer scripts? > > 9 - Are there SPARC packages used either by default or optional that > need to be referenced by the manifest file? > > 10 - Is there a SPARC impact on boot root information in the manifest > file that need to be mentioned? > > (#11 - 16 are finalizer script questions) > > 11 - We need to explain the purpose of stdout and stderr parameters in > finalizer scripts. > > 12 - We need to define the role of the argslist in finalizer scripts. > > 13 - In the Adding Packages custom script example, we need a short > paragraph explaining the example, using > the example specifics. > 14 - In the Testing Packages example, we need a short paragraph > explaining the example, using the example specifics. > 15 - In the Adding a SVR4 Package example, we need a short paragraph > explaining the example, using the example specifics. > > 16 - We have complaint that our examples use XML inconsistently. We > need to check that issue. > > (#17 is distro_const/man page question) > > 17 - We need to compare the Distro_const command table to the > distro_const man page and check both the table and the man page for > any discrepancies or improvements. > > (#18 - 20 are general questions) > > 18 - Do we want to add any DC-specific troubleshooting information? > 19 - Do we want to continue to point to the CD usage TOI? > > 20 - We need to replace the sample manifest file in the appendix with > the latest default manifest file. > > > > > > > > > > > > > > >
