HI Zhongyuan.
zhongyuan sun - Sun Microsystems - Beijing China wrote:
> Hi Jack,
>
> My responses inline.
>
> ?2009?09?03??10:23?Jack Schwartz???
>
>> Hi Zhongyuan.
>>
>> Thanks for your feedback. Responses inline.
>>
>> On 09/02/09 06:13, zhongyuan sun - Sun Microsystems - Beijing China
>> wrote:
>>
>>> Hi Jack,
>>>
>>> Thanks for your document, My comments blow:
>>> 1)I'd like to add a 'drvier name' field into "ddu_package_object", and
>>> also the ddu_packge_lookup function will involve this field when
>>> searching a package containing a driver for a device.
>>>
>>>
>> I can add the driver name to the ddu_package_object if you need it.
>> I'm not sure how the driver name will help you, since whole packages
>> need to be installed and not individual files; please let me know how
>> the driver name will be used so I can explain in the document.
>>
>
> I will use driver name for looking up IPS package besides compatible
> name, usually a IPS package would include compatible name for a device
> driver, just in case the package metadata not contain the device
> information enough I will then lookup by driver name.
>
If the driver name is needed for looking up a package, then it should be
specified as an argument to ddu_package_lookup(). It wouldn't be needed
as part of the ddu_package_object, which is returned as a result of the
lookup.
If the driver name were to be used to lookup a package, where would it
come from though? It would have to come from the database, right? (If
it's already in /etc/driver_aliases, the driver is already installed.)
So passing the compatible name to ddu_package_lookup() (as is already
in the spec) should be enough for ddu_package_lookup() to be able to get
the driver name, in case you want to search by driver name if a search
by compatible name fails.
Please correct me if I am missing something, but I don't think adding
the driver name to the ddu_package_object is helpful.
Thanks,
Jack
>>> 2)In 4.1.2.3 S section, you mentioned "Code checks for blank name and
>>> location fields before attempting to install the package. Other parts
>>> of the code can check for non-blank informational links and display them
>>> as appropriate." I do not quite understand, where do you want to display
>>> the information? to the display output or log file?
>>>
>>>
>> The informational link should be displayed by the GUI. Frank had
>> suggested an "info" hyperlink in a driver line which would bring up
>> the informational link in a browser when clicked.
>>
>
> Ok, Thanks!
>
>
>> Thanks,
>> Jack
>>
>>> Thanks,
>>> Zhongyuan
>>> ?2009?08?29??03:30?Jack Schwartz???
>>>
>>>
>>>> Hi everyone.
>>>>
>>>> The DDU team is supporting the Driver Update project by providing an
>>>> enhanced GUI DDU, a text-mode DDU and a library which AI can call.
>>>>
>>>> As part of the project design, I have uploaded V1 of the programming
>>>> interface spec for the DDU interfaces. They describe how the DDU will
>>>> plug into the installers and/or their environments. The spec is at:
>>>> http://www.opensolaris.org/os/project/caiman/Driver_Update/ddu-prog-iface-spec.txt
>>>>
>>>> Please review and send any comments/questions you may have by next
>>>> Thursday 9/3 COB.
>>>>
>>>> In particular, I would like Ethan (AI lead) and Sue (Text-installer
>>>> lead) and DDU team to please have a look.
>>>>
>>>> Thanks for your time,
>>>> Jack
>>>>
>>>>
>>>
>>>
>
>
