From sacadmin Wed Aug 6 00:55:05 2008 Received: from sac.sfbay.sun.com (localhost [127.0.0.1]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m767t5w7017149; Wed, 6 Aug 2008 00:55:05 -0700 (PDT) Received: (from xc149992@localhost) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8/Submit) id m767t5gU017145; Wed, 6 Aug 2008 00:55:05 -0700 (PDT) Date: Wed, 6 Aug 2008 00:55:05 -0700 (PDT) From: Xiang-Dong Frank Che Message-Id: <200808060755.m767t5gU017145@sac.sfbay.sun.com> To: PSARC-record@sac.sfbay.sun.com Subject: Device Driver Utility [PSARC/2008/504 FastTrack timeout 08/13/2008] Status: RO Content-Length: 557 Template Version: @(#)sac_nextcase 1.66 04/17/08 SMI This information is Copyright 2008 Sun Microsystems 1. Introduction 1.1. Project/Component Working Name: Device Driver Utility 1.2. Name of Document Author/Supplier: Author: Bill Yan 1.3 Date of This Document: 06 August, 2008 4. Technical Description See the case directory for more detail 6. Resources and Schedule 6.4. Steering Committee requested information 6.4.1. Consolidation C-team Name: unknown 6.5. ARC review type: FastTrack 6.6. ARC Exposure: open From Frank.Che@Sun.COM Wed Aug 6 01:18:12 2008 Received: from sunmail2sca.sfbay.sun.com (sunmail2sca.SFBay.Sun.COM [129.145.155.234]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m768ICGv017795 for ; Wed, 6 Aug 2008 01:18:12 -0700 (PDT) Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74]) by sunmail2sca.sfbay.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id m768ICr0006025 for <@sunmail2sca.sfbay.sun.com:PSARC-ext@sun.com>; Wed, 6 Aug 2008 01:18:12 -0700 (PDT) Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0K56008137294V00@nwk-avmta-1.sfbay.Sun.COM> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Wed, 06 Aug 2008 01:18:09 -0700 (PDT) Received: from sineb-mail-2.sun.com ([192.18.19.7]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0K5600M1T726OY50@nwk-avmta-1.sfbay.Sun.COM> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Wed, 06 Aug 2008 01:18:07 -0700 (PDT) Received: from fe-apac-05.sun.com (fe-apac-05.sun.com [192.18.19.176] (may be forged)) by sineb-mail-2.sun.com (8.13.6+Sun/8.12.9) with ESMTP id m768I5e9027264 for ; Wed, 06 Aug 2008 08:18:05 +0000 (GMT) Received: from conversion-daemon.mail-apac.sun.com by mail-apac.sun.com (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) id <0K56005016Y8FY00@mail-apac.sun.com> (original mail from Frank.Che@Sun.COM) for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Wed, 06 Aug 2008 16:18:05 +0800 (SGT) Received: from [129.158.218.60] by mail-apac.sun.com (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) with ESMTPSA id <0K56004BR725PGTM@mail-apac.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Wed, 06 Aug 2008 16:18:05 +0800 (SGT) Date: Wed, 06 Aug 2008 16:17:50 +0800 From: Frank Che Subject: PSARC 2008/504 Device Driver Utility Sender: Frank.Che@Sun.COM To: PSARC-ext@Sun.COM, yan xue yang Message-id: <48995E2E.8020801@sun.com> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 User-Agent: Thunderbird 2.0.0.4 (X11/20070622) Status: RO Content-Length: 6641 I'm sponsoring this fast track for Bill Yan. Requested release binding is patch/micro for OpenSolaris. Timer is set to 08/13/2008. Note that this project depends on the IPS project (PSARC 2008/190) which is still under development now. Frank. 4. Technical Description Summary The intent of this project is to propose the integration of Device Driver Utility to OpenSolaris OS. Motivation to propose this project is to fulfill the increasing requirement from the customer about easily view hardware information in Solaris OS and install missing device driver(s), thus contribute to the adoption of OpenSolaris OS. This project requests a patch/micro release binding to OpenSolaris. 4.1 Proposal 4.1.1 Introduction to Device Driver Utility Device Driver Utility provides information about the devices of the user's native system. Device Driver Utility enables the user to connect to the Image Packaging System (IPS) [1] to search for the device drivers for the devices that do not have a driver attached with it. By using the Device Driver Utility application, the user can do the following: * Get the information of the devices installed on your native system and their corresponding device driver availability status. The following information are displayed on the GUI: - Device name and attributes(device path, vendor ID, device ID etc.) - Device driver availability - Device driver name and status(instance number, attached/detached etc.) * Check the device driver availability for your system devices on IPS. * Download and install the device drivers from IPS for those devices that do not have an attached driver. * Report system configurations to the OpenSolaris Hardware Compatibility List (HCL). 4.1.2 Device Driver Utility components To achieve the above functions, the following components will be implemented: 4.1.2.1 Device information fetcher. This component is designed to probe current system via the libdevinfo interface, walk through device tree and get information of all detected devices and driver information of each device. 4.1.2.2 Solaris driver database. The Solaris driver database is a mapping table between device identifier(normally vendor ID and device ID) and name of Solaris driver. This database includes three sets of information: drivers that are bundle with OpenSolaris, third-party drivers that can be downloaded from an IHV website, drivers that can be downloaded from OpenSolaris community. This database is only used when a device doesn't have a driver. Solaris driver information is extracted from the /etc/driver_aliases file. Third-party and OpenSolaris driver information is manually collected and added to the driver database. The driver database must be updated periodically because new hardware and new Solaris drivers are continually created. 4.1.2.3 User interface. Consider the target user of this tool are most likely don't have much knowledge of Solaris system administration, only graphical user interface is available, written in Python. The user reads device information from this informative GUI, instruct Device Driver Utility to download and install missing driver(s) automatically through a few simple mouse-click, submit hardware information to OpenSolaris HCL using this GUI. 4.1.2.4 Core engine. This component stays in the center of Device Driver Utility. It completes the following fundamental operations: (1) Get device information from device information fetcher. If there is device that missing driver in current OpenSolaris OS, then look up Solaris driver database for the driver name. Pass all these information to GUI for display. (2) Check IPS for driver availability through pkg(1M) command. Search for package on IPS that contains needed driver based on driver name. Download and install certain driver package(s) according to user's instruction. (3) Read hardware-related information from SMBIOS as much as possible, then automatically fill in to OpenSolaris HCL submission table, ask the user to provide other necessary information, then format all these information and pass to OpenSolaris HCL server if the user want to do a submission. Submission is done through HTTPS post method. The user can see what data will be transferred to Sun before the submission is done. 4.1.3 Limitations There are a few limitations in current plan: (1) The following functionality depend on network connectivity to Sun servers: * Check device driver availability via IPS. * Dynamically add driver from IPS. * Submit system configuration to OpenSolaris HCL. (2) If the Solaris driver database is not updated in time(for example, there is driver which can be found in IPS but not in Solaris driver database), the driver search result may not be correct. However, if IPS enables the user to search for a driver package through supported vendor ID and device ID, this limitation will not exist any more. 4.2 Interfaces 4.2.1 Exported Interfaces Exported Interface| Stability | Description ------------------+-------------+---------------------------------------- /usr/bin/ddu | Committed | Device Driver Utility startup script ------------------+-------------+---------------------------------------- SUNWddu | Uncommitted | Package name for Device Driver Utility ------------------------------------------------------------------------- 4.2.2 Imported Interfaces Imported Interface| Stability | Description ------------------+-------------+---------------------------------------- Python 2.4.x | Volatile | PSARC/2005/532 ------------------+-------------+---------------------------------------- libdevinfo.so.1 | Uncommitted | PSARC/1997/127 ------------------+-------------+---------------------------------------- /dev/smbios | Uncommitted | PSARC/2005/483 ------------------+-------------+---------------------------------------- pkg(5): image | Uncommitted | PSARC 2008/190 packaging system | | ------------------------------------------------------------------------- 4.3 References [1] IPS is a repository for OpenSolaris packages where the user can find suitable drivers for the devices. 6. Resources and Schedule 6.4 Steering Committee Requested Information 6.4.1 Consolidation C-team Name: None 6.5 ARC review type: Fast Track 6.6 ARC exposure: Open From Jack.Meng@sun.com Wed Aug 6 02:24:55 2008 Received: from sunmail5.uk.sun.com (sunmail5.UK.Sun.COM [129.156.85.165]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m769OtGU020107 for ; Wed, 6 Aug 2008 02:24:55 -0700 (PDT) Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74]) by sunmail5.uk.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id m769OrNK028318 for <@sunmail2sca.sfbay.sun.com:PSARC-ext@sun.com>; Wed, 6 Aug 2008 10:24:54 +0100 (BST) Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0K5600F05A5HF200@nwk-avmta-1.sfbay.Sun.COM> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Wed, 06 Aug 2008 02:24:53 -0700 (PDT) Received: from sineb-mail-2.sun.com ([192.18.19.7]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0K5600MGVA5GOYB0@nwk-avmta-1.sfbay.Sun.COM> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Wed, 06 Aug 2008 02:24:53 -0700 (PDT) Received: from fe-apac-05.sun.com (fe-apac-05.sun.com [192.18.19.176] (may be forged)) by sineb-mail-2.sun.com (8.13.6+Sun/8.12.9) with ESMTP id m769OpH0002228 for ; Wed, 06 Aug 2008 09:24:51 +0000 (GMT) Received: from conversion-daemon.mail-apac.sun.com by mail-apac.sun.com (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) id <0K5600C01A10LD00@mail-apac.sun.com> (original mail from Jack.Meng@Sun.COM) for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Wed, 06 Aug 2008 17:24:51 +0800 (SGT) Received: from [129.158.144.117] by mail-apac.sun.com (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) with ESMTPSA id <0K5600MEOA5E9M4J@mail-apac.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Wed, 06 Aug 2008 17:24:51 +0800 (SGT) Date: Wed, 06 Aug 2008 17:24:26 +0800 From: Jack Subject: Re: PSARC 2008/504 Device Driver Utility In-reply-to: <48995E2E.8020801@sun.com> Sender: Jack.Meng@sun.com To: Frank Che Cc: PSARC-ext@sun.com, yan xue yang Message-id: <48996DCA.4040400@sun.com> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <48995E2E.8020801@sun.com> User-Agent: Thunderbird 2.0.0.16 (Windows/20080708) Status: RO Content-Length: 7013 Will this utility work during installation? - Jack Frank Che wrote: > I'm sponsoring this fast track for Bill Yan. Requested release binding > is patch/micro for OpenSolaris. Timer is set to 08/13/2008. > > Note that this project depends on the IPS project (PSARC 2008/190) > which is still under development now. > > Frank. > > 4. Technical Description > Summary > The intent of this project is to propose the integration of Device > Driver > Utility to OpenSolaris OS. Motivation to propose this project is to > fulfill > the increasing requirement from the customer about easily view > hardware > information in Solaris OS and install missing device driver(s), thus > contribute to the adoption of OpenSolaris OS. > This project requests a patch/micro release binding to OpenSolaris. > > 4.1 Proposal > 4.1.1 Introduction to Device Driver Utility > Device Driver Utility provides information about the devices of the > user's > native system. Device Driver Utility enables the user to connect to > the > Image Packaging System (IPS) [1] to search for the device drivers > for the > devices that do not have a driver attached with it. By using the > Device > Driver Utility application, the user can do the following: > * Get the information of the devices installed on your native > system and > their corresponding device driver availability status. The following > information are displayed on the GUI: > - Device name and attributes(device path, vendor ID, device ID > etc.) > - Device driver availability > - Device driver name and status(instance number, attached/detached > etc.) > * Check the device driver availability for your system devices on IPS. > * Download and install the device drivers from IPS for those devices > that do not have an attached driver. > * Report system configurations to the OpenSolaris Hardware > Compatibility > List (HCL). > > 4.1.2 Device Driver Utility components > To achieve the above functions, the following components will be > implemented: > > 4.1.2.1 Device information fetcher. > This component is designed to probe current system via the libdevinfo > interface, walk through device tree and get information of all > detected > devices and driver information of each device. > > 4.1.2.2 Solaris driver database. > The Solaris driver database is a mapping table between device > identifier(normally vendor ID and device ID) and name of Solaris > driver. > This database includes three sets of information: drivers that are > bundle > with OpenSolaris, third-party drivers that can be downloaded from > an IHV > website, drivers that can be downloaded from OpenSolaris community. > > This database is only used when a device doesn't have a driver. > > Solaris driver information is extracted from the > /etc/driver_aliases file. > Third-party and OpenSolaris driver information is manually > collected and > added to the driver database. > > The driver database must be updated periodically because new > hardware and > new Solaris drivers are continually created. > > 4.1.2.3 User interface. > Consider the target user of this tool are most likely don't have much > knowledge of Solaris system administration, only graphical user > interface > is available, written in Python. The user reads device information > from > this informative GUI, instruct Device Driver Utility to download and > install missing driver(s) automatically through a few simple > mouse-click, > submit hardware information to OpenSolaris HCL using this GUI. > > 4.1.2.4 Core engine. > This component stays in the center of Device Driver Utility. It > completes > the following fundamental operations: > (1) Get device information from device information fetcher. If there > is device > that missing driver in current OpenSolaris OS, then look up Solaris > driver > database for the driver name. Pass all these information to GUI for > display. > (2) Check IPS for driver availability through pkg(1M) command. Search for > package on IPS that contains needed driver based on driver name. > Download and > install certain driver package(s) according to user's instruction. > (3) Read hardware-related information from SMBIOS as much as possible, > then > automatically fill in to OpenSolaris HCL submission table, ask the > user to > provide other necessary information, then format all these information > and pass > to OpenSolaris HCL server if the user want to do a submission. > Submission is > done through HTTPS post method. The user can see what data will be > transferred > to Sun before the submission is done. > > 4.1.3 Limitations > There are a few limitations in current plan: > > (1) The following functionality depend on network connectivity to Sun > servers: > * Check device driver availability via IPS. > * Dynamically add driver from IPS. > * Submit system configuration to OpenSolaris HCL. > > (2) If the Solaris driver database is not updated in time(for example, > there is > driver which can be found in IPS but not in Solaris driver database), the > driver search result may not be correct. However, if IPS enables the > user to > search for a driver package through supported vendor ID and device ID, > this > limitation will not exist any more. > > 4.2 Interfaces > 4.2.1 Exported Interfaces > Exported Interface| Stability | Description > > ------------------+-------------+---------------------------------------- > /usr/bin/ddu | Committed | Device Driver Utility startup script > > ------------------+-------------+---------------------------------------- > SUNWddu | Uncommitted | Package name for Device Driver > Utility > > ------------------------------------------------------------------------- > > 4.2.2 Imported Interfaces > Imported Interface| Stability | Description > > ------------------+-------------+---------------------------------------- > Python 2.4.x | Volatile | PSARC/2005/532 > > ------------------+-------------+---------------------------------------- > libdevinfo.so.1 | Uncommitted | PSARC/1997/127 > > ------------------+-------------+---------------------------------------- > /dev/smbios | Uncommitted | PSARC/2005/483 > > ------------------+-------------+---------------------------------------- > pkg(5): image | Uncommitted | PSARC 2008/190 > packaging system | | > > ------------------------------------------------------------------------- > > 4.3 References > [1] IPS is a repository for OpenSolaris packages where the user can > find > suitable drivers for the devices. > > > 6. Resources and Schedule > 6.4 Steering Committee Requested Information > 6.4.1 Consolidation C-team Name: None > 6.5 ARC review type: Fast Track > 6.6 ARC exposure: Open > > From Xue-Yang.Yan@sun.com Wed Aug 6 02:46:59 2008 Received: from sunmail4.singapore.sun.com (sunmail4.Singapore.Sun.COM [129.158.71.19]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m769kwW9020701 for ; Wed, 6 Aug 2008 02:46:59 -0700 (PDT) Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74]) by sunmail4.singapore.sun.com (8.13.4+Sun/8.13.3/ENSMAIL,v2.2) with ESMTP id m769kulF013471 for <@sunmail2sca.sfbay.sun.com:PSARC-ext@sun.com>; Wed, 6 Aug 2008 17:46:57 +0800 (SGT) Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0K5600H0BB69WP00@nwk-avmta-1.sfbay.Sun.COM> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Wed, 06 Aug 2008 02:46:57 -0700 (PDT) Received: from sineb-mail-1.sun.com ([192.18.19.6]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0K5600MVIB68OYC0@nwk-avmta-1.sfbay.Sun.COM> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Wed, 06 Aug 2008 02:46:57 -0700 (PDT) Received: from fe-apac-06.sun.com (fe-apac-06.sun.com [192.18.19.177] (may be forged)) by sineb-mail-1.sun.com (8.13.6+Sun/8.12.9) with ESMTP id m769kt75002464 for ; Wed, 06 Aug 2008 09:46:55 +0000 (GMT) Received: from conversion-daemon.mail-apac.sun.com by mail-apac.sun.com (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) id <0K5600001B122Y00@mail-apac.sun.com> (original mail from Xue-Yang.Yan@Sun.COM) for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Wed, 06 Aug 2008 17:46:55 +0800 (SGT) Received: from [129.158.218.53] by mail-apac.sun.com (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) with ESMTPSA id <0K5600BWVB66RGET@mail-apac.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Wed, 06 Aug 2008 17:46:55 +0800 (SGT) Date: Wed, 06 Aug 2008 17:42:14 +0800 From: bill yan Subject: Re: PSARC 2008/504 Device Driver Utility In-reply-to: <48996DCA.4040400@sun.com> Sender: Xue-Yang.Yan@sun.com To: Jack Cc: Frank Che , PSARC-ext@sun.com Message-id: <489971F6.8000701@sun.com> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=UTF-8 Content-transfer-encoding: 8BIT X-Accept-Language: zh-cn X-PMX-Version: 5.4.1.325704 References: <48995E2E.8020801@sun.com> <48996DCA.4040400@sun.com> User-Agent: Mozilla/5.0 (X11; U; SunOS i86pc; zh-CN; rv:1.7) Gecko/20060627 Status: RO Content-Length: 7164 Hi Jack, The tool is bundled in opensolaris livecd. After you boot up the system from opensolaris livecd, you could find the Device Driver Utility icon on the desktop. If you have installed opensolaris on the harddisk, you could launch the tool by System->Administration->Device Driver Utility. Regards, Bill Jack 已写入: > Will this utility work during installation? > > - Jack > > Frank Che wrote: > >> I'm sponsoring this fast track for Bill Yan. Requested release >> binding is patch/micro for OpenSolaris. Timer is set to 08/13/2008. >> >> Note that this project depends on the IPS project (PSARC 2008/190) >> which is still under development now. >> >> Frank. >> >> 4. Technical Description >> Summary >> The intent of this project is to propose the integration of Device >> Driver >> Utility to OpenSolaris OS. Motivation to propose this project is to >> fulfill >> the increasing requirement from the customer about easily view hardware >> information in Solaris OS and install missing device driver(s), thus >> contribute to the adoption of OpenSolaris OS. >> This project requests a patch/micro release binding to OpenSolaris. >> >> 4.1 Proposal >> 4.1.1 Introduction to Device Driver Utility >> Device Driver Utility provides information about the devices of the >> user's >> native system. Device Driver Utility enables the user to connect to the >> Image Packaging System (IPS) [1] to search for the device drivers for >> the >> devices that do not have a driver attached with it. By using the Device >> Driver Utility application, the user can do the following: >> * Get the information of the devices installed on your native system and >> their corresponding device driver availability status. The following >> information are displayed on the GUI: >> - Device name and attributes(device path, vendor ID, device ID etc.) >> - Device driver availability >> - Device driver name and status(instance number, attached/detached >> etc.) >> * Check the device driver availability for your system devices on IPS. >> * Download and install the device drivers from IPS for those devices >> that do not have an attached driver. >> * Report system configurations to the OpenSolaris Hardware Compatibility >> List (HCL). >> >> 4.1.2 Device Driver Utility components >> To achieve the above functions, the following components will be >> implemented: >> >> 4.1.2.1 Device information fetcher. >> This component is designed to probe current system via the libdevinfo >> interface, walk through device tree and get information of all detected >> devices and driver information of each device. >> >> 4.1.2.2 Solaris driver database. >> The Solaris driver database is a mapping table between device >> identifier(normally vendor ID and device ID) and name of Solaris driver. >> This database includes three sets of information: drivers that are >> bundle >> with OpenSolaris, third-party drivers that can be downloaded from an IHV >> website, drivers that can be downloaded from OpenSolaris community. >> >> This database is only used when a device doesn't have a driver. >> >> Solaris driver information is extracted from the /etc/driver_aliases >> file. >> Third-party and OpenSolaris driver information is manually collected and >> added to the driver database. >> >> The driver database must be updated periodically because new hardware >> and >> new Solaris drivers are continually created. >> >> 4.1.2.3 User interface. >> Consider the target user of this tool are most likely don't have much >> knowledge of Solaris system administration, only graphical user >> interface >> is available, written in Python. The user reads device information from >> this informative GUI, instruct Device Driver Utility to download and >> install missing driver(s) automatically through a few simple >> mouse-click, >> submit hardware information to OpenSolaris HCL using this GUI. >> >> 4.1.2.4 Core engine. >> This component stays in the center of Device Driver Utility. It >> completes >> the following fundamental operations: >> (1) Get device information from device information fetcher. If there >> is device >> that missing driver in current OpenSolaris OS, then look up Solaris >> driver >> database for the driver name. Pass all these information to GUI for >> display. >> (2) Check IPS for driver availability through pkg(1M) command. Search >> for >> package on IPS that contains needed driver based on driver name. >> Download and >> install certain driver package(s) according to user's instruction. >> (3) Read hardware-related information from SMBIOS as much as >> possible, then >> automatically fill in to OpenSolaris HCL submission table, ask the >> user to >> provide other necessary information, then format all these >> information and pass >> to OpenSolaris HCL server if the user want to do a submission. >> Submission is >> done through HTTPS post method. The user can see what data will be >> transferred >> to Sun before the submission is done. >> >> 4.1.3 Limitations >> There are a few limitations in current plan: >> >> (1) The following functionality depend on network connectivity to Sun >> servers: >> * Check device driver availability via IPS. >> * Dynamically add driver from IPS. >> * Submit system configuration to OpenSolaris HCL. >> >> (2) If the Solaris driver database is not updated in time(for >> example, there is >> driver which can be found in IPS but not in Solaris driver database), >> the >> driver search result may not be correct. However, if IPS enables the >> user to >> search for a driver package through supported vendor ID and device >> ID, this >> limitation will not exist any more. >> >> 4.2 Interfaces >> 4.2.1 Exported Interfaces >> Exported Interface| Stability | Description >> ------------------+-------------+---------------------------------------- >> >> /usr/bin/ddu | Committed | Device Driver Utility startup script >> ------------------+-------------+---------------------------------------- >> >> SUNWddu | Uncommitted | Package name for Device Driver Utility >> ------------------------------------------------------------------------- >> >> >> 4.2.2 Imported Interfaces >> Imported Interface| Stability | Description >> ------------------+-------------+---------------------------------------- >> >> Python 2.4.x | Volatile | PSARC/2005/532 >> ------------------+-------------+---------------------------------------- >> >> libdevinfo.so.1 | Uncommitted | PSARC/1997/127 >> ------------------+-------------+---------------------------------------- >> >> /dev/smbios | Uncommitted | PSARC/2005/483 >> ------------------+-------------+---------------------------------------- >> >> pkg(5): image | Uncommitted | PSARC 2008/190 >> packaging system | | >> ------------------------------------------------------------------------- >> >> >> 4.3 References >> [1] IPS is a repository for OpenSolaris packages where the user can find >> suitable drivers for the devices. >> >> >> 6. Resources and Schedule >> 6.4 Steering Committee Requested Information >> 6.4.1 Consolidation C-team Name: None >> 6.5 ARC review type: Fast Track >> 6.6 ARC exposure: Open >> >> > From James.McPherson@sun.com Wed Aug 6 03:49:49 2008 Received: from sunmail5.uk.sun.com (sunmail5.UK.Sun.COM [129.156.85.165]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m76Anm97022346 for ; Wed, 6 Aug 2008 03:49:48 -0700 (PDT) Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6]) by sunmail5.uk.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id m76AnkeV001586 for <@sunmail2sca.sfbay.sun.com:PSARC-ext@sun.com>; Wed, 6 Aug 2008 11:49:47 +0100 (BST) Received: from pmxchannel-daemon.nwk-avmta-2.sfbay.sun.com by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0K5600001E2ZW000@nwk-avmta-2.sfbay.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Wed, 06 Aug 2008 03:49:47 -0700 (PDT) Received: from sineb-mail-2.sun.com ([192.18.19.7]) by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0K5600FH2E2XNOC0@nwk-avmta-2.sfbay.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Wed, 06 Aug 2008 03:49:46 -0700 (PDT) Received: from fe-apac-06.sun.com (fe-apac-06.sun.com [192.18.19.177] (may be forged)) by sineb-mail-2.sun.com (8.13.6+Sun/8.12.9) with ESMTP id m76AnjxZ007180 for ; Wed, 06 Aug 2008 10:49:45 +0000 (GMT) Received: from conversion-daemon.mail-apac.sun.com by mail-apac.sun.com (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) id <0K5600K01DYG5800@mail-apac.sun.com> (original mail from James.McPherson@Sun.COM) for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Wed, 06 Aug 2008 18:49:45 +0800 (SGT) Received: from [192.168.1.10] ([220.157.71.44]) by mail-apac.sun.com (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) with ESMTPSA id <0K56009JPE2U8F9G@mail-apac.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Wed, 06 Aug 2008 18:49:44 +0800 (SGT) Date: Wed, 06 Aug 2008 20:49:42 +1000 From: "James C. McPherson" Subject: Re: PSARC 2008/504 Device Driver Utility In-reply-to: <48996DCA.4040400@sun.com> Sender: James.McPherson@sun.com To: Jack Cc: Frank Che , PSARC-ext@sun.com, yan xue yang Reply-to: James.McPherson@sun.com Message-id: <489981C6.50408@Sun.COM> Organization: Sun Microsystems MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=UTF-8 Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <48995E2E.8020801@sun.com> <48996DCA.4040400@sun.com> User-Agent: Thunderbird 2.0.0.14 (X11/20080616) Status: RO Content-Length: 314 Jack wrote: > Will this utility work during installation? The short answer is "yes" - particularly if you're running this from the OpenSolaris 2008.05 (or later) liveCD. James C. McPherson -- Senior Kernel Software Engineer, Solaris Sun Microsystems http://blogs.sun.com/jmcp http://www.jmcp.homeunix.com/blog From James.McPherson@Sun.COM Wed Aug 6 04:18:38 2008 Received: from sunmail2sca.sfbay.sun.com (sunmail2sca.SFBay.Sun.COM [129.145.155.234]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m76BIbtw022831 for ; Wed, 6 Aug 2008 04:18:38 -0700 (PDT) Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11]) by sunmail2sca.sfbay.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id m76BIboJ018033 for <@sunmail2sca.sfbay.sun.com:PSARC-ext@sun.com>; Wed, 6 Aug 2008 04:18:37 -0700 (PDT) Received: from pmxchannel-daemon.brm-avmta-1.central.sun.com by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0K5600001FF0BF00@brm-avmta-1.central.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Wed, 06 Aug 2008 05:18:36 -0600 (MDT) Received: from sineb-mail-1.sun.com ([192.18.19.6]) by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0K5600AZQFEZSLE0@brm-avmta-1.central.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Wed, 06 Aug 2008 05:18:36 -0600 (MDT) Received: from fe-apac-05.sun.com (fe-apac-05.sun.com [192.18.19.176] (may be forged)) by sineb-mail-1.sun.com (8.13.6+Sun/8.12.9) with ESMTP id m76BIY9u007369 for ; Wed, 06 Aug 2008 11:18:34 +0000 (GMT) Received: from conversion-daemon.mail-apac.sun.com by mail-apac.sun.com (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) id <0K5600D01FDYTM00@mail-apac.sun.com> (original mail from James.McPherson@Sun.COM) for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Wed, 06 Aug 2008 19:18:34 +0800 (SGT) Received: from [192.168.1.10] ([220.157.71.44]) by mail-apac.sun.com (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) with ESMTPSA id <0K56003ZVFEXJPE1@mail-apac.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Wed, 06 Aug 2008 19:18:34 +0800 (SGT) Date: Wed, 06 Aug 2008 21:18:32 +1000 From: "James C. McPherson" Subject: Re: PSARC 2008/504 Device Driver Utility In-reply-to: <48995E2E.8020801@sun.com> Sender: James.McPherson@Sun.COM To: Frank Che Cc: PSARC-ext@Sun.COM, yan xue yang Reply-to: James.McPherson@Sun.COM Message-id: <48998888.5060707@Sun.COM> Organization: Sun Microsystems MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=UTF-8 Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <48995E2E.8020801@sun.com> User-Agent: Thunderbird 2.0.0.14 (X11/20080616) Status: RO Content-Length: 8042 Frank Che wrote: > I'm sponsoring this fast track for Bill Yan. Requested release binding > is patch/micro for OpenSolaris. Timer is set to 08/13/2008. > > Note that this project depends on the IPS project (PSARC 2008/190) which > is still under development now. So you want this to go into a Solaris 10 Update? Why? I would have expected "minor" for the release binding since you have a dependency on the IPS project. > Frank. > > 4. Technical Description > Summary > The intent of this project is to propose the integration of Device Driver > Utility to OpenSolaris OS. Motivation to propose this project is to fulfill > the increasing requirement from the customer about easily view hardware > information in Solaris OS and install missing device driver(s), thus > contribute to the adoption of OpenSolaris OS. > > This project requests a patch/micro release binding to OpenSolaris. > > 4.1 Proposal > 4.1.1 Introduction to Device Driver Utility > Device Driver Utility provides information about the devices of the user's > native system. Device Driver Utility enables the user to connect to the > Image Packaging System (IPS) [1] to search for the device drivers for the > devices that do not have a driver attached with it. By using the Device > Driver Utility application, the user can do the following: > * Get the information of the devices installed on your native system and > their corresponding device driver availability status. The following > information are displayed on the GUI: > - Device name and attributes(device path, vendor ID, device ID etc.) > - Device driver availability > - Device driver name and status(instance number, attached/detached > etc.) > * Check the device driver availability for your system devices on IPS. > * Download and install the device drivers from IPS for those devices > that do not have an attached driver. > * Report system configurations to the OpenSolaris Hardware Compatibility > List (HCL). > > 4.1.2 Device Driver Utility components > To achieve the above functions, the following components will be > implemented: > > 4.1.2.1 Device information fetcher. > This component is designed to probe current system via the libdevinfo > interface, walk through device tree and get information of all detected > devices and driver information of each device. > > 4.1.2.2 Solaris driver database. > The Solaris driver database is a mapping table between device > identifier(normally vendor ID and device ID) and name of Solaris driver. > This database includes three sets of information: drivers that are bundle > with OpenSolaris, third-party drivers that can be downloaded from an IHV > website, drivers that can be downloaded from OpenSolaris community. > > This database is only used when a device doesn't have a driver. > > Solaris driver information is extracted from the /etc/driver_aliases file. > Third-party and OpenSolaris driver information is manually collected and > added to the driver database. > > The driver database must be updated periodically because new hardware and > new Solaris drivers are continually created. How often will the database be updated? Who is responsible for updating the database? Who is responsible for ensuring that the information in the database is accurate? > 4.1.2.3 User interface. > Consider the target user of this tool are most likely don't have much > knowledge of Solaris system administration, only graphical user interface > is available, written in Python. The user reads device information from > this informative GUI, instruct Device Driver Utility to download and > install missing driver(s) automatically through a few simple mouse-click, > submit hardware information to OpenSolaris HCL using this GUI. What if the driver is for a network device, and the system has no other network interface installed? What information will be provided to the user so that they can get the driver via other means? > 4.1.2.4 Core engine. > This component stays in the center of Device Driver Utility. It completes > the following fundamental operations: > (1) Get device information from device information fetcher. If there is device > that missing driver in current OpenSolaris OS, then look up Solaris driver > database for the driver name. Pass all these information to GUI for display. > (2) Check IPS for driver availability through pkg(1M) command. Search for > package on IPS that contains needed driver based on driver name. Download and > install certain driver package(s) according to user's instruction. > (3) Read hardware-related information from SMBIOS as much as possible, then > automatically fill in to OpenSolaris HCL submission table, ask the user to > provide other necessary information, then format all these information and pass > to OpenSolaris HCL server if the user want to do a submission. Submission is > done through HTTPS post method. The user can see what data will be transferred > to Sun before the submission is done. I like the sound of this. Will there be just one URL to point both the database queries and submission towards, or will there be multiple locations? If there are multiple locations, how will the information be collated for the database, and how will it be propagated to the other locations? How will you handle secure sites? > 4.1.3 Limitations > There are a few limitations in current plan: > > (1) The following functionality depend on network connectivity to Sun servers: > * Check device driver availability via IPS. > * Dynamically add driver from IPS. > * Submit system configuration to OpenSolaris HCL. > > (2) If the Solaris driver database is not updated in time(for example, there is > driver which can be found in IPS but not in Solaris driver database), the > driver search result may not be correct. However, if IPS enables the user to > search for a driver package through supported vendor ID and device ID, this > limitation will not exist any more. > > 4.2 Interfaces > 4.2.1 Exported Interfaces > Exported Interface| Stability | Description > ------------------+-------------+---------------------------------------- > /usr/bin/ddu | Committed | Device Driver Utility startup script > ------------------+-------------+---------------------------------------- > SUNWddu | Uncommitted | Package name for Device Driver Utility > ------------------------------------------------------------------------- > > 4.2.2 Imported Interfaces > Imported Interface| Stability | Description > ------------------+-------------+---------------------------------------- > Python 2.4.x | Volatile | PSARC/2005/532 > ------------------+-------------+---------------------------------------- > libdevinfo.so.1 | Uncommitted | PSARC/1997/127 > ------------------+-------------+---------------------------------------- > /dev/smbios | Uncommitted | PSARC/2005/483 > ------------------+-------------+---------------------------------------- > pkg(5): image | Uncommitted | PSARC 2008/190 > packaging system | | > ------------------------------------------------------------------------- > > 4.3 References > [1] IPS is a repository for OpenSolaris packages where the user can find > suitable drivers for the devices. > > > 6. Resources and Schedule > 6.4 Steering Committee Requested Information > 6.4.1 Consolidation C-team Name: None > 6.5 ARC review type: Fast Track > 6.6 ARC exposure: Open One final question - is the project team writing this from scratch, or are they leveraging the work of the existing HCTS tool? James C. McPherson -- Senior Kernel Software Engineer, Solaris Sun Microsystems http://blogs.sun.com/jmcp http://www.jmcp.homeunix.com/blog From carlsonj@phorcys.east.sun.com Wed Aug 6 05:04:17 2008 Received: from sunmail4.singapore.sun.com (sunmail4.Singapore.Sun.COM [129.158.71.19]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m76C4G4W023608 for ; Wed, 6 Aug 2008 05:04:17 -0700 (PDT) Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6]) by sunmail4.singapore.sun.com (8.13.4+Sun/8.13.3/ENSMAIL,v2.2) with ESMTP id m76C49q3029564; Wed, 6 Aug 2008 20:04:15 +0800 (SGT) Received: from pmxchannel-daemon.nwk-avmta-2.sfbay.sun.com by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0K5600403HIZ5J00@nwk-avmta-2.sfbay.sun.com>; Wed, 06 Aug 2008 05:04:11 -0700 (PDT) Received: from phorcys.east.sun.com ([129.148.174.143]) by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0K56003FTHIX6L40@nwk-avmta-2.sfbay.sun.com>; Wed, 06 Aug 2008 05:04:10 -0700 (PDT) Received: from phorcys.east.sun.com (localhost [127.0.0.1]) by phorcys.east.sun.com (8.14.3+Sun/8.14.3) with ESMTP id m76C49oh007729; Wed, 06 Aug 2008 08:04:09 -0400 (EDT) Received: (from carlsonj@localhost) by phorcys.east.sun.com (8.14.3+Sun/8.14.3/Submit) id m76C49Pb007726; Wed, 06 Aug 2008 08:04:09 -0400 (EDT) Date: Wed, 06 Aug 2008 08:04:09 -0400 From: James Carlson Subject: Re: PSARC 2008/504 Device Driver Utility In-reply-to: <48998888.5060707@Sun.COM> To: James.McPherson@sun.com Cc: Frank Che , PSARC-ext@sun.com, yan xue yang Message-id: <18585.37689.612955.983678@gargle.gargle.HOWL> MIME-version: 1.0 X-Mailer: VM 7.01 under Emacs 21.3.1 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <48995E2E.8020801@sun.com> <48998888.5060707@Sun.COM> Status: RO Content-Length: 936 James C. McPherson writes: > Frank Che wrote: > > I'm sponsoring this fast track for Bill Yan. Requested release binding > > is patch/micro for OpenSolaris. Timer is set to 08/13/2008. > > > > Note that this project depends on the IPS project (PSARC 2008/190) which > > is still under development now. > > > So you want this to go into a Solaris 10 Update? Why? I would have > expected "minor" for the release binding since you have a dependency > on the IPS project. No -- he specifically mentions "OpenSolaris" as the delivery vehicle, not "Solaris." It's not for an S10 Update. It just has no architectural impact of its own that requires a Minor release binding. Anywhere IPS could go, it would go. -- James Carlson, Solaris Networking Sun Microsystems / 35 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677 From James.McPherson@sun.com Wed Aug 6 05:14:24 2008 Received: from sunmail5.uk.sun.com (sunmail5.UK.Sun.COM [129.156.85.165]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m76CENZ2023815 for ; Wed, 6 Aug 2008 05:14:24 -0700 (PDT) Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6]) by sunmail5.uk.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id m76CEJwJ001911 for <@sunmail2sca.sfbay.sun.com:PSARC-ext@sun.com>; Wed, 6 Aug 2008 13:14:23 +0100 (BST) Received: from pmxchannel-daemon.nwk-avmta-2.sfbay.sun.com by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0K560040BHZWLP00@nwk-avmta-2.sfbay.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Wed, 06 Aug 2008 05:14:20 -0700 (PDT) Received: from sineb-mail-1.sun.com ([192.18.19.6]) by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0K5600331HZV6L70@nwk-avmta-2.sfbay.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Wed, 06 Aug 2008 05:14:20 -0700 (PDT) Received: from fe-apac-05.sun.com (fe-apac-05.sun.com [192.18.19.176] (may be forged)) by sineb-mail-1.sun.com (8.13.6+Sun/8.12.9) with ESMTP id m76CEI9N009532 for ; Wed, 06 Aug 2008 12:14:18 +0000 (GMT) Received: from conversion-daemon.mail-apac.sun.com by mail-apac.sun.com (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) id <0K5600G01HW5B500@mail-apac.sun.com> (original mail from James.McPherson@Sun.COM) for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Wed, 06 Aug 2008 20:14:18 +0800 (SGT) Received: from [192.168.1.10] ([220.157.71.44]) by mail-apac.sun.com (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) with ESMTPSA id <0K560034WHZTJPH1@mail-apac.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Wed, 06 Aug 2008 20:14:18 +0800 (SGT) Date: Wed, 06 Aug 2008 22:14:10 +1000 From: "James C. McPherson" Subject: Re: PSARC 2008/504 Device Driver Utility In-reply-to: <18585.37689.612955.983678@gargle.gargle.HOWL> Sender: James.McPherson@sun.com To: James Carlson Cc: Frank Che , PSARC-ext@sun.com, yan xue yang Reply-to: James.McPherson@sun.com Message-id: <48999592.4060407@Sun.COM> Organization: Sun Microsystems MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=UTF-8 Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <48995E2E.8020801@sun.com> <48998888.5060707@Sun.COM> <18585.37689.612955.983678@gargle.gargle.HOWL> User-Agent: Thunderbird 2.0.0.14 (X11/20080616) Status: RO Content-Length: 966 James Carlson wrote: > James C. McPherson writes: >> Frank Che wrote: >>> I'm sponsoring this fast track for Bill Yan. Requested release binding >>> is patch/micro for OpenSolaris. Timer is set to 08/13/2008. >> > >>> Note that this project depends on the IPS project (PSARC 2008/190) which >>> is still under development now. >> >> So you want this to go into a Solaris 10 Update? Why? I would have >> expected "minor" for the release binding since you have a dependency >> on the IPS project. > > No -- he specifically mentions "OpenSolaris" as the delivery vehicle, > not "Solaris." > > It's not for an S10 Update. It just has no architectural impact of > its own that requires a Minor release binding. Anywhere IPS could go, > it would go. True, and I consider the "patch/micro" request to be incorrect in this context also. James -- Senior Kernel Software Engineer, Solaris Sun Microsystems http://blogs.sun.com/jmcp http://www.jmcp.homeunix.com/blog From carlsonj@phorcys.east.sun.com Wed Aug 6 06:11:24 2008 Received: from sunmail5.uk.sun.com (sunmail5.UK.Sun.COM [129.156.85.165]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m76DBNNI026142 for ; Wed, 6 Aug 2008 06:11:24 -0700 (PDT) Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6]) by sunmail5.uk.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id m76DBB6h025427; Wed, 6 Aug 2008 14:11:18 +0100 (BST) Received: from pmxchannel-daemon.nwk-avmta-2.sfbay.sun.com by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0K560060JKMTYV00@nwk-avmta-2.sfbay.sun.com>; Wed, 06 Aug 2008 06:11:17 -0700 (PDT) Received: from phorcys.east.sun.com ([129.148.174.143]) by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0K56006JSKMRHO00@nwk-avmta-2.sfbay.sun.com>; Wed, 06 Aug 2008 06:11:16 -0700 (PDT) Received: from phorcys.east.sun.com (localhost [127.0.0.1]) by phorcys.east.sun.com (8.14.3+Sun/8.14.3) with ESMTP id m76DBFCh008068; Wed, 06 Aug 2008 09:11:15 -0400 (EDT) Received: (from carlsonj@localhost) by phorcys.east.sun.com (8.14.3+Sun/8.14.3/Submit) id m76DBFFH008065; Wed, 06 Aug 2008 09:11:15 -0400 (EDT) Date: Wed, 06 Aug 2008 09:11:15 -0400 From: James Carlson Subject: Re: PSARC 2008/504 Device Driver Utility In-reply-to: <48999592.4060407@Sun.COM> To: James.McPherson@sun.com Cc: PSARC-ext@sun.com, yan xue yang , Frank Che Message-id: <18585.41715.703204.568984@gargle.gargle.HOWL> MIME-version: 1.0 X-Mailer: VM 7.01 under Emacs 21.3.1 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <48995E2E.8020801@sun.com> <48998888.5060707@Sun.COM> <18585.37689.612955.983678@gargle.gargle.HOWL> <48999592.4060407@Sun.COM> Status: RO Content-Length: 1896 James C. McPherson writes: > James Carlson wrote: > > It's not for an S10 Update. It just has no architectural impact of > > its own that requires a Minor release binding. Anywhere IPS could go, > > it would go. > > True, and I consider the "patch/micro" request to be incorrect > in this context also. Why would that be? "Patch/micro" implicitly authorizes you to deliver via Minor and Major releases, and it's valid even if there are no Patches or Micro release vehicles currently defined or in progress. In addition, when a project asserts a "patch/micro" release binding on Solaris, the project team is not necessarily saying that they *will* backport to something in the S10 patch train or any other one. It says only that the project would be acceptable for such a backport *if* there were a reason or cause to do that. The reasons for a backport (if any) are outside of the ARC's domain -- that's a resources and content issue, not architectural. The ARC doesn't normally review projects against a specific named release or schedule. Instead, it reviews against a *type* of release. In this case, the project team is asserting that the change they're making (adding this new utility) would be an acceptable change in any kind of release -- including a Patch or a Micro release. I agree with them; their project is not making the sorts of changes that would require Minor (or higher) release binding. (For what it's worth, I advised the project team privately to use "patch/micro" to avoid almost exactly this conversation, which almost inevitably comes from someone asserting "micro" binding when a lesser binding will do. Mission failed, I suppose.) -- James Carlson, Solaris Networking Sun Microsystems / 35 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677 From gdamore@Sun.COM Wed Aug 6 07:48:40 2008 Received: from sunmail3mpk.sfbay.sun.com (sunmail3mpk.SFBay.Sun.COM [129.146.11.52]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m76Emeqr029473 for ; Wed, 6 Aug 2008 07:48:40 -0700 (PDT) Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11]) by sunmail3mpk.sfbay.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id m76Emb4Q021764 for <@sunmail2sca.sfbay.sun.com:PSARC-ext@sun.com>; Wed, 6 Aug 2008 07:48:39 -0700 (PDT) Received: from pmxchannel-daemon.brm-avmta-1.central.sun.com by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0K5600F0DP538200@brm-avmta-1.central.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Wed, 06 Aug 2008 08:48:39 -0600 (MDT) Received: from sca-es-mail-2.sun.com ([192.18.43.133]) by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0K5600EJIP522I10@brm-avmta-1.central.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Wed, 06 Aug 2008 08:48:38 -0600 (MDT) Received: from fe-sfbay-09.sun.com ([192.18.43.129]) by sca-es-mail-2.sun.com (8.13.7+Sun/8.12.9) with ESMTP id m76Emcse003914 for ; Wed, 06 Aug 2008 07:48:38 -0700 (PDT) Received: from conversion-daemon.fe-sfbay-09.sun.com by fe-sfbay-09.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) id <0K5600A01OW9DT00@fe-sfbay-09.sun.com> (original mail from gdamore@sun.com) for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Wed, 06 Aug 2008 07:48:37 -0700 (PDT) Received: from [10.7.251.172] by fe-sfbay-09.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0K560054HP4ZD0B0@fe-sfbay-09.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Wed, 06 Aug 2008 07:48:36 -0700 (PDT) Date: Wed, 06 Aug 2008 07:43:27 -0700 From: "Garrett D'Amore" Subject: Re: PSARC 2008/504 Device Driver Utility In-reply-to: <48998888.5060707@Sun.COM> Sender: Garrett.Damore@Sun.COM To: James.McPherson@Sun.COM Cc: Frank Che , PSARC-ext@Sun.COM, yan xue yang Message-id: <4899B88F.2040209@sun.com> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=UTF-8 Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <48995E2E.8020801@sun.com> <48998888.5060707@Sun.COM> User-Agent: Thunderbird 2.0.0.14 (X11/20080616) Status: RO Content-Length: 8660 James C. McPherson wrote: > Frank Che wrote: >> I'm sponsoring this fast track for Bill Yan. Requested release >> binding is patch/micro for OpenSolaris. Timer is set to 08/13/2008. > > >> Note that this project depends on the IPS project (PSARC 2008/190) >> which is still under development now. > > > So you want this to go into a Solaris 10 Update? Why? I would have > expected "minor" for the release binding since you have a dependency > on the IPS project. Yes, minor is appropriate. Note that patch != micro in any case, so you'd need to pick one. (We haven't had a micro release since Solaris 2.5.1.) -- Garrett > >> Frank. >> >> 4. Technical Description >> Summary >> The intent of this project is to propose the integration of >> Device Driver >> Utility to OpenSolaris OS. Motivation to propose this project is >> to fulfill >> the increasing requirement from the customer about easily view >> hardware >> information in Solaris OS and install missing device driver(s), thus >> contribute to the adoption of OpenSolaris OS. >> This project requests a patch/micro release binding to >> OpenSolaris. >> >> 4.1 Proposal >> 4.1.1 Introduction to Device Driver Utility >> Device Driver Utility provides information about the devices of >> the user's >> native system. Device Driver Utility enables the user to connect >> to the >> Image Packaging System (IPS) [1] to search for the device drivers >> for the >> devices that do not have a driver attached with it. By using the >> Device >> Driver Utility application, the user can do the following: >> * Get the information of the devices installed on your native >> system and >> their corresponding device driver availability status. The following >> information are displayed on the GUI: >> - Device name and attributes(device path, vendor ID, device >> ID etc.) >> - Device driver availability >> - Device driver name and status(instance number, >> attached/detached >> etc.) >> * Check the device driver availability for your system devices on >> IPS. >> * Download and install the device drivers from IPS for those devices >> that do not have an attached driver. >> * Report system configurations to the OpenSolaris Hardware >> Compatibility >> List (HCL). >> >> 4.1.2 Device Driver Utility components >> To achieve the above functions, the following components will be >> implemented: >> >> 4.1.2.1 Device information fetcher. >> This component is designed to probe current system via the >> libdevinfo >> interface, walk through device tree and get information of all >> detected >> devices and driver information of each device. >> >> 4.1.2.2 Solaris driver database. >> The Solaris driver database is a mapping table between device >> identifier(normally vendor ID and device ID) and name of Solaris >> driver. >> This database includes three sets of information: drivers that >> are bundle >> with OpenSolaris, third-party drivers that can be downloaded from >> an IHV >> website, drivers that can be downloaded from OpenSolaris community. >> >> This database is only used when a device doesn't have a driver. >> >> Solaris driver information is extracted from the >> /etc/driver_aliases file. >> Third-party and OpenSolaris driver information is manually >> collected and >> added to the driver database. >> >> The driver database must be updated periodically because new >> hardware and >> new Solaris drivers are continually created. > > > How often will the database be updated? > Who is responsible for updating the database? > Who is responsible for ensuring that the information > in the database is accurate? > > >> 4.1.2.3 User interface. >> Consider the target user of this tool are most likely don't have >> much >> knowledge of Solaris system administration, only graphical user >> interface >> is available, written in Python. The user reads device >> information from >> this informative GUI, instruct Device Driver Utility to download and >> install missing driver(s) automatically through a few simple >> mouse-click, >> submit hardware information to OpenSolaris HCL using this GUI. > > What if the driver is for a network device, and the > system has no other network interface installed? > What information will be provided to the user so that > they can get the driver via other means? > > > >> 4.1.2.4 Core engine. >> This component stays in the center of Device Driver Utility. It >> completes >> the following fundamental operations: >> (1) Get device information from device information fetcher. If there >> is device >> that missing driver in current OpenSolaris OS, then look up Solaris >> driver >> database for the driver name. Pass all these information to GUI for >> display. >> (2) Check IPS for driver availability through pkg(1M) command. Search >> for >> package on IPS that contains needed driver based on driver name. >> Download and >> install certain driver package(s) according to user's instruction. >> (3) Read hardware-related information from SMBIOS as much as >> possible, then >> automatically fill in to OpenSolaris HCL submission table, ask the >> user to >> provide other necessary information, then format all these >> information and pass >> to OpenSolaris HCL server if the user want to do a submission. >> Submission is >> done through HTTPS post method. The user can see what data will be >> transferred >> to Sun before the submission is done. > > I like the sound of this. Will there be just one URL to point both > the database queries and submission towards, or will there be multiple > locations? > > If there are multiple locations, how will the information be collated > for the database, and how will it be propagated to the other locations? > > > How will you handle secure sites? > > >> 4.1.3 Limitations >> There are a few limitations in current plan: >> >> (1) The following functionality depend on network connectivity to Sun >> servers: >> * Check device driver availability via IPS. >> * Dynamically add driver from IPS. >> * Submit system configuration to OpenSolaris HCL. >> >> (2) If the Solaris driver database is not updated in time(for >> example, there is >> driver which can be found in IPS but not in Solaris driver database), >> the >> driver search result may not be correct. However, if IPS enables the >> user to >> search for a driver package through supported vendor ID and device >> ID, this >> limitation will not exist any more. >> >> 4.2 Interfaces >> 4.2.1 Exported Interfaces >> Exported Interface| Stability | Description >> >> ------------------+-------------+---------------------------------------- >> >> /usr/bin/ddu | Committed | Device Driver Utility startup >> script >> >> ------------------+-------------+---------------------------------------- >> >> SUNWddu | Uncommitted | Package name for Device Driver >> Utility >> >> ------------------------------------------------------------------------- >> >> >> 4.2.2 Imported Interfaces >> Imported Interface| Stability | Description >> >> ------------------+-------------+---------------------------------------- >> >> Python 2.4.x | Volatile | PSARC/2005/532 >> >> ------------------+-------------+---------------------------------------- >> >> libdevinfo.so.1 | Uncommitted | PSARC/1997/127 >> >> ------------------+-------------+---------------------------------------- >> >> /dev/smbios | Uncommitted | PSARC/2005/483 >> >> ------------------+-------------+---------------------------------------- >> >> pkg(5): image | Uncommitted | PSARC 2008/190 >> packaging system | | >> >> ------------------------------------------------------------------------- >> >> >> 4.3 References >> [1] IPS is a repository for OpenSolaris packages where the user >> can find >> suitable drivers for the devices. >> >> >> 6. Resources and Schedule >> 6.4 Steering Committee Requested Information >> 6.4.1 Consolidation C-team Name: None >> 6.5 ARC review type: Fast Track >> 6.6 ARC exposure: Open > > One final question - is the project team writing this from scratch, > or are they leveraging the work of the existing HCTS tool? > > > James C. McPherson > -- > Senior Kernel Software Engineer, Solaris > Sun Microsystems > http://blogs.sun.com/jmcp http://www.jmcp.homeunix.com/blog From Frank.Che@sun.com Wed Aug 6 09:14:31 2008 Received: from newsunmail1brm.central.sun.com (newsunmail1brm.Central.Sun.COM [129.147.62.245]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m76GEVJe003941 for ; Wed, 6 Aug 2008 09:14:31 -0700 (PDT) Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74]) by newsunmail1brm.central.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id m76GEUBA041222 for <@sunmail2sca.sfbay.sun.com:PSARC-ext@sun.com>; Wed, 6 Aug 2008 10:14:31 -0600 (MDT) Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0K5600C1XT46EQ00@nwk-avmta-1.sfbay.Sun.COM> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Wed, 06 Aug 2008 09:14:30 -0700 (PDT) Received: from sineb-mail-2.sun.com ([192.18.19.7]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0K560083JT434Z60@nwk-avmta-1.sfbay.Sun.COM> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Wed, 06 Aug 2008 09:14:28 -0700 (PDT) Received: from fe-apac-06.sun.com (fe-apac-06.sun.com [192.18.19.177] (may be forged)) by sineb-mail-2.sun.com (8.13.6+Sun/8.12.9) with ESMTP id m76GERdX015819 for ; Wed, 06 Aug 2008 16:14:27 +0000 (GMT) Received: from conversion-daemon.mail-apac.sun.com by mail-apac.sun.com (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) id <0K5600501T3IDN00@mail-apac.sun.com> (original mail from Frank.Che@Sun.COM) for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Thu, 07 Aug 2008 00:14:27 +0800 (SGT) Received: from [123.112.41.166] by mail-apac.sun.com (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) with ESMTPSA id <0K56009RHT408AB7@mail-apac.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Thu, 07 Aug 2008 00:14:27 +0800 (SGT) Date: Thu, 07 Aug 2008 00:14:24 +0800 From: frank Che Subject: Re: PSARC 2008/504 Device Driver Utility In-reply-to: <48998888.5060707@Sun.COM> Sender: Frank.Che@sun.com To: James.McPherson@sun.com Cc: PSARC-ext@sun.com, yan xue yang Message-id: <4899CDE0.80308@sun.com> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=UTF-8 Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <48995E2E.8020801@sun.com> <48998888.5060707@Sun.COM> User-Agent: Thunderbird 2.0.0.16 (Windows/20080708) Status: RO Content-Length: 4147 James C. McPherson Wrote: > How often will the database be updated? When a new driver is added to the IPS or a driver in the IPS is updated to support more devices, the driver database should be updated. If the IPS could support searching drivers by PCI device ID, then this update is not necessary. Contents on third party drivers in the database is updated quarterly depends on whether there are new drivers or driver updates on IHV websites and OpenSolaris community. > Who is responsible for updating the database? > Who is responsible for ensuring that the information > in the database is accurate? This should be the project team's responsibility. > > >> 4.1.2.3 User interface. >> Consider the target user of this tool are most likely don't have >> much >> knowledge of Solaris system administration, only graphical user >> interface >> is available, written in Python. The user reads device >> information from >> this informative GUI, instruct Device Driver Utility to download and >> install missing driver(s) automatically through a few simple >> mouse-click, >> submit hardware information to OpenSolaris HCL using this GUI. > > What if the driver is for a network device, and the > system has no other network interface installed? > What information will be provided to the user so that > they can get the driver via other means? > > In case a third party driver exists, the URL for that driver will be provided on the GUI. > >> 4.1.2.4 Core engine. >> This component stays in the center of Device Driver Utility. It >> completes >> the following fundamental operations: >> (1) Get device information from device information fetcher. If there >> is device >> that missing driver in current OpenSolaris OS, then look up Solaris >> driver >> database for the driver name. Pass all these information to GUI for >> display. >> (2) Check IPS for driver availability through pkg(1M) command. Search >> for >> package on IPS that contains needed driver based on driver name. >> Download and >> install certain driver package(s) according to user's instruction. >> (3) Read hardware-related information from SMBIOS as much as >> possible, then >> automatically fill in to OpenSolaris HCL submission table, ask the >> user to >> provide other necessary information, then format all these >> information and pass >> to OpenSolaris HCL server if the user want to do a submission. >> Submission is >> done through HTTPS post method. The user can see what data will be >> transferred >> to Sun before the submission is done. > > I like the sound of this. Will there be just one URL to point both > the database queries and submission towards, or will there be multiple > locations? > Just one URL for submissions. No database queries. > If there are multiple locations, how will the information be collated > for the database, and how will it be propagated to the other locations? > > > How will you handle secure sites? > > >> 4.1.3 Limitations >> There are a few limitations in current plan: >> >> (1) The following functionality depend on network connectivity to Sun >> servers: >> * Check device driver availability via IPS. >> * Dynamically add driver from IPS. >> * Submit system configuration to OpenSolaris HCL. >> >> (2) If the Solaris driver database is not updated in time(for >> example, there is >> driver which can be found in IPS but not in Solaris driver database), >> the >> driver search result may not be correct. However, if IPS enables the >> user to >> search for a driver package through supported vendor ID and device >> ID, this >> limitation will not exist any more. >> > > One final question - is the project team writing this from scratch, > or are they leveraging the work of the existing HCTS tool? > It reads the device tree through the libdevinfo interface to get device and associated driver information, the same method with the HCTS product. In case no driver is attached for a device, it uses the same driver searching algorithm with the Sun Device Detection Tool product. Also, almost the same driver database. Thanks, Frank. From John.Plocher@sun.com Wed Aug 6 09:56:47 2008 Received: from sunmail5.uk.sun.com (sunmail5.UK.Sun.COM [129.156.85.165]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m76Gul2K009235 for ; Wed, 6 Aug 2008 09:56:47 -0700 (PDT) Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74]) by sunmail5.uk.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id m76Guh3t003112 for <@sunmail2sca.sfbay.sun.com:PSARC-ext@sun.com>; Wed, 6 Aug 2008 17:56:46 +0100 (BST) Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0K5600G05V2KL200@nwk-avmta-1.sfbay.Sun.COM> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Wed, 06 Aug 2008 09:56:44 -0700 (PDT) Received: from sca-es-mail-2.sun.com ([192.18.43.133]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0K56008KNV2K4XC0@nwk-avmta-1.sfbay.Sun.COM> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Wed, 06 Aug 2008 09:56:44 -0700 (PDT) Received: from fe-sfbay-10.sun.com ([192.18.43.129]) by sca-es-mail-2.sun.com (8.13.7+Sun/8.12.9) with ESMTP id m76Guiem018243 for ; Wed, 06 Aug 2008 09:56:44 -0700 (PDT) Received: from conversion-daemon.fe-sfbay-10.sun.com by fe-sfbay-10.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) id <0K5600601UV3N200@fe-sfbay-10.sun.com> (original mail from John.Plocher@Sun.COM) for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Wed, 06 Aug 2008 09:56:44 -0700 (PDT) Received: from [192.168.168.4] ([208.74.177.212]) by fe-sfbay-10.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0K56008GCV29V710@fe-sfbay-10.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Wed, 06 Aug 2008 09:56:33 -0700 (PDT) Date: Wed, 06 Aug 2008 09:56:33 -0700 From: John Plocher Subject: Re: PSARC 2008/504 Device Driver Utility In-reply-to: <48999592.4060407@Sun.COM> Sender: John.Plocher@sun.com To: James.McPherson@sun.com Cc: James Carlson , PSARC-ext@sun.com, yan xue yang , Frank Che Message-id: <4899D7C1.6030108@Sun.Com> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <48995E2E.8020801@sun.com> <48998888.5060707@Sun.COM> <18585.37689.612955.983678@gargle.gargle.HOWL> <48999592.4060407@Sun.COM> User-Agent: Thunderbird 2.0.0.14 (Macintosh/20080421) Status: RO Content-Length: 3725 James C. McPherson wrote: > James Carlson wrote: >> James C. McPherson writes: >>> Frank Che wrote: >>>> Requested release binding is patch/micro for OpenSolaris > True, and I consider the "patch/micro" request to be incorrect The final binding is a synthesis of the team's desires and the type of change actually being proposed. The actual changes set the "low bar", the team's desires can only raise it. Patch/Micro seems appropriate based on the actual change; Minor might be more desirable as a way of preventing feature creep in the Update releases. The former is an ARC call, the other is a project team one. -John < ARC Tutorial Warning It is safe to stop reading now :-) > What is a "Release Binding"? In simplistic terms, a project can be thought of as consuming an existing system, applying some changes to it, and producing a new version of the system. The ARC review focuses on those changes; one of the outcomes of the review is a pronouncement about the magnitude and impact of those changes. That pronouncement is called the Release Binding. At any given time, there are several different releases under construction: Solaris10updateX (a patch gate that allows a restricted set of new features), OpenSolaris/Nevada (a Minor release) and (maybe?) OpenSolaris/Indiana (a Major release). The case's release binding is used to steer a project to the appropriate integration gate for a Major release, a Minor one, or a Micro or Patch. An example: Assume the baseline existing system was the "zpool" command. Grunging thru the ARC case archives, we find several cases that describe zpool's Exported Interfaces; in particular, they set expectations as to their future evolutionary stability. Example1: Another zpool project comes in and says they wish to change the meaning of an existing command line option such that it does a completely different thing. Looking at the previous ZFS ARC cases, we find that the interface stability level for that option was Committed. Looking at the Interface Taxonomy, we find, under the heading "Committed": > Incompatible Change major release (X.0) Thus, the release binding would need to be Major. (Committed Interface + Incompatible change = Major binding) This poses a problem today, since we don't *have* any gates chartered for a Major Release. If the project team was expecting Minor or Patch binding, this would be a good time for an ARC discussion about living up to expectations - and setting them correctly in the first place :-) Example 2: A project comes in and proposes to add a new flag to zpool. The change being proposed is a "compatible" change - existing users of the zpool command won't be impacted by this change. What is the release binding? From the Interface Taxonomy, we find: > A compatible addition is normally permitted in a minor > (X.Y) release; adding features in a micro (X.Y.Z) release, > or in patches makes it hard for ISVs to determine when > they can start depending on the existance of a new feature. Thus, the release binding is at most Minor, but *could* be Micro or Patch if sufficient justification were given. (Compatible feature addition = Minor +/- wiggle room) This "justification" or "wiggle room" is where the project team's desires come in, and is why we usually ask them for their binding suggestion. Assume the final binding is "Patch", with the justification that this change is needed in Solaris10UpdateX. This project would be expected to integrate into S10Ux AND OpenSolaris so that there would not be any feature regressions between the two versions. If there also was a Major gate out there, it would go there as well. -John From gdamore@sun.com Wed Aug 6 10:26:52 2008 Received: from sunmail2sca.sfbay.sun.com (sunmail2sca.SFBay.Sun.COM [129.145.155.234]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m76HQqjZ015425 for ; Wed, 6 Aug 2008 10:26:52 -0700 (PDT) Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6]) by sunmail2sca.sfbay.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id m76HQpAM012984 for <@sunmail2sca.sfbay.sun.com:PSARC-ext@sun.com>; Wed, 6 Aug 2008 10:26:51 -0700 (PDT) Received: from pmxchannel-daemon.nwk-avmta-2.sfbay.sun.com by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0K5600G03WGQEE00@nwk-avmta-2.sfbay.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Wed, 06 Aug 2008 10:26:50 -0700 (PDT) Received: from sca-es-mail-1.sun.com ([192.18.43.132]) by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0K5600FVGWGPQ700@nwk-avmta-2.sfbay.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Wed, 06 Aug 2008 10:26:49 -0700 (PDT) Received: from fe-sfbay-10.sun.com ([192.18.43.129]) by sca-es-mail-1.sun.com (8.13.7+Sun/8.12.9) with ESMTP id m76HQnEW015353 for ; Wed, 06 Aug 2008 10:26:49 -0700 (PDT) Received: from conversion-daemon.fe-sfbay-10.sun.com by fe-sfbay-10.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) id <0K5600601W4OSE00@fe-sfbay-10.sun.com> (original mail from gdamore@sun.com) for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Wed, 06 Aug 2008 10:26:49 -0700 (PDT) Received: from [10.7.251.172] by fe-sfbay-10.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0K56008Q1WGOV7H0@fe-sfbay-10.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Wed, 06 Aug 2008 10:26:48 -0700 (PDT) Date: Wed, 06 Aug 2008 10:21:37 -0700 From: "Garrett D'Amore" Subject: Re: PSARC 2008/504 Device Driver Utility In-reply-to: <4899D7C1.6030108@Sun.Com> Sender: Garrett.Damore@sun.com To: John Plocher Cc: James.McPherson@sun.com, James Carlson , PSARC-ext@sun.com, yan xue yang , Frank Che Message-id: <4899DDA1.7090301@sun.com> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <48995E2E.8020801@sun.com> <48998888.5060707@Sun.COM> <18585.37689.612955.983678@gargle.gargle.HOWL> <48999592.4060407@Sun.COM> <4899D7C1.6030108@Sun.Com> User-Agent: Thunderbird 2.0.0.14 (X11/20080616) Status: RO Content-Length: 4634 John Plocher wrote: > James C. McPherson wrote: >> James Carlson wrote: >>> James C. McPherson writes: >>>> Frank Che wrote: >>>>> Requested release binding is patch/micro for OpenSolaris > >> True, and I consider the "patch/micro" request to be incorrect > > The final binding is a synthesis of the team's desires and the > type of change actually being proposed. The actual changes set > the "low bar", the team's desires can only raise it. > > Patch/Micro seems appropriate based on the actual change; > Minor might be more desirable as a way of preventing feature > creep in the Update releases. The former is an ARC call, > the other is a project team one. My only concern here is that IPS itself is not Patch or Micro. So this case doesn't *itself* have a burden that would require a minor release, but it has a dependency that does. I'm happy with Patch or Micro (but not ambiguous "Patch/Micro"), *provided* that we all understand that this doesn't set a precedent where someone could use this case's binding to bring along the dependency with a stricter binding requirement (IPS in this case) as part of a backport -- at least not without coming back to ARC for a change in the binding on the dependency. (Granted, "backporting" IPS seems a bit unlikely to me. My concern is that a precedent might be set for other less "obvious" cases.) -- Garrett > > -John > > < > ARC Tutorial Warning > It is safe to stop reading now :-) > > > > What is a "Release Binding"? > > In simplistic terms, a project can be thought of as consuming > an existing system, applying some changes to it, and producing > a new version of the system. > > The ARC review focuses on those changes; one of the outcomes > of the review is a pronouncement about the magnitude and > impact of those changes. That pronouncement is called the > Release Binding. > > At any given time, there are several different releases under > construction: > Solaris10updateX (a patch gate that allows a restricted > set of new features), > OpenSolaris/Nevada (a Minor release) and > (maybe?) OpenSolaris/Indiana (a Major release). > > The case's release binding is used to steer a project to > the appropriate integration gate for a Major release, a > Minor one, or a Micro or Patch. > > An example: > > Assume the baseline existing system was the "zpool" command. > Grunging thru the ARC case archives, we find several cases > that describe zpool's Exported Interfaces; in particular, > they set expectations as to their future evolutionary stability. > > Example1: > Another zpool project comes in and says they wish to change > the meaning of an existing command line option such that it > does a completely different thing. Looking at the previous > ZFS ARC cases, we find that the interface stability level > for that option was Committed. Looking at the Interface > Taxonomy, we find, under the heading "Committed": > >> Incompatible Change major release (X.0) > > Thus, the release binding would need to be Major. > (Committed Interface + Incompatible change = Major binding) > This poses a problem today, since we don't *have* any gates > chartered for a Major Release. > > If the project team was expecting Minor or Patch binding, > this would be a good time for an ARC discussion about > living up to expectations - and setting them correctly in > the first place :-) > > > Example 2: > A project comes in and proposes to add a new flag to zpool. > The change being proposed is a "compatible" change - existing > users of the zpool command won't be impacted by this change. > What is the release binding? From the Interface Taxonomy, > we find: > >> A compatible addition is normally permitted in a minor (X.Y) release; >> adding features in a micro (X.Y.Z) release, or in patches makes it >> hard for ISVs to determine when they can start depending on the >> existance of a new feature. > > Thus, the release binding is at most Minor, but *could* be > Micro or Patch if sufficient justification were given. > (Compatible feature addition = Minor +/- wiggle room) > > This "justification" or "wiggle room" is where the project > team's desires come in, and is why we usually ask them for > their binding suggestion. > > Assume the final binding is "Patch", with the justification > that this change is needed in Solaris10UpdateX. This > project would be expected to integrate into S10Ux AND > OpenSolaris so that there would not be any feature > regressions between the two versions. If there also > was a Major gate out there, it would go there as well. > > -John > > > > > > > > From John.Plocher@sun.com Wed Aug 6 10:31:28 2008 Received: from sunmail3mpk.sfbay.sun.com (sunmail3mpk.SFBay.Sun.COM [129.146.11.52]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m76HVSrX015597 for ; Wed, 6 Aug 2008 10:31:28 -0700 (PDT) Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74]) by sunmail3mpk.sfbay.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id m76HVQ58027962 for <@sunmail2sca.sfbay.sun.com:PSARC-ext@sun.com>; Wed, 6 Aug 2008 10:31:28 -0700 (PDT) Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0K5600K0DWOF3Q00@nwk-avmta-1.sfbay.Sun.COM> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Wed, 06 Aug 2008 10:31:27 -0700 (PDT) Received: from sca-es-mail-1.sun.com ([192.18.43.132]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0K5600H46WOEX010@nwk-avmta-1.sfbay.Sun.COM> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Wed, 06 Aug 2008 10:31:26 -0700 (PDT) Received: from fe-sfbay-10.sun.com ([192.18.43.129]) by sca-es-mail-1.sun.com (8.13.7+Sun/8.12.9) with ESMTP id m76HVQmf016048 for ; Wed, 06 Aug 2008 10:31:26 -0700 (PDT) Received: from conversion-daemon.fe-sfbay-10.sun.com by fe-sfbay-10.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) id <0K5600I01WINOB00@fe-sfbay-10.sun.com> (original mail from John.Plocher@Sun.COM) for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Wed, 06 Aug 2008 10:31:26 -0700 (PDT) Received: from [192.168.168.4] ([208.74.177.212]) by fe-sfbay-10.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0K5600HDZWO8KJ20@fe-sfbay-10.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Wed, 06 Aug 2008 10:31:21 -0700 (PDT) Date: Wed, 06 Aug 2008 10:31:20 -0700 From: John Plocher Subject: Re: PSARC 2008/504 Device Driver Utility In-reply-to: <4899DDA1.7090301@sun.com> Sender: John.Plocher@sun.com To: "Garrett D'Amore" Cc: James.McPherson@sun.com, James Carlson , PSARC-ext@sun.com, yan xue yang , Frank Che Message-id: <4899DFE8.5080504@Sun.Com> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <48995E2E.8020801@sun.com> <48998888.5060707@Sun.COM> <18585.37689.612955.983678@gargle.gargle.HOWL> <48999592.4060407@Sun.COM> <4899D7C1.6030108@Sun.Com> <4899DDA1.7090301@sun.com> User-Agent: Thunderbird 2.0.0.14 (Macintosh/20080421) Status: RO Content-Length: 420 Garrett D'Amore wrote: > *provided* that we all understand that this doesn't set a precedent > where someone could use this case's binding to bring along the > dependency with a stricter binding requirement I believe that such a presumption is at the heart of the whole binding/dependency scheme. If you have Patch, and depend on me, but I only have Minor, then QED - you can only *do* Minor. Duh! :-) -John From carlsonj@phorcys.east.sun.com Wed Aug 6 10:38:29 2008 Received: from newsunmail1brm.central.sun.com (newsunmail1brm.Central.Sun.COM [129.147.62.245]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m76HcTA8016874 for ; Wed, 6 Aug 2008 10:38:29 -0700 (PDT) Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74]) by newsunmail1brm.central.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id m76HcMlS006808; Wed, 6 Aug 2008 11:38:23 -0600 (MDT) Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0K5600K03WZZVL00@nwk-avmta-1.sfbay.Sun.COM>; Wed, 06 Aug 2008 10:38:23 -0700 (PDT) Received: from phorcys.east.sun.com ([129.148.174.143]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0K5600H6RWZYXB10@nwk-avmta-1.sfbay.Sun.COM>; Wed, 06 Aug 2008 10:38:23 -0700 (PDT) Received: from phorcys.east.sun.com (localhost [127.0.0.1]) by phorcys.east.sun.com (8.14.3+Sun/8.14.3) with ESMTP id m76HcM33009653; Wed, 06 Aug 2008 13:38:22 -0400 (EDT) Received: (from carlsonj@localhost) by phorcys.east.sun.com (8.14.3+Sun/8.14.3/Submit) id m76HcMR1009650; Wed, 06 Aug 2008 13:38:22 -0400 (EDT) Date: Wed, 06 Aug 2008 13:38:22 -0400 From: James Carlson Subject: Re: PSARC 2008/504 Device Driver Utility In-reply-to: <4899DFE8.5080504@Sun.Com> To: John Plocher Cc: "Garrett D'Amore" , James.McPherson@sun.com, PSARC-ext@sun.com, yan xue yang , Frank Che Message-id: <18585.57742.173878.679172@gargle.gargle.HOWL> MIME-version: 1.0 X-Mailer: VM 7.01 under Emacs 21.3.1 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <48995E2E.8020801@sun.com> <48998888.5060707@Sun.COM> <18585.37689.612955.983678@gargle.gargle.HOWL> <48999592.4060407@Sun.COM> <4899D7C1.6030108@Sun.Com> <4899DDA1.7090301@sun.com> <4899DFE8.5080504@Sun.Com> Status: RO Content-Length: 1400 John Plocher writes: > Garrett D'Amore wrote: > > *provided* that we all understand that this doesn't set a precedent > > where someone could use this case's binding to bring along the > > dependency with a stricter binding requirement > > I believe that such a presumption is at the heart of the whole > binding/dependency scheme. If you have Patch, and depend on me, > but I only have Minor, then QED - you can only *do* Minor. > > Duh! :-) Another way to look at it is this: if we forced every project with one or more dependencies to write its binding in terms of the most-restrictive of the bindings of those dependencies (recursively, of course), then we'd end up with a mess any time a project needed to change its release binding -- we'd have to track down all of the dependent projects and determine whether this dependency was the limiting factor in its binding. That's silly. Instead, we write release bindings that apply to the project at hand. Dependencies are restrictions in addition to and quite apart from that. In other words, it's a boolean AND relationship (need this kind of release AND these dependencies satisfied) and not an OR relationship. -- James Carlson, Solaris Networking Sun Microsystems / 35 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677 From gdamore@sun.com Wed Aug 6 10:41:08 2008 Received: from sunmail4.singapore.sun.com (sunmail4.Singapore.Sun.COM [129.158.71.19]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m76Hf7u3017522 for ; Wed, 6 Aug 2008 10:41:07 -0700 (PDT) Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74]) by sunmail4.singapore.sun.com (8.13.4+Sun/8.13.3/ENSMAIL,v2.2) with ESMTP id m76Hf2fe004610 for <@sunmail2sca.sfbay.sun.com:PSARC-ext@sun.com>; Thu, 7 Aug 2008 01:41:06 +0800 (SGT) Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0K5600L09X4G6R00@nwk-avmta-1.sfbay.Sun.COM> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Wed, 06 Aug 2008 10:41:04 -0700 (PDT) Received: from sca-es-mail-1.sun.com ([192.18.43.132]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0K5600HY6X4GX910@nwk-avmta-1.sfbay.Sun.COM> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Wed, 06 Aug 2008 10:41:04 -0700 (PDT) Received: from fe-sfbay-09.sun.com ([192.18.43.129]) by sca-es-mail-1.sun.com (8.13.7+Sun/8.12.9) with ESMTP id m76Hf4eM017413 for ; Wed, 06 Aug 2008 10:41:04 -0700 (PDT) Received: from conversion-daemon.fe-sfbay-09.sun.com by fe-sfbay-09.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) id <0K5600C01WFK8U00@fe-sfbay-09.sun.com> (original mail from gdamore@sun.com) for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Wed, 06 Aug 2008 10:41:04 -0700 (PDT) Received: from [10.7.251.172] by fe-sfbay-09.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0K560039IX45LVA0@fe-sfbay-09.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Wed, 06 Aug 2008 10:40:54 -0700 (PDT) Date: Wed, 06 Aug 2008 10:35:43 -0700 From: "Garrett D'Amore" Subject: Re: PSARC 2008/504 Device Driver Utility In-reply-to: <18585.57742.173878.679172@gargle.gargle.HOWL> Sender: Garrett.Damore@sun.com To: James Carlson Cc: John Plocher , James.McPherson@sun.com, PSARC-ext@sun.com, yan xue yang , Frank Che Message-id: <4899E0EF.4010507@sun.com> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <48995E2E.8020801@sun.com> <48998888.5060707@Sun.COM> <18585.37689.612955.983678@gargle.gargle.HOWL> <48999592.4060407@Sun.COM> <4899D7C1.6030108@Sun.Com> <4899DDA1.7090301@sun.com> <4899DFE8.5080504@Sun.Com> <18585.57742.173878.679172@gargle.gargle.HOWL> User-Agent: Thunderbird 2.0.0.14 (X11/20080616) Status: RO Content-Length: 1647 James Carlson wrote: > John Plocher writes: > >> Garrett D'Amore wrote: >> >>> *provided* that we all understand that this doesn't set a precedent >>> where someone could use this case's binding to bring along the >>> dependency with a stricter binding requirement >>> >> I believe that such a presumption is at the heart of the whole >> binding/dependency scheme. If you have Patch, and depend on me, >> but I only have Minor, then QED - you can only *do* Minor. >> >> Duh! :-) >> > > Another way to look at it is this: if we forced every project with one > or more dependencies to write its binding in terms of the > most-restrictive of the bindings of those dependencies (recursively, > of course), then we'd end up with a mess any time a project needed to > change its release binding -- we'd have to track down all of the > dependent projects and determine whether this dependency was the > limiting factor in its binding. > > That's silly. Instead, we write release bindings that apply to the > project at hand. Dependencies are restrictions in addition to and > quite apart from that. > > In other words, it's a boolean AND relationship (need this kind of > release AND these dependencies satisfied) and not an OR relationship. > Agreed. This is just the first case I've personally seen where the dependency and dependee had this sort of relationship. The rules being discussed all make sense to me, it just wasn't clear to me that everyone else understood them that way. I still think the project team needs to pick either Patch or Micro. My guess is Patch is probably what is desired. - Garrett From John.Plocher@sun.com Wed Aug 6 10:47:39 2008 Received: from sunmail5.uk.sun.com (sunmail5.UK.Sun.COM [129.156.85.165]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m76Hlclo017797 for ; Wed, 6 Aug 2008 10:47:39 -0700 (PDT) Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6]) by sunmail5.uk.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id m76HlW1N025555 for <@sunmail2sca.sfbay.sun.com:PSARC-ext@sun.com>; Wed, 6 Aug 2008 18:47:37 +0100 (BST) Received: from pmxchannel-daemon.nwk-avmta-2.sfbay.sun.com by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0K5600H03XFDA900@nwk-avmta-2.sfbay.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Wed, 06 Aug 2008 10:47:37 -0700 (PDT) Received: from sca-es-mail-2.sun.com ([192.18.43.133]) by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0K5600F34XFCQJ20@nwk-avmta-2.sfbay.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Wed, 06 Aug 2008 10:47:36 -0700 (PDT) Received: from fe-sfbay-09.sun.com ([192.18.43.129]) by sca-es-mail-2.sun.com (8.13.7+Sun/8.12.9) with ESMTP id m76Hlas6025147 for ; Wed, 06 Aug 2008 10:47:36 -0700 (PDT) Received: from conversion-daemon.fe-sfbay-09.sun.com by fe-sfbay-09.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) id <0K5600H01X5QEV00@fe-sfbay-09.sun.com> (original mail from John.Plocher@Sun.COM) for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Wed, 06 Aug 2008 10:47:36 -0700 (PDT) Received: from [192.168.168.4] ([208.74.177.212]) by fe-sfbay-09.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0K56003KHXFCLVD0@fe-sfbay-09.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Wed, 06 Aug 2008 10:47:36 -0700 (PDT) Date: Wed, 06 Aug 2008 10:47:36 -0700 From: John Plocher Subject: Release Binding digression... (was Re: PSARC 2008/504 Device Driver Utility) In-reply-to: <4899E0EF.4010507@sun.com> Sender: John.Plocher@sun.com To: "Garrett D'Amore" Cc: James Carlson , James.McPherson@sun.com, PSARC-ext@sun.com Reply-to: /dev/null@sun.com Message-id: <4899E3B8.3040608@Sun.Com> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <48995E2E.8020801@sun.com> <48998888.5060707@Sun.COM> <18585.37689.612955.983678@gargle.gargle.HOWL> <48999592.4060407@Sun.COM> <4899D7C1.6030108@Sun.Com> <4899DDA1.7090301@sun.com> <4899DFE8.5080504@Sun.Com> <18585.57742.173878.679172@gargle.gargle.HOWL> <4899E0EF.4010507@sun.com> User-Agent: Thunderbird 2.0.0.14 (Macintosh/20080421) Status: RO Content-Length: 617 [Let's drop this thread - it has almost nothing to do with the case in the Subject line anymore...] Garrett D'Amore wrote: > I still think the project team needs to pick either Patch or Micro. From where I sit, the difference between patch and micro is so thin as to be immaterial - from an ARC perspective. Certainly, there are operational differences between the two, but architecturally, I've been doing this gig for over a decade and I *still* can't nail down any concrete differences between them :-) I'd be just as happy if "Patch" simply went away. With IPS and the repos, it probably will. -John From bpytlik@sun.com Wed Aug 6 16:55:16 2008 Received: from sunmail5.uk.sun.com (sunmail5.UK.Sun.COM [129.156.85.165]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m76NtFvB000579 for ; Wed, 6 Aug 2008 16:55:16 -0700 (PDT) Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74]) by sunmail5.uk.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id m76Nst2n020697 for <@sunmail2sca.sfbay.sun.com:PSARC-ext@sun.com>; Thu, 7 Aug 2008 00:55:14 +0100 (BST) Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0K5700G13EG0ME00@nwk-avmta-1.sfbay.Sun.COM> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Wed, 06 Aug 2008 16:55:12 -0700 (PDT) Received: from sca-es-mail-2.sun.com ([192.18.43.133]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0K5700404EFXYE70@nwk-avmta-1.sfbay.Sun.COM> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Wed, 06 Aug 2008 16:55:09 -0700 (PDT) Received: from fe-sfbay-10.sun.com ([192.18.43.129]) by sca-es-mail-2.sun.com (8.13.7+Sun/8.12.9) with ESMTP id m76Nt9YD005164 for ; Wed, 06 Aug 2008 16:55:09 -0700 (PDT) Received: from conversion-daemon.fe-sfbay-10.sun.com by fe-sfbay-10.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) id <0K5700101EBA6S00@fe-sfbay-10.sun.com> (original mail from bpytlik@sun.com) for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Wed, 06 Aug 2008 16:55:09 -0700 (PDT) Received: from [129.146.228.21] by fe-sfbay-10.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0K5700LMJEFUJTE0@fe-sfbay-10.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Wed, 06 Aug 2008 16:55:06 -0700 (PDT) Date: Wed, 06 Aug 2008 16:55:06 -0700 From: Brock Pytlik Subject: Re: PSARC 2008/504 Device Driver Utility In-reply-to: <4899CDE0.80308@sun.com> Sender: Brock.Pytlik@sun.com To: frank Che Cc: James.McPherson@sun.com, PSARC-ext@sun.com, yan xue yang Message-id: <489A39DA.30702@sun.com> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=UTF-8 Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <48995E2E.8020801@sun.com> <48998888.5060707@Sun.COM> <4899CDE0.80308@sun.com> User-Agent: Thunderbird 2.0.0.14 (X11/20080630) Status: RO Content-Length: 730 frank Che wrote: > James C. McPherson Wrote: >> How often will the database be updated? > When a new driver is added to the IPS or a driver in the IPS is > updated to support more devices, the driver database should be > updated. If the IPS could support searching drivers by PCI device ID, > then this update is not necessary. > > Contents on third party drivers in the database is updated quarterly > depends on whether there are new drivers or driver updates on IHV > websites and OpenSolaris community. > I'm currently working on IPS search. Could you describe a bit about what information you need to be able to search for from IPS? It's possible that we might be able to meet your needs on this front. Thanks, Brock From danek.duvall@sun.com Thu Aug 7 02:39:34 2008 Received: from sunmail4.singapore.sun.com (sunmail4.Singapore.Sun.COM [129.158.71.19]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m779dX9H018431 for ; Thu, 7 Aug 2008 02:39:33 -0700 (PDT) Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74]) by sunmail4.singapore.sun.com (8.13.4+Sun/8.13.3/ENSMAIL,v2.2) with ESMTP id m779dKbY020456; Thu, 7 Aug 2008 17:39:30 +0800 (SGT) Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0K5800E2J5HR5Z00@nwk-avmta-1.sfbay.Sun.COM>; Thu, 07 Aug 2008 02:39:27 -0700 (PDT) Received: from dm-sfbay-02.sfbay.sun.com ([129.146.11.31]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0K58000505HPAP90@nwk-avmta-1.sfbay.Sun.COM>; Thu, 07 Aug 2008 02:39:25 -0700 (PDT) Received: from zruty.sfbay.sun.com (zruty.SFBay.Sun.COM [129.146.168.40]) by dm-sfbay-02.sfbay.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id m779dMx1017817; Thu, 07 Aug 2008 02:39:22 -0700 (PDT) Received: from zruty.sfbay.sun.com (localhost [127.0.0.1]) by zruty.sfbay.sun.com (8.14.2+Sun/8.14.2) with ESMTP id m779dMda010681; Thu, 07 Aug 2008 02:39:22 -0700 (PDT) Received: (from dduvall@localhost) by zruty.sfbay.sun.com (8.14.2+Sun/8.14.2/Submit) id m779dM2J010680; Thu, 07 Aug 2008 02:39:22 -0700 (PDT) Date: Thu, 07 Aug 2008 02:39:21 -0700 From: Danek Duvall Subject: Re: PSARC 2008/504 Device Driver Utility In-reply-to: <489A39DA.30702@sun.com> To: Brock Pytlik Cc: frank Che , PSARC-ext@sun.com, yan xue yang Message-id: <20080807093921.GD9710@zruty.sfbay.sun.com> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT Content-disposition: inline X-PMX-Version: 5.4.1.325704 References: <48995E2E.8020801@sun.com> <48998888.5060707@Sun.COM> <4899CDE0.80308@sun.com> <489A39DA.30702@sun.com> User-Agent: Mutt/1.5.16 (2007-06-27) Status: RO Content-Length: 1178 On Wed, Aug 06, 2008 at 04:55:06PM -0700, Brock Pytlik wrote: > frank Che wrote: > > James C. McPherson Wrote: > >> How often will the database be updated? > > When a new driver is added to the IPS or a driver in the IPS is > > updated to support more devices, the driver database should be > > updated. If the IPS could support searching drivers by PCI device ID, > > then this update is not necessary. > > > > Contents on third party drivers in the database is updated quarterly > > depends on whether there are new drivers or driver updates on IHV > > websites and OpenSolaris community. > > > I'm currently working on IPS search. Could you describe a bit about what > information you need to be able to search for from IPS? It's possible > that we might be able to meet your needs on this front. IPS can already search on a driver action's aliases: % pkg search pci108e,1648 INDEX ACTION VALUE PACKAGE driver_aliases driver bge pkg:/SUNWbge@0.5.11-0.93 The ddu may need to iterate over all the values in a device's "compatible" property in order to find an explicitly registered alias, but that's not too complicated. Danek From Frank.Che@sun.com Thu Aug 7 07:42:29 2008 Received: from sunmail2sca.sfbay.sun.com (sunmail2sca.SFBay.Sun.COM [129.145.155.234]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m77EgTxj024150 for ; Thu, 7 Aug 2008 07:42:29 -0700 (PDT) Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74]) by sunmail2sca.sfbay.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id m77EgSeO019616; Thu, 7 Aug 2008 07:42:28 -0700 (PDT) Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0K5800111JIS5M00@nwk-avmta-1.sfbay.Sun.COM>; Thu, 07 Aug 2008 07:42:28 -0700 (PDT) Received: from sineb-mail-1.sun.com ([192.18.19.6]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0K5800J1SJIQKS80@nwk-avmta-1.sfbay.Sun.COM>; Thu, 07 Aug 2008 07:42:27 -0700 (PDT) Received: from fe-apac-05.sun.com (fe-apac-05.sun.com [192.18.19.176] (may be forged)) by sineb-mail-1.sun.com (8.13.6+Sun/8.12.9) with ESMTP id m77EgQft015656; Thu, 07 Aug 2008 14:42:26 +0000 (GMT) Received: from conversion-daemon.mail-apac.sun.com by mail-apac.sun.com (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) id <0K5800301JI8DM00@mail-apac.sun.com> (original mail from Frank.Che@Sun.COM) ; Thu, 07 Aug 2008 22:42:25 +0800 (SGT) Received: from [129.150.144.20] by mail-apac.sun.com (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) with ESMTPSA id <0K58003YDJINJPA3@mail-apac.sun.com>; Thu, 07 Aug 2008 22:42:25 +0800 (SGT) Date: Thu, 07 Aug 2008 22:42:25 +0800 From: frank Che Subject: Re: PSARC 2008/504 Device Driver Utility In-reply-to: <20080807093921.GD9710@zruty.sfbay.sun.com> Sender: Frank.Che@sun.com To: Danek Duvall Cc: Brock Pytlik , PSARC-ext@sun.com, yan xue yang Message-id: <489B09D1.1080707@sun.com> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <48995E2E.8020801@sun.com> <48998888.5060707@Sun.COM> <4899CDE0.80308@sun.com> <489A39DA.30702@sun.com> <20080807093921.GD9710@zruty.sfbay.sun.com> User-Agent: Thunderbird 2.0.0.16 (Windows/20080708) Status: RO Content-Length: 1518 Danek Duvall Wrote: > On Wed, Aug 06, 2008 at 04:55:06PM -0700, Brock Pytlik wrote: > > >> frank Che wrote: >> >>> James C. McPherson Wrote: >>> >>>> How often will the database be updated? >>>> >>> When a new driver is added to the IPS or a driver in the IPS is >>> updated to support more devices, the driver database should be >>> updated. If the IPS could support searching drivers by PCI device ID, >>> then this update is not necessary. >>> >>> Contents on third party drivers in the database is updated quarterly >>> depends on whether there are new drivers or driver updates on IHV >>> websites and OpenSolaris community. >>> >>> >> I'm currently working on IPS search. Could you describe a bit about what >> information you need to be able to search for from IPS? It's possible >> that we might be able to meet your needs on this front. >> > > IPS can already search on a driver action's aliases: > > % pkg search pci108e,1648 > INDEX ACTION VALUE PACKAGE > driver_aliases driver bge pkg:/SUNWbge@0.5.11-0.93 > > The ddu may need to iterate over all the values in a device's "compatible" > property in order to find an explicitly registered alias, but that's not > too complicated. > > Danek > I will ask the project team to try this solution and see whether it meets their requirement. Before the project team get back with the investigation result, I will mark the status of this project as 'waiting need spec'. Frank. From Frank.Che@sun.com Fri Aug 15 00:06:07 2008 Received: from sunmail5.uk.sun.com (sunmail5.UK.Sun.COM [129.156.85.165]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m7F766vK025731 for ; Fri, 15 Aug 2008 00:06:07 -0700 (PDT) Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6]) by sunmail5.uk.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id m7F75lU9008739 for <@sunmail2sca.sfbay.sun.com:PSARC-ext@sun.com>; Fri, 15 Aug 2008 08:06:05 +0100 (BST) Received: from pmxchannel-daemon.nwk-avmta-2.sfbay.sun.com by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0K5M00J0VRQ4XC00@nwk-avmta-2.sfbay.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Fri, 15 Aug 2008 00:06:05 -0700 (PDT) Received: from sineb-mail-2.sun.com ([192.18.19.7]) by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0K5M00JP2RQ3PP00@nwk-avmta-2.sfbay.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Fri, 15 Aug 2008 00:06:04 -0700 (PDT) Received: from fe-apac-06.sun.com (fe-apac-06.sun.com [192.18.19.177] (may be forged)) by sineb-mail-2.sun.com (8.13.6+Sun/8.12.9) with ESMTP id m7F763ZL019092 for ; Fri, 15 Aug 2008 07:06:03 +0000 (GMT) Received: from conversion-daemon.mail-apac.sun.com by mail-apac.sun.com (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) id <0K5M00001RLPOR00@mail-apac.sun.com> (original mail from Frank.Che@Sun.COM) for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Fri, 15 Aug 2008 15:06:03 +0800 (SGT) Received: from [129.150.144.11] by mail-apac.sun.com (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) with ESMTPSA id <0K5M00BM2RQ2RESR@mail-apac.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Fri, 15 Aug 2008 15:06:03 +0800 (SGT) Date: Fri, 15 Aug 2008 15:06:04 +0800 From: frank Che Subject: PSARC 2008/504 Device Driver Utility Sender: Frank.Che@sun.com To: PSARC-ext@sun.com Cc: Yan Xue Yang Message-id: <48A52ADC.1080600@sun.com> MIME-version: 1.0 Content-type: text/plain; charset=GB2312 Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 User-Agent: Thunderbird 2.0.0.16 (Windows/20080708) Status: RO Content-Length: 604 The case material was updated and saved as 'spec.txt' in the case directory. I'd like to restart the review and set the timer to 08/21/2008. A summary of the updates in the material: 1. After offline communication, the project team would like to use the interface provided by the IPS to search for drivers and packages by PCI IDs. So content on drivers provided by Solaris OS is removed from the driver database. Now the driver database only contains information on third party drivers and OpenSolaris community drivers. 2. Requested release binding was changed from 'patch/micro' to 'micro'. Frank. From gww@eng.sun.com Fri Aug 15 08:06:49 2008 Received: from sunmail4.singapore.sun.com (sunmail4.Singapore.Sun.COM [129.158.71.19]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m7FF6mmN006314 for ; Fri, 15 Aug 2008 08:06:48 -0700 (PDT) Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74]) by sunmail4.singapore.sun.com (8.13.4+Sun/8.13.3/ENSMAIL,v2.2) with ESMTP id m7FF6fSQ002496 for <@sunmail2sca.sfbay.sun.com:PSARC-ext@sun.com>; Fri, 15 Aug 2008 23:06:47 +0800 (SGT) Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0K5N00G05DZ87V00@nwk-avmta-1.sfbay.Sun.COM> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Fri, 15 Aug 2008 08:06:44 -0700 (PDT) Received: from dm-eng-02.sfbay.sun.com ([129.146.11.32]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0K5N00GWXDZ70N00@nwk-avmta-1.sfbay.Sun.COM> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Fri, 15 Aug 2008 08:06:43 -0700 (PDT) Received: from marduk.eng.sun.com (marduk.SFBay.Sun.COM [129.146.108.224]) by dm-eng-02.sfbay.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id m7FF6efM047192; Fri, 15 Aug 2008 08:06:40 -0700 (PDT) Received: from marduk.eng.sun.com (localhost [127.0.0.1]) by marduk.eng.sun.com (8.13.6+Sun/8.12.11) with ESMTP id m7FF3DR8012135; Fri, 15 Aug 2008 08:03:13 -0700 (PDT) Received: (from gww@localhost) by marduk.eng.sun.com (8.13.6+Sun/8.12.11/Submit) id m7FF3DwI012134; Fri, 15 Aug 2008 08:03:13 -0700 (PDT) Date: Fri, 15 Aug 2008 08:03:13 -0700 (PDT) From: Gary Winiger Subject: Re: PSARC 2008/504 Device Driver Utility To: PSARC-ext@sun.com, Frank.Che@sun.com Cc: Xue-Yang.Yan@sun.com Message-id: <200808151503.m7FF3DwI012134@marduk.eng.sun.com> Content-transfer-encoding: 7BIT X-Sun-Charset: US-ASCII X-PMX-Version: 5.4.1.325704 Status: RO Content-Length: 746 > A summary of the updates in the material: > > 1. After offline communication, the project team would like to use the > interface provided by the IPS to search for drivers and packages by PCI > IDs. So content on drivers provided by Solaris OS is removed from the > driver database. Now the driver database only contains information on > third party drivers and OpenSolaris community drivers. Is a case dependency on 2008/190 pkg(5): image packaging system being proposed? > 2. Requested release binding was changed from 'patch/micro' to 'micro'. In practical terms what does this change mean? If 1 is true, wouldn't this case align with 2008/190? I don't recall seeing a Release Binding there, and I'm guessing it is Minor. Gary.. From Frank.Che@Sun.COM Fri Aug 15 08:34:29 2008 Received: from newsunmail1brm.central.sun.com (newsunmail1brm.Central.Sun.COM [129.147.62.245]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m7FFYTDN006844 for ; Fri, 15 Aug 2008 08:34:29 -0700 (PDT) Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11]) by newsunmail1brm.central.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id m7FFYTON047458 for <@sunmail2sca.sfbay.sun.com:psarc-ext@sun.com>; Fri, 15 Aug 2008 09:34:29 -0600 (MDT) Received: from pmxchannel-daemon.brm-avmta-1.central.sun.com by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0K5N00501F9G1L00@brm-avmta-1.central.sun.com> for psarc-ext@sun.com (ORCPT psarc-ext@Sun.COM); Fri, 15 Aug 2008 09:34:28 -0600 (MDT) Received: from sineb-mail-1.sun.com ([192.18.19.6]) by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0K5N00LX0F9F3O50@brm-avmta-1.central.sun.com> for psarc-ext@sun.com (ORCPT psarc-ext@Sun.COM); Fri, 15 Aug 2008 09:34:28 -0600 (MDT) Received: from fe-apac-06.sun.com (fe-apac-06.sun.com [192.18.19.177] (may be forged)) by sineb-mail-1.sun.com (8.13.6+Sun/8.12.9) with ESMTP id m7FFYQcY004071 for ; Fri, 15 Aug 2008 15:34:26 +0000 (GMT) Received: from conversion-daemon.mail-apac.sun.com by mail-apac.sun.com (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) id <0K5N00B01F259T00@mail-apac.sun.com> (original mail from Frank.Che@Sun.COM) for psarc-ext@Sun.COM (ORCPT psarc-ext@Sun.COM); Fri, 15 Aug 2008 23:34:26 +0800 (SGT) Received: from [123.112.47.16] by mail-apac.sun.com (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) with ESMTPSA id <0K5N00BQEF9BRG07@mail-apac.sun.com>; Fri, 15 Aug 2008 23:34:26 +0800 (SGT) Date: Fri, 15 Aug 2008 23:34:18 +0800 From: frank Che Subject: Re: PSARC 2008/504 Device Driver Utility In-reply-to: <200808151503.m7FF3DwI012134@marduk.eng.sun.com> Sender: Frank.Che@Sun.COM To: Gary Winiger Cc: psarc-ext@Sun.COM, Xue-Yang.Yan@Sun.COM Message-id: <48A5A1FA.4090404@sun.com> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <200808151503.m7FF3DwI012134@marduk.eng.sun.com> User-Agent: Thunderbird 2.0.0.16 (Windows/20080708) Status: RO Content-Length: 1062 Gary Winiger Wrote: >> A summary of the updates in the material: >> >> 1. After offline communication, the project team would like to use the >> interface provided by the IPS to search for drivers and packages by PCI >> IDs. So content on drivers provided by Solaris OS is removed from the >> driver database. Now the driver database only contains information on >> third party drivers and OpenSolaris community drivers. >> > > Is a case dependency on 2008/190 pkg(5): image packaging system > being proposed? > What does it mean, how to do that? do we have documents to explain this? > >> 2. Requested release binding was changed from 'patch/micro' to 'micro'. >> > > In practical terms what does this change mean? If 1 is true, > wouldn't this case align with 2008/190? I don't recall seeing > a Release Binding there, and I'm guessing it is Minor. > > > There are quite some mail discussion on this issue and John initiated a new thread for it. In the last several mails, the suggestion is to use either patch or micro. Frank. From Frank.Che@sun.com Thu Aug 21 18:17:27 2008 Received: from sunmail5.uk.sun.com (sunmail5.UK.Sun.COM [129.156.85.165]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m7M1HQsj012036 for ; Thu, 21 Aug 2008 18:17:27 -0700 (PDT) Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74]) by sunmail5.uk.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id m7M1HLah012396 for <@sunmail2sca.sfbay.sun.com:psarc-ext@sun.com>; Fri, 22 Aug 2008 02:17:25 +0100 (BST) Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0K5Z00103A90GO00@nwk-avmta-1.sfbay.Sun.COM> for psarc-ext@sun.com (ORCPT psarc-ext@Sun.COM); Thu, 21 Aug 2008 18:17:24 -0700 (PDT) Received: from sineb-mail-2.sun.com ([192.18.19.7]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0K5Z00K2RA8YS6F0@nwk-avmta-1.sfbay.Sun.COM> for psarc-ext@sun.com (ORCPT psarc-ext@Sun.COM); Thu, 21 Aug 2008 18:17:23 -0700 (PDT) Received: from fe-apac-05.sun.com (fe-apac-05.sun.com [192.18.19.176] (may be forged)) by sineb-mail-2.sun.com (8.13.6+Sun/8.12.9) with ESMTP id m7M1HMOK008171 for ; Fri, 22 Aug 2008 01:17:22 +0000 (GMT) Received: from conversion-daemon.mail-apac.sun.com by mail-apac.sun.com (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) id <0K5Z00I01A7RAC00@mail-apac.sun.com> (original mail from Frank.Che@Sun.COM) for psarc-ext@Sun.COM (ORCPT psarc-ext@Sun.COM); Fri, 22 Aug 2008 09:17:22 +0800 (SGT) Received: from [129.150.144.39] by mail-apac.sun.com (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) with ESMTPSA id <0K5Z00M70A8U9UL3@mail-apac.sun.com> for psarc-ext@Sun.COM (ORCPT psarc-ext@Sun.COM); Fri, 22 Aug 2008 09:17:22 +0800 (SGT) Date: Fri, 22 Aug 2008 09:17:16 +0800 From: frank Che Subject: Re: PSARC 2008/504 Device Driver Utility In-reply-to: <48A5A1FA.4090404@sun.com> Sender: Frank.Che@sun.com To: psarc-ext@sun.com Cc: Xue-Yang.Yan@sun.com Message-id: <48AE139C.7090103@sun.com> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <200808151503.m7FF3DwI012134@marduk.eng.sun.com> <48A5A1FA.4090404@sun.com> User-Agent: Thunderbird 2.0.0.16 (Windows/20080708) Status: RO Content-Length: 55 This fast track case is approved in the PSARC meeting.