Last Contents Next

________________

Installing Skipper

________________

Saving To Disk

If you find that the browser displays funny characters instead of offering to save the download to disk when you click on the links below, try holding down the Shift key when you click. If it then asks what format to save to disk, choose "Source".

The Binary Distribution

If you want to run Skipper without the Festival voice synthesiser or just read the documentation, but you don't want to compile the programs or improve them, you should download the binary distribution. It's slightly easier to install than the source distribution.

Just click on the link below, and save the file in a convenient directory - usually the Skipper user's home directory.

skipper-bin-1.6.0.tgz (1.7 MB)

Windows users can download the binary distribution to browse the documentation offline. WinZip and PkZip can cope with the tgz file format. The homepage is file doc/index.html.

The Source Distribution

If you want to run Skipper with the Festival voice synthesiser, compile the programs or make improvements, you should download the source distribution. Just click on the link below and save the file as for the binary distribution discussed above.

skipper-src-1.6.0.tgz (1.6 MB)

Floppy Disks

Because CD-RW drives are still rare on second hand PCs, some people may prefer to pass Skipper round on floppy disks. This is great because it saves server bandwidth, so long as you check that you still have the latest edition from time to time! The distributions are now too big to fit on one floppy, but you can break them into two pieces like this:


$ dd bs=1024 count=1423 if=skipper-src-1.6.0.tgz of=skipper-src-1.6.0.tgz.A
$ dd bs=1024 skip=1423 if=skipper-src-1.6.0.tgz of=skipper-src-1.6.0.tgz.B

When you want to unpack the files, just stick them together like this:


$ cat skipper-src-1.6.0.tgz.[AB] > skipper-src-1.6.0.tgz

If you are using the binary distribution, remember to say bin instead of src in all those commands! The easiest way to deal with floppy disks is to use the mtools suite, including mcopy and mdel. You usually have to be the administrator to access the floppy drive.

Unpacking

To unpack the distribution, say:


$ tar -zxvf skipper-src-1.6.0.tgz
$ ln -s skipper-src-1.6.0 skipper
$ cd skipper

If you have the binary distribution, remember to say bin instead of src!

Building

The binary distribution is already built. You don't have to do anything to build it.

If you have the source distribution and do not wish to build with the Festival voice synthesiser, just say:


$ make

If you have the source distribution and wish to build with Festival, you should first have downloaded and built Festival in the /opt/voice directory. (See the Installing Festival page for details.) Then to build Skipper, say:


$ make withvoice

There's no autoconf yet, so if you are not using the SuSE Linux distribution you may have to adjust header files and so on.

Installing

Install the programs by using the install script, telling it the keyboard type you are using, and if you want the small examples suitable for a 640 x 480 screen. The possible keyboard types are UK for British, DE for German, NO for Norwegian, ES for Spanish, or US for American. So to install for a British keyboard with a normal 1024 x 768 screen, say:


$ su
# ./install UK

To install for a Spanish keyboard with a 640 x 480 screen, say:


# ./install ES small

Preventing Graphical Login

The graphical display system used on Linux is called X. These days, most Linux system start up with an X login screen. This is not suitable for Skipper systems, because Skipper needs to be set up (or not) differently for each user before X starts.

To prevent X login you must be the administrator. On SuSE or Mandrake Linux, edit the file /etc/inittab and make sure there is a line:


id:3:initdefault:

If that 3 is a 5, change it to 3.

To prevent graphical login on Debian Linux, say:


# rm /etc/default-display-manager
# touch /etc/default-display-manager

When this has been done, the system will display a text login prompt, and after each user has logged in it will display a text terminal command prompt. The user can start X by saying:


$ startx

or alternatively you can edit the file .profile (on SuSE or Debian Linux) or .bash_profile (on Mandrake Linux) in each user's home directory, and add the startx command to the end of the file.

When the users wish to log out after they have logged out of the graphical system and returned to text terminal mode, they can either say:


$ exit

or you can add the command exit to the end of their .profile or .bash_profile file, after the startx command.

Setting Up X

For Skipper users, X has to be set up to take mouse input from Skipper's input processing layer instead of directly from the mouse device. To do this, prepare a special X configuration file for the Skipper users. First, check which version of X you are running by saying:


$ X -version

The first line of output will probably say something like:


XFree86 Version 4.3.0

Which means you are running X version 4. If it says Version 3 something, you are running X version 3.

For version 4, look in the directory /etc/X11. You should find a file called XF86Config-4, or if it not there, the file XF86Config is the second choice. As the administrator, copy this file by saying:


# cd /etc/X11
# cp XF86Config-4 XF86Skipper

or:


# cd /etc/X11
# cp XF86Config XF86Skipper

Now edit XF86Skipper. Look for a Section InputDevice, with a Driver "mouse" in it, like this:


  Driver  	"mouse"
  Option 	"Device"  	"/dev/psaux"
  Option 	"Protocol" 	"PS/2"

The psaux may read mouse or pointer0 instead, and the PS/2 may read IMPS/2 instead. Change the "Device" to "/dev/skipper", and make sure the "Protocol" is "PS/2" , like this:


  Driver  	"mouse"
  Option 	"Device"  	"/dev/skipper"
  Option 	"Protocol" 	"PS/2"

If you are running X version 3, the file you need to copy will be in the directory /etc, and it will be called XF86Config. Copy it to and in the XFSkipper, like this:


# cd /etc
# cp XF86Config XF86Skipper

Then edit XF86Skipper, find the line:


Device          "/dev/psaux"

and change it to read:


Device          "/dev/skipper"

Setting Up Skipper Users

The window manager is the part of X which provides the look and feel of the desktop. For Skipper users, a minimal one called ctwm is most suitable. You need to provide each Skipper user with an X configuration file to start ctwm, a ctwm configuration file that is designed to work with Skipper, and an initial Skipper input layer configuration file that just takes the usual mouse input and forwards it to X. The easiest way to do this is to log on as each Skipper user, and then without starting X, just say:


$ skipuser

You only need to do this once for each Skipper user, and later you can change the Skipper configuration files to something more suitable for each user's needs.

Starting Skipper Users

Once skipuser has been run, you can start the Skipper input processing layer, X and the Skipper onscreen Furniture by saying: and X


$ skiprun

instead of


$ startx

which is the usual command for users who do not need Skipper. Like startx, you can put skiprun in the user's .profile or .bash_profile, so that Skipper and X automatically start whenever the user logs on.

Setting Automatic Login

Where the computer is only going to be used by one Skipper user (which is the best way), it makes sense for the user to be automatically logged on, and Skipper and X to automatically start, whenever the computer is turned on. This is particularly useful if the user can't access the keyboard to log themselves on. Start by adding the skiprun command to the user's .profile or .bash_profile, as described above. Then, as the administrator, edit the file /etc/inittab.

Find the line:


1:2345:respawn:/sbin/mingetty --noclear tty1

and change it to:


1:2345:respawn:su - bilbo

where bilbo is the login name of the Skipper user. Remember - with free software and second hand PCs, providing everyone who needs one with a dedicated computer need not cost money. Each user can then have exactly the input devices they need plugged in all the time and you aren't endlessly plugging and unplugging - which can lead to hardware damage as well as being inconvenient. Another very good reason is that to make progress with computers, people always need time to play and experiment. Sharing computers, putting them in an isolated room, or - even worse - locking them away all tend to stop people exploring playfully.

________________

Last Contents Next

Copyright Alan G. Carter 1998 - 2003
Skipper is provided under the terms of the GNU General Public Licence.
Skipper is hosted by SourceForge.net