From Richard.Elling at Sun.COM Tue May 1 10:28:32 2007 From: Richard.Elling at Sun.COM (Richard Elling) Date: Tue, 01 May 2007 10:28:32 -0700 Subject: [approach-discuss] Re: [tools-discuss] Pkg proposal: top In-Reply-To: <5b5090780704301929n379abfd0l28e02449390f2836@mail.gmail.com> References: <5b5090780704301705v4e5ef5cvd56ac0fe395328b1@mail.gmail.com> <20070501001643.GB641694@sun.com> <5b5090780704301719o51810845je2cf73ea00c23786@mail.gmail.com> <20070501002845.GB654502@sun.com> <5b5090780704301740s4001029asa72d28dda0e9edc4@mail.gmail.com> <46369694.5080409@sun.com> <5b5090780704301929n379abfd0l28e02449390f2836@mail.gmail.com> Message-ID: <463778C0.9020004@sun.com> Brian Gupta wrote: > Solaris ships with top, but it is cleverly hidden on the Companion CD, > and has been for uhmm... maybe 10 years or so. Perhaps the only issue > here is the bundling and PATH? > > Does it have to remain hidden? /usr/bin/top would probably be an easier > place to find it. A solution might be as simple as top being linked to a > script that explains to users prstat useage. Intercepting top just won't work. You are correct that this is an approachability problem in that it should be in the default PATH, even if it is not in /usr/bin. I've not kept up with the SFW or related discussions, which is where this will most likely take place. http://www.opensolaris.org/jive/forum.jspa?forumID=116&start=0 > There are many of us who get used to the features of prstat that don't > exist in top, and therefore forget top exists. Going forward, the > system > monitor may win over both, presuming we can put into it the features > we need. > -- richard > > > What is "The system monitor"? (Could you please provide a link?) Could > "system monitor" support prstat and top "perrsonalities"? Launch -> All Applications -> System Tools -> Performance Monitor What I like about it is that you can quickly resort. I must be getting lazy... :-) -- richard From Nicolas.Williams at sun.com Tue May 1 10:49:56 2007 From: Nicolas.Williams at sun.com (Nicolas Williams) Date: Tue, 1 May 2007 12:49:56 -0500 Subject: [approach-discuss] Re: [tools-discuss] Pkg proposal: top In-Reply-To: <463778C0.9020004@sun.com> References: <5b5090780704301705v4e5ef5cvd56ac0fe395328b1@mail.gmail.com> <20070501001643.GB641694@sun.com> <5b5090780704301719o51810845je2cf73ea00c23786@mail.gmail.com> <20070501002845.GB654502@sun.com> <5b5090780704301740s4001029asa72d28dda0e9edc4@mail.gmail.com> <46369694.5080409@sun.com> <5b5090780704301929n379abfd0l28e02449390f2836@mail.gmail.com> <463778C0.9020004@sun.com> Message-ID: <20070501174955.GY21027@Sun.COM> On Tue, May 01, 2007 at 10:28:32AM -0700, Richard Elling wrote: > Brian Gupta wrote: > >Does it have to remain hidden? /usr/bin/top would probably be an easier > >place to find it. A solution might be as simple as top being linked to a > >script that explains to users prstat useage. > > Intercepting top just won't work. You are correct that this is an > approachability problem in that it should be in the default PATH, even > if it is not in /usr/bin. It should be in /usr/bin/. Making top(1) tell you about prstat might be acceptable if that doesn't intrude too much (i.e., find some unused whitespace in the top screen, or steal a line of output and display a note there -- don't make the user have to "click through" such a note). How about re-implementing top to work the way prstat does (i.e., make it more efficient) but keeping the top UI? > I've not kept up with the SFW or related discussions, which is where > this will most likely take place. The conclusion of those discussions is to integrate/move all non- conflicting commands into /usr/bin (with symlinks left behind where commands are being moved). Nico -- From David.Comay at Sun.COM Tue May 1 12:59:18 2007 From: David.Comay at Sun.COM (David.Comay at Sun.COM) Date: Tue, 1 May 2007 12:59:18 -0700 (PDT) Subject: [gnu-sol-discuss] Re: [approach-discuss] Re: [tools-discuss] Pkg proposal: top In-Reply-To: <20070501174955.GY21027@Sun.COM> References: <5b5090780704301705v4e5ef5cvd56ac0fe395328b1@mail.gmail.com> <20070501001643.GB641694@sun.com> <5b5090780704301719o51810845je2cf73ea00c23786@mail.gmail.com> <20070501002845.GB654502@sun.com> <5b5090780704301740s4001029asa72d28dda0e9edc4@mail.gmail.com> <46369694.5080409@sun.com> <5b5090780704301929n379abfd0l28e02449390f2836@mail.gmail.com> <463778C0.9020004@sun.com> <20070501174955.GY21027@Sun.COM> Message-ID: > Making top(1) tell you about prstat might be acceptable if that doesn't > intrude too much (i.e., find some unused whitespace in the top screen, > or steal a line of output and display a note there -- don't make the > user have to "click through" such a note). One thing I've noticed with at least Ubuntu is the version of top(1) that's shipped differs in a number of ways from the "classic" top that William LeFebvre maintains at http://www.groupsys.com/topinfo/ I think even the man page alludes to it being a reimplementation. So I would prefer seeing prstat(1M) augmented to provide missing information that top provides *where* it makes sense and perhaps provide a compatibility mode to prtstat (which /usr/bin/top could invoke.) dsc From peter.tribble at gmail.com Tue May 1 15:02:47 2007 From: peter.tribble at gmail.com (Peter Tribble) Date: Tue, 1 May 2007 23:02:47 +0100 Subject: [approach-discuss] Re: [tools-discuss] Pkg proposal: top In-Reply-To: <46369694.5080409@sun.com> References: <5b5090780704301705v4e5ef5cvd56ac0fe395328b1@mail.gmail.com> <20070501001643.GB641694@sun.com> <5b5090780704301719o51810845je2cf73ea00c23786@mail.gmail.com> <20070501002845.GB654502@sun.com> <5b5090780704301740s4001029asa72d28dda0e9edc4@mail.gmail.com> <46369694.5080409@sun.com> Message-ID: [recipients trimmed] On 5/1/07, Richard Elling wrote: > Solaris ships with top, but it is cleverly hidden on the Companion CD, > and has been for uhmm... maybe 10 years or so. Perhaps the only issue > here is the bundling and PATH? > > There are many of us who get used to the features of prstat that don't > exist in top, and therefore forget top exists. What are those features? I vastly prefer top, and have wondered whether to expend effort on enhancing prstat to match top, or just continue to use top anyway. The course of least effort wins. > Going forward, the system > monitor may win over both, presuming we can put into it the features we need. Like not simply putting up a grey window saying "the application gnome-system-monitor has crashed". Or improving its performance by at least a factor of 100 to bring it to within acceptable limits. Or working in a dumb telnet or ssh window. We should just ship top and make the customers and users that want it happy. -- -Peter Tribble http://www.petertribble.co.uk/ - http://ptribble.blogspot.com/ From Richard.Elling at Sun.COM Tue May 1 15:41:46 2007 From: Richard.Elling at Sun.COM (Richard Elling) Date: Tue, 01 May 2007 15:41:46 -0700 Subject: [approach-discuss] Re: [tools-discuss] Pkg proposal: top In-Reply-To: References: <5b5090780704301705v4e5ef5cvd56ac0fe395328b1@mail.gmail.com> <20070501001643.GB641694@sun.com> <5b5090780704301719o51810845je2cf73ea00c23786@mail.gmail.com> <20070501002845.GB654502@sun.com> <5b5090780704301740s4001029asa72d28dda0e9edc4@mail.gmail.com> <46369694.5080409@sun.com> Message-ID: <4637C22A.3090906@sun.com> Peter Tribble wrote: > [recipients trimmed] > > On 5/1/07, Richard Elling wrote: >> Solaris ships with top, but it is cleverly hidden on the Companion CD, >> and has been for uhmm... maybe 10 years or so. Perhaps the only issue >> here is the bundling and PATH? >> >> There are many of us who get used to the features of prstat that don't >> exist in top, and therefore forget top exists. > > What are those features? I vastly prefer top, and have wondered whether to > expend effort on enhancing prstat to match top, or just continue to use > top anyway. The course of least effort wins. top is too simple to use on systems with lots of CPUs, processes, or zones. prstat is integrated into the Solaris resource management features so that you can filter out the stuff you don't want to see. What I use mostly is microstate displays, zones, and lwp information. It would be cool to extend top to do this, but it might be a lot of work. NB. system monitor suffers from some of the same scalability issues as top. >> Going forward, the system >> monitor may win over both, presuming we can put into it the features >> we need. > > Like not simply putting up a grey window saying "the application > gnome-system-monitor has crashed". works for me, log a bug. > Or improving its performance by at least a factor of 100 to bring it to > within acceptable limits. it is open source. > Or working in a dumb telnet or ssh window. geez, next you'll want it to support cell phone displays... :-) I have found it to be useful for newbies who have some experience with other platforms, notably windows. It is kinda fun to blow their minds with the memory map ;-) > We should just ship top and make the customers and users that want it > happy. Rephrase: We should just ship top in the end-user cluster, located in /usr/bin, and make the customers and users that want it happy. -- richard From brian.gupta at gmail.com Tue May 1 15:52:44 2007 From: brian.gupta at gmail.com (Brian Gupta) Date: Tue, 1 May 2007 18:52:44 -0400 Subject: [approach-discuss] Re: [tools-discuss] Pkg proposal: top In-Reply-To: References: <5b5090780704301705v4e5ef5cvd56ac0fe395328b1@mail.gmail.com> <20070501001643.GB641694@sun.com> <5b5090780704301719o51810845je2cf73ea00c23786@mail.gmail.com> <20070501002845.GB654502@sun.com> <5b5090780704301740s4001029asa72d28dda0e9edc4@mail.gmail.com> <46369694.5080409@sun.com> Message-ID: <5b5090780705011552k7597f146q2fe1f85fa1dd6dba@mail.gmail.com> I found this interesting document comparing top and prstat: http://www.brendangregg.com/DTrace/prstatvstop.html Summary: --------------- There are arguments for both approaches. Prstat is very closely in sync with Solaris, offering fine grained operations, while having a lower CPU load. Top offers a wide variety of process information, with a wide set of viewing and sorting modes. Top performance is rarely a common issue today, unless you are either using very old hardware, or have massively over provisioned your CPUs. (Best to read it your self, I may have done a bad job paraphrasing) Cheers, Brian -------------- next part -------------- An HTML attachment was scrubbed... URL: From brian.gupta at gmail.com Thu May 31 07:24:39 2007 From: brian.gupta at gmail.com (Brian Gupta) Date: Thu, 31 May 2007 10:24:39 -0400 Subject: [approach-discuss] Re: [osol-discuss] Re: [ogb-discuss] Project Proposal - (what is/was Indiana) In-Reply-To: <5b5090780705310712l4f164c9x7342c1e7bf8eade7@mail.gmail.com> References: <465DFDB0.2050704@sun.com> <20070530231648.GB321658@sun.com> <465E1E98.40207@sun.com> <20070531013922.GE352016@sun.com> <465E63FD.3020307@Sun.Com> <18014.49487.56784.439092@gargle.gargle.HOWL> <637459C5-484E-46DF-ACD6-0F8F6A3C055A@Sun.COM> <18014.54205.352669.793330@gargle.gargle.HOWL> <5b5090780705310712l4f164c9x7342c1e7bf8eade7@mail.gmail.com> Message-ID: <5b5090780705310724q542b8677vd5b85801912a58f6@mail.gmail.com> One other comment. Generally, a project proposal, would be posted to the interested communities for comment, before being submitted fait acompli to the OGB. (I have cc'ed in those communities that I think, at a minimum, should be included brian On 5/31/07, Brian Gupta wrote: > I was in the process of writing my own proposal for a reference build > (I got sidetracked because of all the distracting Indiana discussion), > I am including my incomplete draft proposal for consideration and > comment: > > Proposal OpenSolaris Reference Distribution v0.1 > > 1. Introduction and motivation > > 1.1 Summary > > This project proposes to develop and release weekly distributions that > would be used by OpenSolaris as their reference platform to develop on. > > This is similar to the role Solaris Express Community Edition plays now, > But would be sustained and maintained by the OpenSolaris community, > rather than Sun. The problem with SXCS is that it is not OpenSolaris, > but rather a commercial operating system built by Sun. > > One of the serious issues with this approach, is that developing > OpenSolaris code on a Solaris distribution does not provide any > technical guarantees that the resulting code in unencumbered. > > The motivation behind this proposal is to change the development > environment as it exists today, to put all distributions on equal > footing. If the development platform is unencumbered there is a fair > amount of certainty that the resulting code will be as well. > > 1.2 History and context > > Until recently Solaris and OpenSolaris were controlled by the same > organization, Sun Microsystems. Recently OpenSolaris became an > independent organization, with it's own governing structures and > Constitution. > > After this independence OpenSolaris did not start producing their > own reference distribution, instead continuing to rely on Sun's > Solaris Express Community Edition weekly releases. > > 2. Discussion > > 2.1 Functionality > > There are certain certain bits in Solaris that have not been released > to the community. This new Reference Distribution would be built > without those components. Applicable suitable open source > replacements would be found. If there isn't a suitable replacement, > it would be incumbent upon the OpenSolaris community to develop > suitable replacements. > > 2.2 Components > > 2.3 Documentation > > 2.4 Future projects > > 3. Interfaces > > 3.1 Imported interfaces > > 3.2 Exported interfaces Bundled files > > 4. References > > In addition I have started a Wiki page where we can capture some of > the descions made by the project team. > http://www.genunix.org/wiki/index.php?title=OpenSolaris_Reference_Build > > cheers, > brian > > On 5/31/07, James Carlson wrote: > > Simon Phipps writes: > > > On May 31, 2007, at 13:36, James Carlson wrote: > > > > > > > I don't think anyone is saying that you can't create a distribution > > > > yourself without bothering with any project, community, or governing > > > > board. You can. Knock yourself out. > > > > > > But that's not what's happening. If a Sun-sponsored team went off > > > outside the scope of the community and created a distribution like > > > the one being proposed as "Indiana", all hell would break loose here. > > > > The part that you snipped away was where John Plocher was asserting > > that this case would somehow prevent future distributions (such as the > > ones we now have) from even starting. I don't believe that's the > > case. > > > > > We are now at the stage where (as John Plocher said) for some reason > > > some high-profile individuals are "throwing up logistical barriers to > > > this effort instead of facilitating them", something that has not > > > seemed to happen to a project proposal on OpenSolaris before. > > > > I just don't see it that way. Is having a community endorse this > > project a "barrier?" And one that necessarily causes undue hardship? > > > > If so, then perhaps it's time to amend the constitution we just > > ratified. Merely ignoring it doesn't seem like a reasonable option to > > me. > > > > > Thus, as a community member, I'd like to see a team form and get > > > started. I would really like to see the OGB we elected facilitate > > > rather than obstruct, please. > > > > So far, I haven't seen anyone trying to obstruct. > > > > -- > > James Carlson, Solaris Networking > > Sun Microsystems / 1 Network Drive 71.232W Vox +1 781 442 2084 > > MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677 > > _______________________________________________ > > opensolaris-discuss mailing list > > opensolaris-discuss at opensolaris.org > > > From webmink at sun.com Thu May 31 07:41:44 2007 From: webmink at sun.com (Simon Phipps) Date: Thu, 31 May 2007 15:41:44 +0100 Subject: [approach-discuss] Re: [osol-discuss] Re: [ogb-discuss] Project Proposal - (what is/was Indiana) In-Reply-To: <5b5090780705310724q542b8677vd5b85801912a58f6@mail.gmail.com> References: <465DFDB0.2050704@sun.com> <20070530231648.GB321658@sun.com> <465E1E98.40207@sun.com> <20070531013922.GE352016@sun.com> <465E63FD.3020307@Sun.Com> <18014.49487.56784.439092@gargle.gargle.HOWL> <637459C5-484E-46DF-ACD6-0F8F6A3C055A@Sun.COM> <18014.54205.352669.793330@gargle.gargle.HOWL> <5b5090780705310712l4f164c9x7342c1e7bf8eade7@mail.gmail.com> <5b5090780705310724q542b8677vd5b85801912a58f6@mail.gmail.com> Message-ID: On May 31, 2007, at 15:24, Brian Gupta wrote: > One other comment. Generally, a project proposal, would be posted to > the interested communities for comment, before being submitted fait > acompli to the OGB. (I have cc'ed in those communities that I think, > at a minimum, should be included Actually, I agree with James that the project is so far-reaching that it's a community-wide issue - I think Glynn did the right thing approaching the OGB and osol-discuss lists, although it's good to see which lists you think are affected too. I'd like to see the OGB give positive, supportive guidance (as well as to see your proposal and Glynn's harmonised), probably by selecting or creating a community to work on the proposal you and Glynn are pioneering. But even if it was the wrong choice, I'm eager to have us all channel this "stop energy" and suspicion of Sun into something positive. For goodness sake, Sun's executives are agreeing with you and investing in the idea you were discussing! For folks on those lists Brian added that aren't on OSOL-Discuss: Glynn's proposal can be found at: http://mail.opensolaris.org/pipermail/opensolaris-discuss/2007-May/ 030366.html S. From brian.gupta at gmail.com Thu May 31 07:51:05 2007 From: brian.gupta at gmail.com (Brian Gupta) Date: Thu, 31 May 2007 10:51:05 -0400 Subject: [approach-discuss] Re: [osol-discuss] Re: [ogb-discuss] Project Proposal - (what is/was Indiana) In-Reply-To: References: <465DFDB0.2050704@sun.com> <465E1E98.40207@sun.com> <20070531013922.GE352016@sun.com> <465E63FD.3020307@Sun.Com> <18014.49487.56784.439092@gargle.gargle.HOWL> <637459C5-484E-46DF-ACD6-0F8F6A3C055A@Sun.COM> <18014.54205.352669.793330@gargle.gargle.HOWL> <5b5090780705310712l4f164c9x7342c1e7bf8eade7@mail.gmail.com> <5b5090780705310724q542b8677vd5b85801912a58f6@mail.gmail.com> Message-ID: <5b5090780705310751t3561e065v3bfefbffa30fe35@mail.gmail.com> On 5/31/07, Simon Phipps wrote: > > On May 31, 2007, at 15:24, Brian Gupta wrote: > > > One other comment. Generally, a project proposal, would be posted to > > the interested communities for comment, before being submitted fait > > acompli to the OGB. (I have cc'ed in those communities that I think, > > at a minimum, should be included > > Actually, I agree with James that the project is so far-reaching that > it's a community-wide issue - I think Glynn did the right thing > approaching the OGB and osol-discuss lists, although it's good to see > which lists you think are affected too. I'd like to see the OGB give > positive, supportive guidance (as well as to see your proposal and > Glynn's harmonised), probably by selecting or creating a community to > work on the proposal you and Glynn are pioneering. Would it make sense for a new community called "distros" to be created, with the Reference build being one of possibly many projects within this community? > But even if it was the wrong choice, I'm eager to have us all channel > this "stop energy" and suspicion of Sun into something positive. For > goodness sake, Sun's executives are agreeing with you and investing > in the idea you were discussing! +1 > For folks on those lists Brian added that aren't on OSOL-Discuss: > Glynn's proposal can be found at: > http://mail.opensolaris.org/pipermail/opensolaris-discuss/2007-May/ > 030366.html From al at logical-approach.com Thu May 31 08:28:29 2007 From: al at logical-approach.com (Al Hopper) Date: Thu, 31 May 2007 10:28:29 -0500 (CDT) Subject: [approach-discuss] Re: [osol-discuss] Re: [ogb-discuss] Project Proposal - (what is/was Indiana) In-Reply-To: References: <465DFDB0.2050704@sun.com> <20070530231648.GB321658@sun.com> <465E1E98.40207@sun.com> <20070531013922.GE352016@sun.com> <465E63FD.3020307@Sun.Com> <18014.49487.56784.439092@gargle.gargle.HOWL> <637459C5-484E-46DF-ACD6-0F8F6A3C055A@Sun.COM> <18014.54205.352669.793330@gargle.gargle.HOWL> <5b5090780705310712l4f164c9x7342c1e7bf8eade7@mail.gmail.com> <5b5090780705310724q542b8677vd5b85801912a58f6@mail.gmail.com> Message-ID: On Thu, 31 May 2007, Simon Phipps wrote: > > On May 31, 2007, at 15:24, Brian Gupta wrote: > >> One other comment. Generally, a project proposal, would be posted to >> the interested communities for comment, before being submitted fait >> acompli to the OGB. (I have cc'ed in those communities that I think, >> at a minimum, should be included > > Actually, I agree with James that the project is so far-reaching that it's a > community-wide issue - I think Glynn did the right thing approaching the OGB Agreed - it's a community-wide issue. I would have preferred to have seen Glynns proposal go through some discussion and refinement via osol-discuss before being presented to the OGB. It currently feels unrefined, disorganized and very "last minute" in its current form (IMHO). Which is strange - since its been widely anticipated for weeks now. > and osol-discuss lists, although it's good to see which lists you think are > affected too. I'd like to see the OGB give positive, supportive guidance (as > well as to see your proposal and Glynn's harmonised), probably by selecting > or creating a community to work on the proposal you and Glynn are pioneering. Agreed. Lets see the OGB say "this is how to proceed". > But even if it was the wrong choice, I'm eager to have us all channel this > "stop energy" and suspicion of Sun into something positive. For goodness > sake, Sun's executives are agreeing with you and investing in the idea you > were discussing! Both these project proposals are only good news for OpenSolaris. And its really exciting to see that resources are being made available from the very highest levels of Sun management. > For folks on those lists Brian added that aren't on OSOL-Discuss: Glynn's > proposal can be found at: > http://mail.opensolaris.org/pipermail/opensolaris-discuss/2007-May/030366.html One point I'd like to emphasize, is that if the OGB say (something like) "process A has to be followed" then they should ensure that the implementation resources are pre-allocated to ensure that this happens smoothly and quickly. IOW the resources to ensure that "process A" can be implemented and completed in a timely manner. And this would include having people with the necessary tools/training etc. be ready, willing and able to perform the necessary duties to get it done expeditiously. Then announce it. Regards, Al Hopper Logical Approach Inc, Plano, TX. al at logical-approach.com Voice: 972.379.2133 Fax: 972.379.2134 Timezone: US CDT OpenSolaris Governing Board (OGB) Member - Apr 2005 to Mar 2007 http://www.opensolaris.org/os/community/ogb/ogb_2005-2007/ From Glynn.Foster at Sun.COM Thu May 31 10:14:49 2007 From: Glynn.Foster at Sun.COM (Glynn Foster) Date: Fri, 01 Jun 2007 05:14:49 +1200 Subject: [approach-discuss] Re: [osol-discuss] Re: [ogb-discuss] Project Proposal - (what is/was Indiana) In-Reply-To: References: <465DFDB0.2050704@sun.com> <20070530231648.GB321658@sun.com> <465E1E98.40207@sun.com> <20070531013922.GE352016@sun.com> <465E63FD.3020307@Sun.Com> <18014.49487.56784.439092@gargle.gargle.HOWL> <637459C5-484E-46DF-ACD6-0F8F6A3C055A@Sun.COM> <18014.54205.352669.793330@gargle.gargle.HOWL> <5b5090780705310712l4f164c9x7342c1e7bf8eade7@mail.gmail.com> <5b5090780705310724q542b8677vd5b85801912a58f6@mail.gmail.com> Message-ID: <465F0289.2050705@sun.com> Hey, Al Hopper wrote: > I would have preferred to have seen Glynns proposal go through some > discussion and refinement via osol-discuss before being presented to the > OGB. It currently feels unrefined, disorganized and very "last minute" > in its current form (IMHO). Which is strange - since its been widely > anticipated for weeks now. I have a lot better docs [1] than this one that are a little bit more refined, however I was trying to engage the project proposal process, and really struggled with some of the questions. Glynn [1] Just remember, this is *real time* discussion - there's obviously bits and pieces that we haven't yet figured out. From brian.gupta at gmail.com Thu May 31 10:28:44 2007 From: brian.gupta at gmail.com (Brian Gupta) Date: Thu, 31 May 2007 13:28:44 -0400 Subject: [approach-discuss] Thread to discuss goals for OpenSolaris reference build. (Indiana) Message-ID: <5b5090780705311028h5d8d881bkdc166132616dcd58@mail.gmail.com> I have started compiling a list of goals as a starting point for discussion. I am mainting this list on the following wiki page, but have included the current list to kickstart the conversation: http://www.genunix.org/wiki/index.php/OpenSolaris_Reference_Build#Goals Goals -------- * Support multiple package sets, including a very small, minimal build * Support installation from a minimal boot image, that allows installation from an online package repository. (That includes ON components) * Fully modularized. This even applied to the ON consolidation (This aids in the building of a variety of distros) * Provide a community OpenSolaris development platform. (Currently the only option is SXCE, which is technically a Sun distro. * Must free of all encumbered IP. (IE: It must wholey consist of open-source components) o In answer to how to support binary drivers, the package repository would enable the selection to install proprietary packages, either by reference to the original source or via a redistribution agreement. * Provides a Solaris Standard base to test application compatibility From brian.gupta at gmail.com Thu May 31 22:31:52 2007 From: brian.gupta at gmail.com (Brian Gupta) Date: Fri, 1 Jun 2007 01:31:52 -0400 Subject: [approach-discuss] Like minded individuals let's start working on an "OpenSolaris.org" distro right now. Message-ID: <5b5090780705312231k3c588c09m6b72e75122c2ec03@mail.gmail.com> This thread is for those that *ARE* interested in seeing an OpenSolaris hosted distribution come to fruition. I am starting this in the approach-discuss community, because it is as good a CG (Community Group) as any. I have cross posted to many other communities that *I* felt might want to be a part of this discussion. I have also included the Blastwave community. (Blastwave folks, send an email to approach-discuss-subscribe at opensolaris.org if you want to be a part of the discussion). I apologize in advance for this massive cross posting. I also hope that i did not leave out any CG, or individual that should have been included. (Please feel free to let them know to subscribe to approach-discuss) What this thread is *NOT*: -------------------------------------- This thread is *NOT* a thread were it is appropriate to stage your resistance to an OpenSolaris branded distro. (There are plenty of those going on as well) This thread is *NOT* to discuss how to propose this an official project. (too soon in my opinion) This thread is *NOT* a thread about opensolaris.org governance. (There are plenty of those going on) What this thread *IS*: -------------------------------- This thread *IS* for discussing the logistics of building this distribution. Appropriate topics would include what needs to be done, who is willing to do what, and what are our common goals. Proposals: ---------------- I propose that, for the time being, we use the approach-discuss at opensolaris.org as our discussion forum. (Please register ASAP) I also propose that if you are in favor of this distro coming to be, that you respond to this thread. Please do this even if you can not contribute. It will give other like minded individuals moral support. ;) I also propose referring to this project as OSH (Just so we have a non-controversial name to call it). Naming is something that should be addressed later. Please, let's not belabor this point. I also propose that we need to reach out to the current distros, to see if they would like to be involved in contributing to this distro. (Any volunteers?) Thank You, Brian Gupta P.S. - Please note, that from now on, when I say should, or is, or do, there is an automatic I feel/think/suspect/wonder/please added in front of it. :) P.S.S. - This is really the time to step up and reply, if you are in favor of this. From freetown at gmail.com Thu May 31 23:40:20 2007 From: freetown at gmail.com (Giles Turner) Date: Fri, 1 Jun 2007 14:40:20 +0800 Subject: [approach-discuss] Like minded individuals let's start working on an "OpenSolaris.org" distro right now. In-Reply-To: <5b5090780705312231k3c588c09m6b72e75122c2ec03@mail.gmail.com> References: <5b5090780705312231k3c588c09m6b72e75122c2ec03@mail.gmail.com> Message-ID: > I also propose that if you are in favor of this distro coming to be, > that you respond to this thread. Please do this even if you can not > contribute. It will give other like minded individuals moral support. > ;) aye From dclarke at blastwave.org Thu May 31 23:47:29 2007 From: dclarke at blastwave.org (Dennis Clarke) Date: Fri, 1 Jun 2007 02:47:29 -0400 (EDT) Subject: [approach-discuss] Like minded individuals let's start working on an "OpenSolaris.org" distro right now. In-Reply-To: References: <5b5090780705312231k3c588c09m6b72e75122c2ec03@mail.gmail.com> Message-ID: <34749.72.39.216.186.1180680449.squirrel@mail.blastwave.org> >> I also propose that if you are in favor of this distro coming to be, >> that you respond to this thread. Please do this even if you can not >> contribute. It will give other like minded individuals moral support. >> ;) > aye Dennis From freetown at gmail.com Thu May 31 22:43:31 2007 From: freetown at gmail.com (Giles Turner) Date: Fri, 1 Jun 2007 13:43:31 +0800 Subject: [approach-discuss] Like minded individuals let's start working on an "OpenSolaris.org" distro right now. In-Reply-To: <5b5090780705312231k3c588c09m6b72e75122c2ec03@mail.gmail.com> References: <5b5090780705312231k3c588c09m6b72e75122c2ec03@mail.gmail.com> Message-ID: > I also propose that if you are in favor of this distro coming to be, > that you respond to this thread. Please do this even if you can not > contribute. It will give other like minded individuals moral support. > ;) aye.