Checking out Kitten

Kitten is available from Sandia National Labs, and is the main host OS we are targeting with Palacios. Loosely speaking, core Palacios developers are internal Kitten developers, and internal Palacios developers are external Kitten developers. The public repository for Kitten is at http://code.google.com/p/kitten. To simplify things, we are maintaining a local mirror copy on newskysaw in /home/palacios/kitten that tracks the public repository.

Kitten uses Mercurial for source management, so you will have to make sure the local Mercurial version is configured correctly. Specifically you will probably need to add something like the following Python path to your shell environment.

export PYTHONPATH=/usr/local/lib64/python2.4/site-packages/

You can then clone Kitten from the local mirror. On newskysaw, run:

hg clone /home/palacios/kitten

On newbehemoth, run

hg clone /home-remote/palacios/kitten

On other machines, run

hg clone ssh://you@newskysaw.cs.northwestern.edu//home/palacios/kitten

External developers, run

hg clone https://kitten.googlecode.com/hg/ kitten

Both the Kitten and Palacios clone commands should be run from the same directory. This means that both repositories should be located at the same directory level. The Kitten build process depends on this.

Important: Like Palacios, Kitten is under active development, and its source tree is frequently changing. In order to keep up to date with the latest version, it is necessary to periodically pull the latest changes from the mirror repository by running hg pull followed by hg update.

The current release of Kitten, which will work correctly with the current 1.2 release of Palacios is 1.2.0. To switch to the current release branch, execute

hg checkout release-1.2.0