From jw137282@sac.sfbay.sun.com Thu May 14 00:23:06 2009 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 n4E7N5hU028554 for ; Thu, 14 May 2009 00:23:05 -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 n4E7N3LV011537; Thu, 14 May 2009 01:23:04 -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 <0KJM00K0UHUE8M00@nwk-avmta-1.sfbay.Sun.COM>; Thu, 14 May 2009 00:23:02 -0700 (PDT) Received: from dm-sfbay-01.sfbay.sun.com ([129.145.155.118]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KJM00I76HUDSQ10@nwk-avmta-1.sfbay.Sun.COM>; Thu, 14 May 2009 00:23:01 -0700 (PDT) Received: from sac.sfbay.sun.com (sac.SFBay.Sun.COM [129.146.226.132]) by dm-sfbay-01.sfbay.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id n4E7N0HO035143; Thu, 14 May 2009 00:23:00 -0700 (PDT) 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 n4E7MXD3028546; Thu, 14 May 2009 00:22:33 -0700 (PDT) Received: (from jw137282@localhost) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8/Submit) id n4E7MXck028542; Thu, 14 May 2009 00:22:33 -0700 (PDT) Date: Thu, 14 May 2009 00:22:33 -0700 (PDT) From: James Walker Subject: aalib [LSARC/2009/302 FastTrack timeout 05/21/2009] To: LSARC-ext@sun.com Cc: fan.li@sun.com Message-id: <200905140722.n4E7MXck028542@sac.sfbay.sun.com> Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 Status: RO Content-Length: 13299 I'm sponsoring this familiarity case for Li Fan. The requested release binding is minor. The man pages have been posted in the materials directory. Template Version: @(#)sac_nextcase 1.68 02/23/09 SMI This information is Copyright 2009 Sun Microsystems 1. Introduction 1.1. Project/Component Working Name: aalib 1.2. Name of Document Author/Supplier: Author: Li Fan 1.3 Date of This Document: 14 May, 2009 4. Technical Description Iperf Check List 1.0 Project Information 1.1 Name of project/component AA-lib 1.2 Author of document Fan.Li@Sun.COM 2.0 Project Summary 2.1 Project Description AA-lib is a low level graphic library just as many other libraries are. The main difference is that AA-lib does not require graphics device. In fact, there is no graphical output possible. AA-lib replaces those old-fashioned output methods with powerful ascii-art renderer. AA-lib API is designed to be similar to other graphics libraries so it is very easy to learn. 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 AA-project[1] 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 4.1 Exported Interfaces Interface Name Classification Comments -------------------------- -------------- ---------------------- SUNWaalib Uncommitted Package /usr/bin/aafire Uncommitted Executable binary file /usr/bin/aainfo Uncommitted Executable binary file /usr/bin/aalib-config Uncommitted Executable shell script /usr/bin/aasavefont Uncommitted Executable binary file /usr/bin/aatest Uncommitted Executable binary file /usr/include/aalib.h Uncommitted Header file /usr/lib/libaa.so.1.0.4 Uncommitted AA-lib libarary /usr/lib/libaa.so.1 Uncommitted Library symbolic link /usr/lib/libaa.so Uncommitted Library symbolic link /usr/lib/64/libaa.so.1.0.4 Uncommitted 64-bit AA-lib libarary /usr/lib/64/libaa.so.1 Uncommitted Library symbolic link /usr/lib/64/libaa.so Uncommitted Library symbolic link * 64 = {amd64 | sparcv9} 4.2 Imported Interfaces Interface Name Classification Comments -------------------------- -------------- ---------------------- SUNWslang Committed S-Lang Library SUNWxwrtl Committed X Window System Library SUNWlibmsr Committed Math Libraries (Root) Appendix A - References [1] http://sourceforge.net/projects/aa-project/ OSR ID# 10595 RFE ID# 6822439 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 John.Fischer@sun.com Thu May 14 10:19:22 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 n4EHJMfM006118 for ; Thu, 14 May 2009 10:19:22 -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 n4EHJMb1007167 for <@sunmail2sca.sfbay.sun.com:LSARC-ext@sun.com>; Thu, 14 May 2009 10:19:22 -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 <0KJN0091F9GAIZ00@brm-avmta-1.central.sun.com> for LSARC-ext@sun.com (ORCPT LSARC-ext@Sun.Com); Thu, 14 May 2009 11:19:22 -0600 (MDT) 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 <0KJN008079G84R20@brm-avmta-1.central.sun.com> for LSARC-ext@sun.com (ORCPT LSARC-ext@Sun.Com); Thu, 14 May 2009 11:19:20 -0600 (MDT) 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 n4EHJKSu005111 for ; Thu, 14 May 2009 17:19:20 +0000 (GMT) Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com (Sun Java(tm) System Messaging Server 7u2-7.02 64bit (built Apr 16 2009)) id <0KJN005009AUXQ00@mail-amer.sun.com> for LSARC-ext@Sun.Com (ORCPT LSARC-ext@Sun.Com); Thu, 14 May 2009 11:19:20 -0600 (MDT) Received: from [192.168.10.8] ([unknown] [76.20.56.47]) by mail-amer.sun.com (Sun Java(tm) System Messaging Server 7u2-7.02 64bit (built Apr 16 2009)) with ESMTPSA id <0KJN003W49G06X20@mail-amer.sun.com>; Thu, 14 May 2009 11:19:13 -0600 (MDT) Date: Thu, 14 May 2009 10:17:58 -0700 From: John Fischer Subject: Re: aalib [LSARC/2009/302 FastTrack timeout 05/21/2009] In-reply-to: <200905140722.n4E7MXck028542@sac.sfbay.sun.com> Sender: John.Fischer@sun.com To: James Walker Cc: LSARC-ext@sun.com, Fan.Li@sun.com Reply-to: John.Fischer@sun.com Message-id: <4A0C5246.1080603@sun.com> MIME-version: 1.0 Content-type: text/plain; CHARSET=US-ASCII; format=flowed Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <200905140722.n4E7MXck028542@sac.sfbay.sun.com> User-Agent: Thunderbird 2.0.0.21 (X11/20090323) Status: RO Content-Length: 15171 Fan, The files within bin all seem (with the exception aaconfig-lib) to be example programs for aalib. In fact the man page for aafire states: aafire, aainfo, aasavefont, aatest - aalib example programs So I am not sure why they are being included on Solaris with this project. Or at least I am not sure why they are being include in /usr/bin. Perhaps /usr/demo/aalib would be more appropriate. If they are included in /usr/bin I would also expect the man page to be delivered with an Attributes section. These also do not seem like they should be Uncommitted but Volatile at best. If these are in /usr/demo then they are "Not an Interface". Also if you go the /usr/demo route you might consider including the source code for these demos along with the binary. aaconfig-lib is a utility that makes sense to have in /usr/bin for developers as it informs them of useful information. It should also have a man page with an Attributes section. Thanks, John James Walker wrote: > I'm sponsoring this familiarity case for Li Fan. The requested > release binding is minor. The man pages have been posted in the > materials directory. > > Template Version: @(#)sac_nextcase 1.68 02/23/09 SMI > This information is Copyright 2009 Sun Microsystems > 1. Introduction > 1.1. Project/Component Working Name: > aalib > 1.2. Name of Document Author/Supplier: > Author: Li Fan > 1.3 Date of This Document: > 14 May, 2009 > 4. Technical Description > Iperf Check List > 1.0 Project Information > 1.1 Name of project/component > AA-lib > > 1.2 Author of document > Fan.Li@Sun.COM > > 2.0 Project Summary > 2.1 Project Description > AA-lib is a low level graphic library just as many other libraries are. > The main difference is that AA-lib does not require graphics device. > In fact, there is no graphical output possible. AA-lib replaces those > old-fashioned output methods with powerful ascii-art renderer. AA-lib > API is designed to be similar to other graphics libraries so it is very > easy to learn. > > 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 > AA-project[1] > > 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 > 4.1 Exported Interfaces > > Interface Name Classification Comments > -------------------------- -------------- ---------------------- > SUNWaalib Uncommitted Package > /usr/bin/aafire Uncommitted Executable binary file > /usr/bin/aainfo Uncommitted Executable binary file > /usr/bin/aalib-config Uncommitted Executable shell script > /usr/bin/aasavefont Uncommitted Executable binary file > /usr/bin/aatest Uncommitted Executable binary file > /usr/include/aalib.h Uncommitted Header file > /usr/lib/libaa.so.1.0.4 Uncommitted AA-lib libarary > /usr/lib/libaa.so.1 Uncommitted Library symbolic link > /usr/lib/libaa.so Uncommitted Library symbolic link > /usr/lib/64/libaa.so.1.0.4 Uncommitted 64-bit AA-lib libarary > /usr/lib/64/libaa.so.1 Uncommitted Library symbolic link > /usr/lib/64/libaa.so Uncommitted Library symbolic link > > * 64 = {amd64 | sparcv9} > > 4.2 Imported Interfaces > > Interface Name Classification Comments > -------------------------- -------------- ---------------------- > SUNWslang Committed S-Lang Library > SUNWxwrtl Committed X Window System Library > SUNWlibmsr Committed Math Libraries (Root) > > Appendix A - References > [1] http://sourceforge.net/projects/aa-project/ > > OSR ID# 10595 > RFE ID# 6822439 > > 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 > > _______________________________________________ > opensolaris-arc mailing list > opensolaris-arc@opensolaris.org From James.Walker@sun.com Thu May 14 22:21:01 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 n4F5L0fW017157 for ; Thu, 14 May 2009 22:21:01 -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 n4F5Kv2L011533 for <@sunmail2sca.sfbay.sun.com:LSARC-ext@sun.com>; Fri, 15 May 2009 06:20:59 +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 <0KJO00H036UYUL00@nwk-avmta-1.sfbay.Sun.COM> for LSARC-ext@sun.com (ORCPT LSARC-ext@Sun.COM); Thu, 14 May 2009 22:20:59 -0700 (PDT) Received: from brmea-mail-2.sun.com ([192.18.98.43]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KJO00ACU6UYSP20@nwk-avmta-1.sfbay.Sun.COM> for LSARC-ext@sun.com (ORCPT LSARC-ext@Sun.COM); Thu, 14 May 2009 22:20:58 -0700 (PDT) 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 n4F5Kw4U007167 for ; Fri, 15 May 2009 05:20:58 +0000 (GMT) Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com (Sun Java(tm) System Messaging Server 7u2-7.02 64bit (built Apr 16 2009)) id <0KJO009006Q6CS00@mail-amer.sun.com> for LSARC-ext@Sun.COM (ORCPT LSARC-ext@Sun.COM); Thu, 14 May 2009 23:20:58 -0600 (MDT) Received: from c-67-166-22-238.hsd1.co.comcast.net ([unknown] [129.150.32.21]) by mail-amer.sun.com (Sun Java(tm) System Messaging Server 7u2-7.02 64bit (built Apr 16 2009)) with ESMTPSA id <0KJO00MRB6UYFG40@mail-amer.sun.com> for LSARC-ext@Sun.COM (ORCPT LSARC-ext@Sun.COM); Thu, 14 May 2009 23:20:58 -0600 (MDT) Date: Thu, 14 May 2009 23:20:58 -0600 From: Jim Walker Subject: Re: aalib [LSARC/2009/302 FastTrack timeout 05/21/2009] In-reply-to: <4A0C5246.1080603@sun.com> Sender: James.Walker@sun.com To: John.Fischer@sun.com, Fan.Li@sun.com Cc: LSARC-ext@sun.com Reply-to: James.Walker@sun.com Message-id: <4A0CFBBA.5050207@sun.com> MIME-version: 1.0 Content-type: text/plain; CHARSET=US-ASCII; format=flowed Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <200905140722.n4E7MXck028542@sac.sfbay.sun.com> <4A0C5246.1080603@sun.com> User-Agent: Thunderbird 2.0.0.21 (Macintosh/20090302) Status: RO Content-Length: 1245 John Fischer wrote: > Fan, > > The files within bin all seem (with the exception aaconfig-lib) > to be example programs for aalib. In fact the man page for aafire > states: > > aafire, aainfo, aasavefont, aatest - aalib example programs > > So I am not sure why they are being included on Solaris with this > project. Or at least I am not sure why they are being include in > /usr/bin. Perhaps /usr/demo/aalib would be more appropriate. If > they are included in /usr/bin I would also expect the man page to > be delivered with an Attributes section. These also do not seem > like they should be Uncommitted but Volatile at best. If these > are in /usr/demo then they are "Not an Interface". Also if you > go the /usr/demo route you might consider including the source > code for these demos along with the binary. > > aaconfig-lib is a utility that makes sense to have in /usr/bin > for developers as it informs them of useful information. It > should also have a man page with an Attributes section. I agree. /usr/demo is better and Li Fan can add an aaconfig-lib manpage. Li Fan and I discussed this but he want to try for the more "familiar" location. Li Fan, Can you confirm these changes are ok with you? Cheers, Jim From Fan.Li@sun.com Fri May 15 00:25:20 2009 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 n4F7PJ0s017255 for ; Fri, 15 May 2009 00:25:19 -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 n4F7PGYK054657 for <@sunmail2sca.sfbay.sun.com:LSARC-ext@sun.com>; Fri, 15 May 2009 01:25:19 -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 <0KJO00I0DCM6Z300@nwk-avmta-1.sfbay.Sun.COM> for LSARC-ext@sun.com (ORCPT LSARC-ext@Sun.COM); Fri, 15 May 2009 00:25:18 -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 <0KJO00A9DCM5SOB0@nwk-avmta-1.sfbay.Sun.COM> for LSARC-ext@sun.com (ORCPT LSARC-ext@Sun.COM); Fri, 15 May 2009 00:25:18 -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 n4F7PGCK020942 for ; Fri, 15 May 2009 07:25:16 +0000 (GMT) Received: from conversion-daemon.mail-apac.sun.com by mail-apac.sun.com (Sun Java(tm) System Messaging Server 7u2-7.02 64bit (built Apr 16 2009)) id <0KJO00C00CIB8J00@mail-apac.sun.com> for LSARC-ext@Sun.COM (ORCPT LSARC-ext@Sun.COM); Fri, 15 May 2009 15:25:16 +0800 (SGT) Received: from [129.158.218.202] ([unknown] [129.158.218.202]) by mail-apac.sun.com (Sun Java(tm) System Messaging Server 7u2-7.02 64bit (built Apr 16 2009)) with ESMTPSA id <0KJO002BJCM0O8L0@mail-apac.sun.com> for LSARC-ext@Sun.COM (ORCPT LSARC-ext@Sun.COM); Fri, 15 May 2009 15:25:13 +0800 (SGT) Date: Fri, 15 May 2009 15:22:11 +0800 From: Li Fan Subject: Re: aalib [LSARC/2009/302 FastTrack timeout 05/21/2009] In-reply-to: <4A0CFBBA.5050207@sun.com> Sender: Fan.Li@sun.com To: James.Walker@sun.com Cc: John.Fischer@sun.com, LSARC-ext@sun.com Reply-to: Fan.Li@sun.com Message-id: <4A0D1823.6000401@Sun.com> MIME-version: 1.0 Content-type: text/plain; CHARSET=US-ASCII; format=flowed Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <200905140722.n4E7MXck028542@sac.sfbay.sun.com> <4A0C5246.1080603@sun.com> <4A0CFBBA.5050207@sun.com> User-Agent: Thunderbird 2.0.0.6 (X11/20071119) Status: RO Content-Length: 1637 John and Jim, Thanks for your comments! I agree with you. aafire, aainfo, aasavefont, aatest should be moved to /usr/demo/aalib, and a manpage will be added for aalib-config. For those example programs in /usr/demo/aalib, do they must include source code with them? Where should these source code be placed? Thanks -- Li Fan Jim Walker wrote: > John Fischer wrote: >> Fan, >> >> The files within bin all seem (with the exception aaconfig-lib) >> to be example programs for aalib. In fact the man page for aafire >> states: >> >> aafire, aainfo, aasavefont, aatest - aalib example programs >> >> So I am not sure why they are being included on Solaris with this >> project. Or at least I am not sure why they are being include in >> /usr/bin. Perhaps /usr/demo/aalib would be more appropriate. If >> they are included in /usr/bin I would also expect the man page to >> be delivered with an Attributes section. These also do not seem >> like they should be Uncommitted but Volatile at best. If these >> are in /usr/demo then they are "Not an Interface". Also if you >> go the /usr/demo route you might consider including the source >> code for these demos along with the binary. >> >> aaconfig-lib is a utility that makes sense to have in /usr/bin >> for developers as it informs them of useful information. It >> should also have a man page with an Attributes section. > > I agree. /usr/demo is better and Li Fan can add an aaconfig-lib > manpage. > > Li Fan and I discussed this but he want to try for the more > "familiar" location. > > Li Fan, > > Can you confirm these changes are ok with you? > > Cheers, > Jim From James.Walker@sun.com Fri May 15 07:13:13 2009 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 n4FEDCe7020735 for ; Fri, 15 May 2009 07:13:12 -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 n4FED9NA010686 for <@sunmail2sca.sfbay.sun.com:LSARC-ext@sun.com>; Fri, 15 May 2009 08:13:12 -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 <0KJO00407VHZ0G00@nwk-avmta-1.sfbay.Sun.COM> for LSARC-ext@sun.com (ORCPT LSARC-ext@Sun.COM); Fri, 15 May 2009 07:13:11 -0700 (PDT) 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 <0KJO00ML1VHYJBE0@nwk-avmta-1.sfbay.Sun.COM> for LSARC-ext@sun.com (ORCPT LSARC-ext@Sun.COM); Fri, 15 May 2009 07:13:10 -0700 (PDT) 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 n4FEDAFX005919 for ; Fri, 15 May 2009 14:13:10 +0000 (GMT) Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com (Sun Java(tm) System Messaging Server 7u2-7.02 64bit (built Apr 16 2009)) id <0KJO00300UUMI300@mail-amer.sun.com> for LSARC-ext@Sun.COM (ORCPT LSARC-ext@Sun.COM); Fri, 15 May 2009 08:13:10 -0600 (MDT) Received: from c-67-166-22-238.hsd1.co.comcast.net ([unknown] [67.166.22.238]) by mail-amer.sun.com (Sun Java(tm) System Messaging Server 7u2-7.02 64bit (built Apr 16 2009)) with ESMTPSA id <0KJO000UEVHPJ9D0@mail-amer.sun.com> for LSARC-ext@Sun.COM (ORCPT LSARC-ext@Sun.COM); Fri, 15 May 2009 08:13:05 -0600 (MDT) Date: Fri, 15 May 2009 08:13:01 -0600 From: Jim Walker Subject: Re: aalib [LSARC/2009/302 FastTrack timeout 05/21/2009] In-reply-to: <4A0D1823.6000401@Sun.com> Sender: James.Walker@sun.com To: Fan.Li@sun.com Cc: LSARC-ext@sun.com Reply-to: James.Walker@sun.com Message-id: <4A0D786D.1040702@sun.com> MIME-version: 1.0 Content-type: text/plain; CHARSET=US-ASCII; format=flowed Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <200905140722.n4E7MXck028542@sac.sfbay.sun.com> <4A0C5246.1080603@sun.com> <4A0CFBBA.5050207@sun.com> <4A0D1823.6000401@Sun.com> User-Agent: Thunderbird 2.0.0.21 (Macintosh/20090302) Status: RO Content-Length: 414 Li Fan wrote: > > For those example programs in /usr/demo/aalib, do they must include > source code with them? Where should these source code be placed? > What source code? I didn't see any in your or other aalib packages. If it is not normally delivered, I wouldn't deliver it. But /usr/demo/ and doc locations are not a concern for ARC reviewers anyway. I can help you organize this if needed. Cheers, Jim From John.Fischer@sun.com Fri May 15 08:47:32 2009 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 n4FFlWdu019739 for ; Fri, 15 May 2009 08:47:32 -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 n4FFlUbT007616 for <@sunmail2sca.sfbay.sun.com:LSARC-ext@sun.com>; Fri, 15 May 2009 08:47:32 -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 <0KJO00A09ZV7ZB00@brm-avmta-1.central.sun.com> for LSARC-ext@sun.com (ORCPT LSARC-ext@sun.com); Fri, 15 May 2009 09:47:31 -0600 (MDT) Received: from brmea-mail-4.sun.com ([192.18.98.36]) by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KJO00IKIZV6MWD0@brm-avmta-1.central.sun.com> for LSARC-ext@sun.com (ORCPT LSARC-ext@sun.com); Fri, 15 May 2009 09:47:30 -0600 (MDT) Received: from fe-amer-10.sun.com ([192.18.109.80]) by brmea-mail-4.sun.com (8.13.6+Sun/8.12.9) with ESMTP id n4FFlUWh004617 for ; Fri, 15 May 2009 15:47:30 +0000 (GMT) Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com (Sun Java(tm) System Messaging Server 7u2-7.02 64bit (built Apr 16 2009)) id <0KJO00E00Y4VV800@mail-amer.sun.com> for LSARC-ext@sun.com (ORCPT LSARC-ext@sun.com); Fri, 15 May 2009 09:47:30 -0600 (MDT) Received: from [192.168.10.13] ([unknown] [76.20.56.47]) by mail-amer.sun.com (Sun Java(tm) System Messaging Server 7u2-7.02 64bit (built Apr 16 2009)) with ESMTPSA id <0KJO00CUCZUZ9130@mail-amer.sun.com> for LSARC-ext@sun.com (ORCPT LSARC-ext@sun.com); Fri, 15 May 2009 09:47:24 -0600 (MDT) Date: Fri, 15 May 2009 08:46:09 -0700 From: John Fischer Subject: Re: aalib [LSARC/2009/302 FastTrack timeout 05/21/2009] In-reply-to: <4A0D786D.1040702@sun.com> Sender: John.Fischer@sun.com To: James.Walker@sun.com Cc: Fan.Li@sun.com, LSARC-ext@sun.com Reply-to: John.Fischer@sun.com Message-id: <4A0D8E41.20600@sun.com> MIME-version: 1.0 Content-type: text/plain; CHARSET=US-ASCII; format=flowed Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <200905140722.n4E7MXck028542@sac.sfbay.sun.com> <4A0C5246.1080603@sun.com> <4A0CFBBA.5050207@sun.com> <4A0D1823.6000401@Sun.com> <4A0D786D.1040702@sun.com> User-Agent: Thunderbird 2.0.0.21 (X11/20090323) Status: RO Content-Length: 886 Li Fan, Jim is correct that we are not concerned with this directory. It should be listed in the Interface table as Not an Interface. The source code idea came from me. The reason being is that many of the /usr/demo things have source code associated with them. If you include the source code for these demos simply put it within the same directory (usr/demo/aalib). You do not have to do this part, however. Thanks, John Jim Walker wrote: > Li Fan wrote: >> >> For those example programs in /usr/demo/aalib, do they must include >> source code with them? Where should these source code be placed? >> > > What source code? I didn't see any in your or other aalib packages. > If it is not normally delivered, I wouldn't deliver it. > > But /usr/demo/ and doc locations are not a concern for ARC reviewers > anyway. I can help you organize this if needed. > > Cheers, > Jim From Fan.Li@sun.com Sun May 17 23:58:12 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 n4I6wBGt025653 for ; Sun, 17 May 2009 23:58:12 -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 n4I6w7qH013362 for <@sunmail2sca.sfbay.sun.com:LSARC-ext@sun.com>; Mon, 18 May 2009 07:58:11 +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 <0KJT00D0LVCWL400@nwk-avmta-1.sfbay.Sun.COM> for LSARC-ext@sun.com (ORCPT LSARC-ext@sun.com); Sun, 17 May 2009 23:58:08 -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 <0KJT00D0OVCUK500@nwk-avmta-1.sfbay.Sun.COM> for LSARC-ext@sun.com (ORCPT LSARC-ext@sun.com); Sun, 17 May 2009 23:58:07 -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 n4I6w6vQ019228 for ; Mon, 18 May 2009 06:58:06 +0000 (GMT) Received: from conversion-daemon.mail-apac.sun.com by mail-apac.sun.com (Sun Java(tm) System Messaging Server 7u2-7.02 64bit (built Apr 16 2009)) id <0KJT00200VBYQO00@mail-apac.sun.com> for LSARC-ext@sun.com (ORCPT LSARC-ext@sun.com); Mon, 18 May 2009 14:58:06 +0800 (SGT) Received: from [129.158.218.202] ([unknown] [129.158.218.202]) by mail-apac.sun.com (Sun Java(tm) System Messaging Server 7u2-7.02 64bit (built Apr 16 2009)) with ESMTPSA id <0KJT005NIVCTJK00@mail-apac.sun.com> for LSARC-ext@sun.com (ORCPT LSARC-ext@sun.com); Mon, 18 May 2009 14:58:06 +0800 (SGT) Date: Mon, 18 May 2009 14:55:02 +0800 From: Li Fan Subject: Re: aalib [LSARC/2009/302 FastTrack timeout 05/21/2009] In-reply-to: <4A0D8E41.20600@sun.com> Sender: Fan.Li@sun.com To: John.Fischer@sun.com Cc: LSARC-ext@sun.com Reply-to: Fan.Li@sun.com Message-id: <4A110646.3080100@Sun.com> MIME-version: 1.0 Content-type: multipart/mixed; boundary="Boundary_(ID_fPGE4K1H6D4ThedWthvIpA)" X-PMX-Version: 5.4.1.325704 References: <200905140722.n4E7MXck028542@sac.sfbay.sun.com> <4A0C5246.1080603@sun.com> <4A0CFBBA.5050207@sun.com> <4A0D1823.6000401@Sun.com> <4A0D786D.1040702@sun.com> <4A0D8E41.20600@sun.com> User-Agent: Thunderbird 2.0.0.6 (X11/20071119) Status: RO Content-Length: 4025 This is a multi-part message in MIME format. --Boundary_(ID_fPGE4K1H6D4ThedWthvIpA) Content-type: text/plain; CHARSET=US-ASCII; format=flowed Content-transfer-encoding: 7BIT John, I will discuss with Jim about binaries in /usr/demo. For aalib-config, I have added a manpage. You can get it in attachment. Thanks, -- Li Fan John Fischer wrote: > Li Fan, > > Jim is correct that we are not concerned with this directory. > It should be listed in the Interface table as Not an Interface. > The source code idea came from me. The reason being is that > many of the /usr/demo things have source code associated with > them. If you include the source code for these demos simply > put it within the same directory (usr/demo/aalib). You do > not have to do this part, however. > > Thanks, > > John > > > > > Jim Walker wrote: >> Li Fan wrote: >>> >>> For those example programs in /usr/demo/aalib, do they must include >>> source code with them? Where should these source code be placed? >>> >> >> What source code? I didn't see any in your or other aalib packages. >> If it is not normally delivered, I wouldn't deliver it. >> >> But /usr/demo/ and doc locations are not a concern for ARC reviewers >> anyway. I can help you organize this if needed. >> >> Cheers, >> Jim --Boundary_(ID_fPGE4K1H6D4ThedWthvIpA) Content-type: text/plain; name=aalib-config.text Content-transfer-encoding: 7BIT Content-disposition: inline; filename=aalib-config.text User Commands AALIB(1) NAME aalib-config - script to get information about the installed version of aalib SYNOPSIS aalib-config [--prefix[=DIR]] [--exec-prefix[=DIR]] [--ver- sion] [--libs] [--static-libs] [--cflags] DESCRIPTION aalib-config is a tool that is used to configure to deter- mine the compiler and linker flags that should be used to compile and link programs that use aalib. It is also used internally to the .m4 macros for GNU autoconf that are included with aalib. OPTIONS aalib-config accepts the following options: --version Print the currently installed version of aalib on the standard output. --libs Print the linker flags that are necessary to link a aalib program. --static-libs Print the linker flags that are necessary to link a aalib program statically. --cflags Print the compiler flags that are necessary to com- pile a aalib program. --prefix=PREFIX If specified, use PREFIX instead of the installation prefix that aalib was built with when computing the output for the --cflags and --libs options. This option is also used for the exec prefix if --exec-prefix was not specified. This option must be specified before any --libs or --cflags options. --exec-prefix=PREFIX If specified, use PREFIX instead of the installation exec prefix that aalib was built with when computing the output for the --cflags and --libs options. This option must be specified before any --libs or --cflags options. COPYRIGHT Copyright O 1998 Owen Taylor Permission to use, copy, modify, and distribute this SunOS 5.10 Last change: 1 User Commands AALIB(1) software and its documentation for any purpose and without fee is hereby granted, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting docu- mentation. Modified for aalib by Joey Hess SunOS 5.10 Last change: 2 --Boundary_(ID_fPGE4K1H6D4ThedWthvIpA)-- From John.Fischer@Sun.COM Mon May 18 06:22:18 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 n4IDMGWo028676 for ; Mon, 18 May 2009 06:22:16 -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 n4IDMFGH022905 for <@sunmail2sca.sfbay.sun.com:LSARC-ext@sun.com>; Mon, 18 May 2009 14:22:15 +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 <0KJU00007D50CT00@nwk-avmta-2.sfbay.sun.com> for LSARC-ext@sun.com (ORCPT LSARC-ext@sun.com); Mon, 18 May 2009 06:22:12 -0700 (PDT) Received: from brmea-mail-4.sun.com ([192.18.98.36]) by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KJU00KGDD506O70@nwk-avmta-2.sfbay.sun.com> for LSARC-ext@sun.com (ORCPT LSARC-ext@sun.com); Mon, 18 May 2009 06:22:12 -0700 (PDT) Received: from fe-amer-10.sun.com ([192.18.109.80]) by brmea-mail-4.sun.com (8.13.6+Sun/8.12.9) with ESMTP id n4IDMCsU018054 for ; Mon, 18 May 2009 13:22:12 +0000 (GMT) Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com (Sun Java(tm) System Messaging Server 7u2-7.02 64bit (built Apr 16 2009)) id <0KJU00I00CTC4S00@mail-amer.sun.com> for LSARC-ext@sun.com (ORCPT LSARC-ext@sun.com); Mon, 18 May 2009 07:22:12 -0600 (MDT) Received: from [192.168.10.8] ([unknown] [76.20.56.47]) by mail-amer.sun.com (Sun Java(tm) System Messaging Server 7u2-7.02 64bit (built Apr 16 2009)) with ESMTPSA id <0KJU00MZID4WBC00@mail-amer.sun.com> for LSARC-ext@sun.com (ORCPT LSARC-ext@sun.com); Mon, 18 May 2009 07:22:09 -0600 (MDT) Date: Mon, 18 May 2009 06:20:52 -0700 From: John Fischer Subject: Re: aalib [LSARC/2009/302 FastTrack timeout 05/21/2009] In-reply-to: <4A110646.3080100@Sun.com> Sender: John.Fischer@Sun.COM To: Fan.Li@Sun.COM Cc: LSARC-ext@Sun.COM Reply-to: John.Fischer@Sun.COM Message-id: <4A1160B4.1010409@sun.com> MIME-version: 1.0 Content-type: text/plain; CHARSET=US-ASCII; format=flowed Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <200905140722.n4E7MXck028542@sac.sfbay.sun.com> <4A0C5246.1080603@sun.com> <4A0CFBBA.5050207@sun.com> <4A0D1823.6000401@Sun.com> <4A0D786D.1040702@sun.com> <4A0D8E41.20600@sun.com> <4A110646.3080100@Sun.com> User-Agent: Thunderbird 2.0.0.21 (X11/20090323) Status: RO Content-Length: 1172 +1 Li Fan wrote: > John, > > I will discuss with Jim about binaries in /usr/demo. > > For aalib-config, I have added a manpage. You can get it in attachment. > > Thanks, > -- Li Fan > > John Fischer wrote: >> Li Fan, >> >> Jim is correct that we are not concerned with this directory. >> It should be listed in the Interface table as Not an Interface. >> The source code idea came from me. The reason being is that >> many of the /usr/demo things have source code associated with >> them. If you include the source code for these demos simply >> put it within the same directory (usr/demo/aalib). You do >> not have to do this part, however. >> >> Thanks, >> >> John >> >> >> >> >> Jim Walker wrote: >>> Li Fan wrote: >>>> >>>> For those example programs in /usr/demo/aalib, do they must include >>>> source code with them? Where should these source code be placed? >>>> >>> >>> What source code? I didn't see any in your or other aalib packages. >>> If it is not normally delivered, I wouldn't deliver it. >>> >>> But /usr/demo/ and doc locations are not a concern for ARC reviewers >>> anyway. I can help you organize this if needed. >>> >>> Cheers, >>> Jim > From James.Walker@sun.com Tue May 19 16:39:55 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 n4JNdtDn025866 for ; Tue, 19 May 2009 16:39:55 -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 n4JNdsfF017333 for <@sunmail2sca.sfbay.sun.com:LSARC-ext@sun.com>; Tue, 19 May 2009 16:39:55 -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 <0KJX00E090EIBW00@nwk-avmta-1.sfbay.Sun.COM> for LSARC-ext@sun.com (ORCPT LSARC-ext@Sun.Com); Tue, 19 May 2009 16:39:54 -0700 (PDT) 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 <0KJX0035J0EHDD40@nwk-avmta-1.sfbay.Sun.COM> for LSARC-ext@sun.com (ORCPT LSARC-ext@Sun.Com); Tue, 19 May 2009 16:39:53 -0700 (PDT) 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 n4JNdrHO026646 for ; Tue, 19 May 2009 23:39:53 +0000 (GMT) Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com (Sun Java(tm) System Messaging Server 7u2-7.02 64bit (built Apr 16 2009)) id <0KJX0090009X1U00@mail-amer.sun.com> for LSARC-ext@Sun.Com (ORCPT LSARC-ext@Sun.Com); Tue, 19 May 2009 17:39:53 -0600 (MDT) Received: from [172.20.25.153] ([unknown] [172.20.25.153]) by mail-amer.sun.com (Sun Java(tm) System Messaging Server 7u2-7.02 64bit (built Apr 16 2009)) with ESMTPSA id <0KJX006700EG9AF0@mail-amer.sun.com> for LSARC-ext@Sun.Com (ORCPT LSARC-ext@Sun.Com); Tue, 19 May 2009 17:39:53 -0600 (MDT) Date: Tue, 19 May 2009 17:51:09 -0600 From: Jim Walker Subject: Re: aalib [LSARC/2009/302 FastTrack timeout 05/21/2009] In-reply-to: <200905140722.n4E7MXck028542@sac.sfbay.sun.com> Sender: James.Walker@sun.com To: LSARC-ext@sun.com Cc: Fan.Li@sun.com Reply-to: James.Walker@sun.com Message-id: <4A1345ED.6000302@sun.com> Organization: Sun Microsystems, Inc. MIME-version: 1.0 Content-type: text/plain; CHARSET=US-ASCII; format=flowed Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <200905140722.n4E7MXck028542@sac.sfbay.sun.com> User-Agent: Thunderbird 2.0.0.14 (X11/20080728) Status: RO Content-Length: 304 The case was approved at todays LSARC meeting. The following files have been moved to the demo directory and the aalib-config man page has been added to the case materials. /usr/demo/aalib/aafire /usr/demo/aalib/aainfo /usr/demo/aalib/aasavefont /usr/demo/aalib/aatest Cheers, Jim