Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 37 Next »

Table of Contents

Installing OpenIndiana

You need a PC (32 or 64-bit) with at least 512 megabytes of RAM, and 3 gigabytes of available disk space. You can also use virtual machine software such as VirtualBox or VMware.

The USB image requires a USB storage device larger than 1 gigabyte in size. A 1 gigabyte stick will not work.
To create a live USB in Windows, use the OpenSolaris Live USB Creator.
To create a live USB in Solaris or OpenSolaris, use usbcopy.
To create a live USB on a Unix-like system, download the image for dd or read http://chonan-en.blog.pid0.org/2009/11/how-to-create-opensolaris-live-usb.html to use the standard live USB.

  • Boot your computer with the medium inserted. You may have to change the boot device order in your BIOS configuration.

    In VirtualBox 3.2 or later, "Use host I/O cache" must be enabled in the emulated storage controller used by the virtual machine to successfully boot OpenIndiana.

  • When you see a menu, press Enter to start OpenIndiana on your computer. As it runs, you will be prompted with a few questions.
  • You should eventually be presented with a desktop. You can use the Device Driver Utility to check if your hardware requires additional drivers.
  • Click on Install OpenIndiana to permanently install OpenIndiana on your computer.

If you do not see a menu after booting your computer with the DVD or USB stick, and instead see some text and a "grub>" prompt, there may be an error in your copy of the installer.

If you see a "login:" prompt after selecting your keyboard and language and no desktop appears after several seconds, there may be a problem with the drivers for your graphics hardware. Please let us know if this happens.

The login for the text session is username jack, password jack. The installer is graphical and requires X11, although it is possible to use it over a network with SSH X forwarding if you enable SSH.

Upgrading from OpenSolaris

Our package repository was experiencing availability problems shortly after launch caused by the content distribution network that caches downloads. We believe we have resolved these problems. There may still be errors in the cache. If you experience problems, try a repository mirror.

You can upgrade an existing (x86) OpenSolaris system to OpenIndiana.
From the command line:

pfexec pkg set-publisher --non-sticky opensolaris.org
pfexec pkg set-publisher -P -O http://pkg.openindiana.org/dev openindiana.org
pfexec pkg image-update -v

This will add OpenIndiana as a new boot environment (BE). You will still be able to use your previous OpenSolaris system until you remove the OpenSolaris BE or upgrade the ZFS pool to a newer version.

Please don't remove (unset) the opensolaris.org publisher at this time. Not all of the software has updates in openindiana.org.

In order to upgrade, you should be running OpenSolaris build 134 (snv_134), the last development release published by Oracle.

Upgrading from later builds will NOT work. We have updated our repository so upgrading from later builds including 145 and 146 may work now.

To upgrade from OpenSolaris 2009.06 (snv_111) to snv_134, you can use the following commands:

Please read the release notes first before proceeding!

pfexec pkg install SUNWipkg SUNWipkg-um SUNWipkg-gui
pfexec pkg set-publisher -O http://pkg.openindiana.org/legacy opensolaris.org
pfexec pkg image-update -v

This uses the OpenIndiana snapshot of the OpenSolaris snv_134 dev repository. Once complete you can boot into the new snv_134 boot environment (BE) and upgrade to OpenIndiana.


Diagnosing image-update

The following script can be run to help determine why image-update does nothing OR fails to update as many packages as you expect. It applies to the OpenIndiana 147 release, not to image-updates from the legacy repo.

pfexec pkg install --no-refresh -nv \
pkg:/entire@0.5.11,5.11-0.147:20100914T054011Z \
pkg:/consolidation/X/X-incorporation@0.5.11,5.11-0.148:20100914T034322Z \
pkg:/consolidation/gnome/gnome-incorporation@0.5.11,5.11-0.147:20100917T201104Z \
pkg:/consolidation/gnome_l10n/gnome_l10n-incorporation@0.5.11,5.11-0.147:20100914T030830Z \
pkg:/consolidation/install/install-incorporation@0.5.11,5.11-0.147:20100914T034326Z \
pkg:/consolidation/ips/ips-incorporation@0.5.11,5.11-0.147:20100914T034329Z \
pkg:/consolidation/osnet/osnet-incorporation@0.5.11,5.11-0.148:20100914T034332Z \
pkg:/consolidation/sfw/sfw-incorporation@0.5.11,5.11-0.147:20100914T030830Z \
pkg:/consolidation/solaris_re/solaris_re-incorporation@0.5.11,5.11-0.147:20100914T034340Z \
pkg:/consolidation/xvm/xvm-incorporation@0.5.11,5.11-0.147:20100914T030830Z \
> pkg-debug.log

The output may be HUGE and CONVOLUTED, so please redirect to a file.

Unknown macro: {indo}

You are looking for two strings in the output

1/ "FAIL"

2/ "OBSOLETE"

An existing package which you had installed and working with your current version of the OS, but which depends on a package which has been deleted or renamed since your install, might look like this:

incorporate: SUNWphp52-pgsql@5.2.12-0.146

Requires one of:   pkg://opensolaris.org/SUNWphp52-pgsql@5.2.12,5.11-0.146:20100813T052503Z   (OBSOLETE and incompatible with installed pkgs:   pkg://opensolaris.org/amp-dev@0.5.11,5.11-0.111:20090508T164640Z

Removing pkg://opensolaris.org/amp-dev will get past this particular error - there may be others in your output.

  • No labels