The following minor case updates and corrections have
been made:
- man page update and cleanup
- add MC_PROPERTIES mac_callback flag
- rename MAC_HCK_* mac_hcksum flags to HCK_*
- add LSO_TX_BASIC_TCP_IPV4 flag to interface table
- add MC_* flags to interface table
The case materials have been up
This case has been marked closed approved.
Cheers,
Jim
(cleaned up version)
The case materials have been updated (diff files showing the
changes are included).
This case has received three +1s and the timeout has expired.
I plan to mark this case closed approved at the end of the day.
Cheers,
Jim
The case materials have been updated (diff files showing the
changes have been included).
This case has received three +1s and the timeout has expired.
I plan mark this case closed approved at the end of the day.
Cheers,
Jim
Thanks Mike.
Since this was the remaining item to be addressed, and the timeout has
been reached, I'm going to mark this case closed approved.
Cheers,
Jim
Michael Corcoran wrote:
Here are the anoninfo and cpu_vminfo stats being used.
anoninfo.ani_max;
anoninfo.ani_resv;
Garrett D'Amore wrote:
> Jim Walker wrote:
>> Garrett D'Amore wrote:
>>> Can you add *which* kstats are being used? Individual kstats are
>>> normally not documented, and some of them are more volatile than
>>> others. If this case is going to use
Garrett D'Amore wrote:
> Can you add *which* kstats are being used? Individual kstats are
> normally not documented, and some of them are more volatile than
> others. If this case is going to use kstats, then I think we need to
> document which ones are used in case someone decides to change t
Garrett D'Amore wrote:
> Darren J Moffat wrote:
>>> libstatgrab works with root and non-root privileges. If root privileges
>>> are given, then libstatgrab returns more information. The sg_init()
>>> function performs all the one-time initialization including operations
>>> that use setuid/setgi
Garrett D'Amore wrote:
> Mostly I like this, having reviewed the documentation on the website as
> well.
>
> A few things I'd like to see in this case before I assert +1:
>
>1) a list of the actual interfaces (routines) provided... you'll need
> to provide man pages for them anyway, so this
Robs wrote:
> If someone would help me offline with this, I'd really appreciate it.
Rob,
I can help you. It's a reasonable request.
Cheers,
Jim
--
Jim Walker, http://blogs.sun.com/jwalker
Sun Microsystems, Broomfield, Colorado
An updated 20questions doc has been posted for this case,
which is being reviewed at the PSARC meeting tomorrow.
Cheers,
Jim
This case was approved at todays PSARC meeting.
Cheers,
Jim
Rick Matthews wrote:
> As documented in the man page, are suck(1), blow(1), speedto(1) and
> speedfrom(1) required?
> Or are they just mis-applied to the man page.
They are associated utilities that utilize ettcp.
The project team has reviewed them and decided
they will not be delivered. The man
Garrett D'Amore wrote:
> I believe it is perfectly reasonable to allow users to push their favorite
> bits into /contrib, skip the ARC review, and allow the community to support
> those packages on a caveat emptor basis. The rest of the stuff, we should
> continue reviewing, using the same faculti
Scott Rotondo wrote:
>>
>> USAGE
>> PRIV_FILE_DAC_READ privileges are necessary to use this
>> utility to access /dev/xsvc.
>>
>
> Nit: That's a single privilege. "The PRIV_FILE_DAC_READ privilege is
> necessary ..."
Thanks. Updated.
USAGE
The PRIV_FILE_DAC_READ privilege is
The timeout for this case has expired and all issues
have been addressed, including changing the package
name to SUNWacpidump and using the following text in
the man pages:
USAGE
PRIV_FILE_DAC_READ privileges are necessary to use this
utility to access /dev/xsvc.
The proposal.txt
Nicolas Williams wrote:
> On Tue, Sep 01, 2009 at 10:46:55AM -0700, Garrett D'Amore wrote:
>>>
>>> - /contrib is a not good place for Sun projects to integrate into --
>>> aim for /dev & /release if you can;
>> Why? I think /contrib is perfectly reasonable for projects that just
>> want to ena
Terry (Sarito) Whatley wrote:
> Is it really necessary to use the "pmtools" name? None of the commands seem
> to use this name. There are many other things that might eventually be
> included in a collection of "pm tools", including some we already have
> (powertop comes to mind), and some that
The timeout for this case has been reached and all
issues have been resolved. I'm marking this case
closed approved.
Cheers,
Jim
Garrett D'Amore wrote:
>
> My preference is that if the utility would only ever be run by an
> administrator to debug a service, or to start up something manually that
> should have been started by SMF, then /usr/lib is probably better. If
> it is a reasonable thing that administrators might n
Garrett D'Amore wrote:
> I think that it makes sense to at least *try* to move zebrasrv out of
> /usr/bin. /usr/lib seems the right place for it.
Since zebrasrv has good command definition and /usr/bin is the
familiar location (ie. I'm not seeing /usr/lib being used anywhere
else). I think /usr/
Darren J Moffat wrote:
>
> It is a little unfortunate that we already have usr/sbin/zebra that is
> nothing to do with this. However I don't beleive any changes to this case
> are required as a result of that since there is not path name conflicts even
> though there are similar ones /usr/sbin/z
>>4.5. Interfaces:
>>
>> Exported Interface
>>
>>Interface Classification Comments
>>- -- --
>>SUNWraptorUncommitted Package name
>>SUNWraptor-d
Alfred Peng wrote:
>
> As for the header files, I just compare the new pkgmap with the old one.
> They contain the same set of files. On the other hand, the "Exported
> Interface" /usr/include/webkit-1.0 was declared to be Volatile in the
> previously arc. I think it's not necessary to list the fi
John Fischer wrote:
> Jim,
>
> The OSD (formerly JDS) group will have both a regular end user package
> and a developer package. The developer package will typically contain
> things relating to header files, package configuration scripts and
> sometimes developer documentation. Other packages t
Brian Cameron wrote:
> 4.8. Packaging & Delivery:
>
> The project will be delivering the following packages:
> SUNWwebkit
> SUNWwebkit-devel
What's the difference between the two packages if any?
Cheers,
Jim
BTW. You may want to update 1.4.4. OPG is not a BU
anymore.
This case was approved at todays PSARC meeting.
Cheers,
Jim
Garrett D'Amore wrote:
>
> The other thing is that one could imagine giving folks their own zones
> (sparse root probably!) to do this, which would allow root to be used
> "safely".
We provide development zones in the test farm for this purpose. It's
been available for some time now, and we p
he materials directory.
> Also, some of your exported interfaces are not declared with stability
> levels.
What exported interfaces are you referencing? The 'Faked' functions
are not exported.
Cheers,
Jim
--
Jim Walker, http://blogs.sun.com/jwalker
Sun Microsystems, Broomfield, Colorado
I updated this case to include a pointer to the
gnutls LSARC/2008/341 yaz contract in the materials
directory.
Cheers,
Jim
This case received a +1 and all comments have been
addressed and the timeout has expired. I'm marking
this case closed approved.
Cheers,
Jim
During pkgrti approval Alan Steinberg requested that the Pipe Viewer
package name be changed from SUNWpv to SUNWpipe-viewer so it would
be more descriptive for the user. Huajian from the project team agreed
with this change. I updated the proposal.txt file in the case directory
to show this change.
After reviewing this case with the project team,
I'm marking this case closed withdrawn until
they are in a better position to address the
issues discussed during the arc review and have
the resources needed to complete the project.
Cheers,
Jim
After reviewing this case with the project team,
I'm marking this case closed withdrawn until
they are in a better position to address the
issues discussed during the arc review and have
the resources needed to complete the project.
Cheers,
Jim
All comments for this case have been addressed and
the timeout has been reached.
I'm marking this case closed approved.
Cheers,
Jim
Mark Martin wrote:
4.0 Interfaces
4.1 Exported Interfaces
Interface NameClassificationComments
---
---
SUNWsysbenchUncommittedPackage
As part of the update to guile to provide 64-bit libraries,
libtool, a guile dependency, also needed to provide 64-bit
libraries. libtool64.txt has been added to the case directory
to document this change. This is planned to be updated as
part of the guile integration into the SFW consolidation.
C
Jim Walker wrote:
> Mark Martin wrote:
>> Please find attached (and text inline) the draft opinion for 2008/772
>> Command Assistant. Commentary, concerns, criticisms, and corrections
>> wanted. Please.
>> _
>>
>> Project Private:
&
The project team is updating guile to include 64-bit
versions of the libraries to meet ARC 64-bit library
standards. proposal64bit.txt has been added to the
case directory. autogen and guile are planning to be
integrated into the SFW consolidation.
I think this can be handled as a self review.
Ch
t/lib/stax-ex.jar
> /usr/lib/commandassistant/lib/jaxb-impl.jar
> /usr/lib/commandassistant/lib/activation.jar
>
I cases where jar files are useful beyond Command Assistant
why don't they get moved to /usr/share/lib/java for other
applications to use?
Cheers
This case was approved at todays PSARC meeting.
Cheers,
Jim
This case was approved at todays PSARC meeting.
Cheers,
Jim
--
Jim Walker, http://blogs.sun.com/jwalker
Sun Microsystems, Broomfield, Colorado
Kais Belgaied wrote:
> +1 , a quick question though: the release binding is minor, is there
> a dependency on future minor release features that are not available
> yet as patches to the current minor release of Solaris?
No. But can you rephrase, since the question seems too general.
Cheers,
Jim
Mark Martin wrote:
>
> Minor nit -- you mention it's a "familiarity case", which seems
> reasonable, yet 2.3 says "no".
>
Fixed.
Cheers,
Jim
Garrett D'Amore wrote:
>>
>> I think that was too quick :) The i-team might well agree to patch
>> disktype to use libfstyp as a source of information... I've asked for
>> that, now let's give them a chance to tell us if they're willing to do
>> that :)
>>
>
> Please go back and reread my las
Sebastien Roy wrote:
> I wonder how many other "/usr/bin/pv" commands there are... Here's one
> that's part of the "waon" project, included with Ubuntu:
>
> http://www.kichiki.com/WAON/pv.html
>
> There is even an unresolved bug filed against Ubuntu flagging this exact
> conflict of /usr/bin/pv
Currently, the project team is using the man page directly from
the tarball and tacking on the available and stability information
at the end. However, they will look into your suggestions and work
with the upstream community to improve the man page and or package
functionality.
Cheers,
Jim
Don C
All issues have been addressed and the timeout has been reached.
I'm marking this case closed approved.
Cheers,
Jim
All issues have been addressed and the timeout has expired.
I'm marking this case closed approved.
Cheers,
Jim
James Walker wrote:
> I'm sponsoring this familiarity case for Alex Zhang. The requested
> release binding is minor. The man pages have been posted in the
> materials directory. The OpenSSL contract link will be posted after
> it is approved.
I added the approved openssl contract link to the mater
This case was approved during the PSARC meeting.
Cheers,
Jim
Sebastien Roy wrote:
> Hi Erik,
>
> On Fri, 2009-05-29 at 11:05 -0700, Erik Lafever wrote:
>> Sebastien Roy wrote:
>>> It looks like this project makes no backward incompatible changes to any
>>> existing software. As such, Minor binding seems unnecessarily
>>> restrictive. Why not Patch?
>
> A
Shawn Walker wrote:
> From what I can tell, there seems to be a random naming pattern to
> packages where some of them get named SUNWpyhon-something, others
> SUNWPython-something, and yet others SUNWsomething.
>
> Is there an established practice yet?
For now, we will use SUNWpylint until dir
All issues have been addressed, and the timeout has been
reached. I'm marking this case case closed approved.
Cheers,
Jim
I. Szczesniak wrote:
>>
>> > Unlike previous releases, 5.10.x will not integrate in to O/N, but
>> > will instead move to SFW.
>>
>> I'll be glad to see it go (eventually) for the improvement in build
>> time,
>
> Is this the only justification? Bits delivered via SFW commonly
Garrett D'Amore wrote:
>
> Not architectural in nature, but I wonder if Perl itself is "meaty"
> enough to justify delivering in its own consolidation. It takes a while
> to build. But then I have no insight into the release engineering
> issues associated having multiple consolidations, and
I'm marking this case closed approved.
Cheers,
Jim
--
Jim Walker, http://blogs.sun.com/jwalker
Sun Microsystems, Broomfield, Colorado
application usage and upstream
community to see if other command names should be used in the future.
Cheers,
Jim
--
Jim Walker, http://blogs.sun.com/jwalker
Sun Microsystems, Broomfield, Colorado
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,
This case was approved at the LSARC meeting today.
The project team plans to update the libosip man page
to indicate that libsip is the current preferred sip
library on Solaris/OpenSolaris.
Cheers,
Jim
margot wrote:
>
> The JDK needs to be in the imported interface table.
> And I suppose there is no problem with it running
> on whatever JDK is on the system?
>
> I don't think you need to put the javadocs in the interface
> table. Just a notation that javadocs are being delivered
> would be goo
+1 has been received.
All issues have been addressed and the timeout period has
been reached and I have updated the proposal.txt file to
indicate python 2.6 will be used.
Marking this case closed approved.
Cheers,
Jim
All issues have been addressed and the timeout period has
been reached and I have updated the proposal.txt file to
indicate python 2.6 will be used.
Marking this case closed approved.
Cheers,
Jim
Bobbie wrote:
> After seeing the feedback on logilab-common, I will retarget
> logilab-astng to python 2.6
>
Can I get a +1 from a member on this one?
Thanks,
Jim
--
Jim Walker, http://blogs.sun.com/jwalker
Sun Microsystems, Broomfield, Colorado
Housekeeping...
I'm closing the orphaned ejabberd LSARC/2008/218 case
which was superceded by PSARC/2008/340 which was
approved.
Cheers,
Jim
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/
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 S
James Carlson wrote:
> Jim Walker writes:
>> James Carlson wrote:
>>> I urge the project team to consider bringing in at least one
>>> application that makes use of this library. Libraries without
>>> consumers are, in my opinion, just baggage. And in this c
James Carlson wrote:
>
>>> Are these being delivered by this or by some other project? And do
>>> any of them work with the existing libsip?
>>>
>> These application will not be delivered by this case and I'm not sure if
>> someone is working on porting them. None of them works with libsip.
>
For LSARC, PSARC and the opinion writer(s) to consider
Michael Kearney wrote:
> 1. Lloyd, I like the idea of your annotation but have a couple of
> concerns.
> - Would teams be expected to update third party, open source jar
> files with the annotation?
> - Would the ARC provide the
This case has come to resolution and the timeout extension of
05/08/2009 has been reached, and it has received a +1.
I'm marking it closed approved.
Cheers,
Jim
--
Jim Walker, http://blogs.sun.com/jwalker
Sun Microsystems, Broomfield, Colorado
nk there is
opportunity to improve the current short comings.
Cheers,
Jim
--
Jim Walker, http://blogs.sun.com/jwalker
Sun Microsystems, Broomfield, Colorado
I'm extending the timeout on this case to 5/8/2009.
Cheers,
Jim
Procedural Note.
Before you press send button please remember to prune addresses
that are already on the arc email alias.
If you are sending case related email and you have more
addresses than 1) the arc alias, 2) project team address and
3) the person you are responding to, you probably should d
I'm marking this case status as waiting needs spec.
The project team will check with the beanshell community to
see how they have handled namespace issues in the past
and we will review the findings via email and hopefully
resolve at the next PSARC meeting on 05/13/2009.
Cheers,
Jim
Note.
awstats version 6.9 will be ported instead of version 6.7.
There are no interface changes. I will keep the state
at closed approved.
Cheers,
Jim
This case was approved at todays PSARC meeting.
The project team will look at pointing to filebench
in the man page.
Cheers,
Jim
Phil,
I understand your concerns, that's why we ran it by Brendan, who
ran it by SAE. As you point out there are issues with iozone in
general, and with Solaris. filebench is clearly a much better
benchmarking framework.
But, it is still a commonly used open source benchmark, and if
we don't port
Housekeeping...
I'm closing the orphaned slib LSARC/2008/211 case
which was superceded by PSARC/2008/316 which was
approved.
Cheers,
Jim
--
Jim Walker, http://blogs.sun.com/jwalker
Sun Microsystems, Broomfield, Colorado
The update was approved. I'm marking this case closed approved again.
Cheers,
Jim
Can a member give this a +1 so I can close it?
Thanks,
Jim
Jim Walker wrote:
> I'm reopening this case for comments to allow the addition of the
> following two Project Private directories:
>
> /usr/lib/mrtg2/ Project Private Perl scripts
>
I'm reopening this case for comments to allow the addition of the
following two Project Private directories:
/usr/lib/mrtg2/ Project Private Perl scripts
/usr/share/mrtg2/ Project Private Icon and Image files
Since I don't think these changes are controvers
This case was approved at this weeks PSARC meeting.
Cheers,
Jim
Norm Jacobs wrote:
> Danek Duvall wrote:
>> On Tue, Apr 14, 2009 at 02:19:34AM -0700, James Walker wrote:
>>
>>
>>> /usr/lib/cups/backend/halVolatileCUPS backend
>>> /usr/lib/hal/hal_lpadmin VolatileHAL hot-plug
>>> action
>>>
>>
>> Aren't these r
All issues for this case have been addressed and it
has received two +1s and the timeout has expired.
And, I have added a pointer to the OpenSSL contract-33
file in the materials directory documenting the
approvals. And, I have updated the version number to
the correct version 1.06.32 in the propos
Mark Carlson wrote:
>
> Exported InterfaceClassificationComments
>===
> ==
> /opt/SUNWtipc/lib/libtipcsocket.so UncommittedLibrary
> symbolic link
Since it w
manpage has been added to the materials directory, and the
libxmlrpc-c.3lib manpage has been updated to include information on the
xmlrpc-c-config compile/link helper script.
Cheers,
Jim
--
Jim Walker, http://blogs.sun.com/jwalker
Sun Microsystems, Broomfield, Colorado
Margot Miller wrote:
> +1
>
> Just curious- the man page mentions tools and libraries for XML-RPC.
> Will there be a tools case for this?
Good catch. The example xmlrpc command needs to be added.
Cheers,
Jim
--
Jim Walker, http://blogs.sun.com/jwalker
Sun Microsystems, Broomfield, Colorado
$ISAINFO. /usr/lib/sparcv9 and /usr/lib/amd64 target directories are used
for the 64-bit libraries. "/usr/lib/64" is shorthand.
Cheers,
Jim
--
Jim Walker, http://blogs.sun.com/jwalker
Sun Microsystems, Broomfield, Colorado
This case received two +1s and the timeout has expired.
I am marking the case closed approved.
Cheers,
Jim
This case received a +1 and the timeout has expired.
I am marking this case closed approved.
Cheers,
Jim
This case received a +1 and the timeout has expired.
I am marking it closed approved.
Cheers,
Jim
(back from vacation)
The timeout has been reached for the case with a +1 and
comments have been addressed.
I'm marking this case closed approved.
Cheers,
Jim
This case was approved at todays LSARC meeting.
Cheers,
Jim
usly. :-/
Right. It does fine using only kstat.
Cheers,
Jim
--
Jim Walker, http://blogs.sun.com/jwalker
Sun Microsystems, Broomfield, Colorado
This case was approved at todays PSARC meeting.
Cheers,
Jim
Rick Matthews wrote:
> Are we supporting a particular version of clisp? The community appears
> to be very active.
The project team will be delivering the current clisp version 2.47.
I'll update the checklist.
Cheers,
Jim
components access the network?
>> [*] Yes
>> [ ] No - continue with the next section (section 3.6)
>
> In what way?
>
> I'll give this a +1, even though I think the answers to the checklist
> are not quite accurate. I know the underlying sourceforge project
> better. :-/
I'll update the checklist.
Cheers,
Jim
--
Jim Walker, http://blogs.sun.com/jwalker
Sun Microsystems, Broomfield, Colorado
n /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
I added this information to a Notes section in the proposal.txt file,
and marked this case closed approved.
Cheers,
Jim
--
Jim Walker, http://blogs.sun.com/jwalker
Sun Microsystems, Broomfield, Colorado
1 - 100 of 165 matches
Mail list logo
