[request-sponsor] Come join me on Amrita Vishwa Vidyapeetham, Kerala Sun OSUM on Sun Open Source University Meetup...
On Mon 15 Sep 2008 at 06:32PM, Avinash Joshi wrote: > Sun Open Source University Meetup > > [1]Avinash Avinash Joshi has invited you to join Amrita Vishwa Vidyapeetham, >JoshiKerala Sun OSUM on Sun Open Source University Meetup > [2]Avinash >Joshi Avinash, Please, don't spam lists. Send a single announcement to osol-announce. -dp -- Daniel Price - Solaris Kernel Engineering - dp at eng.sun.com - blogs.sun.com/dp
[request-sponsor] Requesting sponsor for defect 2009
On Mon 14 Jul 2008 at 07:54PM, Dale Ghent wrote: > > Bug: > http://defect.opensolaris.org/bz/show_bug.cgi?id=2009 > > Fix: > http://cr.opensolaris.org/~daleg/defect-2009/ > > Contributor ID: OS0117 Dale, can you bring this on over to pkg-discuss at opensolaris.org? That's where the pkg dev team is located. Just request a code review there, and since you have a contributor ID we'll just have someone apply your exported patch once the review is completed. Thanks (and thanks for working on this!) If you want you can make yourself the Assignee for 2009 in bugzilla. -dp -- Daniel Price - Solaris Kernel Engineering - dp at eng.sun.com - blogs.sun.com/dp
[request-sponsor] 4532599: ptime should report resource usage statistics from /proc for running processes
On Mon 14 Apr 2008 at 12:45PM, Chad Mynhier wrote: > On Mon, Apr 14, 2008 at 5:38 AM, Dan Price wrote: > > On Sat 12 Apr 2008 at 04:32PM, Chad Mynhier wrote: > > > On Thu, Oct 4, 2007 at 2:05 PM, Chad Mynhier > > wrote: > > > > > > I'd like to make a second sponsor request for this. It's been 5 > > > months since I've had any email contact with my sponsor. > > > > That seems slightly unfair since we spoke in person at dtrace.conf, > > and I apologized (and attempted to explain the reasons for) my slow > > progress on > > this. > > You're right, I should have mentioned that detail initially, and I > apologize for the oversight. Yes, we spoke about this at the > conference, but given that you haven't had time to respond to my > emails since then, I figured that you'd also be too busy to work on > the putback. I'm certainly sympathetic to this, in light of the > upcoming release, and I also realize that this putback isn't the > highest priority item on the list. But if someone else is available > to do this, I'd like to just be done with it. I totally agree-- and will see if I can help you locate someone... -dp -- Daniel Price - Solaris Kernel Engineering - dp at eng.sun.com - blogs.sun.com/dp
[request-sponsor] 4532599: ptime should report resource usage statistics from /proc for running processes
On Sat 12 Apr 2008 at 04:32PM, Chad Mynhier wrote: > On Thu, Oct 4, 2007 at 2:05 PM, Chad Mynhier wrote: > > I'd like to request a sponsor for > > http://bugs.opensolaris.org/view_bug.do?bug_id=4532599. This is a bit > > of an odd request given that RFE is marked "6-Fix Understood (Fix is > > known)". It appears that the responsible engineer has left Sun, > > though, so I don't know what state it's actually in. If possible, I'd > > like to adopt (or hijack, if you prefer) this RFE. > > I'd like to make a second sponsor request for this. It's been 5 > months since I've had any email contact with my sponsor. That seems slightly unfair since we spoke in person at dtrace.conf, and I apologized (and attempted to explain the reasons for) my slow progress on this. However, I agree that I'm overloaded with work on the May release at the moment; is someone else available to shepherd this in? We got the PSARC work done some time ago, so this should be straightforward. -dp -- Daniel Price - Solaris Kernel Engineering - dp at eng.sun.com - blogs.sun.com/dp
[request-sponsor] self-service beta testing
On Wed 17 Oct 2007 at 08:41PM, Jim Walker wrote: > Shawn Walker wrote: > > I was wondering if there was some way to upload bfu archives via rsync > > or scp instead of a browser upload similar to how cr.opensolaris.org > > works. > > > > I would much prefer that over using a browser for such a large file :( > I would too, and I am already looking into it. Jim, I built cr.o.o, and would be happy to share technology with you. Send me mail offline or give me a call. -dp -- Daniel Price - Solaris Kernel Engineering - dp at eng.sun.com - blogs.sun.com/dp
[request-sponsor] 4532599: ptime should report resource usage statistics from /proc for running processes
On Thu 04 Oct 2007 at 02:05PM, Chad Mynhier wrote:
> I'd like to request a sponsor for
> http://bugs.opensolaris.org/view_bug.do?bug_id=4532599. This is a bit
> of an odd request given that RFE is marked "6-Fix Understood (Fix is
> known)". It appears that the responsible engineer has left Sun,
> though, so I don't know what state it's actually in. If possible, I'd
> like to adopt (or hijack, if you prefer) this RFE.
>
> I've posted a webrev for a solution here:
> http://interstel.net/~mynhier/4532599/. (Note that this webrev also
> includes the fix for
> http://bugs.opensolaris.org/view_bug.do?bug_id=6234106 ("ptime should
> report microseconds or nanoseconds instead of just milliseconds"), as
> it seems pointless to have microstate stats at a millisecond
> resolution.
Chad, I'm a bit busy but this is an area of interest for me.
I have a PSARC license and at least a passing familiarity with this
sort of code, so I can sponsor this if you wish. Can we collaborate
on this?
-dp
--
Daniel Price - Solaris Kernel Engineering - dp at eng.sun.com - blogs.sun.com/dp
[request-sponsor] 4884338:There should be a generic implementation of strdup() in the kernel
On Fri 07 Sep 2007 at 04:40PM, Dan McDonald wrote: > On Fri, Sep 07, 2007 at 01:34:15PM -0700, Seth Goldberg wrote: > > > You'll also want to ensure that you have some consumers for this > > > functionality-- the obvious thing would be to rip out the various > > > other strdup's which exist. > > > >The obvious question is-- how does one specify whether > >KM_SLEEP/KM_NOSLEEP is used for the underlying allocation (for > >kernel applications). > > The first-cut "obvious" answer is KM_NOSLEEP, since strdup() CAN return NULL > on failure. The "obvious" answer to me is that you would survey all the kernel code which has implemented strdup()-like functionality and then make a decision based on this requirements gathering exercise. FWIW, I had simply assumed that the interface would mimic most other memory allocating interface: strdup(mystr, KM_SLEEP) (or if we're worried that people will make mistakes if it is called "strdup" then call it kstrdup). But again, I think this issue is for the implementor to decide. Probably this belongs on osol-code... :/ -dp -- Daniel Price - Solaris Kernel Engineering - dp at eng.sun.com - blogs.sun.com/dp
[request-sponsor] 4884338:There should be a generic implementation of strdup() in the kernel
On Thu 06 Sep 2007 at 09:16PM, madhav chauhan wrote: > Hi, > > I came across this bug while browsing through the bug database. I am > working on this bug .I have already signed the Sun Contributor > Agreement and my SCA number is OS0106. > > Please let me know the procedure for working on this. Madhav, For some reason I remember Roger objecting to strdup() on principal, but I don't exactly remember why ... although that was 6 or 7 years ago. I have CC'd him. Admittedly, since then we've seen a bunch of new code which defines its own version of strdup. I'm going to move some stuff from the "comments" part of that bug report into the "description"... it should show up there in about 24 hours, and might help you. The other interesting question would be whether this should be placed into the DDI (i.e. strdup(9f) as a peer to strcpy(9f)), although I suppose that could be done later. You'll also want to ensure that you have some consumers for this functionality-- the obvious thing would be to rip out the various other strdup's which exist. -dp -- Daniel Price - Solaris Kernel Engineering - dp at eng.sun.com - blogs.sun.com/dp
[request-sponsor] request sponsor for 6442524
On Mon 04 Dec 2006 at 09:52PM, Stephen Lau wrote: > Since sethostname(3c) simply makes the same call to > sysinfo(SI_SET_HOSTNAME,...), it's certainly not for any performance > benefit. It's probably just cleaner, code-wise. > > I can sponsor this one. Make sure to get codereview from Eric Saxe and Jeremy Teo, who did this work just a few months ago. I was a codereviewer, and the reason is that we identified this issue in the codereview: Dan Price wrote: > Could this use the standards-based library routines gethostname(3c) and > sethostname(3c)? Which turned out to be beneficial, since when we tried this we discovered 6438052 sethostname(3c) missing prototype in unistd.h. My general theory is that when there's a standards based way to do it, it's nice to use that. -dp -- Daniel Price - Solaris Kernel Engineering - dp at eng.sun.com - blogs.sun.com/dp
[security-discuss] sync as non privileged user (Was Re: [request-sponsor] 4967733 and 6400646)
On Fri 03 Nov 2006 at 10:34AM, Casper.Dik at sun.com wrote: > > >> Assuming we do steps 1 and 2 above, do we get into any problems with > >> POSIX compliance if the default basic privilege set does not include > >> PRIV_SYS_SYNC? > > There is no such thing as a "default basic set". > > There's a "basic set" and there's the "default set" users get when > they login; they are generally the same but need not be. > > An administrator CANNOT manipulate the basic set; he can manipulate > the default. > > Making sync() privileged would violate POSIX; but with basic privileges > that is not an issue because everyone gets them in the default > configuration. What SUSv3 seems to say is that I/Os must be scheduled before the sync completes, but the I/Os need not occur prior to the sync(2) call returning. It also says nothing about what might happen if not all of the I/Os complete, or whether the system can be shut down without all I/Os completing. So one wonders whether (in the event an unprivileged user issues a sync) you could just "schedule" the I/O to happen say, 1000 years in the future. The poorly defined spec from POSIX seems to be in conflict with how much effort we might go to in order to comply with it... Maybe there's a more detailed standards definition somewhere I've not seen? -dp -- Daniel Price - Solaris Kernel Engineering - dp at eng.sun.com - blogs.sun.com/dp
[request-sponsor] 4967733 and 6400646
On Sun 29 Oct 2006 at 12:39PM, Mike Gerdts wrote: > 4967733 bad idea for zones to sync(1M) during shutdown > 6400646 zones induce between 0 and 6 calls to sync() on each reboot > > The attached patch addresses these bugs. Contributor agreement is OS0018. I'll sponsor this one. (Uhh, except that you forgot to attach the patch). This is a great bug to fix. I think the remaining question we should investigate is whether sync(2) should do anything at all in a non-global zone (or should somehow be restricted in scope). Probably we should check in with the VM and/or UFS folks about this. I know that at some point the performance guys wanted to make sync's by non-root users do nothing, but IIRC it was deemed too risky or something. Maybe we should go do that for Nevada. Anyone in request-sponsor land have some background info they could point us at? -dp -- Daniel Price - Solaris Kernel Engineering - dp at eng.sun.com - blogs.sun.com/dp
[request-sponsor] request for sponsor to add synaptics support
On Mon 23 Oct 2006 at 05:40PM, Casper.Dik at Sun.COM wrote: > > > >Our driver supports it. > > Excellent. > > (These are all feature requests I got and (partially) implemented for > my driver, so I htink they're important for customers) So Casper, you're sponsoring this, right? -dp -- Daniel Price - Solaris Kernel Engineering - dp at eng.sun.com - blogs.sun.com/dp
[request-sponsor] Fwd: 6471646 - quota -h
On Sat 07 Oct 2006 at 07:45AM, Mike Gerdts wrote: > Any takers on this one? I have a patch ready. > > Contributor # is OS0018. I'll take it. We'll need to prep and file a brief ARC case. Did we ever get a working "humanized" number function in libc? -dp -- Daniel Price - Solaris Kernel Engineering - dp at eng.sun.com - blogs.sun.com/dp
[request-sponsor] request new sponsor for: 4687825
Hi all, Karyn keeps letting me know how I've been lagging on getting my sponsorship duties done for 4687825 *cron* /etc/cron.d/FIFO should move to /var/run/CRONFIFO If there is another sponsor out there who would like to pick this up (and not sit on it like I did), I'd appreciate it; I'm juggling a few too many things to get this done in a timely way. The requester is Rich Lowe. I'll be happy to update the new sponsor with all the state about this which I can remember. Thanks, -dp -- Daniel Price - Solaris Kernel Engineering - dp at eng.sun.com - blogs.sun.com/dp
[request-sponsor] Re: 4687825 - *cron* /etc/cron.d/FIFO should move
On Fri 07 Apr 2006 at 08:54PM, Stephen Potter wrote: > Not realizing this had already been done, I started to look at this the other > night. Surprisingly, I came up with almost exactly the same changes as Rich, > except I only used "/var/run/cron" instead of "/var/run/CRONFIFO". > > I also came up with a couple of issues that need to be considered with this: > 1) Man page update; since man pages have been released as part of ON yet. > 2) When a patch is generated to install this, it will need to make sure it > shuts down cron, deletes the /etc/cron.d/FIFO file and then installs and > restarts cron. Otherwise, there will be an orphaned named pipe lying around > the /etc filesystem. > Thanks Stephen; there are some deeper issues here too, which Rich and I explored. Rich has sent me a revised patch for this, which I haven't dealt with yet. Can we sign you up as a codereviewer? -dp -- Daniel Price - Solaris Kernel Engineering - dp at eng.sun.com - blogs.sun.com/dp
[request-sponsor] Re: [osol-discuss] Contributing Code
On Wed 08 Mar 2006 at 11:42AM, Dan Price wrote:
> On Wed 08 Mar 2006 at 10:49AM, Karyn Ritter wrote:
> > I'll figure out where to put the definitions. This the real status that
> > is in Bugster, so we need to document it anyway
>
> So, I wonder if we could use Perl's WWW::Mechanize [1] or something
> equivalent to automate the updating of pages. Then, Karyn, we could
> write you something which would gather up this info and post it
> every 2 hours, or whatever.
>
> Maybe we could have a Java package [2] (as well as any other languages
> [3]) that manipulates the website as well-- I personally don't like the
> endless CPAN machinations one must go through to get a useful perl.
>
> So this is a fun and challenging project for someone. Any takers?
Nobody ever takes my challenges :(
Anyway, I've completed a prototype of a tool which can do this; for
those interested, it is attached below. You'll need WWW::Mechanize and
either IO::Socket::SSL or Crypt::SSLeay installed, available from
CPAN.
Here's how to use it:
$ cat > ~/.osauth
my_opensolaris_username my_opensolaris_password
^D
$ chmod 600 ~/.osauth
$ ./bender.pl
./bender.pl: you must specify -u
Usage: ./bender.pl [-v] -u -f -x
- Authfile should contain one line with your
OpenSolaris.org username and password.
- Note that you must have permission to edit
the page you are updating, and it must exist already.
$ date | ./bender.pl -u community/zones/moop -f - -x ~/.osauth -v
Get file contents...ok
Get authentication info...ok
Visit http://www.opensolaris.org/os/...ok
Click 'Sign in'...ok
Click 'Login'...ok
Visit http://www.opensolaris.org/os/community/zones/moop ...ok
Open edit...ok
Complete edit...Done.
n.b., for those at Sun, I can't get this to work through the corporate
web proxies (and would love help to do so). You can use a machine with a
transparent proxy, though, and it'll work fine. 'webhop.sfbay' is available
for this purpose upon request (to me). Note also that the script tries
to respect the $http_proxy, etc. environment variables, so you may
need to clear those.
Happy cronjob-ing.
-dp
--
#!/bin/perl
#
# CDDL HEADER START
#
# The contents of this file are subject to the terms of the
# Common Development and Distribution License (the "License").
# You may not use this file except in compliance with the License.
#
# You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE
# or http://www.opensolaris.org/os/licensing.
# See the License for the specific language governing permissions
# and limitations under the License.
#
# When distributing Covered Code, include this CDDL HEADER in each
# file and include the License file at usr/src/OPENSOLARIS.LICENSE.
# If applicable, add the following below this CDDL HEADER, with the
# fields enclosed by brackets "[]" replaced with your own identifying
# information: Portions Copyright [] [name of copyright owner]
#
# CDDL HEADER END
#
#
# Copyright 2006 Sun Microsystems, Inc. All rights reserved.
# Use is subject to license terms.
#
#ident "%Z%%M% %I% %E% SMI"
use LWP::UserAgent;
#use LWP::Debug qw(+);
use WWW::Mechanize;
use Getopt::Std;
my $verbose;
$| = 1;
sub vprint(@) {
my (@msg) = @_;
return if (!$verbose);
print "@msg" if (@msg);
}
sub usage(@) {
my (@msg) = @_;
print "$0: @msg\n" if (@msg);
print "Usage: $0 [-v] -u -f -x \n";
print "\t- Authfile should contain one line with your\n";
print "\t OpenSolaris.org username and password.\n";
print "\t- Note that you must have permission to edit\n";
print "\t the page you are updating, and it must exist already.\n";
exit 2;
}
$starturl = 'http://www.opensolaris.org/os/';
getopts('vf:u:x:');
usage("you must specify -u ") unless defined($opt_u);
usage("you must specify -f ") unless defined($opt_f);
usage("you must specify -x ") unless defined($opt_x);
$myurl = $opt_u;
$myfile = $opt_f;
$myauth = $opt_x;
if (defined($opt_v)) { $verbose = "1"; }
vprint("Get file contents...");
$buffer = "";
open CONTENTS, "$myfile" or die "could not open $myfile";
while () {
$buffer .= $_;
}
vprint("ok\n");
vprint("Get authentication info...");
$username = "";
$passwd = "";
open CONTENTS, "$myauth" or die "could not open $myauth";
($username, $passwd) = split(" ", );
vprint("ok\n");
#
# Log ourselves in.
#
$mech = WWW::Mechanize->
[request-sponsor] SFW source tarball release
On Thu 16 Mar 2006 at 05:20PM, Marilyn Shoemaker wrote: > > > Folks > > The SFW consolidation expects to begin regular source tarball releases > on opensolaris.org within the next week. > > We will accept bug fixes from the community and will follow the ON model > for dealing with those fixes. > > Wendy Phillips, Liane Praza, Bart Smaalders, and Keith Wesolowski are > the advocates who will deal with SFW issues. Can you clarify the word "advocate" in this context? -dp -- Daniel Price - Solaris Kernel Engineering - dp at eng.sun.com - blogs.sun.com/dp
[request-sponsor] Re: [osol-discuss] Contributing Code
On Wed 08 Mar 2006 at 10:49AM, Karyn Ritter wrote: > I'll figure out where to put the definitions. This the real status that > is in Bugster, so we need to document it anyway So, I wonder if we could use Perl's WWW::Mechanize [1] or something equivalent to automate the updating of pages. Then, Karyn, we could write you something which would gather up this info and post it every 2 hours, or whatever. Maybe we could have a Java package [2] (as well as any other languages [3]) that manipulates the website as well-- I personally don't like the endless CPAN machinations one must go through to get a useful perl. So this is a fun and challenging project for someone. Any takers? [1] http://www.perl.com/pub/a/2003/01/22/mechanize.html [2] http://htmlunit.sourceforge.net/ [2] http://wwwsearch.sourceforge.net/mechanize/ -dp -- Daniel Price - Solaris Kernel Engineering - dp at eng.sun.com - blogs.sun.com/dp
[request-sponsor] Re: [osol-discuss] 1 new request-sponsor putback: 39 total
On Thu 02 Mar 2006 at 11:33AM, Alan Coopersmith wrote: > Artem Kachitchkine wrote: > > > >>It would be cool if the diffs would be part of the announcements. > > > > > >The diffs are always attached to the bug ID in the bug database. They > >don't appear on the bugs.opensolarig.org though. I don't see why they > >shouldn't for contributed patches, perhaps it's just a technical problem > >with database export that will be eventually fixed? > > How would it determine which bugs those fields can be exported for? > We can't do it for all bugs, since some contain source which cannot > be disclosed publically. Ones marked with oss-sponsor, perhaps? Or a checkbox? Bugster needs workflow added to it to handle this. -dp -- Daniel Price - Solaris Kernel Engineering - dp at eng.sun.com - blogs.sun.com/dp
[request-sponsor] RFE - zoneadm clone should use zfs snapshot/clone
On Sun 19 Feb 2006 at 08:59PM, Jerry Jelinek wrote: > Mike, > > There is already an RFE open for this: > > 6383119 RFE: add support for using zfs clones when cloning a zone > > and we are in the middle of active development on this feature already. > The code we have will automatically create zfs filesystems when you > install new zones, will destroy the zfs filesystem when you uninstall > the zone and will automatically clone the zone using the appropriate > technique based upon the source and target filesystems. We'll be > starting the architectural review process for these new features > shortly. Once those have been approved by the ARC process, the code > should be available within the open solaris source tree. > > If you are interested, we can take this over to the zones-interest > alias (zones-discuss, that is :) ) Jerry-- I think it'd make a lot of sense to rope Mike in on your writeup-- the one you passed to David and I, and get his feedback before we go to ARC; he's done a lot of thinking on this. And Mike-- if you are planning to work more on zones (which we would love) maybe we can coordinate with you, so we're not duplicating work? We'd also appreciate hearing your thoughts on what we could be doing to make zones more useful for you and your business. The zones team is meeting all week this week to work face to face (we are usually a distributed team) so we'll be planning out the next couple of months of enhancements-- now is a good time to influence our thinking :) -dp -- Daniel Price - Solaris Kernel Engineering - dp at eng.sun.com - blogs.sun.com/dp
[request-sponsor] 6352485 - RFE: add $zonename to the list of macros supported by logadm
On Fri 02 Dec 2005 at 01:34PM, Richard Lowe wrote: > Patch for bug: > 6352485 - RFE: add $zonename to the list of macros supported by logadm > > http://richlowe.net/patches/6352485.diff I'll sponsor this bug fix. It's a smart idea! -dp -- Daniel Price - Solaris Kernel Engineering - dp at eng.sun.com - blogs.sun.com/dp
[request-sponsor] 4687825 - *cron* /etc/cron.d/FIFO should move to /var/run/CRONFIFO
On Fri 02 Dec 2005 at 11:09PM, Richard Lowe wrote: > Patch for bug: > 4687825 - *cron* /etc/cron.d/FIFO should move to /var/run/CRONFIFO > > http://richlowe.net/patches/4687825.diff > > contributor agreement #OS0007 Me me me! I'll sponsor this one, although it may take me until about the 10th of the month to do much with it. -dp -- Daniel Price - Solaris Kernel Engineering - dp at eng.sun.com - blogs.sun.com/dp
[request-sponsor] Round2: Sponsor Proposal
On Thu 27 Oct 2005 at 08:18PM, Mike Kupfer wrote: > > "dep" == David Powell writes: > > dep> One of the problems is that we have no good way to measure the > dep> quality of their mentoring. > > I think the idea was to treat the level-3 folks as interns, similar to > the way new ARC members are brought on board. > > It's been several years since I was on LSARC, but (IIRC) the way we > handled it was that every case got assigned a regular ARC member as the > owner, whether or not there was an intern. If there was an intern, the > intern did most of the work. But the owner got cc'd on all the email. > > Would something like that be sufficient to address your concerns here? ARC interns are (afaik) already experienced engineers. I'm adding a big +1 to what Dave has said thus far; he has made, to me anyway, a persuasive argument that building mentorships, relationships, skills and knowledge is the core task here. I had originally written up some thoughts about different permutations of tier 2, 3, flow of control, etc. but I think I know have to go do some more thinking about what Dave has said, instead. -dp -- Daniel Price - Solaris Kernel Engineering - dp at eng.sun.com - blogs.sun.com/dp
[request-sponsor] please read: sponsor proposal
On Fri 21 Oct 2005 at 02:17PM, Bonnie Corwin wrote: > > What's the minimum qualification for membership in tier 3? > > There is no minimum qualification which is the reason for the partner > requirement. I don't agree with this structure, then. I think that at a minimum, one should be considered a trained, qualified, and active contributor to the release in question. -dp -- Daniel Price - Solaris Kernel Engineering - dp at eng.sun.com - blogs.sun.com/dp
[request-sponsor] please read: sponsor proposal
On Fri 21 Oct 2005 at 12:49PM, Bonnie Corwin wrote: > Nope - you're not the first, so this is my error. > > The original concept of sponsoring had two tiers: CRT advocates and > sponsors. Both tiers require some amount of experience working in and > putting back to the O/N source hierarchy. Both can take a request and > run with it. > > Now there is a third tier which will allow more people to participate. > But people in the third tier need to partner with someone in one of the > other tiers to gain experience. What's the minimum qualification for membership in tier 3? -dp -- Daniel Price - Solaris Kernel Engineering - dp at eng.sun.com - blogs.sun.com/dp
