From Thu Jan 8 17:40:29 2009 Date: Thu, 8 Jan 2009 17:40:29 -0800 (PST) From: Postmaster Subject: Message from mail server Content-Length: 96 Mime-Version: 1.0 Status: RO X-IMAP: 1231465229 4 Delete. This is a system message. --END+PSEUDO-- From jw137282@sac.sfbay.sun.com Mon Jan 5 14:09:00 2009 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 n05M8xgx008264 for ; Mon, 5 Jan 2009 14:09:00 -0800 (PST) Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11]) by sunmail4.singapore.sun.com (8.13.4+Sun/8.13.3/ENSMAIL,v2.2) with ESMTP id n05M8vqh028661; Tue, 6 Jan 2009 06:08:58 +0800 (SGT) 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 <0KD000I07QUW2L00@brm-avmta-1.central.sun.com>; Mon, 05 Jan 2009 15:08:56 -0700 (MST) Received: from dm-sfbay-01.sfbay.sun.com ([129.145.155.118]) by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KD000GP2QUWOC10@brm-avmta-1.central.sun.com>; Mon, 05 Jan 2009 15:08:56 -0700 (MST) Received: from sac.sfbay.sun.com (new-sac.SFBay.Sun.COM [129.146.175.65]) by dm-sfbay-01.sfbay.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id n05M8sQn062029; Mon, 05 Jan 2009 14:08:54 -0800 (PST) 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 n05M8rYE008257; Mon, 05 Jan 2009 14:08:53 -0800 (PST) Received: (from jw137282@localhost) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8/Submit) id n05M8rud008253; Mon, 05 Jan 2009 14:08:53 -0800 (PST) Date: Mon, 05 Jan 2009 14:08:53 -0800 (PST) From: James Walker Subject: conflict [PSARC/2009/003 FastTrack timeout 01/12/2009] To: PSARC-ext@sun.com Cc: Zhang.Xiaoping@sun.com Message-id: <200901052208.n05M8rud008253@sac.sfbay.sun.com> Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 Content-Length: 12764 Status: RO X-Status: $$$$ X-UID: 0000000001 I'm sponsoring this case for Xiao Ping, the timeout is set to expire next Monday January 12, 2009. The requested release binding is minor. The man page has been posted in the materials directory. Template Version: @(#)sac_nextcase %I% %G% SMI This information is Copyright 2009 Sun Microsystems 1. Introduction 1.1. Project/Component Working Name: conflict 1.2. Name of Document Author/Supplier: Author: Xiao Ping 1.3 Date of This Document: 05 January, 2009 4. Technical Description Conflict Check List 1.0 Project Information 1.1 Name of project/component conflict 1.2 Author of document zhang.xiaoping@sun.com 2.0 Project Summary 2.1 Project Description conflict displays conflicting filenames in $PATH[1]. Unlike the csh command which(1), it displays all of the (non-alias) executable files in $PATH[1]. Conflict reports pathname conflicts by making a list of the directories which are listed in the environment variable PATH, and then scanning these directories for executable files. If arguments are given to this program, the test for executable files is limited to the given names (after stripping the directory-prefix). conflict 6.0 will be integrated into the SFW consolidation as part of this proposal, and will be installed as SUNWconflict. A minor release binding is being requested. 2.2 Release binding What is is the release binding? (see http://opensolaris.org/os/community/arc/policies/release-taxonomy/) [ ] Major [*] Minor [ ] Patch or Micro [ ] Unknown -- ARC review required 2.3 Type of project Is this case a Linux Familiarity project? [*] Yes [ ] No 2.4 Originating Community 2.4.1 Community Name conflict[1] - Thomas E. Dickey 2.4.2 Community Involvement Indicate Sun's involvement in the community [ ] Maintainer [ ] Contributor [*] Monitoring Will the project team work with the upstream community to resolve architectural issues of interest to Sun? [*] Yes [ ] No - briefly explain Will we or are we forking from the community? [ ] Yes - ARC review required prior to forking [*] No 3.0 Technical Description 3.1 Installation & Sharable 3.1.1S Solaris Installation - section only required for Solaris Software (see http://opensolaris.org/os/community/arc/policies/install-locations/ for details) Does this project follow the Install Locations best practice? [*] Yes [ ] No - ARC review required Does this project install into /usr under [sbin|bin|lib|include|man|share]? [*] Yes [ ] No or N/A Does this project install into /opt? [ ] Yes - explain below [*] No or N/A Does this project install into a different directory structure? [ ] Yes - ARC review required [*] No or N/A Do any of the components of this project conflict with anything under /usr? (see http://opensolaris.org/os/community/arc/caselog/2007/047/ for details) [ ] Yes - explain below [*] No If conflicts exist then will this project install under /usr/gnu? [ ] Yes [ ] No - ARC review required [*] N/A Is this project installing into /usr/sfw? [ ] Yes - ARC review required [*] No 3.1.1W Windows Installation - section only required for Windows Software (see http://sac.sfbay/WSARC/2002/494 for details) Does this project install software into a :\Program Files\Sun\ or :\Sun\ directory? [ ] Yes [ ] No - ARC review required Does the project use the Windows registry? [ ] Yes [ ] No - ARC review required Does the project use HKEY_LOCAL_MACHINE\SOFTWARE\Sun Microsystems\\ for the registry key? [ ] Yes [ ] No - ARC review required Is the project's stored location HKEY_LOCAL_MACHINE\SOFTWARE\Sun Microsystems\\\Path? [ ] Yes [ ] No - ARC review required 3.1.2 Share and Sharable Does the module include any components that are used or shared by other projects? [ ] Yes [*] No If yes are these components packaged to be shared with the other FOSS? [ ] Yes [ ] No - ARC review required [*] N/A Are these components already in the Solaris WOS? [ ] Yes [*] No - continue with next section (section 3.2) If yes are these newer versions being delivered? [ ] Yes [ ] No - ARC review required If yes are the newer versions replacing the existing versions? [ ] Yes [ ] No - ARC review required 3.2 Exported Libraries Are libraries being delivered by this project? [ ] Yes [*] No - continue with next section (section 3.3) Are 64-bit versions of the libraries being delivered? [ ] Yes [ ] No - ARC review required Are static versions of the libraries being delivered? [ ] Yes - ARC review required [ ] No 3.3 Services and the /etc Directory (see http://opensolaris.org/os/community/arc/policies/SMF-policy/) Does the project integrate anything into /etc/init.d or /etc/rc?.d? [ ] Yes - ARC review required [*] No Does the project integrate any new entries into /etc/inittab or /etc/inetd.conf? [ ] Yes - ARC review required [*] No Does the project integrate any private non-public files into /etc/default or /etc/ configuration files? [ ] Yes - ARC review required [*] No Does the service manifests method context grant rights above that of the noaccess user and basic privilege set? [ ] Yes - ARC review required [*] No 3.4 Security 3.4.1 Secure By Default (see http://opensolaris.org/os/community/arc/policies/secure-by-default/ for details) (see http://www.opensolaris.org/os/community/arc/policies/NITS-policy/ for details) (see parts of http://opensolaris.org/os/community/arc/policies/SMF-policy/ for addtional details) Are there any network services provided by this project? [ ] Yes [*] No - continue with the next section (section 3.4.2) Are network services enabled by default? [ ] Yes - ARC review required [ ] No [ ] N/A Are network services automatically enabled by the project during installation? [ ] Yes - ARC review required [ ] No [ ] N/A Are inbound network communications denied by default? [ ] Yes [ ] No - ARC review required [ ] N/A Is inbound data checked to prevent content-based attacks? [ ] Yes [ ] No - ARC review required [ ] N/A Is the outbound receiver authenticated? [ ] Yes [ ] No - ARC review required [ ] N/A Is the receiver authenticated prior to receiving any sensitive outbound communication? [ ] Yes [ ] No - ARC review required [ ] N/A 3.4.2 Authorization (see http://opensolaris.org/os/community/arc/bestpractices/rbac-intro/ and http://opensolaris.org/os/community/arc/bestpractices/rbac-profiles/ and http://opensolaris.org/os/community/arc/bestpractices/rbac-profiles/ for details) Are there any setuid/setgid privileged binaries in the project? [ ] Yes - ARC review required [*] No - continue with next section (section 3.4.3) If yes then are the setuid/setgid privileges handled by the use of roles? [ ] Yes [ ] No - ARC review required 3.4.3 Auditing (see http://opensolaris.org/os/community/arc/policies/audit-policy/ for details) (see http://opensolaris.org/os/community/arc/caselog/2003/397 for details) Does this component contain administrative or security enforcing software? [ ] Yes - ARC review required [*] No - continue to next section (section 3.4.4) (see http://opensolaris.org/os/community/arc/caselog/2003/397 for details) Do the components create audit logs detailing what took place including what event took place, who was involved, when the event took place? [ ] Yes - ARC contract and Audit project team review required [ ] No - ARC review required 3.4.4 Authentication (see http://opensolaris.org/os/community/arc/policies/PAM/) Do the components contain any authentication code? [ ] Yes [*] No - continue to next section (section 3.4.5) If yes do the components use PAM (plugable authentication modules) for authentication? [ ] Yes [ ] No - ARC review required If yes is a single PAM session maintained during authentication? [ ] Yes [ ] No - ARC review required If yes are the components sufficiently privileged to allow the requested operations (authentication, password change, process credential manipulation, audit state initialization)? [ ] Yes - briefly describe below [ ] No - ARC review required 3.4.5 Passwords (see http://opensolaris.org/os/community/arc/bestpractices/passwords-cli/ and http://opensolaris.org/os/community/arc/bestpractices/passwords-files/ for details) Do any of the components for the project deal with passwords? [ ] Yes [*] No - continue to next section (section 3.4.6) If yes are these passwords entered via the CLI or environment? [ ] Yes - ARC review required [ ] No Are passwords stored within the file system for the component? [ ] Yes [ ] No - continue to next section (section 3.4.6) If yes are the permissions on the file such to protect exposing the password(s)? [ ] Yes [ ] No - ARC review required 3.4.6 General Security Questions (see http://opensolaris.org/os/community/arc/bestpractices/security-questions/ for details) Are there any network protocols used by this project? [ ] Yes [*] No - continue with the next section (section 3.5) Do the components use standard network protocols? [ ] Yes [ ] No - ARC review required Do network services for the project make decisions based upon user, host or service identities? [ ] Yes - explain below [ ] No [ ] N/A Do the components make use of secret information during authentication and/or authorization? [ ] Yes - explain below [ ] No [ ] N/A 3.5 Networking Do the components access the network? [ ] Yes [*] No - continue with the next section (section 3.6) If yes do the components support IPv6? [ ] Yes [ ] No - ARC review required 3.6 Core Solaris Components Do the components of this project compete with or duplicate core Solaris components? [ ] Yes - ARC review required [*] No Examples of Core Solaris Components include but are not limited to: Secure By Default Authorizations PAM -- Plugable Authentication Module Privilege PRM -- Process Rights Management -- Privilege Audit xVm -- Virtualization zones / Solaris Containers PRM -- Process Rights Management RBAC -- Role Based Access Control TX / Trusted Extensions ZFS SMF -- Service Management Facility FMA -- Fault Management Architecture SCF -- Smart Card Facility IPsec 4.0 Interfaces (see http://www.opensolaris.org/os/community/arc/policies/interface-taxonomy/ for details) 4.1 Exported Interfaces Interface Name Classification Comments --------------------------- ----------------------- ----------------------- SUNWconflict Uncommitted Package /usr/bin/conflict Uncommitted Executable binary file 4.2 Imported Interfaces Interface Name Classification Comments --------------------------- -------------------- -------------------------- None Appendix A - References [1] http://invisible-island.net/conflict/conflict.html OSR ID# 10547 RFE ID# 6784379 6. Resources and Schedule 6.4. Steering Committee requested information 6.4.1. Consolidation C-team Name: SFW 6.5. ARC review type: FastTrack 6.6. ARC Exposure: open From Kais.Belgaied@sun.com Wed Jan 7 09:58:03 2009 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 n07Hw3jS014452 for ; Wed, 7 Jan 2009 09:58:03 -0800 (PST) Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6]) by sunmail3mpk.sfbay.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id n07Hw0k3009638; Wed, 7 Jan 2009 09:58:01 -0800 (PST) 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 <0KD400K0D4KNBS00@nwk-avmta-2.sfbay.sun.com>; Wed, 07 Jan 2009 09:57:59 -0800 (PST) Received: from jurassic-x4600.sfbay.sun.com ([129.146.17.63]) by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KD400C304KMP7C0@nwk-avmta-2.sfbay.sun.com>; Wed, 07 Jan 2009 09:57:58 -0800 (PST) Received: from [129.146.11.146] (sr1-jurassic-03.SFBay.Sun.COM [129.146.11.146]) by jurassic-x4600.sfbay.sun.com (8.14.3+Sun/8.14.3) with ESMTP id n07HvvWJ405149; Wed, 07 Jan 2009 09:57:58 -0800 (PST) Date: Wed, 07 Jan 2009 09:57:57 -0800 From: Kais Belgaied Subject: Re: conflict [PSARC/2009/003 FastTrack timeout 01/12/2009] In-reply-to: <200901052208.n05M8rud008253@sac.sfbay.sun.com> To: James Walker Cc: PSARC-ext@sun.com, Zhang.Xiaoping@sun.com Reply-to: Kais.Belgaied@sun.com Message-id: <4964ED25.7030909@Sun.COM> MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1; format=flowed Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <200901052208.n05M8rud008253@sac.sfbay.sun.com> User-Agent: Thunderbird 2.0.0.16 (X11/20080807) Content-Length: 201 Status: RO X-Status: $$$$ X-UID: 0000000002 nit: the case seems to import the PATH env variable. That should be listed in the imported interface Quick question about the -t . Is the expected output limited to executables too ? Kais From Zhang.Xiaoping@sun.com Wed Jan 7 18:27:46 2009 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 n082RjSo004960 for ; Wed, 7 Jan 2009 18:27:46 -0800 (PST) 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 n082RHkP029328 for <@sunmail2sca.sfbay.sun.com:PSARC-ext@sun.com>; Thu, 8 Jan 2009 10:27:45 +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 <0KD400303S68JQ00@nwk-avmta-1.sfbay.Sun.COM> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Wed, 07 Jan 2009 18:27:44 -0800 (PST) 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 <0KD400362S67EK00@nwk-avmta-1.sfbay.Sun.COM> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Wed, 07 Jan 2009 18:27:44 -0800 (PST) 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 n082Rhcd018377 for ; Thu, 08 Jan 2009 02:27:43 +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 <0KD400701S0QKC00@mail-apac.sun.com> (original mail from Zhang.Xiaoping@Sun.COM) for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Thu, 08 Jan 2009 10:27:43 +0800 (SGT) Received: from [129.158.218.164] by mail-apac.sun.com (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) with ESMTPSA id <0KD4000OOS603J20@mail-apac.sun.com>; Thu, 08 Jan 2009 10:27:43 +0800 (SGT) Date: Thu, 08 Jan 2009 10:24:40 +0800 From: Zhang Xiao Ping Subject: Re: conflict [PSARC/2009/003 FastTrack timeout 01/12/2009] In-reply-to: <4964ED25.7030909@Sun.COM> Sender: Zhang.Xiaoping@sun.com To: Kais.Belgaied@sun.com Cc: James Walker , PSARC-ext@sun.com Message-id: <496563E8.7020509@sun.com> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=UTF-8 Content-transfer-encoding: 8BIT X-PMX-Version: 5.4.1.325704 References: <200901052208.n05M8rud008253@sac.sfbay.sun.com> <4964ED25.7030909@Sun.COM> User-Agent: Thunderbird 2.0.0.6 (X11/20071119) Content-Length: 762 Status: RO X-Status: $$$$ X-UID: 0000000003 于 01/08/09 01:57, Kais Belgaied 写道: > nit: the case seems to import the PATH env variable. That should be > listed in the imported interface Done, please check: http://cr.opensolaris.org/~yuntian/conflict_arc/conflict.1 > > Quick question about the -t . Is the expected output limited to > executables too ? No. The following example might be able to explain. bash-3.2# echo $PATH /usr/sbin:/usr/bin:/opt/SUNWstc-stf/bin/i386 bash-3.2# mkfile 1m /usr/bin/1.a bash-3.2# mkfile 1m /usr/sbin/1.b bash-3.2# conflict -t .a.b Current working directory is "/net/tas.eng/export/pub/richard/ws/sfwnv/packages/i386/nightly-nd" :--> /usr/sbin :--:--> /usr/bin :-b:a-: 1 (.a,.b) > > Kais > -- My name is 'Xiao Ping', not 'Zhang'. From James.Walker@sun.com Wed Jan 7 21:36:14 2009 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 n085aDpG024906 for ; Wed, 7 Jan 2009 21:36:13 -0800 (PST) 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 n085a8Ap019185 for <@sunmail2sca.sfbay.sun.com:PSARC-ext@sun.com>; Thu, 8 Jan 2009 13:36:12 +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 <0KD5007010WBLP00@nwk-avmta-1.sfbay.Sun.COM> for PSARC-ext@sun.com (ORCPT PSARC-ext@Sun.COM); Wed, 07 Jan 2009 21:36:11 -0800 (PST) Received: from brmea-mail-1.sun.com ([192.18.98.31]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KD500I9Z0WBWV40@nwk-avmta-1.sfbay.Sun.COM> for PSARC-ext@sun.com (ORCPT PSARC-ext@Sun.COM); Wed, 07 Jan 2009 21:36:11 -0800 (PST) Received: from fe-amer-10.sun.com ([192.18.109.80]) by brmea-mail-1.sun.com (8.13.6+Sun/8.12.9) with ESMTP id n085aBwn004535 for ; Thu, 08 Jan 2009 05:36:11 +0000 (GMT) Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) id <0KD500C010RG3F00@mail-amer.sun.com> (original mail from James.Walker@Sun.COM) for PSARC-ext@Sun.COM (ORCPT PSARC-ext@Sun.COM); Wed, 07 Jan 2009 22:36:11 -0700 (MST) Received: from c-24-8-61-165.hsd1.co.comcast.net ([129.150.32.225]) by mail-amer.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0KD500BEX0W0JP80@mail-amer.sun.com> for PSARC-ext@Sun.COM (ORCPT PSARC-ext@Sun.COM); Wed, 07 Jan 2009 22:36:11 -0700 (MST) Date: Wed, 07 Jan 2009 22:36:00 -0700 From: Jim Walker Subject: Re: conflict [PSARC/2009/003 FastTrack timeout 01/12/2009] In-reply-to: <496563E8.7020509@sun.com> Sender: James.Walker@sun.com To: Zhang Xiao Ping Cc: PSARC-ext@sun.com Reply-to: James.Walker@sun.com Message-id: <496590C0.4050500@sun.com> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=UTF-8 Content-transfer-encoding: 8BIT X-PMX-Version: 5.4.1.325704 References: <200901052208.n05M8rud008253@sac.sfbay.sun.com> <4964ED25.7030909@Sun.COM> <496563E8.7020509@sun.com> User-Agent: Thunderbird 2.0.0.19 (Macintosh/20081209) Content-Length: 432 Status: RO X-Status: $$$$ X-UID: 0000000004 Zhang Xiao Ping wrote: > 于 01/08/09 01:57, Kais Belgaied 写道: > >> nit: the case seems to import the PATH env variable. That should be >> listed in the imported interface I updated the proposal.txt file in the case directory as follows: 4.2 Imported Interfaces Interface Name Classification Comments -------------- -------------- -------------------------- PATH Committed Environment variable Cheers, Jim From James.Walker@Sun.COM Tue Jan 13 13:28:40 2009 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 n0DLSdYq011855 for ; Tue, 13 Jan 2009 13:28:39 -0800 (PST) Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11]) by sunmail5.uk.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id n0DLScVi017376 for <@sunmail2sca.sfbay.sun.com:PSARC-ext@sun.com>; Tue, 13 Jan 2009 21:28:38 GMT 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 <0KDF00F01IBPKX00@brm-avmta-1.central.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@Sun.COM); Tue, 13 Jan 2009 14:28:37 -0700 (MST) Received: from brmea-mail-1.sun.com ([192.18.98.31]) by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KDF0083RIBPG260@brm-avmta-1.central.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@Sun.COM); Tue, 13 Jan 2009 14:28:37 -0700 (MST) Received: from fe-amer-09.sun.com ([192.18.109.79]) by brmea-mail-1.sun.com (8.13.6+Sun/8.12.9) with ESMTP id n0DLSbG5000177 for ; Tue, 13 Jan 2009 21:28:37 +0000 (GMT) Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) id <0KDF00201EMJRM00@mail-amer.sun.com> (original mail from James.Walker@Sun.COM) for PSARC-ext@Sun.COM (ORCPT PSARC-ext@Sun.COM); Tue, 13 Jan 2009 14:28:37 -0700 (MST) Received: from [172.20.25.153] by mail-amer.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0KDF00CMTIBN9Z20@mail-amer.sun.com>; Tue, 13 Jan 2009 14:28:35 -0700 (MST) Date: Tue, 13 Jan 2009 14:52:27 -0700 From: Jim Walker Subject: Re: conflict [PSARC/2009/003 FastTrack timeout 01/12/2009] In-reply-to: <496590C0.4050500@sun.com> Sender: James.Walker@Sun.COM To: Kais Belgaied Cc: Zhang Xiao Ping , PSARC-ext@Sun.COM Reply-to: James.Walker@Sun.COM Message-id: <496D0D1B.2090909@sun.com> Organization: Sun Microsystems, Inc. MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=UTF-8 Content-transfer-encoding: 8BIT X-PMX-Version: 5.4.1.325704 References: <200901052208.n05M8rud008253@sac.sfbay.sun.com> <4964ED25.7030909@Sun.COM> <496563E8.7020509@sun.com> <496590C0.4050500@sun.com> User-Agent: Thunderbird 2.0.0.14 (X11/20080728) Status: RO Content-Length: 728 Kais, or anyone, Can I get a +1, so I can close? It appears all the issues have been addressed. Cheers, Jim Jim Walker wrote: > Zhang Xiao Ping wrote: >> 于 01/08/09 01:57, Kais Belgaied 写道: >> >>> nit: the case seems to import the PATH env variable. That should be >>> listed in the imported interface > > I updated the proposal.txt file in the case directory as > follows: > > 4.2 Imported Interfaces > > Interface Name Classification Comments > -------------- -------------- -------------------------- > PATH Committed Environment variable > > Cheers, > Jim > > -- Jim Walker, http://blogs.sun.com/jwalker Sun Microsystems, Software, Solaris QE x77744, 500 Eldorado Blvd, Broomfield CO 80021 From James.Walker@Sun.COM Tue Jan 13 14:24:10 2009 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 n0DMOAiK014361 for ; Tue, 13 Jan 2009 14:24:10 -0800 (PST) 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 n0DMOAIX012915 for <@sunmail2sca.sfbay.sun.com:PSARC-ext@sun.com>; Tue, 13 Jan 2009 14:24:10 -0800 (PST) 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 <0KDF00L3LKW97M00@brm-avmta-1.central.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Tue, 13 Jan 2009 15:24:09 -0700 (MST) Received: from brmea-mail-2.sun.com ([192.18.98.43]) by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KDF008ENKW8G2B0@brm-avmta-1.central.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Tue, 13 Jan 2009 15:24:08 -0700 (MST) Received: from fe-amer-09.sun.com ([192.18.109.79]) by brmea-mail-2.sun.com (8.13.6+Sun/8.12.9) with ESMTP id n0DMO8mf004360 for ; Tue, 13 Jan 2009 22:24:08 +0000 (GMT) Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) id <0KDF00001JC5R700@mail-amer.sun.com> (original mail from James.Walker@Sun.COM) for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Tue, 13 Jan 2009 15:24:08 -0700 (MST) Received: from [172.20.25.153] by mail-amer.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0KDF00FQZKVVX730@mail-amer.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Tue, 13 Jan 2009 15:23:56 -0700 (MST) Date: Tue, 13 Jan 2009 15:47:47 -0700 From: Jim Walker Subject: Re: conflict [PSARC/2009/003 FastTrack timeout 01/12/2009] In-reply-to: <496D0D1B.2090909@sun.com> Sender: James.Walker@Sun.COM To: PSARC-ext@Sun.COM Cc: Zhang Xiao Ping Reply-to: James.Walker@Sun.COM Message-id: <496D1A13.8040500@sun.com> Organization: Sun Microsystems, Inc. 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: <200901052208.n05M8rud008253@sac.sfbay.sun.com> <4964ED25.7030909@Sun.COM> <496563E8.7020509@sun.com> <496590C0.4050500@sun.com> <496D0D1B.2090909@sun.com> User-Agent: Thunderbird 2.0.0.14 (X11/20080728) Status: RO Content-Length: 332 Mark just informed me that I don't need a +1 since there were comments and they were addressed. This case has timed out. I'll mark it closed approved. Sorry for the spam. Cheers, Jim Jim Walker wrote: > Kais, or anyone, > > Can I get a +1, so I can close? > > It appears all the issues have been addressed. > > Cheers, > Jim