Re: [osol-discuss] How to compile libc or pthread ?
Surely DTrace would be a far better profiling option. Regards, Alan Hargreaves On 11/26/10 05:43, Afantee Lee wrote: Hi, Ian The reason I want to compile pthread model under libc is: I am doing a project, which requires profiling the timing information of the pthread events. thus, My plan is, compile current pthread lib first, then, add profiling code, and recompile it. your suggestions will be greatly appreciated Bests, have a nice thanks giving -- Alan Hargreaves | Principal Technical Support Engineer | Principal Field Technologist Solaris and Networking | Global Systems Support Email: alan.hargrea...@oracle.com Blog: alanhargreaves.wordpress.com Phone: +61-2-8413-5324 | Mobile: +61-416-207-573 Oracle Global Customer Services The MSC and SunSolve Will Soon Retire Find out what you need to know about the migration to My Oracle Support Hardware and Software, Engineered to Work Together Oracle is committed to developing practices and products that help protect the environment ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] The Illumos Project
On 08/02/10 17:20, Cyril Plisko wrote: On Mon, Aug 2, 2010 at 8:40 AM, Stefan Parvu wrote: A number of the community leaders from the OpenSolaris community have been working quietly together on a new effort called Illumos, and we're Why quietly ? Is this a secret organization or !? If you value the community why haven't you talked public *before* your project has started ? I think that is something very much deep inside the community - the love for secrecy. Remember "Secret Six" - many years ago when Sun stopped Solaris x86. Then OpenSolaris Pilot, then many OpenSolaris projects, that were done secretly. It is quite hard to change people' mind and way of thinking. We (community) will get there (being open) eventually, but it will take quite some time. Maybe it's as simple as a few people getting sufficiently sick of seeing the discussion boards full of people saying "Someone should do this" and "Someone should do that"; and decided to simply do something instead of complaining that someone else should do something? Alan Hargreaves (who really has no idea what they will be announcing) ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] good news- opensolaris updated roadmap
bsd wrote: You're right. Someone will still be waiting after 120 days for customer service to come back and help them. Why they continue to wait, who knows? Your implication that a call can be logged with support and no customer contact in 90-120 days is way outside of any kind of process and should have been flagged to management *WELL* before this kind of time. If you can provide me with evidence of such (eg a case number), I would be happy to investigate. I will take the absence of any such evidence to be confirmation that you are simply spreading FUD. Regards, Alan Hargreaves ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] good news- opensolaris updated roadmap
On 6/14/2010 2:09 AM, bsd wrote: I can only think those who keep waiting and waiting for the next release are those who were put on hold by customer service 90 days ago. They are still on hold waiting for someone on customer service to return and pick up. As someone who takes enormous pride in the work I do with Customer service, I can't help but take that statement personally and be terribly insulted by it. I think you need to back up that statement or retract it. Alan Hargreaves ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Any idea of why snv 134 won't accept 'set brand=native' in zonezfg command?
The native brand does not exist in OpenSolaris. The brand you want is "ipkg". Regards, Alan Hargreaves Alex Bisoyannis wrote: Native brands work only on normal Solaris, not OpenSolaris. On Fri, May 28, 2010 at 5:19 PM, Henry Pepper <mailto:henryp...@gmail.com>> wrote: Hi I'm running snv 134 on x86. I've run -- zonecfg -z test create set zonepath=/zones/test set brand=native verify -- I get: -- test: unknown brand. test: Invalid document -- 'lx' and 'ipkg' works fine 'solaris10' brand fails as well. Any idea of what the problem is? Henry ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org <mailto:opensolaris-discuss@opensolaris.org> ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Garrett D'Amore still at Oracle?
Title: signature There were some issues with the email servers over the weekend. Regards, Alan Hargreaves ольга крыжановская wrote: Is Garrett D'Amore still at Oracle? His mail post box is over flowing and I get a DISCARD from the mail server. Olga -- Alan Hargreaves | Principal Technical Support Engineer Solaris and Networking | Global Systems Support Email: alan.hargrea...@oracle.com Blog: alanhargreaves.wordpress.com Phone: +61-2-9844-5379 | Mobile: +61-416-207-573 Oracle Global Customer Services Oracle is committed to developing practices and products that help protect the environment ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Oracle charging for ODF plugin
Responses inline: Svein Skogen wrote: On 22.04.2010 02:27, Alan Hargreaves wrote: You miss the point. This is a discussion list about OpenSolaris. Not about a Microsoft Office Plugins. Not about Solaris. Not about Solaris patches. The only reason to post this stuff (even without comment) would be to sow FUD or dissention. Or to make people aware of a quite disturbing pattern. It's possible, but it looks more like an attempt to weave a conspiracy (which is always possible no matted where you choose to look for your "facts"). Like many here, I have high hopes for OpenSolaris remaining the absolutely best alternative out there for many tasks, but the pattern of changes Oracle are making is rather disturbing. Especially combined with the total lack of communication skills.> Killing the conversation isn't the solution. Again, the things Oracle *has* officially stated about OpenSolaris have been to the positive, and reference is being continually made to them by folks like Matthias. [joke deleted] Quite honestly I'm getting sick of seeing it. Then forward the worrying upwards in the system you now are part of, and let the managers sort things out (usually by escalating it to someone who actually have the authority to do something about the actual problem: Lack of communications). You know what I find really offensive about this statement? It's the implication that those of us who are inside Oracle (as technical people with an interest in OpenSolaris) are NOT doing this. You have no idea what Oracle employees who work with OpenSolaris are doing and saying internally and to imply otherwise is incredibly presumptive. I think it safe to say at the very least that there are a LOT of folks involved in VERY active discussions on many levels internally. There are a lot of us who have put a lot of our lives and ourselves into this project and to even imply that we are sitting on our backsides twiddling our thumbs while this all happens is certainly not helpful and hardly encouraging for us to keep the discussions going. > Killing the conversation isn't the solution. I am not and was not advocating killing the conversation. However talking about the right thing in the right forums would certainly help. I know that there are folks on this forum who *are* engaging their sales representatives, and I've even seen a few writing to Larry Ellison. I also know that there is also a large number of people on this forum that all they have done is to write to this forum. This question is not directed at anyone in particular. It's directed at everyone. One of these actions is helpful. One is not. Which camp do you fall in to? Regards, Alan Hargreaves -- Alan Hargreaves | Principal Technical Support Engineer Solaris and Networking | Global Systems Support Email: alan.hargrea...@oracle.com Blog: <http://alanhargreaves.wordpress.com> Phone: +61-2-9844-5379 | Mobile: +61-416-207-573 Oracle Global Customer Services Oracle is committed to developing practices and products that help protect the environment ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Oracle charging for ODF plugin
Title: signature
You miss the point. This is a discussion list about OpenSolaris. Not
about a Microsoft Office Plugins. Not about Solaris. Not about Solaris
patches. The only reason to post this stuff (even without comment)
would be to sow FUD or dissention.
Quite honestly I'm getting sick of seeing it.
Alan Hargreaves
bsd wrote:
I merely posted a link to an article and refrained from saying anything about Oracle.
If I dared to say anyting about what I think about what Oracle has done so far regarding Solaris 10, patches, the plugin, and what I think they'll do with OpenSolaris, then I'd have pitchforks thrown at me.
Therefore I'm refraining from offering my opinions.
--
Alan Hargreaves | Principal Technical Support Engineer
Solaris and Networking | Global Systems Support
Email: alan.hargrea...@oracle.com
Blog: alanhargreaves.wordpress.com
Phone: +61-2-9844-5379 | Mobile: +61-416-207-573
Oracle Global Customer Services
Oracle is committed to developing practices and products
that help protect the environment
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org
Re: [osol-discuss] toshiba laptops opensolaris preinstalled
Title: signature I would seriously recommend this. Some of the warranty experiences that I have had require you to show the error exists with the tools that the vendor provides for windows. Regardless of the fact I had Solaris spewing messages about unwritable blocks on a disk, they still wanted that message from their diagnostic before they would replace it. Regards, Alan Hargreaves Alan Steinberg wrote: Another alternative is to dual-boot, moving the current Windows aside with gparted (which is on the LiveCD), and installing OpenSolaris on a separate partition. -- Alan On 04/20/10 09:04 AM, Norm Jacobs wrote: I seem to recall that some hardware vendors reluctantly offered refunds for the unused MS Windows software under the right circumstances. You might look at http://en.wikipedia.org/wiki/Windows_refund -Norm On 04/20/10 10:49 AM, Albert Lee wrote: On Tue, 20 Apr 2010 07:45:01 PDT, Edward Martinez wrote: I was wondering if i would be voiding the laptop warranty by erasing windows and installing opensolaris either on a m10 or a portege ? Warranties for general-purpose computer hardware that dictate what software you can install are unheard of! It would be a sad day for our rights if they come to pass. -Albert ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org -- Alan Hargreaves | Principal Technical Support Engineer Solaris and Networking | Global Systems Support Email: alan.hargrea...@oracle.com Blog: alanhargreaves.wordpress.com Phone: +61-2-9844-5379 | Mobile: +61-416-207-573 Oracle Global Customer Services Oracle is committed to developing practices and products that help protect the environment ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Oracle products via IPS
On 4/18/2010 9:05 PM, Alan Hargreaves wrote: On 4/18/2010 8:12 PM, Bob Palowoda wrote: One of the things that folks are going to have to get use to (that includes us new Oracle folks) is that Oracle generally does not talk about it's plans for commercial offerings before they actually announce product. Are you saying Oracle has no intention of making IPS a commercial viable? Why would they employ developers to progress the future packaging system? Should IT managers call the Oracle sales representatives to understand planning for the future? ---Bob NO, what I am saying is that Oracle doesn't talk about things until they make an announcement. No more, no less. There is nothing to read between the lines of what I said. To be even clearer, your question (addressed to technical people) was a question about Oracle using something commercially. There is no possible way that any of us could make a comment in either direction. We are not authorised to do such things. It is unlikely in the extreme that your question will get answered in this forum. Regards, Alan Hargreaves ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Oracle products via IPS
On 4/18/2010 8:12 PM, Bob Palowoda wrote: One of the things that folks are going to have to get use to (that includes us new Oracle folks) is that Oracle generally does not talk about it's plans for commercial offerings before they actually announce product. Are you saying Oracle has no intention of making IPS a commercial viable? Why would they employ developers to progress the future packaging system? Should IT managers call the Oracle sales representatives to understand planning for the future? ---Bob NO, what I am saying is that Oracle doesn't talk about things until they make an announcement. No more, no less. There is nothing to read between the lines of what I said. Regards, Alan Hargreaves ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Oracle products via IPS
One of the things that folks are going to have to get use to (that includes us new Oracle folks) is that Oracle generally does not talk about it's plans for commercial offerings before they actually announce product. Regards, Alan Hargreaves On 4/18/2010 6:45 PM, Bob Palowoda wrote: I have rather a basic question. Considering IPS is a core technology of OpenSolaris distribution and is a key component of any future release of Solaris for Oracle. Does Oracle plan to distribute their Oracle DB and other supporting applications with IPS? If not is their a general statement that Oracle will only officially declare that the SVR4 packaging will be the only way for product distribution in the future? ---Bob ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Solaris 10 - no longer free
Speculation like this leads only to fud. The release about wonderland was weeks ago ... Hardly just surfaced. Come to think of it, so was the announcement about some new features not going into opensolaris. Note that nothing was said about yanking current opensolaris features. Also there is a huge difference between public domain and the license for any free software. Please don't equate the two. Regards, Alan Hargreaves Sent from my iPod On 31/03/2010, at 11:34 PM, Mike DeMarco wrote: Two more items of interest have just surfaced: Oracle has pulled all engineers from wonderland project. Oracle has stated that going forward OpenSolaris will NOT have all packages from Solaris prime. I take this to mean if It has not been put into the public domain already it will be yanked from OpenSolaris. I wonder if this is part of the delay with 2010.3 release? Is Oracle yanking packages from this release now? -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] dtrace
You may also want to have a look at http://opensolaris.org/os/community/dtrace/shells/ Specifically the diffs, which show how the probes were added. alan. Tirthankar wrote: Refer to http://blogs.sun.com/binujp/entry/dtrace_provider_for_python Thanks, Tirthankar http://blogs.sun.com/tirthankar On 03/09/09 11:22, gautham k wrote: how to write our own probes for integrating dtrace with other scripting langauage. eg:python ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org -- Alan Hargreaves - http://blogs.sun.com/tpenta Staff Engineer (Kernel/VOSJEC/Performance) Asia Pacific/Emerging Markets Sun Microsystems ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] /bin/sh was Re: [osol-announce] No update on SXCE Build 79
The functionality to change shell is in passwd, but there is a completely wrong check in there. See CR 6638715 Checks in passwd should be authorisation based, not uid based Which I logged a few weeks back. Back onto the "Let's replace /bin/sh with thread", ... The bit that everyone putting forward this argument seems to overlook is the sheer number of scripts in ON that are written for the bourne shell. Each and every one of these would need to be verified against the new shell. We are not talking a handful of scripts here. This would be a monumental task. So far I have seen people proposing the change, but no volunteers to do this verification. It won't do itself folks. If we are going to do something, then we need to look at the *whole* job, not parts of it. Regards, Alan Hargreaves. Joerg Schilling wrote: > "Ignacio Marambio Catán" <[EMAIL PROTECTED]> wrote: > >>> Seriously; FreeBSD, NetBSD, OpenBSD, GNU/Linux, and many others all >>> provide a better /bin/sh... >>> >> what we really need is a way for users to change their own shells without >> root privileges in /etc/passwd > > I would call this a bug in passwd(1). As the user us allowed to change his > passwd, passwd(1) has the needed privileges to change /etc/passwd. There is > no reason to forbid changing the shell as user if the new and the old shell > are listed in getusershell(3). > > It worked with the chsh(1) on UCB... > > > BTW: what is "orcron(1)"? It is in the "SEE ALSO" part of the passwd(1) > man page... > >> why would you want to change /bin/sh possibly breaking thousands of scripts >> many of which are critical and can't be changed? because you want something >> that is a better interactive shell? there are many of them already, zsh, >> bash, ksh93 and as a user you can pick any of them >> as a rule i leave my root using /bin/sh but you can easily use RBAC to >> create a root like user with a different shell > > Replacing /bin/sh by ksh not only causes problems, it reduces a possible > choice > > Jörg > -- Alan Hargreaves - http://blogs.sun.com/tpenta Staff Engineer (Kernel/VOSJEC/Performance) Systems Technical Support Centre Sun Microsystems ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Correlation of snv_66 to S10 u4
Alan Hargreaves wrote: > Ray Clark wrote: >> What action should I take [1] To bring it to someone's attention, and >> [2] To get a working system in the near term. I am trying to migrate >> from Linux to Solaris, and frankly have not figured out they lay of >> the land yet. >> >> 6528189 consists of a "cp -p" over NFS to a ZFS file system failing, >> giving the message: >> >> "cp: preserving permissions for `t': Invalid argument" >> >> This is from Linux, but I found notes that I think indicated that it >> did this from Solaris too (Can't prove that my me though, only for >> Linux). >> >> Thanks. >> >> >> This message posted from opensolaris.org >> ___ >> opensolaris-discuss mailing list >> opensolaris-discuss@opensolaris.org >> > I did the backport of the fix. It works for sparc but for somereason > it's not working for x86 and I'm currently trying to work out why. > > alan. > Let me clarify that statement. The command now returns an EOPNOTSUPP, but apparantly the cp command still returns a 1 (failure) even though the copy has actually been completed. alan. -- Alan Hargreaves - http://blogs.sun.com/tpenta Staff Engineer (Kernel/VOSJEC/Performance) Systems Technical Support Centre Sun Microsystems ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] NSA has backdoors into Windows?
Alan Hargreaves wrote: Orvar Korvar wrote: I know Solaris 10 is closed source and OpenSolaris is not. I think it will be hard to review all code and compile it yourself to be sure against back doors. Just because you have the code, can read it, and compile it yourself does not guarantee anything. Earlier in the thread David Dyer-Bennet recommended Ken Thompson's 1983 Turing Award Lecture - It's titled "Reflections on Trusting Trust" and you should be able to find it on google. This is definitely recommended reading for anyone who believes that simply having the source and the ability to compile it yourself is simply insufficient. Of course I meant sufficient, not insufficient. alan. -- Alan Hargreaves - http://blogs.sun.com/tpenta Staff Engineer (Kernel/VOSJEC/Performance) Systems Technical Support Centre Sun Microsystems ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] NSA has backdoors into Windows?
Orvar Korvar wrote: > I know Solaris 10 is closed source and OpenSolaris is not. I think it will be > hard to review all code and compile it yourself to be sure against back doors. > > Just because you have the code, can read it, and compile it yourself does not guarantee anything. Earlier in the thread David Dyer-Bennet recommended Ken Thompson's 1983 Turing Award Lecture - It's titled "Reflections on Trusting Trust" and you should be able to find it on google. This is definitely recommended reading for anyone who believes that simply having the source and the ability to compile it yourself is simply insufficient. alan. -- Alan Hargreaves - http://blogs.sun.com/tpenta Staff Engineer (Kernel/VOSJEC/Performance) Systems Technical Support Centre Sun Microsystems ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Correlation of snv_66 to S10 u4
Ray Clark wrote: > What action should I take [1] To bring it to someone's attention, and [2] To > get a working system in the near term. I am trying to migrate from Linux to > Solaris, and frankly have not figured out they lay of the land yet. > > 6528189 consists of a "cp -p" over NFS to a ZFS file system failing, giving > the message: > > "cp: preserving permissions for `t': Invalid argument" > > This is from Linux, but I found notes that I think indicated that it did this > from Solaris too (Can't prove that my me though, only for Linux). > > Thanks. > > > This message posted from opensolaris.org > ___ > opensolaris-discuss mailing list > opensolaris-discuss@opensolaris.org > I did the backport of the fix. It works for sparc but for somereason it's not working for x86 and I'm currently trying to work out why. alan. -- Alan Hargreaves - http://blogs.sun.com/tpenta Staff Engineer (Kernel/VOSJEC/Performance) Systems Technical Support Centre Sun Microsystems ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] How to pass kernel command line to solaris kernel?
borun_fu wrote: such as prom_debug, map_debug. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org These need to be set in your boot environment, ie in /boot/solaris/bootenv.rc have the following line: setprop prom_debug '1' should do it. alan. -- Alan Hargreaves - http://blogs.sun.com/tpenta Staff Engineer (Kernel/VOSJEC/Performance) Systems Technical Support Centre Sun Microsystems ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] How to pass kernel command line to solaris kernel?
borun_fu wrote: such as prom_debug, map_debug. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org Boran, you're asking a lot of small discrete questions here. How about you let us know what it is that you're trying to eithe rdo or find out and we might be able to help you better. Regards, Alan. -- Alan Hargreaves - http://blogs.sun.com/tpenta Staff Engineer (Kernel/VOSJEC/Performance) Systems Technical Support Centre Sun Microsystems ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] What is the best way to deliver test bits?
I'll probably get shot down in flames for this but why not deliver them as a patch? alan. Brian Utterback wrote: Over at the NTP project, we are getting ready to deliver some bits for testing by the community. Some of the deliverables are new (ntpd, sntpd, ntpdc, etc.), some will replace things delivered in the current NTP packages (ntpdate, ntpq, etc.) and some replace man pages delivered in the man page packages. The problem is that we would like to provide test packages to install, but since these are test binaries, we want to be able to uninstall them and put everything back the way it was. The new bits are no problem of course, but how to handle the existing bits? The best thing I could come up with is to save the old bits with a preinstall script and restore them with the postremove script. Is this kosher? Will the pkgadd complain if we install files over files that are already installed? Does anybody have a better idea? Brian Utterback ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org -- Alan Hargreaves - http://blogs.sun.com/tpenta Staff Engineer (Kernel/VOSJEC/Performance) Systems Technical Support Centre Sun Microsystems ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Re: Project Proposal: libc_i18n.a rewrite.
John Sonnenschein wrote: I think I like the "Project Emancipation" title However, as for starting with all of closed bins, as I mentioned in the initial proposal, libc_i18n.a comes first. That bit *MUST* be reimplemented & shoved in to ON as fast as possible. The rest is not as important in as far as you can, theoretically, build a mostly working opensolaris distro without them. The reason why I posted a libc_i18n rewrite is because I don't want to have that finished, waiting for the rest of the emancipation project to finish before getting it in to ON. As soon as libc_i18n is done, I want it upstreamed This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org There are currently two components that are needed before one can do an open build. The first one is one that has been talked a lot about, the other is only required on SPARC, that is the sparc disassembler. If you want a project that has as it's goal to be able to build the opensolaris sources without encumbered binaries, AND you want this to be able to be done on both SPARC and x86, then both of these need to be addressed. I knwo that SPARC is not generally popular here, but if we are going to do something, it needs to be done correctly. alan. -- Alan Hargreaves - http://blogs.sun.com/tpenta Staff Engineer (Kernel/VOSJEC/Performance) Systems Technical Service Center Sun Microsystems ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Project Proposal: libc_i18n.a rewrite.
Do we have a test suite for what we have in libc_i18n.a? If so, we should make that available or at leat have someone who can run it against anything the project produces. +1 alan. Stephen Lau wrote: +1 here's my vote for a project name: Project Emancipation cheers, steve On Thu, Feb 01, 2007 at 10:07:28PM -0800, John Sonnenschein wrote: Currently, there is no possible way to build an opensolaris distribution without including the closed-source libc_i18n.a. What this means is that a traditional distribution is entirely out of the question. This is entirely unacceptable for a project which wishes to call itself "Open Source". I propose that a project be started seeking to re-implement all necessary functions locked up behind that binary. I've done a rudimentary count of the work required, and from what I can tell there's a small number ( 100 - 200 ) utility functions ( wcwidth() for example) that need a rewrite. I would prefer if this project be attached to the name of "closed-reimplementation " or something similar, due to the fact that the primary focus at first will be to remove libc_i18n.a, and that must be integrated without delay, but ultimately I'd like for closed bins to disappear completely. This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org -- Alan Hargreaves - http://blogs.sun.com/tpenta Staff Engineer (Kernel/VOSJEC/Performance) Systems Technical Service Center Sun Microsystems ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] GPLv3?
Alan Hargreaves wrote: Dennis Clarke wrote: In this community project when someone says "Rich" they generally mean Rich Teer. Or, to be more honest, *I* instantly think Rich Teer. It is like, gee, let's go ask Rich and see what he thinks and then we call up Rich Teer and .. well ... see what he thinks. When we say Jonathan .. that means the Schwartz. When we say Scott ... well gee. Its the big guy. Casper is .. Casper. Simon is Simon. These are all first name people in this community. And Rich is .. well, he's Rich you know? It's just us Alans (Coopersmith, DuBoff and Hargreaves) who screw up the first name thing :-D And How could I forget Burlison too. Geez we make it hard, don't we :-D alan. -- Alan Hargreaves - http://blogs.sun.com/tpenta Staff Engineer (Kernel/VOSJEC/Performance) Systems Technical Support Centre Sun Microsystems ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] GPLv3?
Dennis Clarke wrote: On Tue, Jan 30, 2007 at 07:54:48PM -0500, Dennis Clarke wrote: (1) The only "Rich" that has meaning in this OpenSolaris Community is Rich Teer. Mr Green, as far as I know, has never made an appearance here. So I don't know which end of the dog is wagging the tail here. opensolaris-discuss@opensolaris.org In this community project when someone says "Rich" they generally mean Rich Teer. Or, to be more honest, *I* instantly think Rich Teer. It is like, gee, let's go ask Rich and see what he thinks and then we call up Rich Teer and .. well ... see what he thinks. When we say Jonathan .. that means the Schwartz. When we say Scott ... well gee. Its the big guy. Casper is .. Casper. Simon is Simon. These are all first name people in this community. And Rich is .. well, he's Rich you know? It's just us Alans (Coopersmith, DuBoff and Hargreaves) who screw up the first name thing :-D alan -- Alan Hargreaves - http://blogs.sun.com/tpenta Staff Engineer (Kernel/VOSJEC/Performance) Systems Technical Support Centre Sun Microsystems ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Release of OS/Net B56 source ?
Tom Haynes wrote: Roland Mainz wrote: Hi! Does anyone know when the B56 sources will be released ? Seems that this may be the version we'll pick for final code review of the ksh93-integration tree... Bye, Roland http://www.opensolaris.org/os/downloads/ And *Solaris Express, Community Release* – DVD: Download <http://www.opensolaris.org/os/downloads/sol_ex_dvd/> | CD: Download <http://www.opensolaris.org/os/downloads/sol_ex_cd/> Solaris Express, Community Release is Sun's binary release for developers (code named "Nevada"). It contains the latest, unsupported release of the OpenSolaris bits as well as additional technology that has not been released into the OpenSolaris source base. Developers can build the OpenSolaris source by using this release as the base system. It is updated every other Friday. Since B55b just went up 1/19, my guess is that you can expect to see B56 on 2/2. Actually he was after the b56 source drop. I've got the encumbered bins ready, but Stevel has been a little busy to get the other deliverables ready, he suggested within a couple of days when I asked him about 12 hours ago. alan. -- Alan Hargreaves - http://blogs.sun.com/tpenta Staff Engineer (Kernel/VOSJEC/Performance) Systems Technical Service Center Sun Microsystems ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Re: [i18n-discuss] Solaris G11N source code open sourced!
Pablo Costa wrote: Hi all, I just want to wish you and your family a merry christmas. Special thanks to Young and Jim for all support. Best Regards, Does this take us anywhere further to doign something useful with libc_i18n.a ? alan. -- Alan Hargreaves - http://blogs.sun.com/tpenta Staff Engineer (Kernel/VOSJEC/Performance) Systems Technical Service Center Sun Microsystems ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Western Australia (Australia) Timezone...
David Lloyd wrote: Very soon now, WA in Australia will go into Daylight Savings - does anyone know if there's an update for the timezone files for this for Open Solaris? A putback went into Nevada for this today. By the way Very Soon = yesterday. alan. -- Alan Hargreaves - http://blogs.sun.com/tpenta Staff Engineer (Kernel/VOSJEC/Performance) Systems Technical Support Centre Sun Microsystems ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Re: Re: Re: cross compiling and building with open tools only
Haim Zilberbord wrote: one more thing SXCR is free i don't want become beta-tester for nevada express. Ummm then the reason for wanting to play with open solaris is what? Nevada is simply Sun's distro of Open Solaris. i don't feel safe when i can't build any tool form source I honestly believe that that is an extremely dangerous positoin to take, and one that many take in ignorance. Are you saying that you check the tools line of code by line of code before you build anything using them? I'd be very surprised. Also, have you had a read of Ken Thompson's Turing Award ACM paper entitled "Reflections on Trusting Trust". It is an eye opener for those who believe that "having the source" is the be all and end all of trusting software. You can find a copy of the paper at http://cm.bell-labs.com/who/ken/trust.html alan. -- Alan Hargreaves - http://blogs.sun.com/tpenta Staff Engineer (Kernel/VOSJEC/Performance) Systems Technical Service Center Sun Microsystems ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] SXCR 51 delayed slightly
It does make you wonder how curious some folks *actually* are. Obviously not sufficiently so to do something simple like a google search with the following terms: site:www.opensolaris.org zulu alan. Glynn Foster wrote: James Carlson wrote: Glynn Foster writes: delivered project were accidentally sent to the consolidation, and overwrote the correct packages already there. It results in upgrade failures. Hrm, from one vague message to another. Any chance of being just a little bit more open in sake of creating a better informed open development environment? [1] I gave you the details. Someone -- a gatekeeper -- was integrating packages built for an undelivered project, and accidentally delivered them to the WOS itself rather than to the project's dock. It was an "oops" moment. A mistake at the keyboard. Do I need to give the person's _name_? Why? What exactly are you looking for here? The project name (it's "Zulu," if that helps)? Because it makes people [non-Sun, non-ON, whatever] feel like they're part of something rather than the monkeys they currently feel because there's a blindfold around them at almost every corner of this damn project right now. I'm really not asking for too much, just some common courtesy and keeping people in the loop as much as possible [1] Glynn [1] I personally have the key to the magic door that lets me do some simple searches if I cared enough - other people don't have that luxury, and those are the people we're trying to encourage ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org -- Alan Hargreaves - http://blogs.sun.com/tpenta Staff Engineer (Kernel/VOSJEC/Performance) Systems Technical Support Centre Sun Microsystems ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] [Tonight - Updated Speakers] The Ninth meeting of the Sydney Open Solaris User Group
Date: Thursday, September 21 Time: 6:30pm Location: Sun Solution (formerly iForce) Centre. Ground floor 33 Berry St, North Sydney See http://opensolaris.org/os/community/os_user_groups/sosug for a link to a map. Speakers Alan Hargreaves Of non-debug builds, ZFS and BrandZ Alan will talk a bit about adventures in finally getting non-debug encumbered binaries available and some of the things he's been playing with since. Brendan Gregg DTracing javascript in firefox Brendan started working at Sun a few weeks ago and has promised us something interesting. The message I got on Monday on IRC was: (16:51:52) brendang: I may be able to do a world first demonstration of something. I'll let you know ASAP whether I can. (16:52:38) brendang: I'll run it by Bryan in the morning (16:53:32) brendang: it will be a DTrace demo (16:53:32) brendang: quite a strange one ;) I had a bit of a peek at this (since he'll be using my notebook). This is uber-cool. General What I'm doing that is interesting We'll also set some time aside for anyone to spend a few minutes talking about anything that they are doing that they find interesting. If folks are interested, I can also make available copies of the b48 non-debug encumbered-binaries as well as the ones from the b49 nightly that has the brandZ integration. I've also got brandZ running with this non-debug build if anyone wants a look. Notes * The security and safety folks have asked me to ensure that people visiting the iForce Centre sign in when they arrive and sign out when they leave. This is a safety issue so we know who is in the building. The sign in book is at the front desk inside the glass doors. * The main doors lock at about 6:00pm, so we'll make sure that we have someone near them to allow entry to the building. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] The ninth meeting of the Sydney Open Solaris User Group
Date: Thursday, September 21 Time: 6:30pm Location: Sun Solution (formerly iForce) Centre. Ground floor 33 Berry St, North Sydney See http://opensolaris.org/os/community/os_user_groups/sosug for a link to a map. No actual planned speakers but there wil be a number of us (I hope) giving a brief spiel on what we are currently doing that we think might be interesting. It's also been a bit since we got together so a time for informal chat is probably a good thing. We are also fortunate to have Mr Brendan Gregg back with us on a flying trip to Australia. If folks are interested, I can also make available copies of the b48 non-debug encumbered-binaries as well as the ones from the b49 nightly that has the brandZ integration. I've also got brandZ running with this non-debug build if anyone wants a look. Notes * The security and safety folks have asked me to ensure that people visiting the Solution Centre sign in when they arrive and sign out when they leave. This is a safety issue so we know who is in the building. The sign in book is at the front desk inside the glass doors. * The main doors lock at about 6:00pm, so we'll make sure that we have someone near them to allow entry to the building. -- Alan Hargreaves - http://blogs.sun.com/tpenta Staff Engineer (Kernel/VOSJEC/Performance) Systems Technical Support Centre Sun Microsystems ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] Re: [osol-code] Re: on-closed bits suggestion
Folks interested in playing with non-debug bits may find the following url "interesting". http://blogs.sun.com/tpenta/entry/non_debug_opensolaris_build_49 alan. Michael Hayes wrote: Sounds like a wonderful plan. Can't wait to see the binaries :) The debug factor, in all simplicity, is the only thing keeping me from keeping a home-build ON in my system -- I need the speed of a non-debug. Wonderful system though. -Mike -- Alan Hargreaves - http://blogs.sun.com/tpenta Staff Engineer (Kernel/VOSJEC/Performance) Systems Technical Service Center Sun Microsystems ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] OK, let's not go down the path of character assassination
This thread is now starting down the path of character assassination and I *really* think that we don't want to head down that path. There be dragons. Can we now drop this particular direction on the thread? alan. -- Alan Hargreaves - http://blogs.sun.com/tpenta Staff Engineer (Kernel/VOSJEC/Performance) Systems Technical Service Center Sun Microsystems ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Re: Danese Cooper claims CDDL made incompatible with GPL on purpose
Joerg Schilling wrote: Alan Burlison <[EMAIL PROTECTED]> wrote: As far as I can tell this merely mentions that you also maintain an OpenSolaris-derived distribution. Unless the translation is completely wrong I still don't see this as an attack on OpenSolaris, at worst it is saying that the Debian folks think the CDDL and GPL are incompatible and have decided to fork to resolve what they see as a licensing conflict. The original text mentions that "the Problem exists _since_ I am working on my OpenSolaris distribution". This is of course wrong but tries to discredit me _and_ OpenSolaris. The real start for the agressions from Debian was the time when nexenta appeared. This is another hint that Debian is interested to distredit OpenSolaris. Jörg Jorg, in English "since" can have two meanings in this context, let me rewrite the sentence with each of them and then ask a question. 1. "the Problem exists *at the same time he began* working on his OpenSolaris distribution" 2. "the Problem exists because he is working on his OpenSolaris distribution" As you can see, the meanings are substantially different. I read it as #1. My understanding of how you read it is #2. Can you substantiate that, or is it simply perception? That being said, it *is* their distribution and they are entitled to do what they want with it. The way that you licensed the code formerly allows them to fork and run off in their own direction. Fine. That's their prerogative. In doing so they lose your expertise on the toolkit. As regards to Danese's comments, They've been discussed quite sufficiently and that discussion is taking time from doing useful stuff. Let's get on with the useful stuff. alan. -- Alan Hargreaves - http://blogs.sun.com/tpenta Staff Engineer (Kernel/VOSJEC/Performance) Systems Technical Service Center Sun Microsystems ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] S10U2 weirdness
Peter, could I possibly get you to log a support call on this so we can get the appropriate escalation path in place to get a fix done. Provide the bug-id, a pointer to this thread on the jive server and note that a PTS-Kernel Engineer (me), specifically asked for this to be escalated. alan. Dana H. Myers wrote: [EMAIL PROTECTED] wrote: BTW: thermal zone handling was introduced in Nevada build 40 as part of: 6363985 acpica: Metropolis SMB Alerts result in high background system load Metropolis, of course, is the W2100z (The "thermal" event can happen in overtemp conditions and some other conditions; if the _TMP method is never evaluated the event is never cleared) Just to clarify this a bit; CR 6363985 occurs as a result of oddly-written BIOS code and generally has nothing to do with an actual over-temperature condition. Some revisions of the Metropolis BIOS configure the on-board voltage/temperature/fan-speed monitor chip to report an alert if any of these conditions stray outside a specified range; transient power supply variations trigger an alert which looks like an over-temperature condition. The problem is that the BIOS is written oddly; it depends on a thermal zone monitor to deliver the alert to the BIOS. This has nothing to do with temperature. Adding a thermal zone monitor to Solaris solves 6363985 as a side-effect. In fact, the fans in Metropolis are under hardware control and operate completely independently of the thermal zone monitor. I ran an experiment in which I covered all the vents on a Metropolis cabinet and loaded the CPUs, attempting to overheat it, and I could not. What I did discover is that the BIOS will filter-out transient voltage-range events; if something is actually wrong, the BIOS will log a DMI event. The next time you get a chance to reboot the system, I'd suggest looking in the DMI event log and see if there BIOS has logged any related messages. Dana ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org -- Alan Hargreaves - http://blogs.sun.com/tpenta Staff Engineer (Kernel/VOSJEC/Performance) Product Technical Support (APAC) Sun Microsystems I went in the World's Greatest shave for Leukaemia. See http://blogs.sun.com/roller/page/tpenta?entry=hair_yesterday_gone_today ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] S10U2 weirdness
The obvious next question is, is anyone backporting this to the s10 kernel patch? alan. Dana H. Myers wrote: [EMAIL PROTECTED] wrote: BTW: thermal zone handling was introduced in Nevada build 40 as part of: 6363985 acpica: Metropolis SMB Alerts result in high background system load Metropolis, of course, is the W2100z (The "thermal" event can happen in overtemp conditions and some other conditions; if the _TMP method is never evaluated the event is never cleared) Just to clarify this a bit; CR 6363985 occurs as a result of oddly-written BIOS code and generally has nothing to do with an actual over-temperature condition. Some revisions of the Metropolis BIOS configure the on-board voltage/temperature/fan-speed monitor chip to report an alert if any of these conditions stray outside a specified range; transient power supply variations trigger an alert which looks like an over-temperature condition. The problem is that the BIOS is written oddly; it depends on a thermal zone monitor to deliver the alert to the BIOS. This has nothing to do with temperature. Adding a thermal zone monitor to Solaris solves 6363985 as a side-effect. In fact, the fans in Metropolis are under hardware control and operate completely independently of the thermal zone monitor. I ran an experiment in which I covered all the vents on a Metropolis cabinet and loaded the CPUs, attempting to overheat it, and I could not. What I did discover is that the BIOS will filter-out transient voltage-range events; if something is actually wrong, the BIOS will log a DMI event. The next time you get a chance to reboot the system, I'd suggest looking in the DMI event log and see if there BIOS has logged any related messages. Dana ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org -- Alan Hargreaves - http://blogs.sun.com/tpenta Staff Engineer (Kernel/VOSJEC/Performance) Product Technical Support (APAC) Sun Microsystems I went in the World's Greatest shave for Leukaemia. See http://blogs.sun.com/roller/page/tpenta?entry=hair_yesterday_gone_today ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] the grubby looking install process
I think Dennis has a good point. We are looking at two issues that should be *really* simple to do something about. - graphic background for grub on install cd/dvd - numlock on by default What do others think? alan. -- Alan Hargreaves - http://blogs.sun.com/tpenta Staff Engineer (Kernel/VOSJEC/Performance) Product Technical Support (APAC) Sun Microsystems I went in the World's Greatest shave for Leukaemia. See http://blogs.sun.com/roller/page/tpenta?entry=hair_yesterday_gone_today ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Re: DHCP
James Carlson wrote: tyw writes: Hi thanks for the reply. But what I really want is to derive the very next IP that the DHCP server is going to allocate to the next host that sends in a request. This operation will be performed on the server running the DHCP daemon itself. Therefore, I cannot do a release / request because the current machine is on a static IP. Thanks once again. You might get by using ifconfig's "ether" option to change the interface MAC address, and running DHCP. But the question itself doesn't really make sense to me. It sounds like you're trying to find out what the next IP address will be so that you can somehow contact that host by address. That's almost certainly the wrong answer. On any non-trivial network, it's not possible to predict which system will get that next address, so asking for the "next" one doesn't seem like a stable answer. A better answer might be to set up that "next" system to request a particular host name (see dhcpagent(1M)), and then using that name. Or perhaps use static leases. Associate a mac address with a particular address in the DHCP server. alan. -- Alan Hargreaves - http://blogs.sun.com/tpenta Staff Engineer (Kernel/VOSJEC/Performance) Product Technical Support (APAC) Sun Microsystems I went in the World's Greatest shave for Leukaemia. See http://blogs.sun.com/roller/page/tpenta?entry=hair_yesterday_gone_today ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] sgen and other "no_source" stuff
Mike Kupfer wrote: "Alan" == Alan Hargreaves <[EMAIL PROTECTED]> writes: Alan> Any changes made to Steve's current copy of bindrop will need to Alan> be reflected in what I'm doing, so could I please be kept in the Alan> loop? Is it time to put back those tools to the ON gate? mike I can give you a current webrev if you like Mike (I have had an idea to tidy up output, but it's purely aesthetic). alan. -- Alan Hargreaves - http://blogs.sun.com/tpenta Staff Engineer (Kernel/VOSJEC/Performance) Product Technical Support (APAC) Sun Microsystems I went in the World's Greatest shave for Leukaemia. See http://blogs.sun.com/roller/page/tpenta?entry=hair_yesterday_gone_today ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] sgen and other "no_source" stuff
Bonnie Corwin wrote: > > sgen an be available in the ON closed bins tarball - I thought it > already was. > > I'll see what's up. > > Thanks. > > Bonnie As it's an area of code I have a current interest in, I can answer that pretty quickly. There is a nice long list of specific exclusions in the current code to generate the bindrop. Sgen is one of the exclusions. Perhaps it is time to revisit this list. Any changes made to Steve's current copy of bindrop will need to be reflected in what I'm doing, so could I please be kept in the loop? Steve? Mike? alan. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Re: Re: Sun lost one of it's biggest and oldest x86
Jim Grisanzio wrote: And also, I'm going to use my proximity to the rest of Asia to poke around throughout the entire region. I'll do very little travel to the US, actually -- probably only once a year. It will be Asia first, Europe second. But in terms of my online activities, everything stays pretty much as it is now. Given that you will kind of be in the area, we'd love to see you down here to Jim. I'm sure we could work something out :) alan -- Alan Hargreaves - http://blogs.sun.com/tpenta Staff Engineer (Kernel/VOSJEC/Performance) Product Technical Support (APAC) Sun Microsystems I went in the World's Greatest shave for Leukaemia. See http://blogs.sun.com/roller/page/tpenta?entry=hair_yesterday_gone_today ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] [Tuesday] The Seventh Meeting of the Sydney Open Solaris User Group
Date: Tuesday, May 23 [Note the changed Date due to State of Origin] Time: 6:30pm Location: Sun Solution (formerly iForce) Centre. Ground floor 33 Berry St, North Sydney Speaker --- Nathan Kroenert --- Why Niagara is almost as good as Rare Steak. This talk will look at Niagara from a different perspective; That of someone who is more accustomed to working on the much larger enterprise systems. We'll look at some of the strongest and weakest points of the architecture, have a poke at one of the boxes in real life and discuss why optimisation can have such a positive impact on these (and other) systems. I'll try to avoid spending too much time on the usual 'coolthreads/power/coolness/reduced AC/reduced space' ranting... We all know how well these boxes stack up... If there are specific aspects you might like to see covered, whack them onto [EMAIL PROTECTED] and if I can, I'll include them in the talk. [Nathan will also be demonstrating this stuff on a T1000] Notes - * The security and safety folks have asked me to ensure that people visiting the iForce Centre sign in when they arrive and sign out when they leave. This is a safety issue so we know who is in the building. The sign in book is at the front desk inside the glass doors. * The main doors lock at about 6:00pm, so we'll make sure that we have someone near them to allow entry to the building. -- Alan Hargreaves - http://blogs.sun.com/tpenta Staff Engineer (Kernel/VOSJEC/Performance) Product Technical Support (APAC) Sun Microsystems ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] SOSUG#7 - DATE CHANGE
OK, folks the consensus of those who replied to me is that we will shift this to Tuesday May 23. Details can be found at http://opensolaris.org/os/community/os_user_groups/sosug/nextmeeting/ We're still finalising the second speaker, but the kind of thing that Nathan is going to be doing with a T1000 looks really cool. As a teaser, we've been playing with running the sunray software on this while doing all kinds of things to it that it was not designed for and watching how this impacts (or doesn't impact) interactive performance. We hope to have a unit along with a couple of sunrays to demo this stuff. Nathan will definitely be presenting a a look at this box from an unusual viewpoint. I'm also looking at providing time for anyone who is doing anything that they believe is interesting, cool, whatever to spend a couple of minutes to be able to tlak about it. I hope to have the full agenda ready by Friday at which time I'll post it to the lists. alan. -- Alan Hargreaves - http://blogs.sun.com/tpenta Staff Engineer (Kernel/VOSJEC/Performance) Product Technical Support (APAC) Sun Microsystems I went in the World's Greatest shave for Leukaemia. See http://blogs.sun.com/roller/page/tpenta?entry=hair_yesterday_gone_today ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Re: SOSUG #7 - Call for speakers
Rodrick Brown wrote: Does the topic have to be Sun/Solaris Centric? Or would any UNIX related technology talks be allowed such as an authors of well known opensource applications giving overviews? I certainly have no problem with that. On the subject of the meeting date. You know how I mentioned exceptional events? ... My bad for not checking the date. It appears that May 24 is the same day as the State of Origin Rugby League (a rather largely watched match between NSW (where we are) and Queensland). While we have once before had this clash and siply adjourned to a local bar to watch the match, this time it looks like the one of the presenters that we had in mind actually has tickets to the event. Does anoyone have strong feelings for or against Tuesday or Thursday in that week (I'd prefer Tuesday, but not by much). alan. -- Alan Hargreaves - http://blogs.sun.com/tpenta Staff Engineer (Kernel/VOSJEC/Performance) Product Technical Support (APAC) Sun Microsystems I'm going in the World's Greatest shave for Leukaemia. See http://blogs.sun.com/tpenta?entry=raising_money_for_leukaemia_support ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] SOSUG #7 - Call for speakers
In order to try to stop the last minute decisions of when to have meetings and who is speaking, I'm going to try something different for the next few months. ie I'm going to try to be a little more organised ;) Apart from December and exceptional events, we'll have regular meetings on the last Wednesday of the month. While we can always rely on a few of our regulars to come through, it would be nice if we could have some other folk talk about what they are doing or things that they've found interesting. As such I'm asking for volunteers to present. Any empty slots at the time of the close will be filled by pressuring some of the regulars. If we can't get speakers, the meeting will be called off by the Friday before. The Details of the next meeting are: Location: Sun Solution Centre, Lvl 1 33 Berry St, North Sydney Date: Wednesday May 24 Time: 6:30pm Call for Speakers Closes: May 17 Please contact [EMAIL PROTECTED] or [EMAIL PROTECTED] if you would like to present. If you have an idea for a topic you'd like to see, post it to [EMAIL PROTECTED] Breaking News Nathan Kroenert has volunteered to fill one of the speaker slots with a presentation about Niagara" alan. -- Alan Hargreaves - http://blogs.sun.com/tpenta Staff Engineer (Kernel/VOSJEC/Performance) Product Technical Support (APAC) Sun Microsystems I'm going in the World's Greatest shave for Leukaemia. See http://blogs.sun.com/tpenta?entry=raising_money_for_leukaemia_support ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Re: Propose removing [] prefixes in Subject
I've always filtered off Return-path. Pertty much every mailing list that I'm on sets this correctly. alan. -- Alan Hargreaves - http://blogs.sun.com/tpenta Staff Engineer (Kernel/VOSJEC/Performance) Product Technical Support (APAC) Sun Microsystems I'm going in the World's Greatest shave for Leukaemia. See http://blogs.sun.com/tpenta?entry=raising_money_for_leukaemia_support ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] [Tonight!] The sixth meeting of the Sydney Open Solaris User Group
Date: Wednesday, April 26 Time: 6:30pm Location: Sun Solution (formally iForce) Centre. Ground floor 33 Berry St, North Sydney See http://opensolaris.org/os/community/os_user_groups/sosug for a link to a map. Speakers Brendan Gregg Brendan will be speaking about the upcoming Solaris Internals Book. Brendan will chat about the upcoming "Solaris Internals" 2nd edition, an awsome reference that contains many OpenSolaris and Solaris 10 specifics - including DTrace and mdb. He was able to contribute towards this edition, in particular writing material for the second volume (it is now 2 books). When Brendan is not teaching Solaris topics, he spends time playing with DTrace and the DTrace toolkit as well as dabbling in the games community. Bill Moore Bill will be available for an informal Q/A session on pretty much anything you want to ask about OpenSolaris . Bill is an engineer in the ZFS team. It should be an interesting evening and we'd love to see a good turnout. Apologies for the lack of notice, things have been thrown together rather quickly. STOP PRESS -- Jeff Bonwick will also be around tonight! -- Alan Hargreaves - http://blogs.sun.com/tpenta Staff Engineer (Kernel/VOSJEC/Performance) Product Technical Support (APAC) Sun Microsystems I'm going in the World's Greatest shave for Leukaemia. See http://blogs.sun.com/tpenta?entry=raising_money_for_leukaemia_support ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] Re: [Tomorrow Night] The sixth meeting of the Sydney Open Solaris User Group
Alan Hargreaves wrote: Date: Wednesday, January 25 Of course that should have read Wednesday April 26. That's what I get for cut and pasting layouts. alan. Time: 6:30pm Location: Sun Solution (formally iForce) Centre. Ground floor 33 Berry St, North Sydney See http://opensolaris.org/os/community/os_user_groups/sosug for a link to a map. Speakers Brendan Gregg Brendan will be speaking about the upcoming Solaris Internals Book. Brendan will chat about the upcoming "Solaris Internals" 2nd edition, an awsome reference that contains many OpenSolaris and Solaris 10 specifics - including DTrace and mdb. He was able to contribute towards this edition, in particular writing material for the second volume (it is now 2 books). When Brendan is not teaching Solaris topics, he spends time playing with DTrace and the DTrace toolkit as well as dabbling in the games community. Bill Moore Bill will be available for an informal Q/A session on pretty much anything you want to ask about OpenSolaris . Bill is an engineer in the ZFS team. It should be an interesting evening and we'd love to see a good turnout. Apologies for the lack of notice, things have been thrown together rather quickly. alan. -- Alan Hargreaves - http://blogs.sun.com/tpenta Staff Engineer (Kernel/VOSJEC/Performance) Product Technical Support (APAC) Sun Microsystems I'm going in the World's Greatest shave for Leukaemia. See http://blogs.sun.com/tpenta?entry=raising_money_for_leukaemia_support -- Alan Hargreaves - http://blogs.sun.com/tpenta Staff Engineer (Kernel/VOSJEC/Performance) Product Technical Support (APAC) Sun Microsystems I'm going in the World's Greatest shave for Leukaemia. See http://blogs.sun.com/tpenta?entry=raising_money_for_leukaemia_support ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] [Tomorrow Night] The sixth meeting of the Sydney Open Solaris User Group
Date: Wednesday, January 25 Time: 6:30pm Location: Sun Solution (formally iForce) Centre. Ground floor 33 Berry St, North Sydney See http://opensolaris.org/os/community/os_user_groups/sosug for a link to a map. Speakers Brendan Gregg Brendan will be speaking about the upcoming Solaris Internals Book. Brendan will chat about the upcoming "Solaris Internals" 2nd edition, an awsome reference that contains many OpenSolaris and Solaris 10 specifics - including DTrace and mdb. He was able to contribute towards this edition, in particular writing material for the second volume (it is now 2 books). When Brendan is not teaching Solaris topics, he spends time playing with DTrace and the DTrace toolkit as well as dabbling in the games community. Bill Moore Bill will be available for an informal Q/A session on pretty much anything you want to ask about OpenSolaris . Bill is an engineer in the ZFS team. It should be an interesting evening and we'd love to see a good turnout. Apologies for the lack of notice, things have been thrown together rather quickly. alan. -- Alan Hargreaves - http://blogs.sun.com/tpenta Staff Engineer (Kernel/VOSJEC/Performance) Product Technical Support (APAC) Sun Microsystems I'm going in the World's Greatest shave for Leukaemia. See http://blogs.sun.com/tpenta?entry=raising_money_for_leukaemia_support ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Proposal for new Community: Solaris Trusted Extensions
Glenn Faden wrote: I would like to form a new community to discuss issues related to multilevel security and the new Solaris Trusted Extensions technology. This community would be the focal point for several related technologies including multilevel networking, multilevel window systems, multilevel NFS, multilevel printing, and multilevel applications. The Solaris Trusted Extensions source code is now mostly open. The ON components were integrated into Nevada build 37. The X server components were released to X.org on March 31. See http://opensolaris.org/os/community/x_win/sources. Plans are in place for release of the Trusted JDS source code, as well. This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org +1 Having seen teh PSARC cases coming through for this, the technology looks damned interesting. alan. -- Alan Hargreaves - http://blogs.sun.com/tpenta Kernel/VOSJEC/Performance Staff Engineer Product Technical Support (APAC) Sun Microsystems ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Network Configuration Problem
Vincenzo Sciarra wrote: I have a problem with my network. I'll paste below : ** # host google.com google.com has address 64.233.167.99 # ping 64.233.167.99 64.233.167.99 is alive # ping google.com ping: unknown host google.com * The box resolve the host but doesn't ping the hostname. I have set /etc/resolv.conf in unix-like mode Thanks for suggestion Have you configured the hosts line in /etc/nsswitch.conf to contain the keyword dns? I would generally place it after files. alan. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Re: Slowaris vs. Solaris
Darren J Moffat wrote: UNIX admin wrote: Agreed. SMC sucks dead bunnies through a bent straw sideways; but then again, being a hardcore shell guy, perhaps I'm the wrong person to write that. /usr/sadm/bin/sm* is the CLI interface to SMC. What can we do (other than the performance issue) to improve SMC so that "hardcore CLI junkies" and "pointy clickies" would both like it ? Has http://users.tpg.com.au/bdgcvb/DTrace/smc.html been addressed? alan. -- Alan Hargreaves - http://blogs.sun.com/tpenta Staff Engineer (Kernel/VOSJEC/Performance) Product Technical Support (APAC) Sun Microsystems ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Mount fat32 partition
Julian Ortiz wrote:
Hello,
I just got a new Dell optiplex, with a 100-Gb-Sata2 hd.
The hd has two fat partitions:
1. Dell's boot program (10 Mb)
2. Windows XP --fat32. --(My Docs)-- (10 Gb)
In the left over space I installed solaris with / , /export/home, /opt and swap
partitions.
I have been trying to mount the windows partition, running shell command "mount -F autofs /dev/rdisk/(name of disk
partition) /mount/fat32", but no luck yet. Some times I execute "mount" command then cd /mount/fat32
folder and list all files in it but i am getting gibberishh simbols({}>:"<<">')())#$)(##)
Can anyone tell me how to mount a fat32 partition?
This message posted from opensolaris.org
Try using
mount -F pcfs /dev/rdisk/(name of disk partition) /mount/fat32
Autofs is something else entirely.
alan.
--
Alan Hargreaves - http://blogs.sun.com/tpenta
Staff Engineer (Kernel/VOSJEC/Performance)
Product Technical Support (APAC)
Sun Microsystems
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org
Re: [osol-discuss] 20060201 question
Sean Sprague wrote: Hello all, I like the look of the website with its ON Consolidation now in the download section, but in the current README (http://dlc.sun.com/osol/on/downloads/current/README.opensolaris) and the referred-to page of currently known issues (http://opensolaris.org/os/community/onnv/known_issues/), the text states: - The current minimum SXCR build needed to build the OpenSolaris sources is Nevada build 32. - I have not tried a full build of 20060201 yet (or even BFU'd from the archives), but cannot see that SXCR b32 is available yet on the SDLC. I guess that its just a typo in the README? So what build is 20060201? b31 I guess... It's actually b33. Steve made it available pretty much when the build closed. (Kudos Steve). Unfortunately, until we can get some packages (not in ON) up on the download site, you're not going to be able to do a full build. See Steve's blog at http://whacked.net/2006/02/03/nightly-20060201-delivered/ on this issue. He hopes to have something up to address this on Monday. -- Alan Hargreaves - http://blogs.sun.com/tpenta Kernel/VOSJEC/Performance Staff Engineer Product Technical Support (APAC) Sun Microsystems ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] [Tonight!] The fifth meeting of the Sydney Open Solaris User Group
Date: Wednesday, January 25 Time: 6:30pm Location: Sun Solution (formally iForce) Centre. Ground floor 33 Berry St, North Sydney See http://opensolaris.org/os/community/os_user_groups/sosug for a link to a map. Speakers James McPherson James will be speaking on "Getting to know the SAN stack". Sun's SAN Foundation Kit (SFK) is presented, from the hardware (hba) up to the application level (userland). We demonstrate the way your data gets to and from your storage, and present basic SFK debugging techniques using code from the OpenNWS consolidation that will soon be hosted at www.opensolaris.org. James is a developer with the Data Management Group and and has been with Sun for just over six years. Brendan Gregg Brendan will be speaking on "Zone Resource Controls". Zones are great for server consolidation. Picture migrating ten application servers onto one. Now picture application wars, where they wrestle for resources with survival of the fattest. There are several resource control techniques that not only allow applications to coexist peacefully, but allow you control how they use resources. I'll summarise how Zone Resource Controls currently work. When Brendan is not teaching Solaris topics, he spends time playing with DTrace and the DTrace toolkit. Alan Hargreaves If time permits Alan will speak briefly about "Progress on the Non-debug build front". Since we released the code, it's only been possible to build a debug version of OpenSolaris. Well, that's not quite true. There is a way to build a mostly non-debug version using binaries that are already available. I'll also touch on progress being made towards making a set of closed non-debug binaries available more formally. Alan is a staff engineer for the kernel group in Product Technical Support. Notes - * The security and safety folks have asked me to ensure that people visiting the iForce Centre sign in when they arrive and sign out when they leave. This is a safety issue so we know who is in the building. The sign in book is at the front desk inside the glass doors. * The main doors lock at about 6:00pm, so we'll make sure that we have someone near them to allow entry to the building. -- Alan Hargreaves - http://blogs.sun.com/tpenta Kernel/VOSJEC/Performance Staff Engineer Product Technical Support (APAC) Sun Microsystems ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Proposal: OpenSolaris Articles Project
I've just gone through this thread. The things that I have taken to heart are Jim wrote >> Initially, the project will provide support for community members >> interested in writing, editing, and reviewing OpenSolaris content for >> the Articles page: http://www.opensolaris.org/os/articles/. These >> articles could also be used as content for conferences, journals, and >> other forums. >> >> We could develop all kinds of community-wide content, including >> feature articles, community profiles, technical articles, >> commentaries, and Q&As. Over time, the project could expand the >> Articles page to include more multi-media content such as artwork, >> podcasts, screencasts, and videos. As someone who does go around presenting a reasonable amount on Open Solaris, I think this is a wonderful idea. I can see that it is a resource that I coule both lean on and contribute to. Documentation is something that is supposed to be all encompassing and definitive and devoid of opinion. Articles are different. When you present or write for a magazine, you *do* present opinion as well. You don't need to be the definitive statement on how something works (as an example can you imagine presenting directly from the ZFS documentation? I mean it would be damned informative, but very dry - that's not to disparage the ZFS documentation, but that's not what it was written for). I'd also see such a resource useful for the bloggers. alan. Ben Rockwood wrote: To be formal Speaking on behalf of myself, with the honorable Docs community in mind, I do hereby Second the proposal forwarded by Mr Grisanzio from the Great State of California. Great idea Jim. This is something the docs community has wanted very much to do but the rubber hadn't quite hit the road yet. All the enthusiasm around the idea is wonderful and I'm 110% behind it. I yield the remainder of my time to the Honorable Mr. Hahn. benr. Jim Grisanzio wrote: Here is a proposal to form a project to produce article content for opensolaris.org. OpenSolaris Articles Project Community members have been asking if they can write articles for opensolaris.org and what the process would be to produce those articles. Yes, we'd love the content, and no, there's no process right now. The website guidelines say that individual communities are responsible for their own content -- for accuracy, adherence to TOU, etc -- but we don't have any process for developing community-wide content. This proposed Articles Project would develop the necessary processes for article generation and solicit contributors. We'd have to decide what content is needed, who'd write/edit/produce that content, how it would be reviewed for accuracy, in what form it would be published, and where it would be published. So, let's start a project to: * implement an article content review and publishing process * solicit and publish articles from the community * grow that process into a peer-reviewed, community-led system Initially, the project will provide support for community members interested in writing, editing, and reviewing OpenSolaris content for the Articles page: http://www.opensolaris.org/os/articles/. These articles could also be used as content for conferences, journals, and other forums. We could develop all kinds of community-wide content, including feature articles, community profiles, technical articles, commentaries, and Q&As. Over time, the project could expand the Articles page to include more multi-media content such as artwork, podcasts, screencasts, and videos. I suppose we'd need a list. How about [EMAIL PROTECTED] That's it. What do you think? Jim ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org -- Alan Hargreaves - http://blogs.sun.com/tpenta Kernel/VOSJEC/Performance Staff Engineer Product Technical Support (APAC) Sun Microsystems ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Reverting to old build: Solaris Express - Community Release
Karyn, any updates on b30 availability, or (since b31 source is now up) SX:CR b31? alan. Karyn Ritter wrote: I was just notified of a new legal issue with build 30 of the Solaris Express - Community Release. We hope that this is a temporary problem, and that we'll be able to re-post the images for this build shortly. In the meantime, I've changed the links on the download page back to build 28. Because we're posting these more quickly than we've ever released Solaris Express builds, we're bound to encounter some hiccups. I'm hoping that there will be fewer of these in the future. I apologize for the inconvenience, and appreciate your understanding. Thanks, Karyn ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org -- Alan Hargreaves - http://blogs.sun.com/tpenta Kernel/VOSJEC/Performance Staff Engineer Product Technical Support (APAC) Sun Microsystems ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Please update 4113420 (request for ksh93 integration)
James Carlson wrote: Mac writes: To make matters worse, inetd-related services require Sun's /bin/ksh to work because libc's wordexp() has intimate relationship with Sun's ksh. Intimate, to be sure, but I think it might actually be 'wrong' in some respects. For those who have appropriate access (and apologies to the others who are also listening on this list), see CR 4771992. That's something that could stand some attention ... I would agree with you James. I think that the request mentioned in the evaluation needs to be revisted. alan. -- Alan Hargreaves - http://blogs.sun.com/tpenta Kernel/VOSJEC/Performance Staff Engineer Product Technical Support (APAC) Sun Microsystems ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] The fifth meeting of the Sydney Open Solaris User Group
Date: Wednesday, January 25 Time: 6:30pm Location: Sun Solution (formally iForce) Centre. Ground floor 33 Berry St, North Sydney See http://opensolaris.org/os/community/os_user_groups/sosug for a link to a map. Speakers James McPherson James will be speaking on "Getting to know the SAN stack". Sun's SAN Foundation Kit (SFK) is presented, from the hardware (hba) up to the application level (userland). We demonstrate the way your data gets to and from your storage, and present basic SFK debugging techniques using code from the OpenNWS consolidation that will soon be hosted at www.opensolaris.org. James is a developer with the Data Management Group and and has been with Sun for just over six years. Brendan Gregg Brendan will be speaking on "Zone Resource Controls". Zones are great for server consolidation. Picture migrating ten application servers onto one. Now picture application wars, where they wrestle for resources with survival of the fattest. There are several resource control techniques that not only allow applications to coexist peacefully, but allow you control how they use resources. I'll summarise how Zone Resource Controls currently work. When Brendan is not teaching Solaris topics, he spends time playing with DTrace and the DTrace toolkit. Alan Hargreaves If time permits Alan will speak briefly about "Progress on the Non-debug build front". Since we released the code, it's only been possible to build a debug version of OpenSolaris. Well, that's not quite true. There is a way to build a mostly non-debug version using binaries that are already available. I'll also touch on progress being made towards making a set of closed non-debug binaries available more formally. Alan is a staff engineer for the kernel group in Product Technical Support. Notes - * The security and safety folks have asked me to ensure that people visiting the iForce Centre sign in when they arrive and sign out when they leave. This is a safety issue so we know who is in the building. The sign in book is at the front desk inside the glass doors. * The main doors lock at about 6:00pm, so we'll make sure that we have someone near them to allow entry to the building. -- Alan Hargreaves - http://blogs.sun.com/tpenta Kernel/VOSJEC/Performance Staff Engineer Product Technical Support (APAC) Sun Microsystems ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] Building an (almost completely) non-debug OpenSolaris
Apologies for the wide distribution. I've just done a blog up detailing how, using currently available stuff one can build an almost completely non-debug opensolaris. I'm currently running said build on a Ferrari 4005 with the BrandZ code. http://blogs.sun.com/roller/page/tpenta?entry=building_an_almost_completely_non Have fun folks. alan. -- Alan Hargreaves - http://blogs.sun.com/tpenta Kernel/VOSJEC/Performance Staff Engineer Product Technical Support (APAC) Sun Microsystems ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] SOSUG#4 videos available
James McPherson on ZFS and Bryan Cantrill on new stuff in DTrace. Currently only have WMV version 9 video, I'm working on DivX. See the blog for details, I need to get to bed. http://blogs.sun.com/roller/page/tpenta?entry=sosug_4_videos_available alan. -- Alan Hargreaves - http://blogs.sun.com/tpenta Kernel/VOSJEC/Performance Staff Engineer Product Technical Support (APAC) Sun Microsystems ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Re: what is a door file ?
William D. Hathaway wrote: For sample code, Rich Teer has examples (and a whole 40 page chapter on doors) in his excellent "Solaris Systems Programming" book. I would highly recommend this book to anyone that is programming on Solaris. You can download sample source code and find more info on his book at http://www.rite-group.com/rich/ssp/ (the doors chapter is 22). This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org I don't have code samples, but I did a brief writeup on doors for a custoemr magazine a few years back. http://au.sun.com/news/onsun/2002-11/tech_tips.html alan. -- Alan Hargreaves - http://blogs.sun.com/tpenta Kernel/VOSJEC/Performance Staff Engineer Product Technical Support (APAC) Sun Microsystems ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] [Reminder] Sydney Open Solaris User Group meeting tonight
We will be holding the fourth meeting of the Sydney Open Solaris User group Tonight. Date: Monday, October 17 Time: 6:30pm Location: iForce Centre. Ground floor 33 Berry St, North Sydney Speakers Bryan Cantrill - Bryan is in Australia this week to (amongst other things) present a tutorial and plenary at AUUG and do some customer visits. He will also present at SOSUG. Bryan is a senior staff engineer with the Solaris Kernel group and was recently recognised as one of the top innovators under 35 years of age. James McPherson - James recently gave a customer presentation on ZFS and has agreed to give the presentation to this group. I've not seen the presentation, but from all accounts it went very well when he first gave it. James has been "playing" with ZFS for quite some time, particularly with a focus on usability and folks simply doing silly things with it to see how it holds up. James currently works in the Leadville driver group. Notes - There is a rather large internal meeting preceeding us in that conference room with some international visitors (maybe some will hang around); so I've had to move the start time to 6:30. It may also be a little congested around our start time. The security and safety folks have asked me to ensure that people visiting the iForce Centre sign in when they arrive and sign out when they leave. This is a safety issue so we know who is in the building. The sign in book is at the front desk inside the glass doors. The main doors lock at about 6:00pm, so we'll make sure that we have someone near them to allow entry to the building. I am assured taht there will be food/drink provided. = I have also been asked to let folks know that there are still places in available in the Tutorial that Bryan is running on Tuesday at the AUUG Conference. See http://www.auug.org.au for details. alan. -- Alan Hargreaves - http://blogs.sun.com/tpenta Kernel/VOSJEC/Performance Staff Engineer Product Technical Support (APAC) Sun Microsystems ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] SOSUG#4 - Monday October 17
We will be holding the fourth meeting of the Sydney Open Solaris User group next week. Date: Monday, October 17 Time: 6:30pm Location: iForce Centre. Ground floor 33 Berry St, North Sydney See http://opensolaris.org/os/community/os_user_groups/sosug/ for a link to a map. Speakers Bryan Cantrill - Bryan is in Australia this week to (amongst other things) present a tutorial and plenary at AUUG and do some customer visits (If you have not booked a Tuesday afternoon tutorial at AUUG, his is certainly worth considering).When I asked him what he would talk about he had the following to say. Given the number of DTrace mavens, perhaps the talk should be in the DTrace Tips and Tricks vein? I'd rather not give the stock DTrace intro -- if there's one audience on the planet where I can assume some prior DTrace knowledge, SOSUG would be it... Bryan is a senior staff engineer with the Solaris Kernel group and was recently recognised as one of the top innovators under 35 years of age. James McPherson - James recently gave a customer presentation on ZFS and has agreed to give the presentation to this group. I've not seen the presentation, but from all accounts it went very well when he first gave it. James has been "playing" with ZFS for quite some time, particularly with a focus on usability and folks simply doing silly things with it to see how it holds up. James has just moved to the Leadville driver group from PTS. He has been with Sun for just under six years. He says he is not *really* an axe murderer, just plays one on TV. Notes - There is a rather large internal meeting preceeding us in that conference room with some international visitors (maybe some will hang around); so I've had to move the start time to 6:30. It may also be a little congested around our start time. The security and safety folks have asked me to ensure that people visiting the iForce Centre sign in when they arrive and sign out when they leave. This is a safety issue so we know who is in the building. The sign in book is at the front desk inside the glass doors. The main doors lock at about 6:00pm, so we'll make sure that we have someone near them to allow entry to the building. I am assured that there will be food/drink provided at some stage during the evening. -- Alan Hargreaves - http://blogs.sun.com/tpenta Kernel/VOSJEC/Performance Staff Engineer Product Technical Support (APAC) Sun Microsystems ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] License Discuss List?
Simon Phipps wrote: On Sep 13, 2005, at 00:51, Jim Grisanzio wrote: Since we opened in June there have been several long threads on CDDL in general and CDDL vs GPL. As a result of those conversations many people have suggested that we add a license-discuss list. A license-discuss list would have value because CDDL is still new and as the community grows we'll always have a need to educate new people on licensing issues. Also, we are trying to migrate conversations from discuss to more appropriate lists when and if they grow enough to support their own list. Licensing issues probably qualify at this point, so I'm inclined to open up a license-discuss list. If you think this is good, tell me. If you think this is bad, tell me. While superficially tempting, I am not sure this is a good idea. Lists here should relate to groups working towards the goals of the OpenSolaris community. Right now we're not revising the CDDL or addressing component licensing issues, so unlike a community like Debian there is no group with "licenses" as its goal. If you've a good memory you'll remember I am very much in favour of "paving the tracks the walkers make" and directing discussion to specific lists. In this case that's the right policy but the proposed list is the wrong list. In the most recent case, it was not a licensing discussion, but rather the licensing element of a gnu-solaris discussion, concerning the licensing issues surrounding a proposed Debian/Solaris distribution. We directed the discussion to the (otherwise dormant) gnu-solaris list. I think that was the right choice (but then I made it so I would!) and I expect similar future discussions to have a similar outcome. Basic licensing questions belong in an FAQ; discussions not found in an FAQ belong on this list and then need to be distilled to an FAQ; discussions related to a group interest belong on their own list. S. I would have to agree with Simon that it's not a good idea. I stated this same opinion on #opensolaris earlier in the week. By creating such a "discussion" list we could be seen to endorsong the flamewars that already occur. I don't think we want to be a part of that. alan. -- Alan Hargreaves - http://blogs.sun.com/tpenta Kernel/VOSJEC/Performance Engineer Product Technical Support (APAC) Sun Microsystems ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] Bug fix process overly burdonsome ?
Earlier today someone posted a note in response to a blog item from Jim about how overly bureaucartic our current bug fixing process is. I responded in my blog at http://blogs.sun.com/roller/page/tpenta?entry=comment_on_opensolaris_bugfix_process The original poster has responded, and in turn I've asked about exactly what in the process he finds overly burdonsome. If we can get a reasonable dialogue going here, it could get interesting and useful. Maybe we *do* need a simpler process for those who want to suggest fixes but not get involved in the actual putback process. This could be especially useful given how overburdoned the current sponsor team is with this and their other responsibilities. alan. -- Alan Hargreaves - http://blogs.sun.com/tpenta Kernel/VOSJEC/Performance Engineer Product Technical Support (APAC) Sun Microsystems ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Re: GPL & CDDL - incompatibitile., what does this mean? (round 3)
Shawn Walker wrote: FSF's comments about CDDL: "This is a free software license which is not a strong copyleft; it has some complex restrictions that make it incompatible with the GNU GPL. That is, a module covered by the GPL and a module covered by the CDDL cannot legally be linked together. We urge you not to use the CDDL for this reason. Also unfortunate in the CDDL is its use of the term "intellectual property"." I see this quoted a lot, and the part about "cannot legally be linked together" is utter crap. That being said, if you *do* link them together then you are prevented from distributing because you cannot satify the conditoins of both licenses. There is nothing in either license preventing you from linking GPL code and CDDL code on your own systems if you have no intention of distributing it. Richard, as it seems that you are reading this list, is there any chance of getting that FAQ answer clarified? alan. -- Alan Hargreaves - http://blogs.sun.com/tpenta Kernel/VOSJEC/Performance Engineer Product Technical Support (APAC) Sun Microsystems ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] No kernel source updates?
Rich Teer wrote: On Wed, 24 Aug 2005, Mike Kupfer wrote: I agree that polling for changes is a pain. But if we can deliver new updates on a regular basis, and an announcement is posted on the web site front page, is an email announcement really necessary? If you're not reading the announcements on the web site, there may be other useful information you're missing... Something we kicked around in the Pilot program was the concept of an announcement mailing list, e.g., osol-announce. I think such a mailing list would be the perfect vehicle for such announcements (becuase I DO think that that email announcements for this sort of thing are useful), WITHOUT adding to the alreadey-too-busy osol-discuss. I would have thought that this would be the perfect thing to be delivered in an RSS feed. alan. -- Alan Hargreaves - http://blogs.sun.com/tpenta Kernel/VOSJEC/Performance Engineer Product Technical Support (APAC) Sun Microsystems ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] major shortcoming in community bug process
Alan Hargreaves - Product Technical Support (APAC) wrote: Just been having a discussion with a memober of the community (you know who you are; but no names, no pack drill) who logged a bug, had it updated by a sun engineer, but now has a problem because of a combination of the following two facts: 1. the bugs interface does not allow update of an existing bug 2. the bugs interface blanks out the name of the sun engineer doing an update. He is now in the position that he wishes to discuss the bug with the person who updated it, but has no way of doing so. Given that the name is blanked out publicly, I am hesitant (to the point of not doing it) to give out the name of the engineer. I believe that Karyn is going to put the two folks in touch, but let's be real here, Karym is a limited resource and shouldn't have to be doing this. We *need* to address this, I would argue, as a relatively high priority issue. Providing a button for "respond to RE" would help for those bugs with an RE and would be a start, perhaps if there is no RE it should go to the distribution list that a bug update for that cat/subcat already goes to? Better would be to provide a mechanism for a logged in person to update the bug. One might also be able to argue that for the publicly viewable parts of a bug that can be displayed by bugs.opensolaris.org, we shouldnt' be blanking out names. alan. -- Alan Hargreaves - http://blogs.sun.com/tpenta Kernel/VOSJEC/Performance Engineer Product Technical Support (APAC) Sun Microsystems ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] major shortcoming in community bug process
Just been having a discussion with a memober of the community (you know who you are; but no names, no pack drill) who logged a bug, had it updated by a sun engineer, but now has a problem because of a combination of the following two facts: 1. the bugs interface does not allow update of an existing bug 2. the bugs interface blanks out the name of the sun engineer doing an update. He is now in the position that he wishes to discuss the bug with the person who updated it, but has no way of doing so. Given that the name is blanked out publicly, I am hesitant (to the point of not doing it) to give out the name of the engineer. I believe that Karyn is going to put the two folks in touch, but let's be real here, Karym is a limited resource and shouldn't have to be doing this. We *need* to address this, I would argue, as a relatively high priority issue. alan. -- Alan Hargreaves - http://blogs.sun.com/tpenta Kernel/VOSJEC/Performance Engineer Product Technical Support (APAC) Sun Microsystems ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] Re: SOSUG#3 on Tuesday (tomorrow) night
Of course the body shoudl agree with the subject. The meeting is on *Tuesday night* Alan. Alan Hargreaves - Product Technical Support (APAC) wrote: The Sydney Open Solaris User Group will be holding it's third meeting on Thursday night at the iForce Centre, 33 Berry St, North Sydney. Map - http://www.whereis.com/whereis/mapping/zoomMap.do?mapIndex=7&brandId=1&lev el=1 Kavit Munshi will speak about Asterisk on Solaris and I will be attempting to throw something together in the next 24 hours as well. There will also be time amde available for people to take the floor for a few minutes to talk about what they have been doing. We will be looking to start at 6:30pm, but be aware that the doors lock around 6:00. Che hopes to have copies of the video from the first meeting. Our apologies for the late confirmation of time and date. We hope to see you there. Alan Hargreaves -- http://www.opensolaris.org/os/community/os_user_groups/sosug/ -- Alan Hargreaves - http://blogs.sun.com/tpenta Kernel/VOSJEC/Performance Engineer Product Technical Support (APAC) Sun Microsystems ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] SOSUG#3 on Tuesday (tomorrow) night
The Sydney Open Solaris User Group will be holding it's third meeting on Thursday night at the iForce Centre, 33 Berry St, North Sydney. Map - http://www.whereis.com/whereis/mapping/zoomMap.do?mapIndex=7&brandId=1&lev el=1 Kavit Munshi will speak about Asterisk on Solaris and I will be attempting to throw something together in the next 24 hours as well. There will also be time amde available for people to take the floor for a few minutes to talk about what they have been doing. We will be looking to start at 6:30pm, but be aware that the doors lock around 6:00. Che hopes to have copies of the video from the first meeting. Our apologies for the late confirmation of time and date. We hope to see you there. Alan Hargreaves -- http://www.opensolaris.org/os/community/os_user_groups/sosug/ ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] OpenSolaris distributions and package managment
Dave Miner wrote: Joerg Schilling wrote: ... I thought we are still in hope that the SVr4 pkg system will become OpenSource soon. Let me provide an update. We who are responsible for the install and packaging code are just now beginning the diligence research required so that we can release it. The basic plan is to complete the diligence on the package utilities as soon as we can and (assuming we don't find issues) release the package utilities as redistributable binaries ASAP, to be followed by the code; because the package tools live in a different consolidation than the ON pieces released to OpenSolaris so far, so the code release will require more work on our end. The rest of the install code will be dealt with as a separate project. As we're just getting started I can't yet supply any estimate for how quickly this will be completed, just that we're doing the best we can. This is great news Dave. It's always good to see what progress is being made on important issues like this one. Please keep the updates coming :) alan. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Re: Re: Proposal of new community for Solaris x86 device driver
Joerg Schilling wrote: [EMAIL PROTECTED] wrote: Absolutely; but if we can replace /bin/ksh with a dual mode binary which can do both. If the license issues did not change, this would still be a decision that is not useful for OpenSolaris as there would be no source for ksh88. If there is a serious compatibility issue, then Solaris can replace the new executables with ones that are 100% backwards-compatible. There is no reason for OpenSolaris to be so hobbled. Depends on whether OpenSolaris sees 100% (backward) compatibility as a constraint or just a goal. Backward compatibility is important, but having the source is more important. If we like to discuss compatibility issues, please give us a list of deviations to ksh93. And please note that a OpenSolaris PPC port has no chance at all to include ksh88. So let us just use the motto: Provide backwards compatibility where it is possible. With ksh, it does not seem to be possible. Jorg, if the actual differences between ksh88 and ksh93 could be documented (not by source, but by impact) then there would be nothing to stop anyone taking the ksh93 source and implementing a compatability mode based on how it was called. If you have a description of the differences, you don't need the older sources. alan. -- Alan Hargreaves Senior Technical Support Specialist Phone : +61 2 9844 5379Kernel/VOSJEC/Performance Engineer Mobile : +61 416 207 573Product Technical Support (APAC) Fax: +61 2 9844 5311Sun Microsystems http://blogs.sun.com/tpenta 828 Pacific Highway, Gordon NSW 2072 perl -e 'print $i=pack(c5,(41*2),sqrt(7056),(unpack(c,H)-2),oct(115),10);' ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] Re: OpenSolaris World Wide!
For those folk in Australia, http://life.csu.edu.au/geo/findlatlong.html is a good site. They bought the stuff from the Bureau of Stats from the 1996 Census; so it is pretty comprehensive and accurate (gawd, it found the suburb that I live in up on the Central Coast [Mardi]). alan. This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] great, now we can google the source!
[EMAIL PROTECTED] wrote: Just noticed today. For example, googling for "environ_base" takes you straight to ... http://cvs.opensolaris.org/source/raw/usr/src/lib/libc/port/gen/getenv.c ... of course. But still, how cool is that?! It was indexed almost the first day, I think. Who needs cscope now :-) Apparantly a few people still (including me, it's still my source browser of choice - cscope-fast is). I talked abit about cscope-fast while the bfu was running during my talk at SOSUG and there was certainly some interest from folks who had started writing their own scripts to look for stuff in the source while offline. I did a cscope talk for PTS a year or so ago, I might refresh and blog it. I certainly like being able to search for things like - what modifies a variable - what calls a function - what does a function call - in addition to the simpler searches. Chandan's browser is wonderful, *if* you happen to be connected to the net at the time. I spend three hours a day on trains :) alan. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Re: build always uses the gcc
Sunil wrote: why are closed bins available as debug mode only? This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org It's something that I'm spending some time on. It's getting there, albeit slowly. alan. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] SOSUG #2 - July 6
Wednesday, 6:00pm July 6th, SOSUG #2 ! * Where: iForce meeting rooms, ground floor, 33 Berry St, North Sydney. * Speaker: Alan Hargreaves - OpenSolaris builds * Speaker: Boyd Adamson - SMF * plus general discussion on what has been happening. * Afterwards: VC Bar for drinks and State of Origin * Please arrive before 6:00pm - the building doors lock at 6pm. * Be there or be square! (I've always wanted to say that) --- Alan Hargreaves - http://blogs.sun.com/tpenta Kernel/VOSJEC/Performance Engineer Product Technical Support (APAC) Sun Microsystems ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
