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 56 Next »

Table of Contents

Installing OpenIndiana

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

The live 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. For administrative access, prepend your commands with pfexec.

Upgrading from OpenSolaris

In order to upgrade, you should be running OpenSolaris build 134 (snv_134) or 134b (snv_134b), the last releases published by Oracle. Upgrading from later builds including 145 and 146 may work, but is unsupported.

If you are currently running OpenSolaris 2009.06 (snv_111) you can use the following commands to upgrade to build 134 (snv_134):

Please read the release notes before proceeding!
This uses the OpenIndiana snapshot of the OpenSolaris snv_134 dev repository.

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

Once this process completes, you should reboot into the newly created snv_134 boot environment (BE) and proceed with the instructions to upgrade to OpenIndiana.

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 your ZFS pool to a newer version.

If your OpenSolaris b134 console was using a keyboard layout other than "qwerty" please be aware that upon booting into OpenIndiana for the first time, your keyboard layout may be reset to "qwerty".

Our package repository was experiencing availability problems shortly after launch caused by the content distribution network that caches downloads. If you notice hash failures or HTTP error codes, try a repository mirror.

If you experience an issue upgrading, or have other questions, please try the steps below and ask the Mailing Lists. DO NOT comment on this page except for corrections to the content. We are unable to monitor comments, and the existing comments are due to be purged.

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

Diagnosing image-update failures

ERROR
No updates available for this image.

This upggrade failure is usually caused by package dependencies which can't be satisfied by the updated packages. Often, this is because of packages from third-party repositories.

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 release, not to image-updates from the legacy repo.

pfexec pkg install --no-refresh -nv \
 pkg:/entire@0.5.11,5.11-0.148 \
 pkg:/consolidation/cde/cde-incorporation@0.5.11,5.11-0.148 \
 pkg:/consolidation/gfx/gfx-incorporation@0.5.11,5.11-0.148 \
 pkg:/consolidation/jdmk/jdmk-incorporation@0.5.11,5.11-0.148 \
 pkg:/consolidation/sic_team/sic_team-incorporation@0.5.11,5.11-0.148 \
 pkg:/consolidation/cacao/cacao-incorporation@0.5.11,5.11-0.148 \
 pkg:/consolidation/cns/cns-incorporation@0.5.11,5.11-0.148 \
 pkg:/consolidation/l10n/l10n-incorporation@0.5.11,5.11-0.148 \
 pkg:/consolidation/xvm/xvm-incorporation@0.5.11,5.11-0.148 \
 pkg:/consolidation/dbtg/dbtg-incorporation@0.5.11,5.11-0.148 \
 pkg:/consolidation/ub_javavm/ub_javavm-incorporation@0.5.11,5.11-0.148 \
 pkg:/consolidation/gnome_l10n/gnome_l10n-incorporation@0.5.11,5.11-0.148 \
 pkg:/consolidation/sfw/sfw-incorporation@0.5.11,5.11-0.148 \
 pkg:/consolidation/hcts/hcts-incorporation@0.5.11,5.11-0.148 \
 pkg:/consolidation/man/man-incorporation@0.5.11,5.11-0.148 \
 pkg:/consolidation/sunpro/sunpro-incorporation@0.5.11,5.11-0.148 \
 pkg:/consolidation/gnome/gnome-incorporation@0.5.11,5.11-0.148 \
 pkg:/consolidation/admin/admin-incorporation@0.5.11,5.11-0.148 \
 pkg:/consolidation/SunVTS/SunVTS-incorporation@0.5.11,5.11-0.148 \
 pkg:/consolidation/nspg/nspg-incorporation@0.5.11,5.11-0.148 \
 pkg:/consolidation/nvidia/nvidia-incorporation@0.5.11,5.11-0.148 \
 pkg:/consolidation/osnet/osnet-incorporation@0.5.11,5.11-0.148 \
 pkg:/consolidation/solaris_re/solaris_re-incorporation@0.5.11,5.11-0.148 \
 pkg:/consolidation/install/install-incorporation@0.5.11,5.11-0.148 \
 pkg:/consolidation/X/X-incorporation@0.5.11,5.11-0.148 \
 pkg:/consolidation/vpanels/vpanels-incorporation@0.5.11,5.11-0.148 \
 pkg:/consolidation/ips/ips-incorporation@0.5.11,5.11-0.148 \
 > pkg-debug.log 2>&1

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.

Creating the dd USB Live Image from OS X

Using Mac OS X to create the USB Live Image of OpenIndiana? These instructions may help.

You'll need at least a 2GB USB stick; this example uses a 4GB.

OS X includes all tools needed:

  • cURL - the - excellent! -tool for download (to know it is to love it!: cURL - by Daniel Stenberg)
  • md5 - to checksum the download
  • diskutil - to manage your disks
  • dd - writes the bootable image to USB stick

1. Download the dd image, and the corresponding checksum file. Be sure to download the image 'writable with dd'!

$ curl -OL http://dlc.openindiana.org/isos/148/oi-dev-148-x86.usb.writable-with-dd
$ curl -OL http://dlc.openindiana.org/isos/148/oi-dev-148-x86.usb.writable-with-dd.md5

2. Checksum your download - be sure you have a match!

$ cat oi-dev-148-x86.usb.writable-with-dd.md5
c2b907c428eaf3aa624fc057e7849c73c2b907c428eaf3aa624fc057e7849c73

$ md5 oi-dev-148-x86.usb.writable-with-dd
MD5 (oi-dev-148-x86.usb.writable-with-dd) = c2b907c428eaf3aa624fc057e7849c73

3. After plugging in the USB device you will use - and assuming it's been formatted, it will appear in diskutil.

In our example, we've used a 4GB USB stick, disk2, with a 1GB FAT_16 partition:

CAUTION: dd will erase all partitions, and all data, on this stick. Be sure of the disk# you are using!

$ diskutil list
/dev/disk0
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *2.0 TB     disk0
   1:                        EFI                         209.7 MB   disk0s1
   2:                  Apple_HFS iMac                    2.0 TB     disk0s2
/dev/disk2
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:     FDisk_partition_scheme                        *1.0 GB     disk2
   1:                 DOS_FAT_16 DATADISK                1.0 GB     disk2s1

4. unmount the USB stick, if mounted:

$ diskutil unmountDisk /dev/disk2
Unmount of all volumes on disk2 was successful

5. Write the image using dd; we timed it:

$ time dd if=oi-dev-148-x86.usb.writable-with-dd of=/dev/disk2

2160767+0 records in
2160767+0 records out
1106312704 bytes transferred in 1379.597249 secs (801910 bytes/sec)

real	23m0.001s

Welcome to OpenIndiana! Enjoy!

  • No labels