The Aleph ARMLinux CD

If you have bought this book as part of our Aleph ARMLinux distribution then be aware that this follows the hallowed GNU/Linux principle of releasing early and often. The distribution is not yet finely tuned to the needs of various embedded devices. It has parts that are specific to small ARM devices, and parts which are generic, but assume a desktop environment. The specific part contains this document, kernels, utiltites and RAMdisks suitable for the devices covered in the book, pre-compiled x86/ARM toolchains, and current kernel source and ARM patches. The generic part form the bulk of the distribution and is essentially the standard Debian ARM distribution, containing a huge array of packages and all the corresponding sources. These are very useful, providing an enormous library of things that you can run on your ARM hardware, but the Debian installer is not yet set up to install to embedded systems. You need to make your own RAMdisks from the parts available to use these binaries. There are several projects underway to make this process easier, including CML2+OS from http://www.emdebian.org/ which is included. Future releases will have significant improvements in this area.

Have fun!

Introduction

The fundamental requirement for a GNU/Linux system is a kernel and a filing system for it to execute things from.

The kernel is an autonomous piece of code that doesn't need any other files or libraries to get started, although without a root filing system it will simply stop after initialising the system as it no files to operate on.

The filing system can be loaded from a range of different hardware devices (hard disk, RAM, ROM, CD and NFS mount) and must be in a format that the kernel understands. For embedded systems it is often a RAMdisk. The kernel and RAMdisk both need to be loaded to correct places in memory and the kernel executed. This can be done in various ways, typically by loading over a serial connection or from local flash RAM.

In order to be able to load anything from anywhere some kind of bootloader must be present on the target hardware which knows how to load files and execute them. This can be installed in a physical fashion by inserting a pre-programmed ROM/EEPROM or flash chip, but is more usually installed using a JTAG port, which allows instructions to be executed from an external input, and thus an initial program loaded.

As there are so many possible boot scenarios we cannot describe them all in detail. We will describe only the most common (which are the most useful for typical situations) but also make the principles clear so you can do something more exotic if you need to.

Background

The LART is part of a project at the Technical University of Delft to do wearable computer research. The first aspect of this was building a suitable platform as nothing with the right combination of low-power, high-performance and low cost existed at the time. The result is offically the 'Linux Advanced Radio Terminal' but a look at the Canonical Abbreviation/Acronym List suggests this may be a contrived acronym.

Part of the design philosophy was that it could be built without expensive facilities and it was easy to add bits of hardware for your own purposes. This combined with its power/performance ratio makes it an excellent development tool. In practice buying the parts to make them yourself is a time-consuming and difficult process, so Aleph One and Remote12 Systems have made it available as an assembled tested development kit. We hope this document will get you going in LART/ARMLinux development quickly and reasonably painlessly.

Assabet: Background

The Assabet is an SA-1110 evaluation board which may be repackaged as a PDA. Notable features include:

• The availability of programming utilities like the JTAG Programming Software V0.3 (for Windows) and Jflash-Linux (for Linux), and the bootloader Angelboot.

• Neponset - a SA-1111 Development module with many additional interfaces.

• Use of the 2.4 kernel series with support for the Assabet and Neponset via a patch chain.

• The capacity to run MicroWindows although a backlight power source needs to be added on 'build phase 4' or earlier boards.

There is also support for Compact Flash on the Assabet and on PCMCIA support for the Neponset. In addition, the Socket LP-E CF + Card is now operative as is the IBM Microdrive.

Hardware Setup

Note: The behaviour of the hardware, bootloader and kernel can vary because of the presence of Neponset - the Microprocessor Development Module. Readers who intend to use Neponset with Assabet should therefore refer to the section called Install Neponset.

Preparing the Board

• Carefully remove the Li-ion battery and LCD/touchscreen by releasing the fasteners on the board receptacles.

 

Top view of Assabet board

 

Install Angel

On Assabet (and Neponset), the bootloader can be installed by physically inserting the pre-programmed flash chips supplied with the kit.

• Determine whether the board has a WindowsCE bootloader pre-installed by opening the StrataFlash sockets and examining the labels on each memory component. For precise details of the process of manipulating memories, refer to The Intel StrongARM SA-1110 Microprocessor Development Board Users' Guide section 2.3. (See the section called Useful Resources for the appropriate URL).

• Remove all power from the board and remove the jumper from the master power clip if it is installed (this disconnects the battery power). Open Socket E11 (StrataFlash) by sliding the middle panel away from the notch before lifting the doors. Socket E12 can also be opened in a similar way. (E12 is directly opposite to E11 on the other side of the board).

• The WindowsCE parts have a label which is similar to "WinCE E-Boot V3.0 L". Remove these parts with the suction part selector (similar to a pen supplied within a tube) and replace them with the parts which are labelled "Angel DB1110B 207D L".

Power and Serial Connections

• Power, JTAG, RS232 and POTS connections are made through base station - a 14-pin header. Connect the serial cable to your development workstation which - on a SA-1110 - means that the header should be attached to serial port 1.

• LED D4 should light up when the power is applied. Angel will then activate LED D8. After interrupt initialisation, Angel will strobe LED D9 four times. Supplementary information on the reset sequence can be obtained from DB1110_diag.txt which is bundled with Angel (http://developer.intel.com/design/strong/swsup/SA1110AngelKit.htm).

Install Neponset

• It is possible to attach the SA-1111 Development Module by using either of the 140-pin connectors which are found on the Assabet.

• Make a record of the switchpack SW2 settings because these affect selection, bus speed and other important parameters. A comprehensive explanation of switch meanings can be found in the readme.txt which is included in the Angel distribution although a summary of switch meanings is provided in the following table.

Table 4-1. Switch Options for Switchpack SW2

switch	off	on
SW2-1	reserved	reserved
SW2-2	reserved	reserved
SW2-3	debug port is UART3	debug port is UART1b (on Neponset)
SW2-4	bus speed is 103MHz	bus speed is 51MHz (clamped to 51MHz if PLL==147MHz)
SW2-5	flash device page mode enabled	flash device page mode disabled
SW2-6	Angel fast boot mode	Angel debug mode (see DB1110_diag.txt)
SW2-7	PLL==206MHz	PLL==147MHz
SW2-8	boot from flash on Neponset	boot from flash on Assabet

Note: All switches can be left in the off position except for the SW2-8 which can be left on.

Fixing Neponset

Some copies of Neponset may contain a bug involving the on-board Philips UDA1341 audio codec. The bug involves the L3 MODE signal coming from the SA-1111 which is available from PWM1 - the dual-function pin. Phase 4 Neponset boards incorrectly route this signal to PWMO which prevents any configuration of the codec from software. However, this problem may be solved by unsoldering the jumper wire at J7 and moving it immediately adjacent to J4.

base 0xc0008000
entry 0xc0008000
r0 0x00000000
r1 0x00000019
device /dev/ttyS1       
options 9600 8N1
baud 115200
otherfile ramdisk_img.gz
otherbase 0xc0800000
#exec minicom assabet

Introduction: Background

The Linux7k project is an effort to port the widely used Linux kernel to the Psion Series 5 and later pocket computers.

So far the team has ported the Linux 2.2.1 Kernel to the Series 5 and Geofox One and created Arlo and several initial RAMdisks (initrd) for the project. Work then stalled for a while as Psion were slow to release hardware information for later machines, but is now progressing again with the 2.4.1 kernel now booting on a Series 5mx.

Blob

The Boot Loader Object (Blob) allows the user to:

• initialise the hardware (CPU speed, memory, interrupts, RS232);

• boot a Linux kernel and provide that kernel with a RAMdisk;

• download a kernel or a RAMdisk to the target device;

• write a freshly downloaded kernel or RAMdisk to the flash memory (see below for limitations).

Blob was originally written for the LART by Jan-Derk Bakker and Erik Mouw, but has also been modified to work on the Assabet by Jeff Sutherland and Chester and on the Intel Brutus SA-1100 evaluation platform by Erik Mouw, and on the PLEB Linux board by Adam Wiggins. You need to compile the correct version for the hardware you want to use it with as the hardware varies in important ways (processor, memory type and layout, debug serial port).

Consider yourself LARTed!
Running from internal Flash.
Starting the memory tester...
Zeroing memory...0xD0000000
Zeroing done. Testing for aliases...
Loading kernel from flash ....... done
Loading ramdisk from flash ............... done

Blob version 1.0.8-pre2, 
Copyright (C) 1999 2000 Jan-Derk Bakker and Erik Mouw
Copyright (C) 2000 Johan Pouwelse
Blob comes with ABSOLUTELY NO WARRANTY; read the GNU GPL for details.
This is free software, and you are welcome to redistribute it
under certain conditions; read the GNU GPL for details.

Autoboot in progress, press Enter to stop ...

Starting kernel ...

Uncompressing Linux...done.
Now booting the kernel
...

Autoboot aborted
Type "help" to get a list of commands
blob>

 Target board                 lart
 C compiler                   arm-linux-gcc
 C falgs                      -O2 -I/usr/src/arm-linux/linux/include -Wall -nostdinc -mcpu=strongarm110 -mapcs-32 -fomit-frame-pointer -fPIC
 Linker Flags                 -static -nostdlib
 Objcopy tool                 arm-linux-objcopy
 Objcopy flags                -O binary -R .note -R .comment -S
 run-time debug information   no

Patching

This is the process of modifying a set of files with a 'patch' file containing a list of differences between two sets of files. This is how changes to source code are normally distributed. Patch files are generated by the diff command. You need at least version 2.5 of patch for patching the kernel. Here we use patching the binutils source as an example.

A patch is normally downloaded as a gzipped patch file (denoted by it ending in .gz). If so, gunzip it:

gunzip binutils-patch.gz

You can now patch binutils. Go into your unpacked binutils source directory, and run patch with your downloaded patch file, with argument -p1:

cd /usr/src/binutils-version
patch -p1 < binutils-patch

If you aren't sure exactly how a patch should be applied then the --dry-run option is very useful. Adding this means that patch will do its work, giving all the usual output but no changes are made to the files. To check out the effects of the above patch command, for example, you do:

patch -p1 --dry-run < binutils-patch

You should see a plethora of messages like:

Hunk #1 succeeded at 112

After patching has finished, you can check whether things have worked by searching for files ending in .rej (rejected patches):

% find . -name '*.rej'

In theory, there should be none of these files; all of the patches should have succeeded. However, if there are one or two failed files, it doesn't necessarily mean it won't build especially if the failed files are documentation or have names like README or endings like .info or .texi.

If you have several of these files, however, it could indicate something seriously wrong, and that it won't build. Check that the version of the source the patch is intended to be applied to matches the version of code you have. Also sometimes patches are 'reversed' - i.e. they have the original and modified source version the wrong way round in the diff command that generated the patches. Patch is smart and if it looks like this is the case it will offer to do them all 'backwards' for you.

The -p1 in the above example refers to how many directory '/' separators patch should strip off the filenames before patching. This is to allow for differences in the depth of nesting between the source tree the patch was created on and the one it is being applied to. Normally you will find that -p1 or -p0 is correct. If a patch doesn't seem to work then looking at the depth of filename nesting in it and using a different -p option is the first thing to try.

Once you understand how this works you can save some commands by combining the unzipping and patching commands into one line like this:

zcat binutils-patch.gz | patch -p1 

or, if the patch you have is bzipped instead of gzipped, then do:

bzcat binutils-patch.bz2 | patch -p1

Toolchain overview

The toolchain actually consists of a number of components. The main one is the compiler itself gcc, which can be native to the host or a cross-compiler. This is supported by binutils, a set of tools for manipulating binaries. These components are all you need for compiling the kernel, but almost anything else you compile also needs the C-library glibc. As you will realise if you think about it for a moment, compiling the compiler poses a bootstrapping problem, which is the main reason why generating a toolset is not a simple exercise.

This chapter contains information on how the toolchain fits together and how to build it. However, for most developers it is not necessary to actually do this. Building the toolchain is not a trivial exercise and for most common situations pre-built toolchains already exist. Unless you need to build your own because you have an unusual situation not catered for by the pre-built ones, or you want to do it anyway to gain a deeper understanding, then we strongly recommend simply installing and using a suitable ready-made toolchain.

Logging in

Afte installing GNU/Linux, either on the desktop, or on a target device and booting up, you should be met by the following:

armlinux login:

If this is the first time that you have logged in, then you will have to initially log in as the root user which is accomplished by typing root before pressing Return.

You will then see that the prompt is represented by a hash sign (#) which means that you are looking at the root prompt. In contrast, the prompt for non-root users is usually represented by a dollar sign.

[root@armlinux /root]#

or for the non-root user:

[paulw@armlinux paulw]$

Although it is possible to work with your new Linux system at this stage, we would advise you to immediately refer to the section called Accounts for the specifics of creating a user account.

Permissions

Although you should now have some appreciation of the Linux filesystem it is important to realise that Linux can be used in a multi-user or networked environment. It is therefore sensible to learn about the various types of role and permission which can be associated with a file so that the file owner can decide exactly who has access to files.

Any user may consequently fit into any one of three roles which include:

1. the ownership role

2. the group role

3. the other role

The owner of a file can change file permissions at will. Moreover, a file may be associated with a group which is useful in a collaborative project context in which file access can be restricted to group members. Finally, the other role applies to a user who is neither the owner of the file nor the member of the group which is associated with the file.

In a similar vein, for every Linux file, three types of permission can be applied to each of the three roles. These permission switches are as follows

1. R (Read): enables the user to read files, or (for a directory) to list files on the system

2. W (Write): allows for the alteration or deletion of files, or (for a directory) deleting, adding and renameing of files

3. Execute (Execute): allows for the execution of a file where it is an executable or for changing directories.

In order to clarify matters, this information can be most effectively presented in tabular form. Note that a dash in the line of text denotes the absence of a permission whilst r, w or e indicates that one of the three types of switch is activated.

To illustrate all of the above, consider a situation where we want to know the permissions which apply to a particular file. After invoking the ls -l <filename> command, our hypothetical output might look some thing like the following:

—rw—r——r—— 1 paul paul 388 June 10 09:30 notes.txt

Reading across the listing from left to right, the first character position show the file's filetype which in this example is a normal file. Other possibilities include:

1. d for a directory

2. c for a device

3. b for a socket

4. s for a pipe

The remaining nine bits apply to the user, group and other roles respectively with three bits being alotted to each of the roles. Thus our hypothetical output shows that the user has read and write permissions whilst the group and other roles have read permission only. Note also that a dash denotes the absence of a permission.

If however, it becomes necessary to change file permissions, this can be accomplished by:

1. setting file permissions with octal numbers

2. setting file permissions with a combination of symbols

3. setting the setuid, setgid and sticky bits

To alter a file's permissions with numbers, Linux uses four numbers which determine permission types including:

1. 4: read permissions

2. 2: write permissions

3. 1: execute permissions

4. 0: no permissions

Therefore, to alter the permissions status of our hypothetical file so that the group has read and write permissions, we would add 4 (read permission) and 2 (write permission) together before issuing the following command:

chmod 664 notes.txt

The following table summarises the situation thus far:

In a situation where it is necessary to set permissions one role and one permission at a time, the symbolic permission notation can be used. In order to make use of this facility, the user need only remember that permissions may be granted or denied by using the following three symbols in conjunction with the read, write and execute switches that we have already encountered:

1. u signifies the user/owner role

2. g represents the group role

3. o signifies the other role

Therefore, in order to allocate a group read and write permissions for the file notes.txt using symbolic notation, the user could enter the following command:

chmod g+rw notes.txt

Because many permutations are possible when using this method, the table below gives some indication of how permissions may be alterred. Note that "+" means that permission is granted whilst "-" shows that permission is denied.

Of course, there is much more that could be said about permissions but for further details on the specifics of topics like sticky bits, shadow passwords and filesystem maintenance, consult the relevant man page. Refer to the section called Help! for advice on using man.

The important thing to remember is that if you are having a problem with missing files or some other mysterious error, it is very often due to incorrect permissions somewhere in the system. Always remember to check.

Alternative Filesystems

ARMLinux can similarly make use of a range of filesystems in addition to its own Second Extended filesystem (ext2fs).

Under Linux the user will however have to mount a device before it can be accessed and used. This is done with the mount command but you will initially have to edit the /etc/fstab file as the root user in order to avail of this facility. This file is also used to specify which filesystems should be mounted automatically at boot time. To edit this file - which is just a text file - use Vim to open the file with the following command:

vim /etc/fstab

If your file doesn't include a line like the following:

/dev/hda1     /adfs     adfs       noauto,user   0   0

then you should add one in order to be able to read your RISC OS drive from ARMLinux. Note that if your RISC OS drive is RISC OS 4 with long filenames then this is not supported at the time of writing so you can skip this section. The format of this file is explained in man fstab.Save and quit by depressing the ESC key, waiting for a beep and then typing :wq /etc/fstab. Where this line is missing, type it in from scratch noting that there should be no spaces between noauto any punctuation and user. if you want this drive to be automatically mounted on boot then change the final 0 to a 1. You will then need to make a mount directory.

mkdir /adfs

Congratulations, you are now in a position to mount your RISC OS filesystem with the following command:

mount /adfs

You can now access your files from the /adfs directory.

Debian Package Management

In order to take full advantage of Debian, you need to learn a little about the package management system which underpins it. Debian packages everything in .DEB files. These packages are controlled by a program called dpkg, or from a friendlier front-end such as dselect or apt. The system is extremely powerful; every file on your system is known about by the system and it takes care of a great deal of complexity when installing, removing or upgrading software. It knows about the interdependencies between pieces of software and if you ask to install something it will also get the other things it needs. It knows which files are configuration files and will not overwrite them when upgrading a package. It can also upgrade a running system without breaking things and lets you find out what is on your system. To a large extent the package management system is what makes Debian special and once you understand it you will find it a marvellous facility.

dselect is the interface that you will first use. It was designed when Debian had 500 rather than 5000 packages and suffers a bit because of this, but it is quite straightforward to use and a good introduction to the package system. Later you will just use apt to install new software. Once apt has been taught where to get software (usually off the CD and off the net) you can say things like apt-get install <software> and it will go away and get it for you, then install it, install anything else necessary and configure them all, often without asking you any further questions apart from telling you which CD to insert or if the download size is OK.

It is important to understand however that if you want to install software that is not in the Debian archive then everything is not taken care of for you and you will have to understand what is going on and do some work yourself. For example, if obtaining a package from a distribution which is meant for x86-based PCs, you will have to compile it from source as the binary versions supplied will not work on an ARM-based machine. Such a procedure is outside this manual's scope but - assuming that you want to use a package which is on the ARMLinux CD or in the huge Debian archive - read on!

dpkg can for example be used to install a package by using the i (or --install) switch.

dpkg -i /cdrom/debian/dists/potato/main/binary-arm/utils/mc<TAB>

Note that the <TAB> above means press the TAB key, not type in those letters. This uses the shell's filename expansion facility to fill in the end of the filename. It's a marvellous facility. If it beeps then there is more than one possible answer - press <TAB> again to see the list. It even works on commands.

However, it is standard practice to use apt instead to save typing long pathnames, like this:

apt-get install mc

Here apt knows where to look for packages, finds mc and then uses dpkg to actually do the installation, but saves you worrying about the actual location of the package.

What you have just done is to use dpkg to install Midnight Commander (mc) - a visual shell which does not need X Windows - on your system. Conversely, you may choose to delete or uninstall a package which can be accomplished by using the -r (or --remove) switch. The following command consequently removes mc.

dpkg -r mc

Don't be too hasty however. MC is an excellent way of navigating the filesystem when used in conjunction with the shell. So why not learn a bit about it before using dpkg's -r switch?

Congratulations, you've managed to mount your filesystem and have a look at some files. Before removing your CD-ROM, you will need to use the umount command which can either be used to unmount the current filesystem or a specific directory. But please be careful with your typing and key in umount rather than unmount. If it tells you that the filesystem is busy then your current directory is probably in the mounted filesystem. You need to change directory elsewhere before you can umount.

umount /dev/cdrom

or

umount /cdrom

In order to find out about other filesystem types and the specifics of the mount and umount commands, you can take advantage of the range of commands and applications which are briefly described in the section called Help!.

Editing with ae

ae can be activated by typing:

1. ae at the shell prompt

2. ae <filename> where you wish to work on a pre-existing file.

Two screens will then appear: an editing screen into which you can type and a help screen which provides a selection of useful commands. If you have used ae before, you can toggle the help screen on and off by typing C-x+C-h.

ae operates, like many Linux editors, via a series of control characters. C-x therefore instructs the user to depress the C (Ctrl) and x keys at the same time.

Typing a non-control character consequently has the the effect of placing the character which you have typed at the cursor. When you have finished your work, type C-x+C-s to save the current file to disc or C-x+C-c to save and exit.

ae is therefore very easy to use although its simplicity conceals a number of sophisticated features which include:

• The ability to work with multiple buffers by using a root buffer and a series of virtual folds which correspond to the files to be edited.

• User configurable key bindings.

For further information on ae, visit the editor's home page at http://www.interalpha.net/customer/nyangau/ae/platform.htm/.

Editing with Jed

Jed can be driven from a series of menus or with a combination of shortcuts. Jed is a modeless editor which means that you do not have to be in different modes to edit or insert text. Jed is also very easy to use and offers a range of facilities which include:

• Colour syntax highlighting which can be useful for debugging your documents.

• Special features which are activated on the basis of filetype.

• Extensibility via the C-like S language.

Jed can be invoked by typing:

1. jed at the shell prompt.

2. jed <filename> at the shell prompt where you wish to edit a specific file.

3. C-x+C-f in the mini-buffer. If you choose this command, you will see Enter Filename in the mini-buffer.

In addition to commands which begin with the Ctrl character, Jed also uses the ESC key for a number of commands. ESCn therefore means that you should press ESC before releasing it and pressing key n.

Assuming that you are working on the file readme.txt, type jed <readme.txt> at the shell prompt. You can then insert and edit text and move around the document by using the arrow keys. When you have finished the session, type C-x+C-s to save your document to disc. You can then exit from Jed by typing C-x+C-c.

The Jed screen contains a number of features which may be unfamiliar to you. These are:

1. A Menu Bar across the top of the screen.

2. A Mode Line containing useful information.

3. A Mini-Buffer which is below the Mode Line.

The Menu Bar contains the menu options which you can use as an alternative to the keyboard shortcuts. To activate the Menu Bar, press the F10 key and select the menu which you require by using the arrow keys. The menu options should be self-explanatory with the possible exception of the Buffers option. A buffer is essentially a temporary workspace inside which you perform your work until you save any changes which are then written to the file.

In contrast, the Mode Line provides information about the document which you are currently working on. If you can see two asterisks (**) on the extreme left of the mode line, this is an indication that you have made changes to a document which has not been saved to disc. The mode line also tells you where you are in the document in terms of a line number as well as giving an indication of the current editing mode. Editing modes essentially help you to efficiently edit your documents by activating features like syntax colouring and specific formatting styles.

Finally, the Mini-Buffer is located below the Mode Line and echoes commands back to the user. Try keying in C-x+C-v to find an alternative file and you should get the idea but remember to hit the Return button after you have finished typing.

You should now know enough about Jed to perform simple editing. Jed also comes with its own form of on-line Help which can be activated by pressing C-h+C-h. A number of useful WWW resources are also available so point your browser to http://space.mit.edu/%7Edavis/doc/jed.html/ and http://www.geocities.com/mmarko.geo/jed/ Finally, take a look at Appendix A which lists some useful Jed commands. Please be aware however that the table uses commands which assume that Jed is using Emacs keybindings.

Editing with Vim

Vim is another editor which you can learn how to use. Vim also comes with an excellent tutorial which you can avail of by typing the following command at the prompt:

vimtutor

You can also save a bit of typing by using the filename completion facilities of the Bash shell. Simply type vim/usr/doc/vim and then press <TAB> so the shell fills in the remainder of the directory name, then you can enter the tutor and press <TAB> again to get the rest.

The tutorial will open from within Vim and you will then be able to learn enough to perform most of your editing activities. But just in case you want to familiarise yourself with Vim without recourse to the tutorial, what follows is an introduction to the editor's capabilities.

Vim is a modal editor which means that there are different modes for performing different tasks. Vim consequently operates in command mode when commands are being issued or in insert mode when text is entered on the screen. Although the method of issuing commands with a key press may seem counter-intuitive and positively archaic in comparison with more conventional point-and-click methods, it is actually a very efficient method of working and should be perservered with if at all possible.

In order to become conversant with Vim, we therefore suggest that you learn a few new commands per day and practice! Appendix B lists some of the common commands that you are likely to need.

For more information on Vim, consult its home page http://www.vim.org/ or check out one of the many books which are available on Vi - Vim's predecessor.

Overview

After having learnt something about text editing, it seems sensible to provide a brief introduction to the subject of printing under Linux. Although word processors are available for Linux, you will still need to learn something about traditional UNIX tools like the lpr printer daemon and the power of PostScript - a language which is used to describe page layouts.

Although using the command line to print documents is not the easiest way to produce a hard copy of your documents, this approach has considerable advantages over the use of a conventional word processor like OpenOffice or Abiword because the user creates plain text files which are portable across platforms. Moreover, although BSD-derived packages like lpr are more difficult to learn about than GUI based printer management tools, the Berkeley UNIX (BSD) approach gives the user a fine-grained control over the printer.

Planning Ahead

Because of the complexity of the printer configuration process, we shall not discuss the topic in any detail. We would however, advise any user to do the following:

• Obtain your printer's technical specifications which will usually be available from the manufacturer's web site.

• Read through all relevant document - both HOWTOs and man pages - before doing anything.

• Check that your printer is working from within RISC OS before attempting to configure it for Linux.

• Do a test print using the lptest utility.

• Edit the /etc/printcap file where necessary.

• Ensure that Ghostscript works both with the X Windows System and through the shell.

• Use an application like magicfilter which helps you to configure your printer.

A Simple Example

Assuming that you have successfully configured your printer, printing through the shell generally involves two stages:

1. the user creates a document with an editor like Vim or Emacs which may be interlaced with formatting instructions. Such formatting instructions are typically specific to either TeX or Groff.

   A number of filters may also be applied to the file if the user intends to do things like formatting line lengths. Other examples of typical filters include Enscript and a range of magic filters which convert to PostScript on the basis of a file's initial filetype.

2. The file is then sent to the printer by using lpr, Enscript or Ghostscript.

With regard to point two, lpr could be used to print a plain text file formatted according to personal preference. If a more complex document has been generated with either TeX or Groff which includes floating objects like tables and graphs, then one possible alternative would be to convert the file to PostScript as a prelude to printing to a PostScript printer. Groff and TeX files can for example both be converted to PostScript using Dvips - a DVI to PostScript driver. Alternatively, users without a PostScript printer can also take advantage of Ghostscript- a program which can be used as a PostScript viewer, file converter and printer driver.

So in order to make the process more meaningful, let's use a fictitious document to illustrate the process in action. Suppose we have written a letter to a friend using LaTeX - the TeX macro set. For those who are unfamiliar with LaTeX, a sample file together with formatting instructions, is listed below:

\documentclass[a4 paper,12pt]{letter}
\name{Mr A. L. User}
\address{ARMLinux Users' Group\\
         Torvald's Road\\
         Linuxland}
\signature{ARMLinux User}
\date{June 12, 2000}
 \begin{document}
  \begin{letter}{Aleph One\\
                 The Old Courthouse\\
                 Bottisham\\
                 Cambridge}
\opening{Dear Aleph One}
I am writing to say how pleased I am with Aleph ARMLinux. Yes it
is very different from RISC OS but it's worth perservering with.
\closing{Yours sincerely}
  \end{letter}
 \end{document}

You would of course create this document with your favourite editor before saving it as letter.tex. Don't forget the suffix which indicates that the file is a LaTeX source file. letter.tex would then be processed by using the latex command to create a Device-Independent or DVI file - letter.dvi - with the dvi suffix.

latex letter

You are now ready to convert letter.dvi to PostScript by using Dvips. If you are successful, you will be left with letter.ps.

dvips -o letter.ps letter.dvi

And finally, print using either lpr Enscript or Ghostscript.

lpr letter

You can also print the raw LaTeX file with the pr command although this would not be particularly appropriate in a situation where one wished to process the formatting instructions as opposed to seeing them on the page.

pr letter

Resources

There is a wealth of information on printing and related utilities under Linux.

But your first port of call should be the:

Aleph ARMLinux CD

The printing HOWTOs are available on the CD in the Docs.Html-Howto. The relevant man pages are, as always, ever useful.

PostScript

General PostScript and Ghostscript resources are available from http://www.geocities.com/SiliconValley/5682/postscript.html/. PostScript-specific information can also be found on Adobe's web site at http://www.adobe.com/print/postscript/.

Ghostscript

Ghostscript's Home Page can be found at http://www.cs.wisc.edu/~ghost/ whilst the Ghostscript Manual is available from http://www.pdflib.com/gsmanual/index.html/.

TeX

Point your browser to http://www.tug.org/in order to learn about printing TeX-related files. Similarly, http://www.sunsite.ubc.ca/Resources/Graphics/dvips/ is the link to a comprehensive manual on the DVI to PostScript driver.

The Client-Server Model

Although it is possible to work entirely through the shell, modern Linux distributions allow the user to work through a GUI and ARMLinux is no exception! Indeed, if your preferred method of working is to point-and-click, then you will feel very much at home with this distribution.

However, a brief explanation of the X Windows System is in order so that you can take advantage of the power which is at your fingertips.

The X Windows System or "X" as it is more commonly known is based on a client-server way of doing things in which the server program determines access to your graphics hardware. The client, in contrast, is simply an applications program like xpdf or one of the many types of window manager. Although X clients usually run locally, remote connection to a client is possible and can be very useful in situations where you need to access an important file on another computer. RISC OS users will no doubt be interested to know that it is even possible to start up an X-Server under RISC OS itself if you take advantage of an application like !X (http://gnome.co.uk/) or !X-Server (http://kyllikki.fluff.org/software/x/).

Window Managers and X Applications

There are many window mangers available for GNU/Linux so for reasons of brevity, we will confine ourselves to a description of Window Maker's basic features because this is the default desktop for Debian.

X Windows can be activated with the startx command. . To start Window Maker simply press the right mouse button and click on WindowManagers and then on the wmaker sub-menu.

When you fire up Window Maker, you will notice a number of distinctive features which include:

• The Window Maker Workspace from which you can launch applications by clicking with the right mouse button before choosing the application which you require.

• An Applications Dock on the right hand side of your screen which is used to activate applications which you use regularly.

• A series of Miniwindows at the bottom of your screen. The Miniwindow is made up of an icon and a title and appears when you temporarily close an application window.

To end your Window Maker session, click on the workspace with your right mouse button and select WindowManagers and Exit or Exit Session. If you choose Exit Session, all applications will be closed.

For further information, take a look at the official Window Maker web site (http://www.windowmaker.org/) which has links to mailing lists, user guides and sample configuration files where you wish to customise your setup.

Congratulations, you can now use all of the X applications which are on the CD but you will need to make a few changes to the default configuration before X Windows is fully usable.

• Add the line *input: true to the .X defaults file which will be in your home directory. This should solve the problem of being unable to type into dialogue boxes under X.

• You will need to install pcnfsd if you wish to use the Network Filing System (NFS) for sharing files over a network to a RISC OS machine or a PC. It is not needed for UNIX-UNIX sharing. Supplementary information on this topic can be found on the CD in Docs/html-howto. The Networking HOWTO is also required reading.

So we've taken a look at Window Maker itself and in order to help you to use this window manager, what follows is a description of some of the core X applications which you may find useful. If you decide to install an application, follow the instructions in the section called Alternative Filesystems which tell you how to install a package by using dpkg.

X Applications

xterm

A window containing the shell. xterm allows the user to cut-and-paste and to scroll. To close the xterm window, type exit at the prompt, press Ctrl+D or select Close with your mouse by clicking on the button on the extreme left of the fvwm titlebar.

xpdf

A viewer for Portable Document Format (PDF) files. xpdf has been ported to RISC OS by Leo Smiers.

xfig

A program which is ideal for the production of complex drawings which can be saved in a variety of formats including PostScript and LaTeX.

xv

Allows the user to view and convert images in a variety of formats including GIF, JPEG and TIFF. Facilities are also available for image cropping, rotation, gamma correction and for the capturing of screenshots.

games

You can even have some fun with Linux by playing games like xmahjonng, xgalaga or xgammon. If you want to have fun without using X, then why not check out bsd-games - a collection of classic non-X games including battleshar, gomoku and phantasia?

Connecting to the Net with PPP

In order to get on-line you will need to set up your dial-up connection so we'll help you to do this by taking a look at the Point-to-Point Protocol (PPP).

This section has consequently been written for those who wish to gain a general sense of what is involved before consulting alternative resources. Newbies should therefore read this section before referring to the PPP-HOWTO which is on the CD in Docs.Html-Howto. Useful information can also be gained from the README.linux file in /usr/doc/ppp-2.2.0f-2, the pppd man pages and from the PPP FAQ (http://cs.uni-bonn.de/ppp/faq.html/). Users who wish to establish their own PPP server or to set up a Wide Area Network (WAN) will also find these resources helpful. Moreover, those who wish to use the Debian distribution of ARMLinux should refer to install.en.txt on the CD in Debian.docs for an explanation of pppconfig. Debian users will also find the wvdial dialler to be invaluable.

At present, you may set up your internet connection by:

1. Writing your own scripts.

2. Using the pppsetup program.

PPPsetup

The pppsetup program is an effective alternative for those who feel intimidated by the process of hand-crafting an internet connection. PPPsetup is available from http://members.nbci.com/chrissawer/ and was orginally derived from PPP version 2.3.5. Newbies should consequently note that the chat and chat.8 files should be placed in /usr/sbin and /usr/man/man8 respectively. The program also needs a current version of chat which can be downloaded from ftp://cs.anu.edu/pub/software/ppp/.

Debian Guides

Debian Developers' Reference

http://www.debian.org/doc/packaging-manuals/developers-reference/

Debian FAQ-O-Matic

http://www.debian.org/cgi-bin/fom/

Debian GNU/Linux: Guide to Installation and Usage

http://www.newriders.com/debian/html/noframes/

Debian New Maintainers' Guide

http://www.debian.org/doc/maint-guide/

Debian Packaging Manual

http://www.debian.org/doc/packaging-manuals/packaging.html/

Debian Policy Manual

http://www.debian.org/doc/debian-policy/

dselect Documentation for Beginners

ftp://ftp.debian.org/dists/stable/main/disks-*/current/doc/dselect-beginner.*/

Debian Mailing Lists

There are a number of mailing lists for this Linux distribution but <debian-user@lists.debian.org> is a good place to direct your questions. To subscribe, type "subscribe" in the subject line and mail to <debian-user-REQUEST@lists.debian.org>

In order to find out about other mailing lists, take a look at mailing-lists/txt which is on the Aleph One CD in the Doc directory.

You can also refer to the section called Mailing Lists for details of ARM-specific lists.

Debian Help

You can similarly learn how to solve Debian-specific problems by pointing your browser to http://www.debianhelp.org/.

linux-arm

<linux-arm@lists.arm.linux.org.uk>. This is the main ARMLinux list which covers ARMLinux topics not specific to and of the other mailing lists. This covers all architectures that ARMLinux is used on (Desktops, PDAs, development boards etc), so much of the discussion is not specifically related to your machine. Users who have ceased to be newbies will find this of interest. To subscribe send "subscribe" (in the body of the message) to <linux-arm-request@lists.arm.linux.org.uk>, or use the web interface at:http://www.arm.linux.org.uk/armlinux/mailinglists.shtml.

linux-arm-kernel

<linux-arm-kernel@lists.arm.linux.org.uk> is for kernel-related discussions, generally of a technical nature. This normally covers the kernel, related tools and new hardware. If you are a Linux beginner you won't understand a word of what goes on here :-) This is the place for those interested in the grubby stuff. To subscribe send "subscribe" (in the body of the message) to <linux-arm-kernel-request@lists.arm.linux.org.uk>.

linux-arm-announce

<linux-arm-announce@lists.arm.linux.org.uk> is a moderated low-traffic list for announcements relevant to ARMLinux. To subscribe send "subscribe" (in the body of the message) to <linux-arm-announce-request@lists.arm.linux.org.uk>.

armlinux-toolchain

<ARMLinux-toolchain@lists.armlinux.org>This list serves mainly as a place for developers to discuss any aspect of the GNU development toolchain on the ARM architecture (including other operating systems). It's also a diagnostic forum to an extent, if you're having problems. http://www.armlinux.org/cgi-bin/mailman/listinfo/armlinux-toolchain and fill in the form. An archive of submissions to this group is also available from http://www.armlinux.org/pipermail/armlinux-toolchain/

ARMLinux-newbie

There is a mailing list specifically for people new to ARMLinux, where you are positively encouraged to ask stupid questions. This is aimed at users as opposed to developers, particularly RISC OS machine users and PDA users ,and is at <ARMLinux-newbie@lists.armlinux.org>. This is not the place to ask about toolchains, the kernel, or any development-type questions. This is the place for installation problems, and questions about software that just crashes or doesn't seem to work right. We recommend that all users join this list so that the community can help each other out and compare notes. An archive of submissions to this group is also available from http://www.armlinux.org/pipermail/armlinux-newbie/.

Debian ARM

If you are using, or working on, the Debian ARM distribution then <debian-arm@lists.debian.org> is the place to talk to other users and developers about any ARM-specific issues. Debian has loads of maiing lists for other aspects of the distribution.

Emdebian

<emdebian-discuss@lists.sourceforge.net> is a project to make Debian work on small embedded systems and PDAs. It supplies a very good Toolchain and experimental software (CML2+OS)to generate small installations and kernels from the huge Debian archve. It needs some more active developers - join this list if you think you can help or are interested in the design process.

Lart

<lart@lart.tudelft.nl> is the place for all tings LARTy. All LART users should be subscribed here. Its the place to get hardware or software help and discuss the possibilities of your LART.

Psion PDAs

<linux-7110@sourceforge.net> is concerned with the Psion 5/5mx/7 port of ARMLinux. This is a list both for developers and users. Information for the 5mx has recently been obtained from Psion so the list has been revitalised with the new porting activity.

StrongARM issues

<sa1100-linux@pa.dec.com> is for those who are interested in StrongARM-specific issues - primarily kernel development.

iPAQ PDAs

The iPAQ has proved a very popular ARM/PDA development platform due to Compaq's support. There is an active community working on distributions and the hardware on this list: <ipaq@handhelds.org>. Handhelds.org also has other lists, not necessarily specifc to ARM.

Books On-Line

A number of commercially available books and sample chapters are also available on-line including:

Learning Debian GNU/Linux

http://www.oreilly.com/catalog/debian/chapter/index.html/

Learning the Vi Editor

http://www.oreilly.com/catalog/vi6/chapter/ch08.html/

The UNIX CD Bookshelf

http://www.oreilly.com/catalog/unixcd/chapter/index.html/