Hi Jack, A few comments inline...
> Hi everyone. > > I have some loose ends to tie up or confirm with regards to the system > specification manifest passed to the Distro-Constructor. > > Questions: > ---------- > > 1) Not sure what extra things DC needs to do to provide for a live-image > installable image or a repo-installable image. It will need to include > an installer, but how does that fit with the manifest? > > Isn't this just an artifact of the installer, whether or not it intalls from an image or from a repo? So, wouldn't this just be the install pkg? > 2) Disk and network parameters for installation are still TBD. > > 3) There are some things which cannot be known by the DC but which are > needed by it. For example, if someone specifies they want a certain > locale, I don't want to hardwire into DC a package name delivering that > locale. For maintainability, these things will have to go into a > manifest. I'm thinking of putting them into a manifest different than > the one for user-specified parameters. That way if the supported locale > list changes, one can just upgrade their DC and get the changes without > worry of overwriting or having to merge the user's existing > user-specified parameter manifest. > > I think that the locale==pkg isn't correct. At least not with the direction the g11n folks are going. Just to keep that in mind. In general I am not sure why you would need to keep this in a different manifest. If the list of supported locales changes, the user still has to specify what locale(s) they want to install as part of the image, correct? So, they would have to modify their user manifest anyway. > Assumptions: > ------------ > > 1) When installing from the live image that all parameters are AS-IS > from the live image. (e.g. same users, files, locales, etc) > > Just to be clear, you are saying that what's on the image is what they get? Not that they can modify any of these during installation? > 2) A list of supported keyboard types is not included because all are > currently delivered in a single package and I assume it will stay that > way once packages are refactored (as keyboard map files are small). > This is not to be confused with locales which are included in the manifest. > > We run sysidkbd right now, which gets the list of supported keyboards from the file on the system. What will replace the keyboard mechanism? And, will we need to list the supported keyboard types in the future? thanks, sarah **** > Other items: > ------------ > > 1) The manifest now specifies tags and attributes can be specified for > each package or incorporation. This is the plan for narrowing down what > gets installed. (Tags are for file types, and attributes deal with > packages.) > > 2) I have added a query for the zfs compression type and level for the > live CD and installed image. > > Comments/Questions? > > Thanks, > Jack > _______________________________________________ > caiman-discuss mailing list > caiman-discuss at opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/caiman-discuss > >
