Bill Yan wrote: > > Frank Ludolph ???: > >> >> >> zhongyuan sun - Sun Microsystems - Beijing China wrote: >> >>> Hi Frank, >>> >>> Thanks, This is more clear to me! >>> >>> One think I want to clarify is the *possibility* of the "Driver" >>> Column, >>> So far we have IPS/SVR4/DUimage, what about third-party driver which >>> only release source code? can we put "Source Code" in the "Driver" >>> Column and set the website URL in the "Info" column? >> >> I think not source, at least in the "missing drivers" view. The >> booted system wouldn't be able to download and build. Maybe in the >> regular DDU panel. >> >>> Also what about >>> other exceptions? when neither of the IPS/SVR4/DUimage/Source code type >>> were found, can we put "Missing driver" in the driver column? >>> >> >> Please don't put "Missing driver" in the driver column. Ideally the >> column would be empty when first opened and driver names would appear >> when the driver has been loaded - makes it easy to distinguish which >> drivers are missing/loaded. I decided to put the third-party links >> there because it seemed reasonable even though it makes missing >> drivers harder to find - the column isn't blank - but didn't want to >> add another column. >> >> Frank > > Hi Frank, > > Currently the URL for the third party driver in the driver db usually > point to a webpage, not the actual package file. And in the URL there > may be several drivers for customer to download. For example, the > URL(http://homepage2.nifty.com/mrym3/taiyodo/eng/) contains many NIC > drivers. It's difficult for user to choose which driver to download if > user doesn't know the name of missing driver. So it's better to figure > out a way to provide the name of missing driver on GUI and not to > confuse the user at the same time. Yes, as I understand it this is the "Info" link that is currently implemented in the DDU database. The user would follow it, choose a driver by scanning through the list for the device manufacturer and model, download the driver, use the Browse button to enter its file path into File/URL field (or type the path directly into the field), and click the install button. (Actually, in the example you gave I see that most of the drivers are in source form, so the user would have to download the source and compile it. It would be great if someone would compile these and put them in the /contrib repository - I'm not suggesting that the DDU team do that ;-)
I'm not sure what you are proposing. Do you want to replace "Info" with the name of the driver if it is known? I think that would be okay. > > Another approach is we update the dirver db, so the URL for the third > party dirver will point to a actual package file. In this way, user > wouldn't need to know the name of missing driver. But after > discussion, we feel it's not quite feasible. This is because the link > to the actual pakcage file may become broken or out of date if new > version of the driver comes out. It is also difficult for us to > maintain the driver db as there are hundreds third party drivers out > there, and we wouldn't know when those drivers will be updated. The download link is the added link that Jack and I are suggesting be added to the DDU catalog. It is optional, that is, it might be empty for a known device driver. I do understand the potential db maintenance issue you raise. Too bad more sites don't maintain a "latest version" link... Frank > > > Thanks, > Bill > >>> Thanks, >>> Zhongyuan >>> >>> ?2009?08?27??09:20?Frank Ludolph??? >>> >>> >>>> zhongyuan sun - Sun Microsystems - Beijing China wrote: >>>> >>>>> Hi Frank,Jack >>>>> >>>>> Thanks for the information of p5i. Yes we need a XML >>>>> representation of >>>>> the information in the .p5i file. >>>>> >>>>> I used to think p5i file is a little different with a regular package >>>>> format. I mean a IPS/SVR4/DUimage driver package can physically >>>>> deploy >>>>> directories/files to a system and then attach a driver for a specific >>>>> hardware. While a p5i file is just a pointer to a web location and It >>>>> depend on a IPS package. So far I have not fount a p5i file been >>>>> released independently. >>>>> >>>>> Can we just put p5i information in the Info column? For example, >>>>> when a >>>>> IPS driver was found for a missing driver hardware, then the Driver >>>>> column display "IPS" and the "Info" column was available and show the >>>>> p5i file information in it. Of course the information can be >>>>> clicked and >>>>> then invoke system installation routine. >>>>> >>>>> Also please clarify more about "Info" column, I think most of the >>>>> time >>>>> it's not available except for displaying the third-party driver >>>>> information? >>>>> >>>>> Thanks a lot Frank,Jack. >>>>> >>>>> Zhongyuan >>>>> >>>>> >>>> >>>> Zhongyuan, >>>> >>>> Here is an updated screenshot of the "missing driver" panel. >>>> >>>> Note that the Driver column contains two strings, "SVR4" and >>>> "Info". The SVR4 tells the user that there is a URL or pathname >>>> that can be used to download a file that contains the driver (or >>>> perhaps a p5i file that can be used to get the driver from a >>>> repository). When the device is selected the path/URL is displayed >>>> in the File/URL field. >>>> >>>> The second string, "Info" is a web link (note the underline). If >>>> the user clicks on this link, a web browser should open and the >>>> driver information web page displayed. >>>> >>>> This assumes that this information exists in the DDU catalog. >>>> >>>> Hope this helps clear things up. >>>> >>>> Frank >>>> >>> >>> >>> >> >
