Vita Nuova Vita Nuova
 HOME   PRODUCTS   SOLUTIONS   RESOURCES   DOWNLOADS   ABOUT US 
  spacer
Inferno Fourth Edition: download and installation
 

Fourth Edition (20071003)

Inferno can run as either a native operating system or as a hosted virtual operating system. This document explains how to configure the system for basic networking when installing to a hosted environment. Fourth Edition Inferno can run as a hosted virtual operating system on top of Plan 9, Unix or Windows. In this document, the term Unix is used to cover all supported variants, currently FreeBSD, Irix, Linux, MacOSX (both PowerPC and x86) and Solaris, and the term Windows covers Windows Nt, Windows 2000, and Windows XP. (Windows 95, 98 and Me are not supported by this version of Inferno.)

1. Preparation

You should ensure that there is at least 220 Mbytes of free space on the filesystem. (That includes enough space to rebuild the system from source.)

For installation, you will generally follow the same instructions as for installing Inferno from CDROM, given in the file install.pdf (also available in the distribution itself).

2. Download

You have got two choices: download component packages, or download a complete installation CD image in ISO9660 format (to burn onto a real CD for installation, or to install from the image file if your operating system software allows that).

All files for download have been compressed with gzip.

2a. Choice 1: Install from CD image

Download the single file: The CD contains all supported platforms.

2b. Choice 2: Install from component packages

You will need to download two or more files, putting them all into the same temporary directory, which will act as the Inferno `installation directory' once they are all unpacked.
The file MD5sums lists the MD5 hash for each file, although download errors will usually be detected by gunzip on decompression.
  • Platform-independent components and source
    PackageRequired?Size (bytes)Contents
    inferno.tgz Yes 15 Mbytes the Inferno application environment:
    Limbo source, compiled Dis, fonts, and configuration and data files
    src.tgz Optional 4 Mbytes basic source package: the C source for
    • the Dis virtual machine
    • supporting libraries
    • the hosted Inferno system

    Required for porting or recompilation of hosted or native kernels.
    os.tgz Optional 1.8 Mbytes native source package: the C source for various sample native kernels
    Not needed if using only hosted Inferno
    utils.tgz Optional 1.1 Mbytes source package: the C source for supporting build tools including mk
    and cross-compilers for all native kernels
    Required to build hosted and/or native kernels
  • Platform-specific components (executables)
    PackageSize (bytes)Built on ...
    FreeBSD.tgz 3.1 Mbytes FreeBSD 6.0-RELEASE
    Irix.tgz 8.3 Mbytes Irix 5.3
    Linux.tgz 4 Mbytes FC4
    MacOSX.tgz 3.1 Mbytes MacOSX 10.4 (power AND i386)
    Nt.tgz 4.7 Mbytes Windows 2000
    Plan9.tgz 2 Mbytes Plan 9
    Solaris.tgz 8.2 Mbytes Solaris 2.6

3. Installation

The installation directory contains a minimal Inferno root filesystem that is used by the installation program, which is Inferno itself. The CD image contains the installation directory in a ready-to-use form; if downloading separate packages, they must first be unpacked to form the installation directory, as described below. The install subdirectory contains an installation program for each platform. For Windows systems, it is a setup.exe program. For Plan 9 and Unix systems, it is a shell script: Plan9.rc, Irix-mips.sh, Linux-386.sh, and so on. Each platform subdirectory (Plan9, Linux, or Nt) includes the Inferno executable emu (or emu.exe for Windows) for that platform in the directory:
platform/architecture/bin
The installation script (or setup.exe on Windows) uses a cut-down Inferno image to unpack the full installation.

3a. Installing from a CD-ROM

Use gunzip (or WinZip) to unpack the gzip'd ISO9660 image. Use your system's CD burning software to burn that image onto a CD. (On Unix systems, there is often a system-dependent way of mounting the contents of a CD image in a file without first burning a CD: you can do that instead if you know how.)

To install Inferno from a CD-ROM you need to find the Inferno installation directory on the CD-ROM. Unless Inferno is sharing the CD-ROM with other software it will be the top level directory on the CD-ROM.

The Inferno installation directory is likely to contain (at least) the following files and directories:

LICENCE
Irix
FreeBSD/
Linux/
Nt/
MacOSX/
Plan9/
Solaris/
dis/
install/
install.pdf		# installation guide
mnt/
n/
tmp/
The CD-ROM can be used to install Inferno to more than one platform. The installation directory contains a subdirectory for each of the platforms supported by the software on the CD-ROM.

3b. Installing from component packages

The component files are in gziped tar format and should all be unpacked into the same temporary directory. We will call this directory the Inferno installation directory.

On Windows
Unpack the files with WinZip and remember to select the Use folder names tickbox in the WinZip Extract dialog box otherwise the archive directory hierarchy will not be preserved.

On Plan 9
Unpack the files with gunzip and tar:
for(a in inferno src utils Plan9){gunzip <$a.tgz | tar xv}

On Unix or Linux
Unpack the files with tar and use the -p option to ensure that the correct file permissions are taken from the archive file. If your tar has no -p option, you should run:
umask 0
to disable masking of the file permissions before running tar. For example, to unpack the archives on Linux using the -z option to invoke gzip:
tar xzpf inferno.tgz
tar xzpf src.tgz
tar xzpf utils.tgz
tar xzpf Linux.tgz
On systems for which tar has no -z option, you must use gzip directly:
gunzip <inferno.tgz | tar xpf -
gunzip <Linux.tgz | tar xpf -
etc.
All systems
Once you unpack the component files you should see (at least) the following files and directories in the installation directory:
LICENCE
dis/
install/
install.pdf
In addition, you should see a platform subdirectory, named Plan9, Linux, or Nt depending upon which platform component you downloaded.

Once you have completed the installation you can delete the installation directory and its contents.

3c. Performing the Installation

Full installation instructions are in the file install.pdf in the installation directory. The following sections give instructions for unpacking the contents of the installation directory but do not describe how to set up the system initially; see the installation PDF file for that.

First, read the licence in the file LICENCE. If you do not agree to the terms and conditions of the licence you should not install the Inferno software and should remove any downloaded Inferno files.

You need to decide on a suitable location for Inferno; if you are installing on a Windows platform the installation program (setup.exe) will create this directory for you, on other platforms you should ensure that the directory exists and has suitable access permissions.

The usual Inferno installation directory is /usr/inferno for Plan 9, /usr/inferno or /home/inferno for Unix systems, and c:\users\inferno on Windows systems, but you can use any name you like that does not yet exist. This directory will form the root of the Inferno filesystem; the installation program will install files into and below this inferno_root directory.

Windows
To install Inferno on a Windows platform you should:
  1. Run the setup.exe program located in the install subdirectory of the media directory.
  2. Enter the pathname of the chosen inferno_root directory and press Enter.
The installation program will then perform the following tasks:
  1. Execute Nt\386\bin\emu.exe to unpack the Inferno and Nt components.
  2. Copy the LICENCE file to the root of the Inferno filesystem.
  3. Rename the file emu.new to emu.exe in the Nt\386\bin directory of the new Inferno filesystem.
  4. Create an entry in the Windows registry for the location of the Inferno root directory.
  5. Create a Windows Start Menu shortcut to emu.exe entitled: Vita Nuova Inferno.
When installing on Windows NT or Windows 2000, the installation program determines if the current user belongs to the Administrators group. If so, the Start Menu entry is created in the All Users profile, otherwise it is created in the user's private profile.
Plan 9
To install Inferno on the Plan 9 platform:
  1. You might optionally first create a user inferno to own the files. (If you do, you will either need to install the software as that user, or switch permission checking off to allow the installation software to change file ownership.)
  2. Make the target directory: mkdir inferno_root
  3. Run
    rc /install_path/install/Plan9.rc -u  inferno_root
    
    Where install_path is the full pathname to the media directory and inferno_root is the chosen Inferno root directory. The installation program will then perform the following tasks:
    1. Execute Plan9/$cputype/bin/emu to unpack the Inferno and Plan 9 components.
    2. Copy the LICENCE file to the root of the Inferno filesystem.
    3. Rename the file emu.new to emu in the Plan9/$cputype/bin directory of the new Inferno filesystem.
    The -u option causes the ownership and group membership of the installed files to be taken from the archive. If you omit it, the files will be owned by you.
  4. Make sure that the window is able to scroll to display the list of directories that the installation software prints. You may need to select the scroll option from the menu displayed when you click on the middle mouse button in the output window to enable this.
Unix (including Linux and FreeBSD)
On Posix systems, files installed from the distribution will have owner and group determined by the owner and group of the user who performs the installation. (At our site, we create a new user, inferno, and become that user before installing.)

To install Inferno on a Unix or Linux platform you should:

  1. Optionally, add a new user to own the files; become that user (eg, using su appropriately).
  2. Make the installation directory: mkdir inferno_root
  3. Run sh /install_path/install/platform-arch.sh inferno_root.
Where platform and arch are one of the supported combinations of Unix variant and CPU architecture, install_path is the full pathname to the media directory and inferno_root is the chosen inferno_root directory. The installation program will then perform the following tasks:
  1. Execute platform/arch/bin/emu to unpack the Inferno and platform components.
  2. Copy the LICENCE file to the root of the Inferno filesystem.
  3. Rename the file emu.new to emu in the platform/arch/bin directory of the new Inferno filesystem.

3d. Linux version differences

The Linux executable in Linux.tgz was built using Fedora Core 4 (FC4). With src.tgz installed, you can rebuild the emu executable for your own Linux system:
	cd install_path/emu/Linux; mk clean; mk install
They might need Native Posix Threads support configured.

4. Configuring and running Inferno

See the installation guide install.pdf (or installation.pdf) online or in the distribution package.

Copyright © 2006 Vita Nuova Holdings Limited.