Groundbreaking research in the labs of the Sun X team has developed a highly experimental process for upgrading the X packages on an IPS machine to build 132 with only minimal damage to the surrounding environment or laboratory assistants. Much thanks are due for advice and answers provided by Rich from the IPS team and Rich from the ON-IPS project.
We are sharing this with you, our select audience, in order to start getting feedback on whether this is a workable method of delivering packages for testing - right now this is the result of much manual trial and error and will need a lot of automation before it can become part of our regular build process. Disclaimer: This is all highly experimental and has had only very very limited human trials. It is not FDA approved and may cause your hair to fall out (or be ripped out in frustration) or other unforeseen side effects. Full environmental impact studies have not yet been performed. You *will* want to do this on a new boot environment which you are willing to throw away later, since it's impossible to know yet how upgrade will work from this to the not-yet-existent real build 132 of the entire WOS. I will suggest for now that when 132 comes out you switch back to your existing nv_131 boot environment and upgrade it. Don't put any data into this boot environment you are not willing to permanently lose. This does not actually contain the binaries from the official RE build version of the X build 132 packages, but my personal build of a workspace synced to the same point, due to some issues that will be fixed in future X builds. It should still contain all of the build 132 fixes as listed on: http://hub.opensolaris.org/bin/view/Community+Group+x_win/changelogs-nv_130 These packages are x86 only because our experimentation has not yet progressed to the point of combining SPARC and x86 packages into a single repository. ---------------------------------------------------------- That said, how do you install it, if you've chosen to take the risk? First, decide if you want to set up your own repo to host it or use the repo I'm running on a test machine in my office. If you're outside the Sun firewall, you have no choice and must setup your own repo. If you're inside the Sun firewall, but have a slow link to Menlo Park, you may want your own repo. If you want reliability & connectivity guarantees, you will want your own repo - this is a test machine in my office, which is usually up, but not monitored, nor will there be coverage to fix it if it's down when I'm not in the office. To upgrade a machine using my existing repo: ** First upgrade your boot environment to build 131 using pkg image-update and the instructions/workarounds in the release notes at: http://mail.opensolaris.org/pipermail/opensolaris-announce/2010-January/001375.html After you are booted into the nv_131 boot environment: pfexec beadm create opensolaris-131-X132 pfexec beadm mount opensolaris-131-X132 /mnt pfexec pkg -R /mnt set-publisher -P -g \ http://alf.sfbay.sun.com:10000/ X pfexec pkg -R /mnt set-publisher --non-sticky opensolaris.org pfexec pkg -R /mnt uninstall entire pfexec pkg -R /mnt install X-incorporation pfexec /sbin/bootadm update-archive -R /mnt pfexec beadm umount opensolaris-131-X132 pfexec beadm activate opensolaris-131-X132 pfexec reboot To create your own repo on the local machine: (I assume you're doing this on an OpenSolaris host that is not already using /var/pkg/repo to run an IPS repo.) wget -O /tmp/X-IPS-132.tar.bz2 \ http://dlc.sun.com/osol/x/downloads/B132/X-IPS-132.tar.bz2 pfexec pkgsend -s file:///var/pkg/repo create-repository \ --set-property publisher.prefix=X cd /var/pkg/repo pfexec gtar -jxf /tmp/X-IPS-132.tar.bz2 svcadm enable pkg/server Now perform the process above with http://localhost:80/ in place of http://alf.sfbay.sun.com:10000/ when you set-publisher. Obviously we can start making scripts to handle parts of this more automatically, but first we need feedback to help decide if we're even on the right path, so please let me know what you think. Oh, and of course, once you've got the bits installed, if you find issues, please let me know that too, so we can determine if something went wrong in the IPS package generation process or if it's a bug that will also affect the real build 132. -- -Alan Coopersmith- alan.coopersmith at sun.com Sun Microsystems, Inc. - X Window System Engineering
