Hi Karen.
> I have a couple of comments/questions about the new diagram.
>
> 1) It's very hard for me to distinguish the colors grey/purple/light 
> blue.  I am not
> sure whether it is my monitor or my eyes.  I think it would be easier to 
> read if
> they are very different colors.
>   
OK.  I'll change the colors.
> 2) I am confused about the separation of the
> Distro-Specific Processing module and the Generic Media-Specific Processing
> module.  From what I understand in the diagram, the Distro-Specific 
> processing is provided by the project
> team, and the media-specific processing module will be provided by the 
> DC.
This is correct.  Distro-specific processing is specific to the distro 
being made, and so is provided by the project team.  Generic 
media-specific processing is any generic processing required for the 
type of media being created.
>   I am confused because I think
> that even media-specific processing is unique based on the end goals of 
> projects that uses the DC.
> So, I don't see how DC can provide "generic" media-specific modifications.
> Thinking about all the special processing we did for the Slim CD in the 
> Oct preview, I really can't separate
> which part is the distro-specific processing and which part is the 
> media-specific processing.  Can you
> give an example?
>   
Distro-specific processing can include media processing as well as 
anything else specific to the distro.  The generic processing was to be 
provided by us as a starting point, done in the spirit of "Why make all 
projects reinvent the wheel?"  In the simple cases, that would be all 
that is needed.  If projects required more processing, they can add what 
they need.

The finalizer can be set up to call any processing script, whether 
generic or distro-specific, in any order.  If tweeks need to be make 
after the generic processing, call a distro-specific script after the 
generic one.  This wasn't made clear in the diagram;  the accompanying 
text in the design doc needs to explain this.

Does this answer your question?

    Thanks,
    Jack
> Thanks,
>
> --Karen
>
> Jack Schwartz (Home Login) wrote:
>   
>> Hi everyone.
>>
>> I have revised the Distro-Constructor (DC) architectural diagram 
>> (attached) with the following goals:
>> - To describe in finer granularity the processing involved to 
>> accommodate all kinds of projects and produce different kinds of media.
>> - To show which modules are provided in the DC kit and which modules 
>> are or can be provided by the project using the kit.
>> - To show how the finalizer fits in to coordinate processing.
>>
>> The modules in blue are the Distro-Constructor proper, and include the 
>> framework from which all project- and media-specific modules are 
>> called.  The yellow module generates the manifest which is fed to the 
>> DC to set it up.
>>
>> Projects supply zero or more Distro-Specific 
>> scripts/programs/python-functions (grey) to change the generic image 
>> layout to suit their needs.
>>
>> One of the Generic Media-Specific Processing modules is called to 
>> prepare the image layout for a specific type of media.  This 
>> processing deals only with image layout prep, e.g. moving files 
>> around, not with actual generation of the image.  Image Prep modules 
>> will be provided for many media types.  Projects can supplement the 
>> list with their own modules if desired (so the list is in purple).
>>
>> Projects determine the order of processing as part of DC 
>> configuration.  It is possible to do Distro-Specific Processing after 
>> generic media processing, if required.
>>
>> When layout of the image is completed, the media generation utilities 
>> are called to create it.  This may be creating an ISO for a CD, or 
>> writing a bootable USB stick, for example.
>>
>> Thanks to Jean for raising the question, and to Jean and Karen for 
>> their feedback on this thread.
>>
>> Please let me know your comments by Monday.  I plan on updating the 
>> document in the gate on Monday afternoon.
>>
>>    Thanks,
>>    Jack
>>
>>
>> ------------------------------------------------------------------------
>>
>>     
>
> _______________________________________________
> caiman-discuss mailing list
> caiman-discuss at opensolaris.org
> http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
>   


Reply via email to