If you are using Cool Stack or Web Stack for your AMP (Apache, PHP and MySQL) stack needs on either Solaris 10 or Red Hat Enterprise Linux, then you might want to check out the latest development build update of Web Stack. This build delivers PHP 5.2.12 , Apache 2.2.14 etc.
For more information on how to update to this build, please refer to my earlier blog on this topic. If you run into any issues, please use our forum for any trouble shooting tips.
Hi All,
So I'm just playing with B132 on the Acer One 8.9".
Even though I downloaded the flash plugin from Adobe and installed it to /usr/lib/firefox/plugins it would not show up in firefox.
I found out in the end that you need to have SUNWmlib installed for the flash plugin to work.
I also tested the attachment in the http://defect.opensolaris.org/bz/show_bug.cgi?id=14099 , after a restart both the Acer One 8.9" and MSI wind could run compiz.
I went to the Tokyo2Point0 event last night.
There were 250
people there, so it was a packed house for sure. Really nice to catch up with a
bunch of people. I haven't been to one of these events in many months.
Just been too busy. It was also to good to see Michael Sullivan do a
short talk on the OpenSolaris
Bible Translation Project, too.
The OpenSolaris Community in Japan will participate at the Spring Tokyo
Open Source Conference with three talks from Keiichi Oono, Kenichi
Mizoguchi, and Masafumi Ohta on February 27th. See Ohta-san's announcement in Japanese and English.
For those of you that require license acceptance or display for your packages, you should be aware that starting with OpenSolaris development build b131, new functionality will be delivered to support license acceptance and display.
The following fixes and enhancements were integrated:
These changes were made to support packages that require display or acceptance of license related data during package install and update operations. As a result of these changes, the pkg(1) client and client API require explicit acceptance and/or indication of license display during install and update operations.
Please note that (currently) no packages exist that use this functionality, but they are expected in the near future.
If any of the license actions contained in a package being installed or updated have must-accept=true, the following pkg(1) subcommands require that the new --accept option be provided before the operation will proceed:
In addition, all of the above subcommands also now have a --licenses option to display the payload of all the licenses for packages part of the operation. For example:
pkg install -n --licenses foo
The above command would display all of the licenses for the packages that would be installed or updated if the package 'foo' were installed or updated. If the --accept option is not provided, and a license requires acceptance, the pkg(1) client will now exit with exit code 6, indicating license acceptance failure. If a license requires display, the pkg(1) client will display it during install/update operations; this cannot be suppressed.
Version 29:
Incompatible with clients using versions 0-28:
The ImageInterface class has changed as follows:
The LicenseInfo class has changed as follows:
The PlanDescription class has changed as follows:
To use this new license acceptance functionality, simply add must-accept=true or must-display=true (as appropriate) to license actions in your package manifest. An example pkgsend sequence might look like this:
open licensed@1.3,5.11-0 add depend type=require fmri=baz@1.0 add file /tmp/libc.so.1 mode=0555 owner=root group=bin path=/lib/libc.so.1 add license /tmp/libc.copyright license=libc.copyright must-display=True add license /tmp/libc.license license=libc.license must-accept=True close
Please note that this functionality is not supported before build 131, and that you should use this functionality sparingly. must-accept=true should not be placed on the majority of open source licenses (BSD, GPL, etc.) and must-display should only be set if absolutely necessary.
Comments or concerns should be sent to the pkg-discuss mailing list on opensolaris.org.
Changeset 1736 in the pkg(5) gate made the following changes:
11522 pkg should require publisher prefix to match repository information
7156 client image api needs image creation interface
12744 update_publisher over-zealously testing publisher validity
14203 image-create usage doesn't mention mirror / origin options
pkg image-create -p <uri> /target
pkg set-publisher -g http://pkg.opensolaris.org/contrib \
contrib.opensolaris.org
pkg set-publisher -p http://pkg.opensolaris.org/contrib
Incompatible with clients using API versions 0-31.
The ImageInterface class has changed as follows:
- The add_publisher and update_publisher methods now validate the image's publisher configuration against the origins of the publisher. If any of the origins are found to not match, an UnknownRepositoryPublishers exception will be raised. If one of the new repository origins does not provide publisher configuration information or it is incomplete, a RepoPubConfigUnavailable exception will be raised.
The pkg.client.api module has changed as follows:
The pkg.client.api_errors modules has changed as follows:
Feedback is welcomed on the pkg-discuss mailing list on opensolaris.org.
I can't count how many times I've read in the various OpenSolaris forums "Read the release notes."
It's true, the OpenSolaris release notes are chock full of good information. However, where are these mysterious release notes?
The release notes are posted by David Comay to the osol-announce and indiana-discuss mailing lists. However, you have to filter through all the other traffic on those lists to find them.
I've thought about setting up a wiki pointing to them, but that's just one more thing I'd forget to maintain. Instead, here's a quick Google search that seems to do the trick. If you can think of a better way to customize it, please let me know.
Earlier today I was thinking about the original "good luck" email I
sent to the OpenSolaris Pilot Community just before we opened the
project in June of 2005. Fortunately, the opensolaris-discuss public
archive actually goes back 9 months before we launched, so this
mail survives in the open and from the other threads you get a glimpse into some of the very
earliest conversations taking place when the project was private. Anyway, what
strikes me is how different the situation was back then, how utterly
conservative we were, and how my thinking has changed as a result of my
experiences all along the way. A day after I sent this email, we
opened. See my opening blog
here, and the
result of that opening announcement here. History. Always
enlightening.
[osol-discuss] Good Luck and Thank You
Jim Grisanzio Jim.Grisanzio at Sun.COM
Mon Jun 13 17:27:01 PDT 2005
Hello, OpenSource Pilot Community. I just wanted to chime in before the fur really flies around here: Good Luck, and Thank You! You all deserve Sun's thanks for your efforts and your patience this year. It should be wild day tomorrow, for sure, so light up those blogs and start talking, guys. The engineers are leading this launch tomorrow, make no mistake about it. Oh, and if you want to bring someone into the program, you *don't* have to call me and sign another f****** NDA. Just do it. I can't tell you how happy I am to not have to dig out another NDA. Not that I could read the damn thing but whatever. It's such a cold way to start a friendly little conversation, don't you think? Also, I've tried to honor as many of your requests (and those from internal people) as possible to get people into the program. We ended up with 145, but quite frankly, dozens and dozens of developers never made it in due to lack of time or resources. We even had a dozen Chinese engineers all briefed, translated, and NDA-signed but couldn't get export control approval in time. It drove me nuts for three months. I'm more than a bit pissed about that one. Anyway, I hope you are happy with the results of what we are all releasing. The core team here has worked almost non-stop for weeks on this to get ready for the final push. We wanted to do more, you know that, but hey, look at where we were last year and look at the potential tomorrow brings. Also, the OpenSolaris team internally really has been genuine in their intentions, I can assure you. At times we've not been as open as we could have been -- we get that -- but I hope you believe me when I say that many people on the team fought hard on your behalf all year long. Every time you told us we were full of shit on something we took it to heart and it went up line. There were a few, ah, heated, conversations regarding some of the issues that were discussed in the pilot. We won some and we lost some, but every time we moved a little closer to our goal of openness. As you've seen, this stuff takes time. I wish we could have exposed more of that process to you. Next time it will probably be easier to do that. As this program has grown it's garnered attention from all across Sun and from Sun's competitors and supporters. Just recently, I've heard from executives and engineers traveling to South America and to Asia, and they report that there *absolutely* is massive community interest out there. Even Wall Street has noticed. Some people are probably a bit confused since the Solaris community was supposed to be dead by now. Well, too bad. It's too late. They lost their window of opportunity to crush us. Our next step is to stay positive and to engage the interest we know is there, make it tangible, and grow this OpenSolaris community. In a very real way, you've all been part of something special here. You've helped change this company and potentially an entire market along the way. Some people may not know this quite yet, but they'll surely find out tomorrow. You are some of the most knowledgeable people in the world about Solaris, and you've help make OpenSolaris a possibility. Congratulations and we'll see you on the other side. Jim
It matters greatly who wins the war because the winners write the
history and they rarely -- if ever -- characterize events accurately.
That's what makes history fun. It's a puzzle and it's always changing. In this case I'm talking
about Caesar, who in 58 A.D.
destroyed the Celts in Gaul (France), killed and enslaved millions,
took the gold, propagandized the history, and went on to rule Rome as
Emperor. Nice guy. That is of you like vicious dudes running psychotic
military dictatorships. But whatever. The point is that the Romans won,
so their view of things survived throughout the ages. But I'm more interested in what was lost? What did the Romans conveniently leave out of their history?
For that, check out The Primitive Celts, an entertaining and fascinating look at the Celts, who the Romans say were mere barbarians. But were they? Seems some archaeologists are discovering the Celts actually had a highly developed society with the most advanced calender at the time and a sophisticated economy based on a variety of trades. They minded gold all across Europe, and they built a vast network of roads to facilitate international trade. Generally, the contrast to Rome was nearly total. Where the Celts decentralized things into a web and community-like structure, the Romans centralized them into a rigid hierarchy. And that proved a critical and fatal difference -- at least in ancient times. Centralization won. Big time, actually.
But I wonder if that distinction remains true today. What's the better concept around which to build a society in 2010? And, more importantly, who wins the war when these differences collide for whatever reason? Surely the world today is substantially different than when the Romans were wrecking the place two thousand years ago, but would their systems prevail today? You can look at this from the perspective of a county or a company or even a project. It's just the management of resources to achieve a goal. Nothing more. But my question asks which is better and who wins now?
Just since Wednesday of this week here are a few things that have happened:
And, yes, lots of work. For example several new systems installed for our automated test and certification solution, approximately 60 customers and countless prospects have had their questions answered, and significant recruiting work on our immediate priorities including inside sales, sales engineering, software develand support.
Hopefully this behind the scenes look into life at a fast growing start-up is of interest to some of you out there.
Hi All,
So to fix the B132 rge pcie problems on the MSI Wind you need to copy the B130 /kernel/drv/rge somewhere on the system after the pkg image-update, on the first boot after B132 update, copy the stored rge into /kernel/drv and reboot, the errors should go away.
For some reason the Xorg on my system is trying to load the 64 bit libglx.so, which stops compiz running, you can just link the /usr/lib/xorg/modules/extensions/GL/libglx.so back to the /usr/lib/xorg/modules/extensions/libglx.so.
What's pissing me off, is during a restart the link gets set back to the 64/libglx.so, not sure what's doing this yet.
USB sd card ready is not working now either, and cpu 1 is still running at 100% after a resume.
Dave
I am moving my PostgreSQL on OpenSolaris realted entries to a new external blog. Since it is not part of my $dayjob anymore. Hope you update your bookmarks too.
Read "Building latest PostgreSQL CVS Head on OpenSolaris".
Here is a nice example from Serbia demonstrating the value of building a local OpenSolaris community. It can lead to some very interesting organizations paying very close attention to what you are doing. Congrats, guys! Some of the OpenSolaris User Groups are doing some really interesting work out there, and they are contributing to the overall community in a very big way.
XXX cl_runtime: [ID 856360 kern.warning] WARNING: QUORUM_GENERIC: quorum_read_keys error:
Reading the registration keys failed on quorum device /dev/did/rdsk/d7s2 with error 22.
406 int
407 quorum_scsi_sector_read(
[...]
449 error = quorum_ioctl_with_retries(vnode_ptr, USCSICMD, (intptr_t)&ucmd,
450 &retval);
451 if (error != 0) {
452 CMM_TRACE(("quorum_scsi_sector_read: ioctl USCSICMD "
453 "returned error (%d).\n", error));
454 kmem_free(ucmd.uscsi_rqbuf, (size_t)SENSE_LENGTH);
455 return (error);
456 }
457
458 //
459 // Calculate and compare the checksum if check_data is true.
460 // Also, validate the pgres_id string at the beg of the sector.
461 //
462 if (check_data) {
463 PGRE_CALCCHKSUM(chksum, sector, iptr);
464
465 // Compare the checksum.
466 if (PGRE_GETCHKSUM(sector) != chksum) {
467 CMM_TRACE(("quorum_scsi_sector_read: "
468 "checksum mismatch.\n"));
469 kmem_free(ucmd.uscsi_rqbuf, (size_t)SENSE_LENGTH);
470 return (EINVAL);
471 }
472
473 //
474 // Validate the PGRE string at the beg of the sector.
475 // It should contain PGRE_ID_LEAD_STRING[1|2].
476 //
477 if ((os::strncmp((char *)sector->pgres_id, PGRE_ID_LEAD_STRING1,
478 strlen(PGRE_ID_LEAD_STRING1)) != 0) &&
479 (os::strncmp((char *)sector->pgres_id, PGRE_ID_LEAD_STRING2,
480 strlen(PGRE_ID_LEAD_STRING2)) != 0)) {
481 CMM_TRACE(("quorum_scsi_sector_read: pgre id "
482 "mismatch. The sector id is %s.\n",
483 sector->pgres_id));
484 kmem_free(ucmd.uscsi_rqbuf, (size_t)SENSE_LENGTH);
485 return (EINVAL);
486 }
487
488 }
489 kmem_free(ucmd.uscsi_rqbuf, (size_t)SENSE_LENGTH);
490
491 return (error);
492 }
56 -> __1cXquorum_scsi_sector_read6FpnFvnode_LpnLpgre_sector_b_i_ 6308555744942019 enter
56 -> __1cZquorum_ioctl_with_retries6FpnFvnode_ilpi_i_ 6308555744957176 enter
56 - __1cZquorum_ioctl_with_retries6FpnFvnode_ilpi_i_ 6308555745089857 rc: 0
56 -> __1cNdbg_print_bufIdbprintf6MpcE_v_ 6308555745108310 enter
56 -> __1cNdbg_print_bufLdbprintf_va6Mbpcrpv_v_ 6308555745120941 enter
56 -> __1cCosHsprintf6FpcpkcE_v_ 6308555745134231 enter
56 - __1cCosHsprintf6FpcpkcE_v_ 6308555745148729 rc: 2890607504684
56 - __1cNdbg_print_bufLdbprintf_va6Mbpcrpv_v_ 6308555745162898 rc: 1886718112
56 - __1cNdbg_print_bufIdbprintf6MpcE_v_ 6308555745175529 rc: 1886718112
56 - __1cXquorum_scsi_sector_read6FpnFvnode_LpnLpgre_sector_b_i_ 6308555745188599 rc: 22
21 -> __1cNdbg_print_bufIdbprintf6MpcE_v_ 6309628794339298 quorum_scsi_sector_read: checksum mismatch.
Some images from the OpenSolaris Night Seminar in Tokyo earlier this evening with presentations from Junko Yoshida, Mami Sueki, and Shoji Haraguchi. Video from Shoji Haraguchi here.
Hundreds more images from the OpenSolaris community in Japan right here.
The message was simple:
Today's my last day at Sun. I'll miss it. Seems only fitting to end on a #haiku. Financial crisis/Stalled too many customers/CEO no more
Please post your thoughts on Jonathan's leaving. Its a mixed emotion... on one hand he set some great goals and put a fire under things. A lot of us believed in him. And yet, he failed to execute and ultimately was responsible for Sun's demise. Could someone else have done a better job and still kept the culture alive? I don't know honestly.
I'll continue to stay neutral on the subject and reserve judgment until the behind-the-scenes stories trickle out over the next months and years. Jonathan screwed up, yes, but I think that Jonathan also got screwed himself, more than we realize. Time will tell.
In other news, Oracle is finally doing what has needed to be done for years: Oracle to Revamp Sun Supply Chain. One of the biggest complaints by customers for years has been inability to get timely delivery of systems. Its good to see signs of that era ending.
Also, Project Darkstar & Kenai are being axed. Project Kenai, a SourceForge like project hosting service provided free by Sun, will close its doors on April 2nd 2010. You have untill then to get stuff out. One of the most important projects there, Immutable Service Containers (ISC) has moved to OpenSolaris.org.
Hi All,
So I've been working on a Samsung NC20, working to get a solid base working with Ubuntu 9.10 and an AT&T 3G usb modem.
I was creating the best hardware platform for a JavaFX project to run on, I'm sending the Samsung to the JavaFX team today.
I was left with the AT&T 3G usb modem, so I thought, why not install Ubuntu on the MSI Wind.
It already had Window 7 and OpenSolaris B131 and a 40Gb fat32 partition between the two OS's, so I decided to install Ubuntu 9.10 here.
Now the MSI will boot Windows 7, Ubuntu 9.10 or OpenSolaris B131.
I may even try to get the AT&T modem working under OpenSolaris.
Before I decided to blog this, I figured I would first search to check out if there are other blogs that discuss the techniques required to recover a system. Turns out sriram blog talks about using beadm technique but here a bit more elaborate version.
Our local admin was trying to upgrade the AI server to a newer build. The system was installed with OpenSolaris 2009.06 and he had published a number of install services. However a simple pkg image-update failed miserably and so did pkg install SUNWipkg. A quick investigation revealed that someone had added an older version 2008.11 version of the SUNWipkg(pkg verify is your friend). This normally would be possible, but the user had added the SVR4 version of SUNWipkg. So the system was not upgradable. A reinstall was not the answer he wanted to hear.
So here's what we did:
1. Created a new beadm from the snapshot and activated it.
2. Rebooted to the new BE and mounted the old one.
3. pkg image updated the old BE.
4. Upon successful completion, activated the old BE and rebooted it.
These are the steps. All these commands were run as root. The name of the BE was opensolaris.
1. beadm create -e opensolaris@install opensolaris-1
2. beadm activate opensolaris-1; reboot
3. (after logging in), beadm mount opensolaris /mnt
4. pkg -R /mnt SUNWipkg
5. pkg -R /mnt image-update
6. reboot.
The waiting is over, deal is done. Sun + Oracle = Oracle. I am glad I made it across but it is sad to see old friends depart. The move to Oracle will definitely require one to adapt to new ways which at times will be challenging. But for me it's a marked timeline in my life. I will be a bit nostalgic about the past, but it's time to move on and look at the future and hope its bright.
Recently, Sun published Sun Alert for recently discovered security vulnerability within Sun Web Server and immediately released updates to Web Server 7 and Web Server 6.1 release train to address these discovered vulnerabilities.
If you are running Sun Java System / iPlanet / Sun ONE Web Server, we strongly urge to upgrade to this latest update.