[webstack-discuss] Update Squid Proxy Server to 2.7STABLE5 [LSARC/2009/130 FastTrack timeout 03/01/2009]
Adrian Chadd wrote: > > > > I think this is O.K and does not require an ARC case since it > > > is an update in the minor version. So it would be possible to > > > integrate 2.7STABLE6 instead. > > > > 2.7.* to 2.7.* is only bug fixes correct? > > No. Can you elaborate? What is incompatible from 2.7STABLE5 to 2.7STABLE6? -- Jyri J. Virkki - jyri.virkki at sun.com - Sun Microsystems
shmux [PSARC/2009/150 FastTrack timeout 03/10/2009]
+1. This seems like it could have been self-review to me, based on the answers to the questions. -- Garrett James Walker wrote: > I'm sponsoring this familiarity case for Lily Li. The requested > release binding is minor. The man page has 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: >shmux > 1.2. Name of Document Author/Supplier: >Author: Lily Li > 1.3 Date of This Document: > 03 March, 2009 > 4. Technical Description > Shmux Check List > 1.0 Project Information > 1.1 Name of project/component > shmux > > 1.2 Author of document > Lily.Li at Sun.COM > > 2.0 Project Summary > 2.1 Project Description > shmux is program for executing the same command on many hosts in parallel. > For each target, a child process is spawned by shmux, and a shell on the > target obtained one of the supported methods: rsh, ssh, or sh. The output > produced by the children is received by shmux and either (optionally) > output > in turn to the user using an easy to read format, or written to files for > later processing making it well suited for use in scripts. > > shmux-1.0.2 will be integrated into the SFW consolidation as part of > this proposal, and will be installed as SUNWshmux. A minor release > binding is 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 > shmux [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 drive>:\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\\ id>\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 >
shmux [PSARC/2009/150 FastTrack timeout 03/10/2009]
I'm sponsoring this familiarity case for Lily Li. The requested release binding is minor. The man page has 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: shmux 1.2. Name of Document Author/Supplier: Author: Lily Li 1.3 Date of This Document: 03 March, 2009 4. Technical Description Shmux Check List 1.0 Project Information 1.1 Name of project/component shmux 1.2 Author of document Lily.Li at Sun.COM 2.0 Project Summary 2.1 Project Description shmux is program for executing the same command on many hosts in parallel. For each target, a child process is spawned by shmux, and a shell on the target obtained one of the supported methods: rsh, ssh, or sh. The output produced by the children is received by shmux and either (optionally) output in turn to the user using an easy to read format, or written to files for later processing making it well suited for use in scripts. shmux-1.0.2 will be integrated into the SFW consolidation as part of this proposal, and will be installed as SUNWshmux. A minor release binding is 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 shmux [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
epydoc [PSARC/2009/149 FastTrack timeout 03/10/2009]
I'm sponsoring this familiarity case for Jeffrey Huang. 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: epydoc 1.2. Name of Document Author/Supplier: Author: Jeffrey Huang 1.3 Date of This Document: 03 March, 2009 4. Technical Description epydoc Check List 1.0 Project Information 1.1 Name of project/component epydoc 1.2 Author of document Jeffrey.Huang at Sun.COM 2.0 Project Summary 2.1 Project Description Epydoc is a tool for generating API documentation for Python modules, based on their docstrings. Epydoc supports two output formats (HTML and PDF), and four markup languages for docstrings (Epytext, Javadoc, ReStructuredText, and plaintext). 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 epydoc - Edward Loper [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 p
[webstack-discuss] Update Squid Proxy Server to 2.7STABLE5 [LSARC/2009/130 FastTrack timeout 03/01/2009]
> >1.1. Project/Component Working Name: > > Update Squid Proxy Server to 2.7STABLE5 > >1.2. Name of Document Author/Supplier: > > Author: Rahul Nair > >1.3 Date of This Document: > > 23 February, 2009 This case timed out last Friday, there are no open issues and had a +1 from Margot, so closing it as approved. -- Jyri J. Virkki - jyri.virkki at sun.com - Sun Microsystems
[webstack-discuss] Update Squid Proxy Server to 2.7STABLE5 [LSARC/2009/130 FastTrack timeout 03/01/2009]
rahul wrote: > > | There is a security bug in 2.7STABLE5 - > | http://www.squid-cache.org/Advisories/SQUID-2009_1.txt > | > | Will you now target 2.7STABLE6 instead? > > I think this is O.K and does not require an ARC case since it > is an update in the minor version. So it would be possible to > integrate 2.7STABLE6 instead. 2.7.* to 2.7.* is only bug fixes correct? In general always integrate the latest version, which often may change from the time a case is filed to the time you eventually integrate. So most likely 2.7STABLE6, yes (unless upstream updates again before you finish integration process ;-) You do of course have to review all changes from 2.7STABLE5 to 2.7STABLE6 and make sure they are all bug fixes which do not impact compatibility of public interfaces in any way. In the unlikely event there is some problematic change, then come back to the ARC and document it for review. -- Jyri J. Virkki - jyri.virkki at sun.com - Sun Microsystems
Parted - GNU Partition Editor [PSARC/2009/145 FastTrack timeout 03/06/2009]
>Casper.Dik at Sun.COM writes: >> Specify disk (enter its number): 0 >> selecting c1t0d0 >> [disk formatted] >> Warning: Current Disk has mounted partitions. >> /dev/dsk/c1t0d0s0 is currently mounted on /a. Please see umount(1M). >> /dev/dsk/c1t0d0s1 is currently used by swap. Please see swap(1M). >> /dev/dsk/c1t0d0s7 is part of active ZFS pool export. Please see zpool(1M). >> >> Now I think gparted is aimed at "single disk systems" but do we need >> to give a warning if we change the disk with gparted? > >I thought that 'parted' was for real partitions, not Solaris slices. >Does libdiskmgt know much about the "in use" status for real >partitions? Well, certainly for EFI labeled disks. Why would these be different? "I used this free partition but now XP is gone". Casper
Parted - GNU Partition Editor [PSARC/2009/145 FastTrack timeout 03/06/2009]
>> If you port it to Solaris, do you also use libdiskmgmt? >> > >I am not using libdiskmgmt. The reason I ask this is: Specify disk (enter its number): 0 selecting c1t0d0 [disk formatted] Warning: Current Disk has mounted partitions. /dev/dsk/c1t0d0s0 is currently mounted on /a. Please see umount(1M). /dev/dsk/c1t0d0s1 is currently used by swap. Please see swap(1M). /dev/dsk/c1t0d0s7 is part of active ZFS pool export. Please see zpool(1M). Now I think gparted is aimed at "single disk systems" but do we need to give a warning if we change the disk with gparted? Casper
CPU Idle Notification [PSARC/2009/115 FastTrack timeout 02/25/2009]
I've not got time to spend on this right now... I'm very sorry. I'm leaving town for a week on Friday, and I am buried under my other work. If you can wait until after March 15 (I know, that's hard), you'll get a lot better response from me. -- Garrett Randy Fishel wrote: > On Fri, 27 Feb 2009, Artem Kachitchkine wrote: > > >> Liu, Jiang wrote: >> >>> Hi Randy, Garrent and Artem, >>> I have made some changes/enhancements to CPU idle notification PSARC >>> onepager according to kindly feedbacks from PSARC/Tesla review. Could you >>> please >>> help to review it again? The attachments is the latest PSARC onepager and a >>> diff file with previous version. The main changes include: >>> 1) Add more comments to function parameters and return value. >>> 2) Provide a suite of interfaces to access CPU idle properties instead >>> of directly accessing data structure fields in previous version.3) Add >>> constraints to call some interfaces. >>> >> Looks good to me! >> >> -Artem >> >> > > > I forgot to mention that I put Gerry's spec update and diffs in the > case directory, should someone want to re-review it (spec.txt, > spec.diff). I have also reset the timer to 3/6. I hadn't seen any > comments since Artem's, but want to give others further chance to > make any comments. > > > Randy >
Parted - GNU Partition Editor [PSARC/2009/145 FastTrack timeout 03/06/2009]
>Mark Logan writes: >> I only buried ntfsprogs because I thought it would be easier to make it >> through PSARC that way. I guess I miscalculated. I did not hack >> ntfsprogs at all, it was the easiest thing to port. I have no problem >> delivering ntfsprogs in its entirety and in /usr/bin, if that is the >> consensus. > >+1 on the project. > >If Volatile, then it'll be up to the Install people to figure out how >they're going to depend on it, so that's just delaying the matter. The open question I have is: "do we really a new profile". There's already a "File System Management". (includes commands like format, fsck, newfs, mkfs). Hm, not fdisk, though Casper
DELL RD1000 on OpenSolaris 2008.11 svn101 rc2
Hi, silverh7: can you tell me what happens when try to format or access the disk? i am not familiar with zfs, but run 'format -e' without 'label' will not destroy the data. can you put your 'format -e' result into here? i am not sure the problem is caused by the RD1000. -- This message posted from opensolaris.org
Parted - GNU Partition Editor [PSARC/2009/145 FastTrack timeout 03/06/2009]
On Tue, 2009-03-03 at 08:56 -0800, Mark Logan wrote: > James Carlson wrote: > > Garrett D'Amore writes: > > > > > I don't know about savings of effort, but if we're not making them > > > public interfaces, then I prefer them in /usr/lib/parted, where folks > > > are less likely to find them by "accident" and infer (possibly false) > > > things about their suitability for public use. > > > > > > That said, I'd hope that if we ever shipped the public ones, that this > > > project could be converted to use the public ones instead of keeping its > > > own private copies. > > > > > > > There are some questions behind what I'm asking. If these are hacked > > versions of those utilities, then I'd like to understand how we will > > deal with the 1991/061 rules. If they're not hacked, then I'm a > > little puzzled on why they're buried. It's not as if this project > > team appears to want to promise a great deal of stability for parted > > itself (they're saying "Volatile," so it can't be used easily within > > the installer), so I don't understand drawing the "support" line at > > parted itself and excepting away ntfsprogs. What support? > > > > > > I only buried ntfsprogs because I thought it would be easier to make > it through PSARC that way. I guess I miscalculated. I did not hack > ntfsprogs at all, it was the easiest thing to port. I have no problem > delivering ntfsprogs in its entirety and in /usr/bin, if that is the > consensus. +1 from me. -M
tcpdump [PSARC/2009/147 FastTrack timeout 03/10/2009]
James Carlson wrote: > What's the point? > > tcpdump is enough like snoop that it seems to me that there's not a > great reason to do this. Instead, it'd be much nicer to see wireshark > integrated (which includes a command line tool that's more powerful > than either tcpdump *or* snoop), and also have snoop yanked from the > product. > > The time spent here could be better spent elsewhere. > >> /usr/bin/tcpdump Uncommitted Executable binary file > > If this just _has to_ be integrated, I think it belongs in /usr/sbin, > just like snoop. It's administrative in nature. tcpdump is on the top 25 miss list, so I guess someone wants it. The project team will reconsider the target directory and it back to you. Cheers, Jim -- Jim Walker, http://blogs.sun.com/jwalker Sun Microsystems, Broomfield, Colorado
clisp [PSARC/2009/141 FastTrack timeout 03/05/2009]
Are we supporting a particular version of clisp? The community appears to be very active. -- Rick James Walker wrote: > I'm sponsoring this familiarity case for Charles He. The requested > release binding is minor. The man page has 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: >clisp > 1.2. Name of Document Author/Supplier: >Author: Charles He > 1.3 Date of This Document: > 26 February, 2009 > 4. Technical Description > clisp Check List > 1.0 Project Information > 1.1 Name of project/component > clisp > > 1.2 Author of document > Zheng.he at Sun.COM > > 2.0 Project Summary > 2.1 Project Description > Common Lisp is a high-level, general-purpose, object-oriented, dynamic, > functional programming language. > > CLISP is a Common Lisp implementation by Bruno Haible, then of Karlsruhe > University, and Michael Stoll, then of Munich University, both in Germany. > It implements the language described in the ANSI Common Lisp standard with > many extensions. > > CLISP includes an interpreter, a compiler, a debugger, CLOS, MOP, a > foreign > language interface, i18n, POSIX and Perl regular expressions, a socket > interface, fast bignums, arbitrary precision floats, and more. An X11 > interface is available through CLX, Garnet and CLUE/CLIO. Command line > editing is provided by readline. CLISP runs Maxima, ACL2 and many other > Common Lisp packages. > > 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 > GNU CLISP > 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 drive>:\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\\ id>\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 ne
[kerberos-discuss] Kerberos CCAPI [PSARC/2009/030 FastTrack timeout 01/22/2009]
Shawn M Emery wrote: > Rick Matthews wrote: >> Shawn, >> Correct me if I'm wrong, but I think you were going to do an >> umbrella clarifying this case. > > Yes, I'll file the umbrella case after I finish the prototype. By then > I will have a better understanding of resource requirements (memory foot > print, restart timers, files accessed, and all the other details that > were requested during the initial review). > >> Wyllys, I think this should be in "waiting needs spec" until then. > Shawn. OK, I will update it. -Wyllys
CPU Idle Notification [PSARC/2009/115 FastTrack timeout 02/25/2009]
On Fri, 27 Feb 2009, Artem Kachitchkine wrote: > Liu, Jiang wrote: > > Hi Randy, Garrent and Artem, > > I have made some changes/enhancements to CPU idle notification PSARC > > onepager according to kindly feedbacks from PSARC/Tesla review. Could you > > please > > help to review it again? The attachments is the latest PSARC onepager and a > > diff file with previous version. The main changes include: > > 1) Add more comments to function parameters and return value. > > 2) Provide a suite of interfaces to access CPU idle properties instead > > of directly accessing data structure fields in previous version.3) Add > > constraints to call some interfaces. > > Looks good to me! > > -Artem > I forgot to mention that I put Gerry's spec update and diffs in the case directory, should someone want to re-review it (spec.txt, spec.diff). I have also reset the timer to 3/6. I hadn't seen any comments since Artem's, but want to give others further chance to make any comments. Randy
[arc-discuss] [Fwd: [osol-announce] ARC cases will be unavailable on opensolaris.org for 24 hours]
Garrett D'Amore wrote: >> Looking at the schedules, either today or Thursday would be a much >> better time for this, as PSARC's weekly meeting is scheduled for >> Wednesday at 18:00 UTC (10AM PST). Cutting out access during that >> time may break the open review of (at least) "Boomer," which I expect >> to generate significant interest. >> >> I suppose that if this timing is absolutely necessary, we could find >> some other temporary means for publishing materials manually >> (cr.opensolaris.org?), but I don't know what options are possible here >> because I (the current PSARC co-chair) wasn't contacted before this >> decision was made. OK, we'll push it back until Thursday. >> In any event, we don't have much time to make these arrangements, so >> please let us know what work-arounds we'll have available for our open >> PSARC meeting. > > As the Boomer project lead, I've been almost completely unable to > publish materials on the ARC website. I've been mirroring them on > cr.opensolaris.org. > > I'd *prefer* to have Boomer materials made available on the main > website, and to have it up. But if we can't get updated materials > posted to it, then it may not matter much. > > This breakage is causing me severe heartache. :-( I can assure you it is a minor twinge compared to mine. -- Alan Burlison --
[kerberos-discuss] Kerberos CCAPI [PSARC/2009/030 FastTrack timeout 01/22/2009]
On Tue, Mar 03, 2009 at 10:43:29AM -0800, Henry B. Hotz wrote: > Perhaps I said this before, but when you implement CCAPI, you also > need to make sure that Java is able to use CCAPI ccaches. (Apple > didn't do that. ;-) Done, because JGSS now has a JNI bridge to libgss.
Parted - GNU Partition Editor [PSARC/2009/145 FastTrack timeout 03/06/2009]
Casper.Dik at Sun.COM writes: > Specify disk (enter its number): 0 > selecting c1t0d0 > [disk formatted] > Warning: Current Disk has mounted partitions. > /dev/dsk/c1t0d0s0 is currently mounted on /a. Please see umount(1M). > /dev/dsk/c1t0d0s1 is currently used by swap. Please see swap(1M). > /dev/dsk/c1t0d0s7 is part of active ZFS pool export. Please see zpool(1M). > > Now I think gparted is aimed at "single disk systems" but do we need > to give a warning if we change the disk with gparted? I thought that 'parted' was for real partitions, not Solaris slices. Does libdiskmgt know much about the "in use" status for real partitions? -- James Carlson, Solaris Networking Sun Microsystems / 35 Network Drive71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677
[kerberos-discuss] Kerberos CCAPI [PSARC/2009/030 FastTrack timeout 01/22/2009]
Rick Matthews wrote: > Shawn, > Correct me if I'm wrong, but I think you were going to do an > umbrella clarifying this case. Yes, I'll file the umbrella case after I finish the prototype. By then I will have a better understanding of resource requirements (memory foot print, restart timers, files accessed, and all the other details that were requested during the initial review). > Wyllys, I think this should be in "waiting needs spec" until then. Shawn. -- > On 02/04/09 12:16, Rick Matthews wrote: >> Shawn, >> I think there continues to be lack of understanding on this >> fast-track. Your suggestion of an umbrella >> case is a good one. I'd like to de-rail this case until that umbrella >> has occurred. >> -- >> Rick >> >> > -- > - > Rick Matthews email: Rick.Matthews at sun.com > Sun Microsystems, Inc. phone:+1(651) 554-1518 > 1270 Eagan Industrial Road phone(internal): 54418 > Suite 160 fax: +1(651) 554-1540 > Eagan, MN 55121-1231 USAmain: +1(651) 554-1500 > - >
[kerberos-discuss] Kerberos CCAPI [PSARC/2009/030 FastTrack timeout 01/22/2009]
Henry B. Hotz wrote: > Perhaps I said this before, but when you implement CCAPI, you also > need to make sure that Java is able to use CCAPI ccaches. (Apple > didn't do that. ;-) Yes, I've already contacted the Java security group and the contact there is aware of these changes and had said that they would support it. Shawn. -- > On Mar 3, 2009, at 10:08 AM, Rick Matthews wrote: > >> Shawn, >> Correct me if I'm wrong, but I think you were going to do an >> umbrella clarifying this case. >> Wyllys, I think this should be in "waiting needs spec" until then. >> Thanks >> -- >> On 02/04/09 12:16, Rick Matthews wrote: >>> >>> Shawn, >>> I think there continues to be lack of understanding on this >>> fast-track. Your suggestion of an umbrella >>> case is a good one. I'd like to de-rail this case until that >>> umbrella has occurred. >>> -- >>> Rick >> -- >> - >> Rick Matthews email: Rick.Matthews at sun.com >> Sun Microsystems, Inc. phone:+1(651) 554-1518 >> 1270 Eagan Industrial Road phone(internal): 54418 >> Suite 160 fax: +1(651) 554-1540 >> Eagan, MN 55121-1231 USAmain: +1(651) 554-1500 >> - > > -- > The opinions expressed in this message are mine, > not those of Caltech, JPL, NASA, or the US Government. > Henry.B.Hotz at jpl.nasa.gov, or hbhotz at oxy.edu > > >
EOF of xorgcfg & xorgconfig [PSARC/2009/148 FastTrack timeout 03/10/2009]
I am sponsoring this fast-track on behalf of the X11 Engineering Team. The timeout is set for Monday, March 10, 2009. -Alan Coopersmith- alan.coopersmith at sun.com Sun Microsystems, Inc. - X Window System Engineering 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: EOF of xorgcfg & xorgconfig 1.2. Name of Document Author/Supplier: Author: Alan Coopersmith 1.3 Date of This Document: 03 March, 2009 4. Technical Description The X.Org community recently released Xorg server version 1.6. This version no longer includes the xorgconfig text UI or xorgcfg GUI for creating and editing xorg.conf files. These utilities had not been kept up to date with advances in Xorg configuration in recent releases, and were mostly unmaintained and unused in the community, since most Linux distros used their own configuration tools. Solaris has defaulted to autoconfiguration for Xorg, and improvements there have continually reduced the need for xorg.conf files, and when they are needed, reduced the amount of boilerplate needed to modify the auto-configuration. When overriding the configuration settings is necessary, a configuration file may still be created with Xorg -configure. (Users of nvidia graphics additionally may use the nvidia-provided configuration tools nvidia-settings and nvidia-xconfig.) This case announces the EOF of, and removes, the xorgcfg & xorgconfig utilities for creating or updating xorg.conf configuration files. This case delivers in two phases: 1) In a patch release, announces the obsolesence of and future removal plans for, xorgcfg & xorgconfig. Exported Interfaces: /usr/X11/bin/xorgconfig ObsoletePSARC 2004/184 (was External) /usr/X11/bin/xorgcfgObsoletePSARC 2005/225 (path was Stable, options Volatile) 2) In a minor release, removes the following from the X consolidation: The entire SUNWxorg-cfg package, including /usr/X11/bin/xorgcfg From SUNWxorg-server: /usr/X11/bin/xorgconfig From SUNWxwplr: /etc/security/exec_attr entries for xorgconfig & xorgcfg Exported Interfaces: /usr/X11/bin/xorgconfig Removed /usr/X11/bin/xorgcfgRemoved 6. Resources and Schedule 6.4. Steering Committee requested information 6.4.1. Consolidation C-team Name: X Consolidation (Desktop C-Team) 6.5. ARC review type: FastTrack 6.6. ARC Exposure: open
Parted - GNU Partition Editor [PSARC/2009/145 FastTrack timeout 03/06/2009]
On Tue, Mar 03, 2009 at 03:39:24PM -0500, James Carlson wrote: > Casper.Dik at Sun.COM writes: > > Specify disk (enter its number): 0 > > selecting c1t0d0 > > [disk formatted] > > Warning: Current Disk has mounted partitions. > > /dev/dsk/c1t0d0s0 is currently mounted on /a. Please see umount(1M). > > /dev/dsk/c1t0d0s1 is currently used by swap. Please see swap(1M). > > /dev/dsk/c1t0d0s7 is part of active ZFS pool export. Please see zpool(1M). > > > > Now I think gparted is aimed at "single disk systems" but do we need > > to give a warning if we change the disk with gparted? > > I thought that 'parted' was for real partitions, not Solaris slices. > Does libdiskmgt know much about the "in use" status for real > partitions? Given xVM and VirtualBox, shouldn't it?
Parted - GNU Partition Editor [PSARC/2009/145 FastTrack timeout 03/06/2009]
Scott Rotondo wrote: > Phi Tran wrote: >> Casper.Dik at Sun.COM wrote: >>> The open question I have is: "do we really a new profile". There's >>> already a "File System Management". (includes commands like format, >>> fsck, newfs, mkfs). Hm, not fdisk, though >>> >> >> I agree that the "File System Management" profile should be used. A >> new profile will not be needed since auths will not be used. >> >> Phi > > Just as an aside, if you were adding new authorizations, there's no > reason you couldn't add them to the File System Management profile. Yes, I was mistaken. > > I'm glad that you've decided to use an existing profile and not add new > authorizations. I just wanted to clarify that these are two separate > decisions. Got it. Thanks. Phi
PSARC 2009/138 VLAN ID for virtual interface
Based on current discussion here, the specification is updated. -Cecilia
PSARC 2009/137 Bandwidth Limit for Virtual Interface
Based on current discussion here, the specification and documents are updated. -Cecilia
Parted - GNU Partition Editor [PSARC/2009/145 FastTrack timeout 03/06/2009]
Casper.Dik at Sun.COM wrote: >> Casper.Dik at Sun.COM writes: >> >>> Specify disk (enter its number): 0 >>> selecting c1t0d0 >>> [disk formatted] >>> Warning: Current Disk has mounted partitions. >>> /dev/dsk/c1t0d0s0 is currently mounted on /a. Please see umount(1M). >>> /dev/dsk/c1t0d0s1 is currently used by swap. Please see swap(1M). >>> /dev/dsk/c1t0d0s7 is part of active ZFS pool export. Please see zpool(1M). >>> >>> Now I think gparted is aimed at "single disk systems" but do we need >>> to give a warning if we change the disk with gparted? >>> >> I thought that 'parted' was for real partitions, not Solaris slices. >> Does libdiskmgt know much about the "in use" status for real >> partitions? >> > > Well, certainly for EFI labeled disks. Why would these be different? > > "I used this free partition but now XP is gone". > > Casper > > Parted has code in it to prevent modification of in-use partitions. It calls an OS stub before doing anything dangerous. I will use libdiskmgmt to fill in that stub for Solaris. Mark
Parted - GNU Partition Editor [PSARC/2009/145 FastTrack timeout 03/06/2009]
Phi Tran wrote: > Casper.Dik at Sun.COM wrote: >> The open question I have is: "do we really a new profile". There's >> already a "File System Management". (includes commands like format, >> fsck, newfs, mkfs). Hm, not fdisk, though >> > > I agree that the "File System Management" profile should be used. A > new profile will not be needed since auths will not be used. > > Phi Just as an aside, if you were adding new authorizations, there's no reason you couldn't add them to the File System Management profile. I'm glad that you've decided to use an existing profile and not add new authorizations. I just wanted to clarify that these are two separate decisions. Scott -- Scott Rotondo Principal Engineer, Solaris Security Technologies President, Trusted Computing Group Phone/FAX: +1 408 850 3655 (Internal x68278)
tcpdump [PSARC/2009/147 FastTrack timeout 03/10/2009]
James Walker writes: > 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 Shouldn't tcpdump be added to the Network Management profile in /etc/security/exec_attr, just like snoop is? Rainer -- - Rainer Orth, Faculty of Technology, Bielefeld University
Parted - GNU Partition Editor [PSARC/2009/145 FastTrack timeout 03/06/2009]
Phi Tran writes: > >> Not sure if we're reviewing these bits here (isn't that for the later > >> LSARC case?), but, as a nit, I wouldn't make package names > >> "Committed," but rather Uncommitted. > > I thought package names should be Committed due to this document: > http://sac.sfbay.sun.com/cgi-bin/bp.cgi?NAME=stability.bp > Package names are Committed because other packages and customer > Jumpstart profiles must reference them. Interesting point; that BP should probably be revisited. Package dependencies are a bit in the air right now. In any event, I'd be happy with any value here. We've used "Uncommitted" in many cases, but I don't think it's actually significant, so it's just a nit. -- James Carlson, Solaris Networking Sun Microsystems / 35 Network Drive71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677
2009/139 CIFS CATIA Translation Share Property
Those questions don't seem relevant to this fasttrack. How a name in the file system came to contain a / would be an issue for the local operating system and/or the local file system. For the purpose of this fasttrack, if a file name returned by the local file system contained a / it would be converted, as indicated by the translation table, to 0x00f8 before that name is propagated to a Windows client. The left column of the table represents the list of characters that are illegal in Windows file names. There is no requirement that these characters be legal on any file system. Alan -- This message posted from opensolaris.org
Parted - GNU Partition Editor [PSARC/2009/145 FastTrack timeout 03/06/2009]
On Mon, 2009-03-02 at 14:38 -0800, Phi Tran wrote: ... > 4.2.3. ntfsprogs > > Parted uses ntfsprogs [3] to resize, create or delete NTFS disk > partitions and filesystems. ntfsprogs [3] is a collection of > command-line utilities, one utility for each operation, e.g. > ntfsresize and mkntfs. > > ntfsprogs required very few changes to port to Solaris. ... > > 4.3. Interfaces Exported > > Interface NameClassificationComments > --- --- > SUNWpartedCommitted Package name > (Phase 1) > /usr/share/man/man8/parted.8 Volatile Manual page (Phase > 1) > /usr/bin/parted Volatile Parted launcher > shell script (Phase 1) > /usr/lib/parted/partedVolatile Parted application > (Phase 1) > /usr/lib/parted/mkntfsVolatile ntfsprogs > application (Phase 1) > /usr/lib/parted/ntfsresizeVolatile ntfsprogs > application (Phase 1) > /usr/lib/parted/ntfsfix Volatile ntfsprogs > application (Phase 1) > /usr/lib/parted/ntfsclone Volatile ntfsprogs > application (Phase 1) Was there any consideration given to delivering ntfsprogs as public utilities (rather than project private)? I see that a limited sub-set of ntfsprogs is being delivered, no doubt because thats the sub-set that gparted uses, but if ntfsprogs were to be delivered in /usr/[s]bin it would be great to see the other utilities included (ntfscp, ntfsls, ntfscat ...). I expect the demand for user-accessible ntfsprogs will increase once ntfs-3g is delivered. -M
2009/139 CIFS CATIA Translation Share Property
dcragun wrote: > > Date: Thu, 26 Feb 2009 08:36:01 -0500 From: James Carlson > > > > Jordan Brown writes: > > > > I am sponsoring the following for fast track approval. The timer > > > > expires Wednesday 4 March 2009. > > > > You didn't specify a release binding or a stability level for the new > > interfaces. > > > > I'll guess at "patch/micro" and "Committed," and give it a +1 > > (including the likely not-so-interesting '/' translation). > > So what is supposed to happen if a process tries to access or create a > file with a pathname containing a '/' character? When creating a file, > when is a '/' a directory separator and when is it a character in a > filename? That's up to to the local operating system and the local file system, and has nothing to do with this fasttrack. For the purpose of this fasttrack, how a name in the file system came to contain a / is not relevant. For this fasttrack, if a file name returned by the local file system contained a / it would be converted, as indicated by the translation table to 0x00f8, before that name is propagated to a Windows client. The left column of the table represents the list of characters that are illegal in Windows file names. There is no requirement that these characters be legal on any file system. > If I have a file with filename "a/b" and a directory with filename "a" > and a file in that directory with filename "b", which file does an > open() of "a/b" open for me? If there is no directory "a", but there is > a filename "a/b", will open() of "a/b" give me ENOENT because "a" isn't > an existing directory. (Note that according to the standards, the > command: > printf "%s/%s" $(dirname a/b) $(basename a/b) > is supposed to print "a/b", not "./a/b" (i.e., they work on strings, not > on pathnames.) Those questions don't seem relevant to this fasttrack. Alan
Parted - GNU Partition Editor [PSARC/2009/145 FastTrack timeout 03/06/2009]
Mark Logan writes: > I only buried ntfsprogs because I thought it would be easier to make it > through PSARC that way. I guess I miscalculated. I did not hack > ntfsprogs at all, it was the easiest thing to port. I have no problem > delivering ntfsprogs in its entirety and in /usr/bin, if that is the > consensus. +1 on the project. If Volatile, then it'll be up to the Install people to figure out how they're going to depend on it, so that's just delaying the matter. -- James Carlson, Solaris Networking Sun Microsystems / 35 Network Drive71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677
Parted - GNU Partition Editor [PSARC/2009/145 FastTrack timeout 03/06/2009]
Mark Logan writes: > I only buried ntfsprogs because I thought it would be easier to make it > through PSARC that way. I guess I miscalculated. I did not hack > ntfsprogs at all, it was the easiest thing to port. I have no problem > delivering ntfsprogs in its entirety and in /usr/bin, if that is the > consensus. Thanks; I think that's a big improvement. For what it's worth, "making it through PSARC" is not the best approach to take. ARC review is a peer technical review, just like code or design review. The fact that it has some formal infrastructure support is just thanks to some long-ago forethought about the problem. It could have been done for other reviews as well. The best way to manage it is to make good engineering choices, then explain what you're doing, just as you'd do for any other review. If that means you're delivering two or three or twenty separate FOSS packages in a single project, then that's fine. Do it if it makes sense. > Also maybe I need to rethink the Volatile stability. I wrongly assumed > that FOSS had to be Volatile. Also the goal is to get the OpenSolaris > installer to use either Parted or GParted, their choice, so I need to > choose the correct stability to achieve that. If it's the GUI that they'll use, I'd expect that all you need is to have the path name '/usr/sbin/gparted' made Committed (probably not this case). If it's the command line, then it's '/usr/sbin/parted' plus perhaps one or two of the command-line options. In any event, choosing stability level is always a mixture of things: - How often it's expected to change. (For many things, this can be inferred from how often it has changed in the past.) - How much change is expected. (Just little tweaks and new features each month, or major breakage every other day?) - How you'll deal with change. (If they break it upstream, do you want to fork? Help them fix it? Freeze our delivered bits and never upgrade? Or just deliver the brokenness to your users?) - How your customers or users will deal with change. (Is someone building software on top of it? What individual parts do they depend on? Are there any parts that are unimportant and thus changeable?) The *one* thing that isn't in that mix is the author. Interface stability and thus architectural review doesn't depend on who wrote the code. "FOSS" and "Volatile" really have little or nothing to do with each other. (In fact, it was the conflation of "Open Source" with "External" in the old taxonomy that forced us to rewrite it and invent "Volatile." It's a little disheartening to hear that the same aliasing is going on.) -- James Carlson, Solaris Networking Sun Microsystems / 35 Network Drive71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677
[kerberos-discuss] Kerberos CCAPI [PSARC/2009/030 FastTrack timeout 01/22/2009]
Shawn, Correct me if I'm wrong, but I think you were going to do an umbrella clarifying this case. Wyllys, I think this should be in "waiting needs spec" until then. Thanks -- On 02/04/09 12:16, Rick Matthews wrote: > Shawn, > I think there continues to be lack of understanding on this > fast-track. Your suggestion of an umbrella > case is a good one. I'd like to de-rail this case until that umbrella > has occurred. > -- > Rick > > -- - Rick Matthews email: Rick.Matthews at sun.com Sun Microsystems, Inc. phone:+1(651) 554-1518 1270 Eagan Industrial Road phone(internal): 54418 Suite 160 fax: +1(651) 554-1540 Eagan, MN 55121-1231 USAmain: +1(651) 554-1500 -
LSARC/2009/127 - JDOM
+1 Rick Matthews wrote: > Per last weeks meeting, I have modified the case materials as follows: >-) Added the package name to the exported interfaces. >-) Added the jar file to the exported interfaces. >-) Deleted the interface table from the FOSS checklist, and > referred to the >proposal.txt >-) Gathered the FastTrack submission, FOSS checklist and man page > into a file >called Proposal.txt (in the materials directory). > Please inform myself or Vivek if this is less than required. >
LSARC/2009/126 - xom
+1 Thanks Margot Rick Matthews wrote: > Per last weeks meeting, I have modified the case materials as follows: >-) Added the package name to the exported interfaces. >-) Added the jar file to the exported interfaces. >-) Deleted the interface table from the FOSS checklist, and > referred to the >proposal.txt >-) Gathered the FastTrack submission, FOSS checklist and man page > into a file >called Proposal.txt (in the materials directory). > Please inform myself or Vivek if this is less than required. >
Parted - GNU Partition Editor [PSARC/2009/145 FastTrack timeout 03/06/2009]
Garrett D'Amore writes: > I don't know about savings of effort, but if we're not making them > public interfaces, then I prefer them in /usr/lib/parted, where folks > are less likely to find them by "accident" and infer (possibly false) > things about their suitability for public use. > > That said, I'd hope that if we ever shipped the public ones, that this > project could be converted to use the public ones instead of keeping its > own private copies. There are some questions behind what I'm asking. If these are hacked versions of those utilities, then I'd like to understand how we will deal with the 1991/061 rules. If they're not hacked, then I'm a little puzzled on why they're buried. It's not as if this project team appears to want to promise a great deal of stability for parted itself (they're saying "Volatile," so it can't be used easily within the installer), so I don't understand drawing the "support" line at parted itself and excepting away ntfsprogs. What support? -- James Carlson, Solaris Networking Sun Microsystems / 35 Network Drive71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677
Parted - GNU Partition Editor [PSARC/2009/145 FastTrack timeout 03/06/2009]
On Tue, Mar 03, 2009 at 09:06:45AM -0800, Garrett D'Amore wrote: > That's not what the project team decided to do. Project teams do get to make such decisions today. But it's worth asking "why?" if asking causes them to re-think the matter. > The project team hasn't committed to supporting ntfsprogs for other > uses. While it would have been nice of them to do so, they didn't, and > I don't think its PSARC's role to require them to do so either. If every i-team did this we'd end up with a truly ugly, unfriendly system, so at some point the ARC has to consider whether to let project teams get away with this. The ARC ought to at least raise the issue in the hopes of getting the i-team to reconsider, or, if nothing else, to document the rationale for choosing to hide away FOSS dependencies. The latter might be helpful to future i-teams working in the same area.
Parted - GNU Partition Editor [PSARC/2009/145 FastTrack timeout 03/06/2009]
Casper.Dik at Sun.COM wrote: > >> If it's not setuid, then it won't gain any privileges just because you >> define these authorizations. You would want to include the command in an >> RBAC profile so that users who have the profile can run it with the >> necessary privileges. In that case, there is probably no reason for the >> additional authorization check. >> > > > And I'd prefer that: a exec_attr and a RBAC profile; if you want to check > for the authorization, you will need to change more to the source. > I will add it to the File System Management profile as you suggested. > I'm assuming that it will not automatically "work" on Solaris. > > If you port it to Solaris, do you also use libdiskmgmt? > I am not using libdiskmgmt. Mark > Casper > >
Parted - GNU Partition Editor [PSARC/2009/145 FastTrack timeout 03/06/2009]
Casper.Dik at Sun.COM wrote: >> Mark Logan writes: >>> I only buried ntfsprogs because I thought it would be easier to make it >>> through PSARC that way. I guess I miscalculated. I did not hack >>> ntfsprogs at all, it was the easiest thing to port. I have no problem >>> delivering ntfsprogs in its entirety and in /usr/bin, if that is the >>> consensus. >> +1 on the project. >> >> If Volatile, then it'll be up to the Install people to figure out how >> they're going to depend on it, so that's just delaying the matter. > > > The open question I have is: "do we really a new profile". There's > already a "File System Management". (includes commands like format, > fsck, newfs, mkfs). Hm, not fdisk, though > I agree that the "File System Management" profile should be used. A new profile will not be needed since auths will not be used. Phi
[arc-discuss] [Fwd: [osol-announce] ARC cases will be unavailable on opensolaris.org for 24 hours]
[Thanks to Alan Coopersmith for forwarding the original message.] Alan Burlison writes: > Our investigations into the recent stability issues with OpenSolaris.org > have identified the ARC case archive on the site as a potential problem > area. As part of the analysis we will be making all pages under the ARC > community, including ARC case files, unavailable for 24 hours as of > 9:00am UTC on Wednesday March 4th. Looking at the schedules, either today or Thursday would be a much better time for this, as PSARC's weekly meeting is scheduled for Wednesday at 18:00 UTC (10AM PST). Cutting out access during that time may break the open review of (at least) "Boomer," which I expect to generate significant interest. I suppose that if this timing is absolutely necessary, we could find some other temporary means for publishing materials manually (cr.opensolaris.org?), but I don't know what options are possible here because I (the current PSARC co-chair) wasn't contacted before this decision was made. In any event, we don't have much time to make these arrangements, so please let us know what work-arounds we'll have available for our open PSARC meeting. -- James Carlson, Solaris Networking Sun Microsystems / 35 Network Drive71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677
Parted - GNU Partition Editor [PSARC/2009/145 FastTrack timeout 03/06/2009]
Garrett D'Amore writes: > Mark Phalan wrote: > > Was there any consideration given to delivering ntfsprogs as public > > utilities (rather than project private)? > > I see that a limited sub-set of ntfsprogs is being delivered, no doubt > > because thats the sub-set that gparted uses, but if ntfsprogs were to be > > delivered in /usr/[s]bin it would be great to see the other utilities > > included (ntfscp, ntfsls, ntfscat ...). I expect the demand for > > user-accessible ntfsprogs will increase once ntfs-3g is delivered. > > > > I think such utilities might be useful, but its not this project. OK, then, I think that begs two questions: - If the ntfsprogs utilities were already included in the product as a supported feature, would this project use them as-is or would it still need to ship its own private variants? - Is there some savings in effort for locating the binaries in /usr/lib/parted versus in /usr/sbin? -- James Carlson, Solaris Networking Sun Microsystems / 35 Network Drive71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677
[kerberos-discuss] Kerberos CCAPI [PSARC/2009/030 FastTrack timeout 01/22/2009]
Perhaps I said this before, but when you implement CCAPI, you also need to make sure that Java is able to use CCAPI ccaches. (Apple didn't do that. ;-) On Mar 3, 2009, at 10:08 AM, Rick Matthews wrote: > Shawn, > Correct me if I'm wrong, but I think you were going to do an > umbrella clarifying this case. > Wyllys, I think this should be in "waiting needs spec" until then. > Thanks > -- > On 02/04/09 12:16, Rick Matthews wrote: >> >> Shawn, >> I think there continues to be lack of understanding on this fast- >> track. Your suggestion of an umbrella >> case is a good one. I'd like to de-rail this case until that >> umbrella has occurred. >> -- >> Rick > -- > - > Rick Matthews email: Rick.Matthews at sun.com > Sun Microsystems, Inc. phone:+1(651) 554-1518 > 1270 Eagan Industrial Road phone(internal): 54418 > Suite 160 fax: +1(651) 554-1540 > Eagan, MN 55121-1231 USAmain: +1(651) 554-1500 > - -- The opinions expressed in this message are mine, not those of Caltech, JPL, NASA, or the US Government. Henry.B.Hotz at jpl.nasa.gov, or hbhotz at oxy.edu
Parted - GNU Partition Editor [PSARC/2009/145 FastTrack timeout 03/06/2009]
SUNWgparted Committed Package name (Phase 2) /usr/share/man/man8/gparted.8 Volatile Manual page (Phase 2) /usr/bin/gparted Volatile GParted application (Phase 2) >> >> Not sure if we're reviewing these bits here (isn't that for the later >> LSARC case?), but, as a nit, I wouldn't make package names >> "Committed," but rather Uncommitted. I thought package names should be Committed due to this document: http://sac.sfbay.sun.com/cgi-bin/bp.cgi?NAME=stability.bp Package names are Committed because other packages and customer Jumpstart profiles must reference them. Phi
Parted - GNU Partition Editor [PSARC/2009/145 FastTrack timeout 03/06/2009]
On Tue, Mar 03, 2009 at 08:13:00AM -0800, Garrett D'Amore wrote: > I don't know about savings of effort, but if we're not making them > public interfaces, then I prefer them in /usr/lib/parted, where folks > are less likely to find them by "accident" and infer (possibly false) > things about their suitability for public use. I think it takes more effort to argue over whether to make them public or not than it takes to just make them public. If the i-team doesn't want to support the bloody things then they should just be made Volatile -- they'd still be useful, so why hide them? > That said, I'd hope that if we ever shipped the public ones, that this > project could be converted to use the public ones instead of keeping its > own private copies. More work for the next i-team. Why is that good? If every bit of FOSS was integrated like this we'd end up with a mish-mash of stuff in /usr/lib that third parties would *still* find *and* use -- that sounds like a negative architectural externality of letting this case through as-is. IMO, if integrating FOSS X requires integrating FOSS Y, then integrate both -- don't hide FOSS Y.
Parted - GNU Partition Editor [PSARC/2009/145 FastTrack timeout 03/06/2009]
>If it's not setuid, then it won't gain any privileges just because you >define these authorizations. You would want to include the command in an >RBAC profile so that users who have the profile can run it with the >necessary privileges. In that case, there is probably no reason for the >additional authorization check. And I'd prefer that: a exec_attr and a RBAC profile; if you want to check for the authorization, you will need to change more to the source. I'm assuming that it will not automatically "work" on Solaris. If you port it to Solaris, do you also use libdiskmgmt? Casper
Parted - GNU Partition Editor [PSARC/2009/145 FastTrack timeout 03/06/2009]
>+1. > >Do we really need to introduce a new set of RBAC authorizations for >this? I'd have guessed that low-level sys_devices or whatever access >would have been sufficient. You'll still need a profile and possible an exec_attr entry too. But is there any reason not to add this to the "File System Management" profile? Casper
Libunique for OpenSolaris [LSARC/2009/142 FastTrack timeout 03/10/2009]
Margot, On Mon, 2009-03-02 at 16:30 -0800, Margot Miller wrote: > The UNIQUE_BACKEND environment variable should be > added to exported interface table. Added in exported interface table. Exported InterfacesClassificationComments -------- SUNWlibunique Uncommitted Package name SUNWlibunique-develUncommitted Package name /usr/lib/pkgconfig/unique-1.0.pc Uncommitted pkg-config file /usr/lib/amd64/pkgconfig/unique-1.0.pc Uncommitted 64-bit pkg-config file /usr/lib/libunique-1.0.so.0Volatile C library /usr/lib/amd64/libunique-1.0.so.0 Volatile 64-bit C library /usr/include/unique-1.0/unique Volatile header files /usr/share/gtk-doc/html/unique Volatile gtk-doc files UNIQUE_BACKEND environment variableVolatile environment variable to define backend > Please add the man page to the materials. And I assume > that the UNIQUE_BACKEND is documented in the man page? Yes. Attach the man page. Thanks, Halton. -- next part -- C Library Functions libunique-1.0(3) NAME libunique-1.0 - A library for writing single instance appli- cations DESCRIPTION libunique-1.0 is a library for writing single instance applications. If you launch a single instance application twice, the second instance will exit quietly or will send a message to the running instance. libunique-1.0 makes it easy to write these kind of applica- tions, by providing a base class, taking care of all the IPC machinery needed to send messages to a running instance, and also handling startup notification. libunique-1.0 supports two IPC backends: bacon and dbus. When dbus is used, the messages are transmitted through D- Bus private channel. When bacon is used, libunique-1.0 uses PF_UNIX family socket(3head) to allow communications between processes on the same machine. ENVIRONMENT VARIABLES See environ(5) for descriptions of environment variables. UNIQUE_BACKEND The default backend is dbus. User can over- ride the default backend by setting the UNIQUE_BACKEND environment variable with the name of the desired backend. FILES The following files are used by this library: /usr/lib/libunique-1.0.so API shared library /usr/share/gtk-doc/html/unique Location of developer documentation ATTRIBUTES See attributes(5) for descriptions of the following attri- butes: SunOS 5.11 Last change: 27 Feb 20091 C Library Functions libunique-1.0(3) | ATTRIBUTE TYPE| ATTRIBUTE VALUE | |_|_| | Availability| SUNWlibunique | |_|_| | Interface stability | Volatile| |_|_| SEE ALSO attributes(5), environ(5),gnome-interfaces(5), socket(3head) NOTES Written by Halton Huo, Sun Microsystems Inc., 2009. SunOS 5.11 Last change: 27 Feb 20092
Libunique for OpenSolaris [LSARC/2009/142 FastTrack timeout 03/10/2009]
On Mon, 2009-03-02 at 14:17 -0800, John Fischer wrote: > +1 assuming that 64-bit versions of the library and pkg-config file. John, Added in exported interfaces. Thanks, Halton.
mrtg [PSARC/2009/120 FastTrack timeout 02/27/2009]
Thanks Jim, then I'll start to prepare the C-Team checklist. Lizhong Jim Walker wrote: > Lizhong Li wrote: >>> James Carlson wrote: >>> >>> Should probably say something about where passwords are stored, just >>> for completeness. >>> >> Generally command 'cfgmaker' is used to introduce a config file for >> 'mrtg' like this: >> # cfgmaker public at 192.168.1.100 > mrtg.cfg >> So the 'community' password is stored in the file mrtg.cfg , it's >> owned by root and could be saved in any location. The clients from >> web can't see this file since they can just access the files allowed >> by apache. > > I added this information to a Notes section in the proposal.txt file, > and marked this case closed approved. > > Cheers, > Jim > -- Thanks, Lizhong
Parted - GNU Partition Editor [PSARC/2009/145 FastTrack timeout 03/06/2009]
Nicolas Williams wrote: > On Tue, Mar 03, 2009 at 09:06:45AM -0800, Garrett D'Amore wrote: > >> That's not what the project team decided to do. >> > > Project teams do get to make such decisions today. But it's worth > asking "why?" if asking causes them to re-think the matter. > > >> The project team hasn't committed to supporting ntfsprogs for other >> uses. While it would have been nice of them to do so, they didn't, and >> I don't think its PSARC's role to require them to do so either. >> > > If every i-team did this we'd end up with a truly ugly, unfriendly > system, so at some point the ARC has to consider whether to let project > teams get away with this. > > The ARC ought to at least raise the issue in the hopes of getting the > i-team to reconsider, or, if nothing else, to document the rationale for > choosing to hide away FOSS dependencies. The latter might be helpful to > future i-teams working in the same area. > Agree on all points. The question was valid, and in this case it sounds like the project team has agreed to change their plans. As long as its simply ARC asking project teams for their rationale, and not *requiring* project teams to do something their disinclined to do. -- Garrett
Parted - GNU Partition Editor [PSARC/2009/145 FastTrack timeout 03/06/2009]
James Carlson wrote: > Phi Tran writes: > >>> GNU Partition Editor (Parted) [1] is a command-line application that allows >>> you to resize, create or delete disk partitions and filesystems. The goal >>> is to put it on the OpenSolaris Live CD. That way one could shrink the >>> Vista or other NTFS partition and create space to install OpenSolaris. Many >>> x86 machines come preinstalled with Vista. The availability of Parted would >>> increase adoption of OpenSolaris by making it easier to create a dual-boot >>> environment. >>> > > First of all: "yay!" > > And I agree with the others about RBAC (should be exec_attr) and I > have the same questions about ntfsprogs (why not just deliver this?). > Thanks for the support. I will change it to exec_attr. > >>> GParted is Phase 2 of this project. There will be a separate LSARC case. >>> > > Which one will the installer use? I would have expected that it uses > gparted. > We talked to the OpenSolaris Installation people and they haven't decided which one they want to use yet. > >>> /usr/share/man/man8/parted.8 Volatile Manual page (Phase 1) >>> > > This belongs in 1M. There's no "8" on Solaris. > There is an "8" in Nevada. But I will move them if that is the right thing to do. > >>> /usr/bin/parted Volatile Parted launcher shell >>> script (Phase 1) >>> > > It would be nice if we could stick to putting administrative utilities > into /usr/sbin. Is that possible, or is there something out there > that depends on having '/usr/bin/parted' leading to the command line > version of this utility? > I didn't think about that. /usr/sbin does sound like a better choice. I will make that change. > >>> SUNWgparted Committed Package name (Phase 2) >>> /usr/share/man/man8/gparted.8 Volatile Manual page (Phase 2) >>> /usr/bin/gparted Volatile GParted application >>> (Phase 2) >>> > > Not sure if we're reviewing these bits here (isn't that for the later > LSARC case?), but, as a nit, I wouldn't make package names > "Committed," but rather Uncommitted. > > And the path for gparted really should be Committed. There's no > obvious way it could change other than by removal. > I will make both of these changes. Mark
Parted - GNU Partition Editor [PSARC/2009/145 FastTrack timeout 03/06/2009]
Mark Logan wrote: > James Carlson wrote: >> Garrett D'Amore writes: >> >>> I don't know about savings of effort, but if we're not making them >>> public interfaces, then I prefer them in /usr/lib/parted, where folks >>> are less likely to find them by "accident" and infer (possibly false) >>> things about their suitability for public use. >>> >>> That said, I'd hope that if we ever shipped the public ones, that this >>> project could be converted to use the public ones instead of keeping its >>> own private copies. >>> >> >> There are some questions behind what I'm asking. If these are hacked >> versions of those utilities, then I'd like to understand how we will >> deal with the 1991/061 rules. If they're not hacked, then I'm a >> little puzzled on why they're buried. It's not as if this project >> team appears to want to promise a great deal of stability for parted >> itself (they're saying "Volatile," so it can't be used easily within >> the installer), so I don't understand drawing the "support" line at >> parted itself and excepting away ntfsprogs. What support? >> >> > > I only buried ntfsprogs because I thought it would be easier to make > it through PSARC that way. I guess I miscalculated. I did not hack > ntfsprogs at all, it was the easiest thing to port. I have no problem > delivering ntfsprogs in its entirety and in /usr/bin, if that is the > consensus. Okay, that would be better if you're game. It does non-trivially expand the scope of this case though. May I instead recommend you submit a case for just ntfsprogs, and make this one a dependent of it? > > Also maybe I need to rethink the Volatile stability. I wrongly assumed > that FOSS had to be Volatile. Also the goal is to get the OpenSolaris > installer to use either Parted or GParted, their choice, so I need to > choose the correct stability to achieve that. Uncommitted is probably better. Or, you wind up needing a contract. Nobody can meaningfully import a Volatile interface. - Garrett
[arc-discuss] [Fwd: [osol-announce] ARC cases will be unavailable on opensolaris.org for 24 hours]
Jim Carlson wrote: > [Thanks to Alan Coopersmith for forwarding the original message.] Well, you should all be on opensolaris-announce, but while we discussed autosubscribing all new accounts back when you were on the OGB, I don't think we ever followed through to make it happen, so we know many people aren't. -- -Alan Coopersmith- alan.coopersmith at sun.com Sun Microsystems, Inc. - X Window System Engineering
Parted - GNU Partition Editor [PSARC/2009/145 FastTrack timeout 03/06/2009]
Nicolas Williams wrote: > On Tue, Mar 03, 2009 at 08:13:00AM -0800, Garrett D'Amore wrote: > >> I don't know about savings of effort, but if we're not making them >> public interfaces, then I prefer them in /usr/lib/parted, where folks >> are less likely to find them by "accident" and infer (possibly false) >> things about their suitability for public use. >> > > I think it takes more effort to argue over whether to make them public > or not than it takes to just make them public. If the i-team doesn't > want to support the bloody things then they should just be made > Volatile -- they'd still be useful, so why hide them? > > >> That said, I'd hope that if we ever shipped the public ones, that this >> project could be converted to use the public ones instead of keeping its >> own private copies. >> > > More work for the next i-team. Why is that good? > > If every bit of FOSS was integrated like this we'd end up with a > mish-mash of stuff in /usr/lib that third parties would *still* find > *and* use -- that sounds like a negative architectural externality of > letting this case through as-is. > > IMO, if integrating FOSS X requires integrating FOSS Y, then integrate > both -- don't hide FOSS Y. > I agree that it would have been better to integrate a complete copy of ntfsprogs, make it public, and probably run it as a separate case that is a dependency upon this one. That's not what the project team decided to do. The project team hasn't committed to supporting ntfsprogs for other uses. While it would have been nice of them to do so, they didn't, and I don't think its PSARC's role to require them to do so either. -- Garrett
Parted - GNU Partition Editor [PSARC/2009/145 FastTrack timeout 03/06/2009]
James Carlson wrote: > Garrett D'Amore writes: > >> I don't know about savings of effort, but if we're not making them >> public interfaces, then I prefer them in /usr/lib/parted, where folks >> are less likely to find them by "accident" and infer (possibly false) >> things about their suitability for public use. >> >> That said, I'd hope that if we ever shipped the public ones, that this >> project could be converted to use the public ones instead of keeping its >> own private copies. >> > > There are some questions behind what I'm asking. If these are hacked > versions of those utilities, then I'd like to understand how we will > deal with the 1991/061 rules. If they're not hacked, then I'm a > little puzzled on why they're buried. It's not as if this project > team appears to want to promise a great deal of stability for parted > itself (they're saying "Volatile," so it can't be used easily within > the installer), so I don't understand drawing the "support" line at > parted itself and excepting away ntfsprogs. What support? > > I only buried ntfsprogs because I thought it would be easier to make it through PSARC that way. I guess I miscalculated. I did not hack ntfsprogs at all, it was the easiest thing to port. I have no problem delivering ntfsprogs in its entirety and in /usr/bin, if that is the consensus. Also maybe I need to rethink the Volatile stability. I wrongly assumed that FOSS had to be Volatile. Also the goal is to get the OpenSolaris installer to use either Parted or GParted, their choice, so I need to choose the correct stability to achieve that. Mark
OpenSolaris ARC meeting today, 3/3 is canceled.
OpenSolaris ARC meeting today, 3/3 is canceled.
tcpdump [PSARC/2009/147 FastTrack timeout 03/10/2009]
On Tue, 2009-03-03 at 01:28 -0800, James Walker wrote: >tcpdump 4.0.0 will be integrated into the SFW consolidation as part of >this proposal, and will be installed as SUNWtcpdump. Doesn't tcpdump 4.0.0 require libpcap 1.0.0? SFW has 0.9.8. As an aside, beware that 1.0.0 doesn't compile on Solaris; I submitted a fix for that upstream that was integrated into the source a few weeks ago, so the next release will be usable. If tcpdump 4.0.0 is in fact dependent on libpcap 1.0.0, then I suspect that this case will either need to have a case dependency on an as-yet-to-be-submitted case to upgrade libpcap to 1.0.x, or include the libpcap 1.0.x in this case. If it's not dependent on libpcap 1.0.0, then please ignore my ramblings. :-) Please specify either way. -Seb
Parted - GNU Partition Editor [PSARC/2009/145 FastTrack timeout 03/06/2009]
James Carlson wrote: > Garrett D'Amore writes: > >> Mark Phalan wrote: >> >>> Was there any consideration given to delivering ntfsprogs as public >>> utilities (rather than project private)? >>> I see that a limited sub-set of ntfsprogs is being delivered, no doubt >>> because thats the sub-set that gparted uses, but if ntfsprogs were to be >>> delivered in /usr/[s]bin it would be great to see the other utilities >>> included (ntfscp, ntfsls, ntfscat ...). I expect the demand for >>> user-accessible ntfsprogs will increase once ntfs-3g is delivered. >>> >>> >> I think such utilities might be useful, but its not this project. >> > > OK, then, I think that begs two questions: > > - If the ntfsprogs utilities were already included in the product as > a supported feature, would this project use them as-is or would it > still need to ship its own private variants? > > - Is there some savings in effort for locating the binaries in > /usr/lib/parted versus in /usr/sbin? > I don't know about savings of effort, but if we're not making them public interfaces, then I prefer them in /usr/lib/parted, where folks are less likely to find them by "accident" and infer (possibly false) things about their suitability for public use. That said, I'd hope that if we ever shipped the public ones, that this project could be converted to use the public ones instead of keeping its own private copies. -- Garrett
[arc-discuss] [Fwd: [osol-announce] ARC cases will be unavailable on opensolaris.org for 24 hours]
Alan Burlison wrote: > [Thanks to Alan Coopersmith for forwarding the original message.] > > Alan Burlison writes: > >> Our investigations into the recent stability issues with OpenSolaris.org >> have identified the ARC case archive on the site as a potential problem >> area. As part of the analysis we will be making all pages under the ARC >> community, including ARC case files, unavailable for 24 hours as of >> 9:00am UTC on Wednesday March 4th. >> > > Looking at the schedules, either today or Thursday would be a much > better time for this, as PSARC's weekly meeting is scheduled for > Wednesday at 18:00 UTC (10AM PST). Cutting out access during that > time may break the open review of (at least) "Boomer," which I expect > to generate significant interest. > > I suppose that if this timing is absolutely necessary, we could find > some other temporary means for publishing materials manually > (cr.opensolaris.org?), but I don't know what options are possible here > because I (the current PSARC co-chair) wasn't contacted before this > decision was made. > > In any event, we don't have much time to make these arrangements, so > please let us know what work-arounds we'll have available for our open > PSARC meeting. > As the Boomer project lead, I've been almost completely unable to publish materials on the ARC website. I've been mirroring them on cr.opensolaris.org. I'd *prefer* to have Boomer materials made available on the main website, and to have it up. But if we can't get updated materials posted to it, then it may not matter much. This breakage is causing me severe heartache. :-( - -Garrett
tcpdump [PSARC/2009/147 FastTrack timeout 03/10/2009]
James Walker writes: >Tcpdump is a common packet sniffer that runs under the command line. >It allows the user to intercept and display TCP/IP and other packets >being transmitted or received over a network to which the computer is >attached. Tcpdump works on most Unix-like OS, and uses libpcap library >to capture packets. What's the point? tcpdump is enough like snoop that it seems to me that there's not a great reason to do this. Instead, it'd be much nicer to see wireshark integrated (which includes a command line tool that's more powerful than either tcpdump *or* snoop), and also have snoop yanked from the product. The time spent here could be better spent elsewhere. > /usr/bin/tcpdump Uncommitted Executable binary file If this just _has to_ be integrated, I think it belongs in /usr/sbin, just like snoop. It's administrative in nature. -- James Carlson, Solaris Networking Sun Microsystems / 35 Network Drive71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677
Parted - GNU Partition Editor [PSARC/2009/145 FastTrack timeout 03/06/2009]
Phi Tran writes: > > GNU Partition Editor (Parted) [1] is a command-line application that allows > > you to resize, create or delete disk partitions and filesystems. The goal > > is to put it on the OpenSolaris Live CD. That way one could shrink the > > Vista or other NTFS partition and create space to install OpenSolaris. Many > > x86 machines come preinstalled with Vista. The availability of Parted would > > increase adoption of OpenSolaris by making it easier to create a dual-boot > > environment. First of all: "yay!" And I agree with the others about RBAC (should be exec_attr) and I have the same questions about ntfsprogs (why not just deliver this?). > > GParted is Phase 2 of this project. There will be a separate LSARC case. Which one will the installer use? I would have expected that it uses gparted. > > /usr/share/man/man8/parted.8 Volatile Manual page (Phase 1) This belongs in 1M. There's no "8" on Solaris. > > /usr/bin/parted Volatile Parted launcher shell > > script (Phase 1) It would be nice if we could stick to putting administrative utilities into /usr/sbin. Is that possible, or is there something out there that depends on having '/usr/bin/parted' leading to the command line version of this utility? > > SUNWgparted Committed Package name (Phase 2) > > /usr/share/man/man8/gparted.8 Volatile Manual page (Phase 2) > > /usr/bin/gparted Volatile GParted application > > (Phase 2) Not sure if we're reviewing these bits here (isn't that for the later LSARC case?), but, as a nit, I wouldn't make package names "Committed," but rather Uncommitted. And the path for gparted really should be Committed. There's no obvious way it could change other than by removal. -- James Carlson, Solaris Networking Sun Microsystems / 35 Network Drive71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677
Parted - GNU Partition Editor [PSARC/2009/145 FastTrack timeout 03/06/2009]
Mark Phalan wrote: > On Mon, 2009-03-02 at 14:38 -0800, Phi Tran wrote: > > ... > >> 4.2.3. ntfsprogs >> >> Parted uses ntfsprogs [3] to resize, create or delete NTFS disk >> partitions and filesystems. ntfsprogs [3] is a collection of >> command-line utilities, one utility for each operation, e.g. >> ntfsresize and mkntfs. >> >> ntfsprogs required very few changes to port to Solaris. >> > ... > >> 4.3. Interfaces Exported >> >> Interface NameClassificationComments >> --- --- >> SUNWpartedCommitted Package name >> (Phase 1) >> /usr/share/man/man8/parted.8 Volatile Manual page (Phase >> 1) >> /usr/bin/parted Volatile Parted launcher >> shell script (Phase 1) >> /usr/lib/parted/partedVolatile Parted application >> (Phase 1) >> /usr/lib/parted/mkntfsVolatile ntfsprogs >> application (Phase 1) >> /usr/lib/parted/ntfsresizeVolatile ntfsprogs >> application (Phase 1) >> /usr/lib/parted/ntfsfix Volatile ntfsprogs >> application (Phase 1) >> /usr/lib/parted/ntfsclone Volatile ntfsprogs >> application (Phase 1) >> > > > Was there any consideration given to delivering ntfsprogs as public > utilities (rather than project private)? > I see that a limited sub-set of ntfsprogs is being delivered, no doubt > because thats the sub-set that gparted uses, but if ntfsprogs were to be > delivered in /usr/[s]bin it would be great to see the other utilities > included (ntfscp, ntfsls, ntfscat ...). I expect the demand for > user-accessible ntfsprogs will increase once ntfs-3g is delivered. > I think such utilities might be useful, but its not this project. -- Garrett > -M > >
ZFS dataset property to support SMB [PSARC/2009/140 FastTrack timeout 03/05/2009]
>>> >>> If I were to set a label using sharesmb that would cause zfs to share >>> tank/photos, which I may not want shared. >> >> I do not understand that. > [..] > > The sharesmb syntax will not allow me to set sharesmb to off AND > set other options. Got it. After thinking about it some more I believe your approach is, indeed, better and more consistent than other options. Thanks for taking your time to explain it. -- Regards, Cyril
tcpdump [PSARC/2009/147 FastTrack timeout 03/10/2009]
I'm sponsoring this familiarity case for Robin Guo. The requested release binding is minor. The man page has 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: tcpdump 1.2. Name of Document Author/Supplier: Author: Robin Guo 1.3 Date of This Document: 03 March, 2009 4. Technical Description 1.0 Project Information 1.1 Name of project/component tcpdump 1.2 Author of document robin.guo at sun.com 2.0 Project Summary 2.1 Project Description Tcpdump is a common packet sniffer that runs under the command line. It allows the user to intercept and display TCP/IP and other packets being transmitted or received over a network to which the computer is attached. Tcpdump works on most Unix-like OS, and uses libpcap library to capture packets. tcpdump 4.0.0 will be integrated into the SFW consolidation as part of this proposal, and will be installed as SUNWtcpdump. 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 tcpdump.org 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://openso
Parted - GNU Partition Editor [PSARC/2009/145 FastTrack timeout 03/06/2009]
Garrett D'Amore wrote: > +1. > > Do we really need to introduce a new set of RBAC authorizations for > this? I'd have guessed that low-level sys_devices or whatever access > would have been sufficient. I agree with Garrett, auths here is the wrong model an exec_attr entry with the relevant privileges is a better match here. Adding the auths requires forking the code base for no reason and provides no real benefit over an exec_attr entry. -- Darren J Moffat
