On 02/26/10 01:17 AM, Frank Che wrote: >> 4.2.3 Enhance driver installation capability >> Current Device Driver Utility only installs driver from IPS >> repository. In >> case the driver supplier provides driver in other format, or network >> connection is not available(for example, network controller driver is >> missing), the user need to install driver(s) in other format. In this >> project, Device Driver Utility will be enhanced to be able to install >> driver(s) in P5I [3], DU-Image [4] and SVR4 [5] formats via call "pkg" >> and >> "pkgadd" commands.
Has the project team been in contact with the pkg team to ensure that drivers installed using this tool won't be automatically removed from their installed locations during pkg image-update? > 4.4 Exported Interfaces > > Interface | Stability | Description > ------------------------+-------------+---------------------------------- > /usr/ddu/ddu-text.py | Uncommitted | Command to invoke text mode UI This doesn't seem right. There's already a /usr/bin/ddu command, and that appears to be the public interface (not the /usr/ddu/ddu.py script to which the /usr/bin/ddu symbolic link points to). Isn't /usr/ddu/ddu-text.py actually a Project Private interface? > ------------------------+-------------+---------------------------------- > ddu_devscan() | Uncommitted | DDU library API [2] > ------------------------+-------------+---------------------------------- > ddu_package_lookup() | Uncommitted | DDU library API [2] > ddu_build_repo_list() | | > ddu_install_package() | | > ------------------------+-------------+---------------------------------- > ddu_repo_object | Uncommitted | DDU library object [2] > ddu_package_object | | > ddu_dev_data | | > ------------------------+-------------+---------------------------------- What about the library itself? Is it a C library, a python module, something else...? Based on the materials, I don't understand the semantics of /usr/bin/ddu --silent. Basically, I don't grok section 2.1 of your "programming interface spec" (and it seems to be more than a programming interface spec). You explain when --silent is used, but not what it does. This seems central to the proposal, and I'd like to understand this. A ddu(1M) man page would help. -Seb
