UNIX Consulting and Expertise
Golden Apple Enterprises Ltd. » Posts in 'opensolaris' category

Bordeaux running on OpenIndiana Comments Off on Bordeaux running on OpenIndiana

The Bordeaux Technology group have today announced they have a build of Bordeaux running on OpenIndiana. Bordeaux is a commercial implementation of WINE, and they provide support contracts and incident support – ideal for corporate environments where supportability of Open Source solutions is an issue.

Bordeaux itself provides support for:

  • Microsoft Office Suite of Applications. Microsoft Word, Excel, PowerPoint, Access
  • Internet Explorer. Web Developers frequently need to run multiple versions of Internet Explorer to compare how a website will look to all users running different revisions of the browser software
  • Consumer Video Games. In many cases these contain copy-protection systems that are impossible to port to another platform. This makes vendors reluctant to invest the capital in acquiring another system that will work on other platforms
  • Adobe Photoshop CS and CS2
  • Custom applications for which replacement is not available or development/purchase of a replacement is not economically feasible when compared to the cost of maintaining the existing application in a legacy emulation environment

To so quickly have a build of commercial software for OpenIndiana is a great endorsement, especially when it’s something as useful as Bordeaux.

You can head over to their store and pick up the Bordeaux for Solaris license for only $25, including support.

Upgrading from OpenSolaris 2009.06 to OpenIndiana 1 comment

I’ve written up instructions for this on the OpenIndiana Wiki, but am still seeing a number of questions on how to do this, so thought I’d stick a quick post up here as well, covering how to upgrade from OpenSolaris 2009.06 to OpenIndiana.

The first thing to remember is that, unlike lesser operating systems, Boot Evironments (BEs) mean that you an upgrade with impunity – if it all goes wrong, you just reboot, select the previous working BE, and carry on.

The majority of people will have OpenSolaris 2009.06, the last OpenSolaris distribution. This release snv_111, which wasn’t the last OpenSolaris project release. Confused? We all are.

The direct upgrade from snv_111 to OpenIndiana is problematic – a lot of things have changed, not least the updates to the packaging system. So this needs to be done in two stages – first, update to snv_134 (which would have become the OpenSolaris 2010.03/05/whatever distribution) and then jump to OpenIndiana (oi_147).

So, the first step is to tell OpenSolaris to look at the snv_134 repository hosted by OpenIndiana:

pfexec pkg set-publisher -O http://pkg.openindiana.org/legacy opensolaris.org

This is a snapshot of Sun’s snv_134 repository – as I’m not sure how long that will hang around, it’s best to go through the OpenIndiana repos instead.

Next, we need to tell OpenSolaris to do an image update – basically, dig through the list of local packages, the list of packages in the new repo, find the updates, and then install them:

pfexec pkg image-update

This will take some time, so head off with a coffee and catch up with the OpenIndiana mailing lists and the IRC channel.

Once image-update has finished, you can reboot your machine. The new BE will have been selected as the default, so your machine should boot straight into snv_134.

Start up another terminal session, and we pretty much do the same thing.

pfexec pkg set-publisher --non-sticky opensolaris.org
pfexec pkg set-publisher -g http://pkg.openindiana.org/dev openindiana.org

Once we’ve setup which repos to use, we then need to tell pkg that we’d prefer to use the OpenIndiana ones:

pfexec pkg set-publisher -P openindiana.org

Then we purge anything old, and do a full image-update:

pfexec pkg uninstall entire
pfexec pkg image-update

Once again image-update will do it’s thing, and at the end you’ll be asked to reboot. You’ll find OpenIndiana now on the boot menu – enjoy!

Note that at every stage, you can reboot, select your old or previous BE from the boot menu, and boot back into a known, working environment. This makes testing updates and new releases much less hazardous, and means it’s very easy to get stuck in and try out OpenIndiana for yourself.

OpenSolaris lives! OpenIndiana announced Comments Off on OpenSolaris lives! OpenIndiana announced

Now that Alasdair has started to spread the news ahead of next week, I can share the details of OpenIndiana.

OpenIndiana is a continuation of the OpenSolaris operating system. It was conceived during the period of uncertainty following the Oracle takeover of Sun Microsystems, after several months passed with no binary updates made available to the public.

The project will be formally unveiled with an announcement next Tuesday.

OpenIndiana is part of the Illumos Foundation, and provides a true open source community alternative to Solaris 11 and Solaris 11 Express, with an open development model and full community participation.

Come along on Tuesday – either in person if you’re in London, or online – and see what OpenIndiana is about, then get involved. If you’ve got OpenSolaris 2009.06 machines you’ll really want to know about this.

OGB resigns, OpenSolaris canned – or is it? Comments Off on OGB resigns, OpenSolaris canned – or is it?

As expected the OpenSolaris OGB have officially thrown in the towel. Plans have been leaked internally from Oracle showing that they are going to stop open development of OpenSolaris.

All pretty much expected, and hopefully this will be the ‘jumpstart’ that the OpenSolaris community needs to start pushing community distros and community code.

What a lot of the peanut gallery commentators have missed is that this doesn’t spell the end of any OpenSolaris development. Oracle will still release code, just after a long-ish delay. This is a clearly a tactic to address people like Nexenta, who are directly competing with Oracle in the open storage space – where there’s an awful lot of money up for grabs.

There are pluses and minuses for all of this – to get an idea read these posts from Ben Rockwood and Joerg Mollenkamp to see the view from both sides of the fence.

The big plus for existing Solaris shops – and yes, it is a plus – is the return of Solaris Express. Specifically Solaris 11 Express, which should be appearing sometime after OpenWorld.

The death of SX:CE was a massive mistake from Sun – OpenSolaris was too far ahead of current shipping Solaris versions, and it made any sort of planning or roadmap to implement new features impossible, especially in a large environment. You know, those big corporate Solaris/SPARC shops who paid Sun’s bills?

The return of Solaris Express gives these guys – the ones who pay big money to Oracle – a chance to evaluate new features, plan out a deployment/upgrade strategy. Which means it’s much more likely they’ll stick with Solaris, take advantage of the new features – and continue to pay money to Oracle.

Sadly for Oracle they seem to have handled Solaris with all the deftness and tact of IBM with OS/2. Getting all bullish with licensing and support costs without giving your customers solid roadmaps and upgrade plans is pretty amateurish.

Configuring Sun’s Extras repository in OpenSolaris Comments Off on Configuring Sun’s Extras repository in OpenSolaris

OpenSolaris by default comes configured to pull packages from at least one repository – the main one at OpenSolaris.org. You can configure other repositories fairly easily – both Blastwave and Sunfreeware some available with IPS versions of their existing Solaris packages.

However, Sun also offer two extra repositories – one for those with a support contract for OpenSolaris, and one containing extra software – a bit like the old Extras CD that came with the Solaris media pack.

The main site for accessing all of this is https://pkg.sun.com If you don’t already have a Sun ID and password, you’ll need to follow the links from that page to register for them (don’t worry, it’s free). Then login, and you can see you’re presented with links to generate Certificates for the two repositories. Let’s assume you’re not a corporate user and don’t have a support contract, and concentrate on the Extras repository.

Click the link to generate the key and certificate for pkg.sun.com/opensolaris/extra and save them somewhere safe – you’ll be needing them again. For example, I tend to stick them in /var/ssl/pkg as well as keeping copies in my home directory.

Now what we need to do is add the Extras repository as a publisher in the package management system, and then link the key and certificate to that publisher.

So in this example we can accomplish this in one command (note the backslash to fit it across two lines):

$ pfexec pkg set-publisher -O https://pkg.sun.com/opensolaris/extra \
-k /var/pkg/ssl/OpenSolaris_extras.key.pem -c /var/pkg/ssl/OpenSolaris_extras.certificate.pem extra

All this does is:

  • adds a new repository at https://pkg.sun.com/opensolaris/extra
  • links the key (-k) /var/pkg/ssl/OpenSolaris_extras.key.pem to it
  • links the certificate (-c) /var/pkg/ssl/OpenSolaris_extras.certificate.pem to it
  • gives it the name ‘extra’ in the package manager

That’s all there is to it. Now you can use the standard OpenSolaris package management commands:

  • pkg refresh will update the catalog with the packages from the new repository
  • pkg install can be used to install them

And of course, if you’re using the OpenSolaris package manager gui, you can select the new repository from the drop-down list of available repositories, and then browse through from there.

Top of page / Subscribe to new Entries (RSS)