Installing LTSP in Debian

Choosing DHCP and TFTP servers in Debian

Available DHCP servers:

Package Name	Description	Remarks
dhcp3-server	ISC dhcpd v3.0	Supports conditional logic - RECOMMENDED
dhcp	ISC dhcpd v2.0	Works with LTSP but doesn't support conditional logic in config file
udhcpd	very small DHCP server	untested
dnsmasq	small DHCP server and more	works, supports conditional logic, very different syntax

Available TFTP servers:

Package Name	Description	Remarks
atftpd	Advanced TFTP server	Works well with LTSP - RECOMMENDED
tftpd-hpa	HPA's tftp server	Works well with LTSP
tftpd	Internet trivial file transfer protocol server	based on the original BSD tftp server. It doesn't support the blksize or the tsize options, which are required for PXE booting - NOT RECOMMENDED for LTSP
dnsmasq	small TFTP server and more	works with version 2.42 or newer

---

LTSP 5.1

---

Installing LTSP 5.1 in Debian 5 ( Lenny ) with Floppy gPXE and Etherboot Workstations

Due to a recent change in the versions of files contained in Debian's Lenny repository, it is no longer possible to run etherboot workstations with LTSP 5.1. When following the instructions in the below-referenced howto, you must setup a gPXE image booting floppy workstation. None of the recommended etherboot images are usable.

CastAway - 29 May 2009

---

I have just posted a howto on the installation of LTSP 5.1 in Lenny which tells how to setup floppy image booting workstations.

The most interesting aspect of the howto are the directions on how to use gPXE images with a floppy image booting workstation. gPXE images offer the ability of command-line entries at the workstation while the workstation is actually booting. (However, special files, not available with LTSP, are required to accomplish this.) Because gPXE images are so new I have been unable to find any other step-by-step instructions for their use in LTSP and Debian.

The posting can be found at:

http://gardanier.net/2.html

CastAway - 24 April 2009; revised 29 May 2009.

---

LTSP 5.0

---

Solving Installation Problems in LTSP 5 & Debian Etch

first off, please take a look at http://wiki.debian.org/LTSP/Howto

unfortunately, etch is missing some support for things like local devices (ltspfs), though newer versions of ltsp and ltspfs have been backported for etch (see the above howto for how to get backported packages).

if you have any troubles with ltsp5 on debian, please use the debian bug tracking system http://bugs.debian.org/src:ltsp to report issues, and please consider using the reportbug utility to do so (http://packages.debian.org/reportbug).

to keep track of the progress of ltsp in debian, see: http://packages.qa.debian.org/ltsp

VagrantCascadian^? 2007-09-06

---

Installing LTSP 5 with Etherboot Floppy Workstations in Debian 4 Etch

Introduction

If you are not fortunate enough to have workstations with PXE-enabled motherboards which can actually boot with PXE, you cannot setup an LTSP 5 network in Debian 4. And were you to attempt setup of etherboot workstations, they would not work even with known good (LTSP 4) images. At best only one or two workstations would boot. The remainder would not.

This post describes how to install etherboot floppy workstations which boot successfully every time. This post is an extract of the original which contains detailed instructions, examples of modified files, trouble-shooting hints, etc:

Debian 4: How to Install LTSP 5 with Etherboot Floppy Workstations http://www.linuxagora.com/vbforum/showthread.php?t=860

The test network used was comprised of RealTek 8139 network cards and older ati and nvidia graphics adapters. It was the same network described above in my beginner's howto for installing LTSP 4 in Debian 3.

For etherboot to be successful in Debian's LTSP 5, three challenges must be faced. The first and second are met by these instructions. The third remains for someone else to accomplish:

• Prevent server errors while downloading the LTSP linux kernel to the workstation;
• Find etherboot images that will work with the defective linux kernel installed by LTSP 5;
• Build a new linux kernel for LTSP 5 which is compatible with all etherboot images, including those from romomatic.

Procedure

1. Install LTSP.

apt-get  install  ltsp-server-standalone  openssh-server
ltsp-build-client

2. Modify /etc/exports. Add the following text at the end of the file:

"/opt/ltsp  *(rw,no_root_squash,async,no_subtree_check)"   {do not enter quotation marks}

3. Modify /etc/dhcp3/dhcp.conf:

Copy the following text and paste it into a new file. Do not try to type it. Then change all IP addresses to those in use in your own network.

######## 
#  /etc/dhcp3/dhcpd.conf -- CORRECTED LTSP-5 VERSION

#  This file uses an IP address of 150 for your server.
#  IP addresses 100-110 are used for your workstations.

#  Comments, indicated by "<--(text)", show where specific 
#  modifications are required to adapt my version of
#  dhcpd.conf to your own network.  Most of the corrections
#  entail entering your network's general address; some are
#  the specific address on your network for a specific computer.

#  Beware of "; { }" in the following text. If you erase one 
#  of these punctuation marks or type one in the wrong place,
#  dhcpd.conf will *not* work.

#  If you have a cable/router or dsl/router making dhcp assignments, 
#  you need to refer *non-LTSP* computers to the router for  
#  their IP address assignments.  In this situation you must leave 
#  the following line as it is, commented *out*.
  
#authoritative;

subnet 192.168.2.0 netmask 255.255.255.0 {   #<--your networks IP 
  range 192.168.2.100 192.168.2.110;         #<--workstation IP range 
  option domain-name "MyLTSP.com";           #<--make up a name  
  option domain-name-servers 192.168.2.150;  #<--LTSP server IP address
  option broadcast-address 192.168.2.255;    #<--your network IP address
  option routers 192.168.2.1;                #<--your router IP address
  option subnet-mask 255.255.255.0;


  if substring( option vendor-class-identifier, 0, 9 ) = "PXEClient" {
    filename "/ltsp/i386/pxelinux.0";      
  }
  else{
    filename "/ltsp/i386/nbi.img";          
  }
  option root-path "/opt/ltsp/i386";
  next-server  192.168.2.150;                #<--LTSP server IP address 
}

#
########

4. Revise /etc/inetd.conf:

Open the file and scroll down to the entry for "tftp". At the end of the line -- but not on a new line -- enter the following text:

"-r  blksize"   {do not enter quotation marks}

5. Create an /opt/ltsp/i386/etc/lts.conf file.

Lts.conf is not routinely installed by LTSP 5. It is needed to force default values for the workstations' ati and nvidia graphics adapters. Create the file manually. Do not copy and paste.

###############
# /opt/ltsp/i386/etc/lts.conf -- LTSP VERSION
#

[Default]
XSERVER  = vesa
X_MODE_0 = 1024x768

#
#########

6. Reboot your server to force Linux to reread your newly revised files.

7. Obtain an etherboot image for your workstation floppy.

1) The Thinclient multi-rom etherboot floppy image is available from:

http://sourceforge.net/project/showfiles.php?group_id=80408

At the bottom of the page navigate to "thinstation contrib > Universal network boot floppy/cd/hd > BootDisk522b.zip". Save and extract the image.

2) A specific floppy disk image for your NIC can be obtained from Debian:

apt-get  install  etherboot

Search through the /usr/share/etherboot directory. Look for the DSK.GZ version of the NIC image you need. ZDSK and ELF images can also be used. Extract the image.

8. Copy the etherboot image to a floppy disk.

dd if=/<path>/<NIC-name>.dsk   of=/dev/fd0   bs=1k

9. Test your etherboot image.

1) First boot the LTSP server.

2) Next insert the etherboot image floppy in your workstation. With your server running and the login screen visible, boot the workstation.

The booting process may momentarily hang with a "time out" warning. Generally within 20-25 seconds the workstation will then resume loading the LTSP files. If successful, the scrolling of text on the display screen will culminate with the LTSP login screen. Future boots will not hang. If on the first boot, booting does not resume after the "time out" warning, reboot the workstation. The reboot attempt should be successful.

CastAway - 12 September 2007

---

Installing LTSP 5 in Debian Etch

---

some of the suggestions below seem overly complicated for most installations...

VagrantCascadian^? 2007-09-06

---

Edit by CastAway -- 7 June 2007:

The following method for installing LTSP 5 in Debian Etch did not work for me. The dhcp daemon chokes on the line in dhcpd.conf which contains "MOPTS....". In addition, this method recapitulated all of the problems described in my recent article:

Installing LTSP in Debian 4.0: Which version--LTSP 5 or LTSP 4.2? http://www.linuxagora.com/vbforum/showthread.php?t=749

---

The installation of LTSP 5 in Etch requires a few modifications. The following is a method which works for me. (Everything is stolen; nothing is mine. Sources/references are at the end.)

A.) Setup a Debian Etch server. There are a lot of good instructions around.

B.) We need root permissions to do all the next steps.

C.) Get the basic packages. Open an xterm (or equivalent):

apt-get install ltsp-server openssh-server

D.) Built the ltsp client in the same xterm (I only use i386 clients with my amd64 server):

ltsp-build-client --dist etch --arch i386

Optional, you can use your own mirror (or local mirror) with an additional parameter (e.g. this is my local mirror, you have to pick another one):

ltsp-build-client --dist etch --arch i386 --mirror http://192.168.0.11/mirrors/etch

The ltsp-build-client script needs a lot of time (especially with a non local mirror).

E.) If you want to have local device access you need some Debian Sid (= Debian unstable) packages. These packages are at the moment not available for Etch (as of april 2007). Don't care about "unstable", they worked fine for me.

Point your favorite browser to:

http://packages.debian.org/unstable/net/ltspfs

and get the package for your server (!!!) architecture (for me it is amd64 = ltspfs_0.4.3+debian2_amd64.deb).

Then go for: http://packages.debian.org/unstable/net/ltspfsd

and get the package for your clients (!!!) architecture (for me it is i386 = ltspfsd_0.4.3+debian2_i386.deb)

F.) Install the ltspfs server (!!!) package:

In an xterm as root go to the just downloaded ltspfs server package and type (remember, amd64 is my server architecture, you may have another one):

dpkg -i ltspfs_0.4.3+debian2_amd64.deb

G.) Copy the ltspfsd client package into your chroot: In an xterm as root go to the just downloaded ltspfsd client (!!!) package and type:

cp ltspfsd_0.4.3+debian2_i386.deb /opt/ltsp/i386/root

H.) Now we do some action in the chroot:

You are root and type in an xterm:

chroot /opt/ltsp/i386

From now you are in the client environment (!!!), go to:

cd /root

and there install the client ltspfsd package:

dpkg -i ltspfsd_0.4.3+debian2_i386.deb

I.) Sound needs some extra help, so type in the same client environment (chroot):

apt-get install libasound2 libesd-alsa0 alsa-oss alsa-base linux-sound-base aumix

J.) We are already in the same client environment (chroot). The sound volume is 0 as default so we need a little pump up:

cd /etc

Here you have to create a file named "aumixrc" with this content:

vol:84:84:P pcm:85:85:P line:0:0:P mic:0:0:P cd:0:0:P pcm2:85:85:P igain:0:0:P line1:0:0:P dig1:0:0:P

You can do that with:

vi aumixrc

Pressing "i" (only the letter i) and pasting the above lines. Pressing of the esc - key and ":x" will save the file.

K.) There is one package missing. As of april 2007 the package "lsof" (part of local cdrom) is absent by default, so in the same client environment (chroot):

apt-get install lsof

L.) Remote logging is not working and need to be fixed, so in the same client environment (chroot):

cd /etc/rc2.d

mv K10sysklogd S10sysklogd

mv K11klogd S11klogd

M.) Delete all (!) entries in /etc/hostname in the chroot, then you have the right terminal name (from dhcpd) and everything works fine:

cd /etc

rm hostname

touch hostname

N.) Leaving the chroot, type:

exit

O.) We're back onto the server and enabling remote logging:

cd /etc/default

Edit the file "syslogd" to make sure the the following line is present:

SYSLOGD="-r"

Then restart the logging with:

/etc/init.d/sysklogd restart

P.) NFS configuration:

cd /etc

Make sure that in the file "exports" the following line is present:

/opt/ltsp 192.168.0.0/255.255.255.0(ro,no_root_squash,async,subtree_check)

You have to adapt the 192.168.0.0 to your network settings!

Restart the nfs - server:

/etc/init.d/nfs-kernel-server restart

Q.) Finally, the dhcpd configuration:

cd /etc/dhcp3

You have to edit the file "dhcpd.conf". This may be very tricky, because this depends on your specific hardware. Here is a part of my configuration, you have to adapt it:

#######

ddns-update-style none;

default-lease-time 21600;
max-lease-time 21600;

option subnet-mask                  255.255.255.0;
option broadcast-address            192.168.0.255;
option routers                      192.168.0.100;
option domain-name-servers          192.168.0.100;
option domain-name                  "YourDomain";

option root-path                    "/opt/ltsp/i386";

option option-128 code 128 = string;
option option-129 code 129 = text;

option option-128  e4:45:74:68:00:00;
option option-129  "MOPTS=nolock,ro,wsize=2048,rsize=2048";

authoritative;

log-facility local7;

subnet 192.168.0.0 netmask 255.255.255.0 {
    use-host-decl-names      on;
    option log-servers       192.168.0.11;

host x04 {
          hardware ethernet     XX:XX:XX:XX:XX:XX;
          fixed-address         192.168.0.54;
          next-server 192.168.0.11;
          if substring (option vendor-class-identifier, 0, 9) = "PXEClient" {
                        filename "/ltsp/i386/eb-5.4.3-via-rhine.zpxe";
                        }
          else if substring (option vendor-class-identifier, 0, 9) = "Etherboot" {
                        filename "/ltsp/i386/pxelinux.0";
                        }
         }

}

#######

After editing dhcpd.conf you must instruct the dhcp deamon to read the new version:

/etc/init.d/dhcp3-server restart

Notes:

1) Change XX:XX:XX:XX:XX:XX to the MAC address of your workstation's network card.

2) Obtain the *.zpxe files from http://rom-o-matic.net/.

R.) Fuse support for local device access.

Be sure that the packages fuse-utils & libfuse2 are installed (on the server):

apt-get install fuse-utils libfuse2

Load the fuse module in a console (server):

modprobe fuse

Then go to /etc/modules on the server and add one line with:

fuse

After that run this command (in the same console):

update-modules

S.) So far you are ready, I only have some little hints:

If you are low on client memory you can save some kilobytes by deactivating useless tty's. Switch to chroot and edit /etc/inittab:

comment out the lines:

#2:23:respawn:/sbin/getty 38400 tty2
#3:23:respawn:/sbin/getty 38400 tty3
#4:23:respawn:/sbin/getty 38400 tty4
#5:23:respawn:/sbin/getty 38400 tty5
#6:23:respawn:/sbin/getty 38400 tty6

If something goes wrong, it may help switching to the first tty and login at the client as root. To do that you need to give root a password. So switch to chroot and type "passwd" and enter a password.

Booting the client takes a lot of time now (since LTSP 5), you can improve that by optimizing the lts.conf file (e.g. naming a xorg.conf file). I will post a lts.conf file in the future.

References:

LTSP 5: http://www.ltsp.org

Debian: http://www.debian.org

Ubuntu: http://www.ubuntu.com

LTSP/Howto: http://wiki.debian.org/LTSP/Howto

NO remote - logging, BUG: #410485: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=410485

---

Printing with LTSP 5 in Debian Etch

If you have a printer connected to a terminal with LTSP 5 and Debian Etch you will be disappointed. It will not work. If, as me, you used LTSP (<= 4.2) for years with no such problems you can get really mad. Nevertheless I honestly like LTSP & Debian.

I googled around and found that there maybe is a licence problem with the print server application "lp_server". I also found this statement from Vagrant Cascadian: "... as we had to remove lp_server due to unclear copyright licensing ..." (see http://lists.alioth.debian.org/pipermail/pkg-ltsp-devel/2006-November/000462.html).

There are some debian lp_server packages around but nothing created for etch (so far as I can see).

I tried to use cups at the terminal with no success (you need rw access and I want to keep my terminal file system as small as possible).

I have to get my printer working as soon as possible. Here is my (very dirty) solution (ONLY for i386 clients):

A.) Copy the lp_server file to your client file system.

I got the lp_server sources from ltsp.org (via the LTSP 4.2 LBE) and compiled them for i386 (etch - architecture).

Do this for yourself or get it here: http://www.jumako.de/transfer/lp_server

Copy lp_server to /sbin in your client (!!!) file system (for me it is: /opt/ltsp/i386/sbin/lp_server). This file must have the execution flags.

If you copy from the above url, you do this on your own risk. I am not responsible for any damage to your computer.

B.) Modify start_printer

You have to patch the script start_printer (for me it is: /opt/ltsp/i386/usr/lib/ltsp/startprinter). There is a line with ". /etc/ltsp_functions". You have to change this line to ". /usr/lib/ltsp/ltsp_functions".

C.) Modify ltsp-client-setup

You have to enable printing in ltsp-client-setup (for me it is: /opt/ltsp/i386/etc/init.d/ltsp-client-setup).

Before the function

configure_syslog() {

cat < /etc/syslog.conf

. @${SYSLOG_HOST-$SERVER}

EOF

}

paste this 6 lines:

configure_printer() {

for prn_dev in $(env | awk -F= '$1 ~ /^PRINTER_[0-9]_DEVICE/ { print $1 }'); do

prn_no=`echo $prn_dev | cut -f2 -d'_'`

/usr/lib/ltsp/start_printer $prn_no &

done

}

And in the same file before the line

configure_syslog || true

paste this line

configure_printer || true

I've got this informations from:

https://launchpad.net/ubuntu/+source/ltsp/+bug/93863/comments/1

D.) lts.conf

Enable a printer in your lts.conf. For me it looks like that:

[XX:XX:XX:XX:XX:XX]

PRINTER_0_DEVICE = /dev/usb/lp0

PRINTER_0_TYPE = U # P-Parallel, S-Serial, U-USB

PRINTER_0_PORT = 9100 # tcp/ip port: defaults to 9100

PRINTER_0_WRITE_ONLY = Y

Where XX:XX ... is the IP of your workstation.

E.) Sorry for my ugly patches.

I know that the LTSP people are working for a perfect solution.

---

Scanning with LTSP 5 in Debian Etch

Note: This is a description for a scanner physically connected to a terminal (not to the server).

A.) This first step is optional (for Epson scanners only):

If you have an Epson Perfection 2480 Photo (or another Epson scanner) you may need the firmware files. Get it here:

http://www.avasys.jp/english/linux_e/dl_scan.html

You have to select the model and the distribution that you are using, for me it is the Perfection 2480 PHOTO (same as the GT-F500).

I downloaded this file: iscan-plugin-gt-f500-1.0.0-1.c2.i386.rpm. The extension c2 is for for gcc 3.4 or later (fits perfectly for my i386 etch clients).

To convert this rpm file I use alien, so type in an xterm (as root):

apt-get install alien

Then I convert the package in an tgz file:

alien --to-tgz iscan-plugin-gt-f500-1.0.0-1.c2.i386.rpm

List all files to search for the firmware with:

tar -tzf iscan-plugin-gt-f500-1.0.0.tgz

and extract the firmware file:

tar -x -zf iscan-plugin-gt-f500-1.0.0.tgz ./usr/share/iscan/esfw41.bin

Then copy the firmware file to it's new location:

cd ./usr/share/iscan/

cp esfw41.bin /opt/ltsp/i386/usr/lib/hotplug/firmware

B.) chroot

You have to be root in the chroot LTSP client environment for the next steps, so get the power with these commands in an xterm (or equivalent):

su

chroot /opt/ltsp/i386

C.) Install necessary packages

Thanks to the Debian package system it's easy to get almost all software:

apt-get install libexif12 libgphoto2-2 libgphoto2-port0 libieee1284-3 libltdl3 libsane libsane-extras sane-utils

D.) User 'saned' needs an additional group:

usermod -a -G scanner saned

E.) Modify /etc/inetd.conf

Open /etc/inetd.conf (e.g. with vi) and add at the end of the file (after '#:OTHER: Other services') this line:

sane-port stream tcp nowait saned.saned /usr/sbin/saned saned

F.) The initial openbsd-inetd links are wrong.

Delete them with (be sure that you are in the client - chroot!):

rm /etc/rc*/*openbsd*

Create new one's:

ln -s ../init.d/openbsd-inetd /etc/rc2.d/S20openbsd-inetd
ln -s ../init.d/openbsd-inetd /etc/rc3.d/S20openbsd-inetd
ln -s ../init.d/openbsd-inetd /etc/rc4.d/S20openbsd-inetd
ln -s ../init.d/openbsd-inetd /etc/rc5.d/S20openbsd-inetd

ln -s ../init.d/openbsd-inetd /etc/rc0.d/K20openbsd-inetd
ln -s ../init.d/openbsd-inetd /etc/rc1.d/K20openbsd-inetd
ln -s ../init.d/openbsd-inetd /etc/rc6.d/K20openbsd-inetd

Check if everything is fine:

ls -l /etc/rc*/*openbsd*

G.) Leave chroot

Leave the chroot:

exit

H.) Install necessary packages (server)

Thanks to the Debian package system it's easy to get almost all software (as root):

apt-get install libsane libsane-extras sane-utils

I.) Set user grants

You have to set the saned group for every scanner user, e.g. for the user 'jumako':

usermod -a -G saned jumako

J.) saned.conf � Configuration (client)

cd /opt/ltsp/i386/etc/sane.d

Modify the saned.conf file. Put the IP � address of your server, e.g.:

#
# saned.conf
#
# The contents of the saned.conf  file  is  a  list  of  host  names,  IP
# addresses or IP subnets (CIDR notation) that are permitted to use local
# SANE devices. IPv6 addresses must be enclosed in brackets,  and  should
# always  be specified in their compressed form.
#
# The hostname matching is not case-sensitive.
#
192.168.0.11

K.) net.conf � Configuration (client)

cd /opt/ltsp/i386/etc/sane.d

Modify the net.conf file. Put the IP � addresses & names of your server, scanner � terminal � client and localhost here, e.g.:

# This is the net config file.  Each line names a host to attach to.
# If you list "localhost" then your backends can be accessed either
# directly or through the net backend.  Going through the net backend
# may be necessary to access devices that need special privileges.
192.168.0.59
x09
localhost
192.168.0.11
s01

Explanation: x09 & 192.168.0.59 is the IP and the name of my scanner � terminal, s01 & 192.168.0.11 is the IP and the name of my server. Normally the IP should be sufficient but I saw a lot of trouble in the past with this configuration, so I use both.

L.) Modify the dll.conf (client)

cd /opt/ltsp/i386/etc/sane.d

Enable only two lines, one with 'net' and the other one with the name of your (!) scanner backend (for me: snapscan -> works with Epson scanner).

It has to look like this:

# enable the next line if you want to allow access through the network:
net
snapscan
#abaton
#agfafocus
#apple
#avision
#artec
#artec_eplus48u
#as6e
...

Here you find an overview of supported backends:

http://www.sane-project.org/sane-mfgs.html

M.) Modify the conf � file of your scanner backend (client)

cd /opt/ltsp/i386/etc/sane.d

This step depends on your scanner.

For me I only have to modify this line in the 'snapscan.conf' file (the firmware location from step A.):

firmware /usr/lib/hotplug/firmware/esfw41.bin

You find some information within the specific conf � file.

N.) Modify dll.conf (server)

cd /etc/sane.d/

Modify dll.conf.

Enable only the line with 'net'.

It has to look like this:

# enable the next line if you want to allow access through the network:
net
#abaton
#agfafocus
#apple
#avision
#artec
#artec_eplus48u
#as6e
...

O.) Modify net.conf (server)

cd /etc/sane.d/

Modify net.conf.

Put the IP � address of your scanner � terminal � client (!) here, e.g.:

# This is the net config file.  Each line names a host to attach to.
# If you list "localhost" then your backends can be accessed either
# directly or through the net backend.  Going through the net backend
# may be necessary to access devices that need special privileges.
192.168.0.59

P.) Restart your client terminal and your are ready

LTSP 4

---

Revised 26 September 2006

Installing LTSP 4.1 in Debian 3.1 Sarge & Etch:

A Step-by-Step Guide for the Beginner

Introduction

This guide allows you to setup a Linux server to which any computer can connect as a workstation. You can browse the internet, download files, read and save your mail, or work on a manuscript in WordPerfect 8 -- all on the server. Performing such tasks in Linux avoids most of the "animal kingdom pests" that thrive in the DOS/Windows community. And your server can be left running constantly, or turned on and off from the workstation.

NOTE:

1. This How-To has been updated. It now includes instructions for Debian etch. Separate instructions, given in brackets {ETCH:}, are shown for etch where installation between the two distributions differs. (The version of etch used for the test-install was a daily build containing the AMD64-generic kernel, dated 08/08/2006.) Although a recent article on the web states that running LTSP on an amd64 server requires workstations that have amd64 processors, I had no difficulties with my athlon 2400 workstations.

Manual installation of the xserver in etch can be difficult because the new version from X.org can be installed from multiple components. It may be easier for the beginner to install xserver by choosing "Desktop" installation in addition to "Basic" installation. This way xserver is more likely to work immediately, and you will get Gnome as well.

2. The downloaded files referred to in this document are current as of 16 August 2006.

3. Read the Comments & Notes Section at end of the article before starting.

---

Partitioning the Server Hard Drive

See Comment #5, "Partitioning & Backup," before creating partitions. The directions in the following section are for DOS partitioning only.

1. Start with a clean hard disk.

2. Create all partitions in DOS before installing Linux. (I use Partition Magic installed on a DOS-bootable floppy disk for this task.)

(1) Create a small Primary Partition for DOS. This will hold such utilities as Drive Image 2002 for DOS backup of your root and home partitions, and, if necessary, your boot manager.

(2) Create an Extended Partition. In it create Logical Partitions for your Linux installation: a root partition (/); a home partition (/home); and a swap (swap) partition. At the end of the Extended Partition create a Logical DOS FAT32 Partition (archive) for backups of your Linux root and home partitions.

3. Install a boot manager program.

---

Installing the Debian Operating System

1. Boot the cdrom. Enter "linux26" at the boot prompt. This enables you to install kernel-image-2.6.8-2. {ETCH: Enter "installgui".}

2. Setup your hard drive by manually editing the partition table.

(1) Setup the root (/) partition first. Make selections as follows:

_1 Use as: "Ext3 file system".

_2 Format the partition: "Yes"

_3 Mount point: "/"

(2) Write down the root partition's ID# - i.e., /dev/hda6. You will need this information later.

(3) Next setup the /home and swap partitions.

3. The Debian base system will then be installed.

4. Do NOT install the grub boot loader on the master boot record. Instead install grub on the hard disk in your ROOT partition (e.g. dev/hda6).

5. Debian will reboot.

6. Setup time, users and passwords.

7. Choose to add a mirror. Choose http or ftp and select a source. Apt will then update the sources list.

8. Do NOT choose any additional packages for installation {ETCH: Add "Desktop".} Installation of files will be completed. During setup of the mail system, accept all defaults.

---

Setting Up X-windows

1. Log into Debian with your USER name and password. {ETCH: If you included Gnome in your initial installation, select Application > Accessories and drag the xterminal icon to the desktop. Then click on the icon to start xterminal.} At the prompt, change to ROOT by entering "su" and, when requested, the ROOT password. For the remainder of this How-To, all commands are run at the ROOT prompt.

2. At this stage Debian has no graphic capabilities. {ETCH: If you have chosen to install "Desktop" along with the base system, you have graphic capabilities. Skip this step and proceed to Step #6 below.} Install x-window as follows:

apt-get   install   x-window-system

3. Allow x-server to autodetect your video hardware.

(1) It will most likely identify your mouse incorrectly. If necessary, change the mouse port. Change the mouse type.

(2) Chose MEDIUM option for selecting your monitor's characteristics.

4. Before you can use x-window, you will need a window manager (IceWM). Also obtain a desktop manager (gdm), a graphic editor (gedit), and a file manager (mc).

apt-get   install   icewm   gdm   gedit   mc

Configure gdm by selecting "gdm", not the default "xdm."

5. Start the xserver.

startx

You should be taken directly to the IceWM desktop.

6. Configure gdm so that root can login with gdm. Click xterminal. At the prompt enter:

gdmsetup

1) Select the "Security" tab.

2) Check "Allow root to login with GDM".

3) Click "Close.

{ETCH: The gdm menu is different:

1) Select the "Security" tab.

2) Check "Allow local system administrator login".

3) Click "Close".}

7. Finally, REBOOT your server to confirm that all changes made above are correct. (Be sure to remove the cdrom.)

reboot  -n

---

Downloading and Configuring Ancillary Software Necessary for LTSP

Log in as ROOT. Open xterminal.

1. Install a web browser. {ETCH: Skip this step.}

apt-get   install   mozilla-firefox

Now you will be able to copy the pre-configured sample files, found in this How-To in the LTPS Wiki forum, directly to your computer. This technique is described in the introduction to the section on "Preconfigured Files."

2. Assign your network a static IP address.

(1) Make a copy of the original etc/network/interfaces file.

cp   /etc/network/interfaces   /etc/network/interfaces-original

(2) Obtain your IP address. At the prompt, enter:

ifconfig

On the second line of the listing for eth0, in the format xxx.xxx.xxx.yyy, is the current IP address of your server. This is what mine read originally:

inet addr: 192.168.2.23

where xxx.xxx.xxx is your network's address, and yyy (23) is your server's specific address on your network. Copy down the network address, xxx.xxx.xxx.

(3) Copy the text of sample File #8-A into a new document and save as /etc/network/interfaces. {ETCH: Use sample File #8-B instead.} The preconfigured files assume a network address of xxx.xxx.xxx.100 for your LTSP server. Change all other references to your network address (xxx.xxx.xxx) accordingly. Save the new file as /etc/network/interfaces.

3. Reload the new copy of your interfaces file:

ifdown   eth0
ifup   eth0

4. Obtain the four Debian packages needed to install LTSP:

apt-get    install    nfs-kernel-server    dhcp3-server

During the ensuing installation, when the dhcpd3-server is being installed, you will be asked "What network interface should the DHCP server use?". Enter "eth0".

apt-get    install     atftpd     libwww-perl

When the "configuring atftpd" screen appears, enter "xxx.xxx.xxx.0-255", where xxx.xxx.xxx. is your network IP address (see above). Accept all other defaults.

{ETCH: You will not have to enter any data during Step #4.}

---

Installation and Preliminary Setup of LTSP

1. Download the LTSP installation package:

apt-get    install     ltsp-utils

2. Start the LSTP setup program by entering:

ltspadmin

3. From the ltspadmin menu, do the following (the menu is counterintuitive):

(1) Select "Configure the installer options".

(2) At the prompt "Where to retrieve packages from?", accept the suggested default web site.

(3) Accept the [/opt/ltsp] installation directory.

(4) For both HTTP and FTP proxy, hit [Enter].

(5) Answer [Y] to continue. You are returned to the main menu.

(6) Select "Install/Update LTSP Packages".

(7) On the next screen the names of the available LTSP packages will be downloaded from the internet.

_1 Select [A] to install all of the packages.

_2 Then hit [Q] to close the menu.

(8) Answer [Y] to install. The files will be downloaded and installed.

(9) Select "Configure LTSP" from the main menu. Ltspadmin will check to see if all the necessary files have been installed. Hit [Enter].

(10) Next,

_1 "Show the status of all services" by hitting [S]. Some of these services will be started in the next step.

_2 Hit [Enter] to return to the previous menu.

(11) Choose "Configure services manually" by hitting [C].

(12) Step through each category. Enter [Y] to all suggested choices:

_1) Accept runlevel=2 for your Debian installation.

_2) Choose which network interface to use, "eth0".

_3) During xdmcp installation, answer [N] to "disable graphical logon on server" if you wish to continue using the logon screen that you have been using. If you chose [Y], then your computer will boot to the prompt; after logging on you will have to type "startx" to start IceWM.

{ETCH: Xdm will be listed as missing in this step. Ignore the error: xdm is not necessary since you will be using gdm instead.}

(13) Finally, enter [Q], [Q] to quit ltspadmin.

---

Files Which Require Little or No Modification for LTSP

1. /etc/hosts.allow

2. /etc/hosts

This file will function as modified by LTSP. However, you may want to remove or disable hosts (use "#") not listed in your dhcpd.conf file. Or you may want to use different host names and addresses.

3. /etc/exports

LTSP sets up your file server with a /home directory which is on the root partition. You can replace it with your own /home directory, which is on the separate partition /home, by adding it to the exports file. This will give you access to all of your data, whether working at the server or at a workstation. Add the following line to /etc/exports:

/home     xxx.xxx.xxx.yyy/255.255.255.0(rw,no_root_squash)

Modify xxx.xxx.xxx.yyy by using the IP address already setup in exports during LTSP installation.

4. /opt/ltsp/i386/etc/lts.conf

If your workstation has an optical mouse with a scroll wheel, you will need to make extensive changes in your lts.conf file. Therefore, it is easier to modify File #5, after you have copied it to your computer than to edit your current version. BE SURE TO CHANGE THE IP ADDRESS LISTED IN THE SAMPLE FILE TO THAT OF YOUR OWN LTSP SERVER.

5. /etc/gdm/gdm.conf

IMPORTANT: Confirm that XDMCP has been set up correctly. At the prompt, enter:

gdmsetup

1) Select "XDMCP" tab.

2) Confirm that "XDMCP" is enabled. Confirm it is listening on UDP Port 177.

{ETCH: The gdm menu is different:

1) Select "Remote" tab. Change "Remote logon disabled" to "Plain".

2) Click "Close".}

---

dhcpd.conf -- The One File Which Requires Extensive Modification for LTSP

This file resides in the directory /etc/dhcp3/.

A sample file, dhcpd.conf.sample, is added by LTSP during installation. It is a reference file only -- it will not run without modification.

1. Navigate to the /etc/dhcp3 directory. Save the original file.

cp   dhcpd.conf.   dhcpd.conf-original

2. Now copy dynamic-dhcpd.conf File #1 to your /etc/dhcp3 directory, saving it with the same name, dynamic-dhcpd.conf.

3. Copy the dynamic version to dhcpd.conf:

cp   dynamic-dhcpd.conf   dhcpd.conf

4. Assign the proper permissions, if necessary, to dhcpd.conf:

chmod  644   dhcpd.conf

5. Update the IP addresses and other data in your new version of dhcpd.conf. The lines requiring revision are identified; additional instructions are in the header of dhcpd.conf.

{ETCH: Uncomment the line "next-server"; modify its IP address. This line is found at the top of the file.}

6. Start the dhcpd3 demon. Whenever dhcpd.conf is modified, the dhcpd3 demon must be stopped and restarted to load the revised file. Gross errors in the file will be listed on your console display if the demon fails to start. (However, the demon can load a non-functional configuration file without an error message.)

(Note: The dhcpd3 demon is not started when LTSP is installed. Thus it is not necessary to kill it in order to load your newly revised dhcpd.conf file. This first time only, start the demon by entering just "/usr/sbin/dhcpd3".)

To restart the demon, first find the process number of the dhcpd3 demon that is currently running; kill it; then restart the demon:

ps   -A                      [find process# of dhcpd3, e.g. 1043]           
kill   dhcpd3-process#       [e.g., "kill 1043"]
/usr/sbin/dhcpd3

7. Reboot the computer ("reboot -n") and login as root. Open xterminal.

8. Run "ltspadmin". Choose "Configure LTSP", [Enter], [S], [Enter]. You should find that all parameters are now enabled and running with the exception of xdmcp:

xdmcp     YES     Enabled: no     Running: YES      xdm, gdm  Using: gdm 

Xdm is not enabled because we are using gdm instead!

{ETCH: Ignore all references to xdmcp. Xdm is not installed.}

---

Setting Up a Floppy-Drive LTSP Workstation

1. You must identify the manufacturer or the NIC chip in your network card or motherboard. This information is listed in the specifications for your motherboard and is also listed by the Windows Device Manager. Several 'detective' programs that may be of aid in identifying your NIC can be found at:

http://www.pigtail.net/LRP/swap.html#nic

2. Obtain a Linux floppy disk boot image (.zdsk) from:

http://www.rom-o-matic.net

Select your workstation's NIC from the list. Accept the default setting "floppy bootable ROM image". Next click the "get rom" button and download the image to your computer. See Comment #6 regarding ISA & PCI NIC chip images.

3. Write the image to a floppy disk with "cat" if using Linux, "rawrite" if using Windows. (See directions at the bottom of rom-o-matic web page.)

4. Turn on the server. Let it boot to the gdm logon screen. Then boot the workstation with the floppy boot disk containing the .zdsk image.

If your workstation cannot successfully connect with the server:

(1) You may need to try another .zdsk ROM image;

(2) Your dhcpd.conf file is incorrect. This may be due to incorrect IP addresses; incorrect text references; or improper bracket { } usage.

For additional help, the LTSP 4.1 manual has a good help section. Find it at:

http://www.ltsp.org/documentation/index.php

5. Repeat this section, making a specific boot disk for each different brand of network card or motherboard lan in use.

ONCE YOU HAVE SUCCESSFULLY COMPLETED YOUR LTSP INSTALLATION, SKIP TO THE LAST SECTION OF THIS GUIDE FOR DIRECTIONS ON FINE-TUNING YOUR LTSP NETWORK.

=============================================================================

Setting Up a Hard-Drive LTSP Workstation

If you would like a workstation with a minimal hard drive installation version for booting LTSP, go to the following section. If you want a deluxe version which can remotely start your server, skip the following section and go the next section.

In either situation you must first install DOS on the workstation's C: partition. Your DOS directions will guide you through (1) setting up partitions with FDISK; (2) formatting your partition with DOS; and (3) installing the DOS system files.

To modify your new DOS partition so that it is compatible with the instructions given here, you will need to make the following changes.

1. Verify the name of the directory that DOS has been installed in. If it has been installed in "c:\dos", skip this step. If it has been installed in the "c:\another-directory", enter the following at the C:\ prompt:

cd  \
c:\another-directory\move    c:\another-directory    c:\dos

2. Save your current autoexec.bat and config.sys files by renaming them:

rename    c:\autoexec.bat    c:\autoexec.sav
rename    c:\config.sys      c:\config.sav

3. Create a temporary autoexec.bat for use until you complete the LTSP installation:

copy   con   c:\autoexec.bat   [Enter]
path=c:\;c:\dos;     [Enter]
[Ctrl] + [Z]   
[Enter]

4. Reboot your workstation:

[Ctrl] + [Alt] + [Del]

5. Enter the following at the prompt:

type   c:\autoexec.bat

If the data you entered for you temporary autoexec.bat was correct, the following will be displayed on the screen.

path=c:\;c:\dos;

If incorrect, go back to Step #3 and repeat it and the succeeding steps.

6. Install your boot manager. (Try it out to understand how it works!)

==========================================================================

Version #1: Minimal Hard Drive Installation

On my workstation the boot manager offers a choice of MSDOS 7.1, Windows-XP or Libranet 2.8.1. By choosing MSDOS 7.1, I have the options of booting as an LTSP workstation, a pen version of Linux, or MSDOS version 7.1 (extracted from Windows 98). The following directions will install the same options for your DOS partition. You can modify these choices later by altering the autoexec.bat and config.sys files.

1. Using the server or another computer, download the .com version of the boot image for your network card at:

http://www.rom-o-matic.net

(1) Rename this file to meet the DOS 8+3 format: 8 characters, a period, and 3 characters -- no spaces. For this file to function properly, you must keep the "com" extension. Example:

this.much.too_long-name.476934.com  ---->  rtl-8139.com

(2) Take a DOS-formatted floppy disk and label it "transfer".

(3) Copy the renamed boot .rom to your "transfer" floppy disk.

2. Copy File #2, config.sys, and File #3, autoexec.bat - minimal version, to the "transfer" floppy disk.

3. Power on your workstation. From the boot menu select the DOS partition. At the C:\ prompt make a new directory, c:\ltsp.

mkdir   c:\ltsp

Copy your renamed .com boot image from the "transfer floppy" to the C:\ltsp directory.

copy   a:rtl-8139.com   c:\ltsp\*.*

4. Copy File #2, config.sys and File #3, autoexec.bat - minimal version, from the "transfer" floppy disk to the DOS root directory, C:\.

copy   a:autoexec.bat     c:\autoexec.bat
copy   a:config.sys       c:\config.sys

5. Now revise the autoexec.bat file on your hard drive C\:

edit    C:\autoexec.bat

Change the first entry under ":ltsp" so that it refers to your own specific .com boot image (and not to mine, as listed below):

c:\ltsp\rtl-8139.com

6. Turn on your LTSP server. (Your server MUST be running and have booted to the gdm logon screen before you can boot your workstation.)

7. Reboot your workstation. Select the DOS partition from the boot menu screen. When DOS loads, select LTSP Boot. Logon to the server from your workstation.

ONCE YOU HAVE SUCCESSFULLY COMPLETED YOUR LTSP INSTALLATION, SKIP TO THE LAST SECTION OF THIS GUIDE FOR DIRECTIONS ON FINE-TUNING YOUR LTSP NETWORK.

============================================================================

Version #2: Deluxe Hard Drive Installation

Materials Required:

(1) A DOS .com boot ROM image for your workstation network card from:

http://www.rom-o-matic.net

Rename this file to fit the DOS 8+3 format. (See directions in Step #1 in the section above.)

(2) The packet driver and driver text file for you network card. They should be on the floppy disk or cdrom that came with your NIC or motherboard. All packet drivers do not use the same software interrupt, so you will need the text file to know the specific interrupt!

(3) The DOS WOL (Wake On Lan) program, DOSWOL11.ZIP, found at:

http://users.ohiohills.com/fmacall/DOSWOL11.ZIP

(4) PBAT32.ZIP, which contains a "digital" delay timer, wait4. This archive of DOS utilities is found at:

http://home.mnet-online.de/horst.muc/int/pbats32.zip

Extract the files for wait4.

(5) The WOL cable for your network card.

(6) The manual for your SERVER motherboard for information on WOL socket location and details of WOL settings in the BIOS.

Note: Be sure that each of the following sections has been completed successfully before moving on to the next section.

---

SERVER

Configuring the Server's Hardware for Remote Booting

1. Motherboard with WOL socket:

(1) Connect the WOL socket on the network card to the WOL socket on the motherboard using the WOL cable.

(2) Boot your server and enter the BIOS setup. Look in the Power Management Setup. WOL may be found in Wake Up Events in such subcategories as Wake Up by PCI Card, Wake Up by Ring/Lan or IRQs Activity Monitoring. Enable the proper settings. Enable an IRQ if necessary (see below).

2. Motherboard without WOL socket:

(1) If your motherboard does not have a WOL socket, it probably is not needed. The bios has provisions for monitoring PCI slot activity.

(2) Boot your server and enter the Bios setup. In Power Management Setup look for WOL (PME#) From Soft-Off and enable it. WOL may be referenced in a section such as IRQ/Event Activity Detect. Subcategories to check are IRQ Event Activity Detection where you can enable Power-on by PCI Card, or enable an IRQ. In the latter situation you want to enable the IRQ of the NIC.

3. Determining the NIC's interrupt (IRQ):

Check the computer terminal's display while it boots. By putting a floppy disk without system files into the floppy drive and booting, the error message will prevent the boot data from being overwritten on the screen. Alternatively, you can identify the NIC interrupt by using the diagnostics program that sometimes comes with NIC or motherboard software. If you have Windows XP installed on the workstation computer, check Device Manager for the interrupt.

---

Configuring the Server's Software for Remote Booting

1. ethtool must be installed in Linux so that the NIC in the server can respond to a "magic packet" sent to it by the workstation.

(1) Boot the server and logon as root.

(2) Obtain ethtool and install it:

apt-get   install   ethtool

(3) Check to be sure ethtool is running:

ethtool   eth0

A listing on the console display of eth0's settings will be displayed. Look for these lines near the bottom:

Supports Wake-on:  pumbg   [g = magic packet support turned on]
Wake-on: d                 [d = WOL service disabled]
Link detected: yes

(4) Now turn on WOL support:

ethtool   -s   eth0   wol   g

(5) Repeat Step #(3) above. The following should now be displayed:

Supports Wake-on:  pumbg 
Wake-on: g                 [g = WOL service enabled]
Link detected: yes

(6) Add the following line to /etc/network/interfaces. It should be entered as the last line in the file:

up   ethtool   -s   eth0   wol   g

(7) Reboot ("reboot -n") and login as root.

(8) Ascertain ethtool is now running with the new parameters:

ethtool   eth0

The results should be those seen in Step #(5) above.

2. Obtain the MAC (hardware) address for the server's network card. This number is needed by the workstation so that it can address the magic packet to the server. In the terminal on the SERVER enter the following:

ifconfig

On the screen, under settings for eth0, the first line contains the hardware address (HWaddr):

HWaddr xx:xx:xx:xx:xx:xx:xx

---

<<>>

Testing the .com Boot ROM Image

First, prepare a floppy disk. Label it "deluxe." Unless noted otherwise, it will be the floppy disk you will use for the remainder of the installation.

1. Format the floppy disk with DOS and add the DOS system files to it.

In Debian use your favorite utility. In Windows right click on the Floppy Drive A: icon. Then left click on "format"; left click on "create a MS-DOS startup disk." In DOS go to the C: prompt and enter:

format  a:  /s  /u

2. Next copy the following files to the floppy disk:

(1) rom-o-matic boot image (.com version) for the workstation NIC.

Before copying this file to the floppy disk, you must rename it to meet the DOS 8+3 format: 8 characters, a period, and 3 characters -- no spaces. For this file to function properly, you must keep the "com" extension. Example:

this.much.too_long-name.476934.com ---->  rtl-8139.com

(2) packet driver and packet driver text for the workstation NIC;

(3) doswol.exe; doswol.cfg; doswol.txt;

(4) wait4.com, wait4.txt, wait4.pat.

3. Now turn on your workstation. Boot the DOS partition. For the remainder of the How-To, you will perform all operations in DOS at the C:\ prompt.

4. Prepare an autoexec.bat file on the floppy by entering:

edit   a:\autoexec.bat

The script should contain only the name of the boot rom file. Example:

@echo  on
rtl-8139.com

Instead of rtl-8139.com, substitute the name of the .com boot rom file you downloaded from rom-o-matic and have previously renamed in the 8+3 format.

5. Edit doswol.cfg on the floppy disk. Newer routers prevent LTSP workstations from starting the server if doswol.exe uses its default settings. (My �hardwired� SMC router worked perfectly using the default settings; my wireless LinkSys router failed.) Therefore, you will need to change the first option in doswol.cfg.

edit  a:\doswol.cfg

At the beginning of the file, find the default entry:

my_ip=BOOTP

Change this to either:

my_ip=DHCP

or:

my_ip=192.168.2.1     [replace IP with your own router�s IP address]

Save the changes with [Alt] + [F], then [X], and then [Enter].

6. With the Server ON and the gdm logon screen displayed, reboot the workstation using this floppy. If the workstation eventually displays a logon screen, you have the right boot ROM image. If you are unable to log on, then you may have downloaded the wrong .com image.

Sometimes at rom-o-matic it is difficult to determine which image your NIC uses and you may have to try several before you are successful.

---

Testing the Packet Driver and the Magic Packet

1. The packet driver for your network card will now be added to the batch file. Read the text file for the workstation's NIC packet driver. BE SURE TO ENTER THE SOFTWARE INTERRUPT AFTER THE NAME OF THE PACKET DRIVER.

2. Edit autoexec.bat on the "deluxe" floppy disk and add the packet driver file name and its software interrupt. Insert the packet driver and interrupt data so it is the second line:

@echo  on
F5D5000    0x7e     
rtl-8139.com

3. Now add doswol to the script, replacing the MAC address in the example with the MAC address of YOUR Server. Enter the command as the third line:

@echo  on
F5D5000   0x7e
doswol   00:50:BA:8A:75:8B
rtl-8139.com

4. Do a soft shutdown ("halt -n")of the server and LEAVE THE SERVER OFF. Reboot your workstation using the same floppy. The server should awaken automatically. However, you will NOT be able to log on: your workstation will timeout before the server has fully booted and is ready to accept remote logons.

If you cannot awaken the server:

(1) Check for typographical errors or incorrect order of the commands in the autoexec.bat file. Also check the software interrupt and the MAC address for accuracy.

(2) NOTE: After an unsuccessful attempt to awaken your server by the workstation, boot the server manually. Then log on as root and open xterminal. After 10 or 15 seconds perform a soft shutdown of the server. (You can also shutdown the server from the gdm logon screen.) This will "clear" the data channel for ethtool which apparently becomes confused after it has received an incorrectly sent magic packet. When it becomes confused, it will not respond even when it later receives a properly configured packet. This little trick will save you much frustration!

---

Testing the Digital Countdown Timer

1. Now that you have a functioning boot disk (the "deluxe" floppy) that awakens your server, add the graphic timer. First, set the boot manager on the SERVER to boot automatically to Debian 3.1 after only a 4 or 5 second delay. Then time how long it takes your server to boot to the Debian login screen. Add 10 seconds more as a buffer. Use this calculation as the boot time delay for the "wait4" command. After the designated time, "wait4" will allow the boot command (the last line of autoexec.bat) to be issued.

2. Add these changes to the autoexec.bat file on your floppy disk. Enter the command for wait4, along with the delay time, on the fourth line. (In the below example it is 1 minute, 40 seconds):

@echo  on
F5D5000   0x7e
doswol   00:50:BA:8A:75:8B       
wait4   +1:40   /B   /D   /C12
rtl-8139.com

3. Now initiate a software shutdown of the server. Do NOT perform a hardware shutdown.

4. Reboot the workstation using your newly revised "deluxe" floppy disk. The server should awaken, and at the end of your calculated delay, the workstation should begin downloading files from the server. Logon as USER, not root, from the workstation's logon screen.

---

Installing the Server-Booting Software on the Work Station

1. Take a fresh DOS formatted floppy disk. Label it "wiki-files".

2. Using your Linux or Windows computer, access the LTSP Wiki and access this How-To. Copy to the "wiki-files" floppy disk the following three files: File #2, config.sys* File #7, autoexec.bat -- deluxe version; and File #6, ltsp.bat.

3. Move to your LTSP workstation. Turn on the computer and boot the DOS partition. Insert the "wiki-files" floppy disk. Copy the two startup files from the floppy to your workstation's root directory, C:\.

copy   a:autoexec.bat     c:\*.*
copy   a:config.sys       c:\*.*

4. Now, insert the "deluxe" floppy disk. Rename autoexec.bat on the FLOPPY disk to ltsp.xxx.

rename   a:autoexec.bat    a:ltsp.xxx

5. Make a directory, c:\ltsp, for your LTSP files on the root drive, C:\.

mkdir   c:\ltsp

6. Copy all the files on your "deluxe" floppy disk to c:\ltsp.

xcopy    a:*.*    c:\ltsp\*.*

7. Now remove the "deluxe" disk and insert the "wiki-files" floppy disk. Copy File #6, ltsp.bat, to your c:\ltsp directory.

copy   a:ltsp.bat    c:\ltsp\ltsp.bat

8. Transfer the data from your c:\ltsp\ltsp.xxx file to all four sections of c:\ltsp\ltsp.bat, replacing the sample data in the batch file with:

(1) The packet driver name and software interrupt for your NIC;

(2) Your server's MAC address after the doswol command;

(3) The delay time after wait4;

(4) The rom-o-matic .com boot image for your workstation.

9. The config.sys and autoexec.bat files on C:\ do not need to be modified.

10. Now test the newly installed LTSP boot files on the workstation's hard drive as follows:

(1) Shut down the server (software shutdown).

(2) Boot the workstation. When the boot manager menu appears,

(3) Select the DOS partition. When the DOS partition boots,

(4) Select LTSP Boot from the DOS menu. At the conclusion of the countdown, your server will awaken.

(5) When the LTSP login screen appears on your workstation, logon as USER (not root).

ONCE YOU HAVE SUCCESSFULLY COMPLETED YOUR LTSP INSTALLATION, SKIP TO THE LAST SECTION OF THIS GUIDE FOR DIRECTIONS ON FINE-TUNING YOUR LTSP NETWORK.

---

Providing for Easy Remote Shutdown of the LTSP Server

Create an icon for �PowerOFF� on all your workstation desktops. With it you can shutdown the server from any LTSP workstation as well as from the server console itself.

First, open a terminal on the LTSP server. Switch to root, "su". Perform all of the following operations as root unless specifically noted otherwise.

1. Obtain sudo to empower users to run poweroff, and icemc to install the PowerOFF icon on the IceWM tool bar.

apt-get   install   sudo   icemc

2. Modify /etc/sudoers. Assign each user the ability, through sudo, to run PowerOFF. (The poweroff command can normally only be exercised by root.) You must use the special editor "visudo" to modify etc/sudoers; do not use a text editor, such as gedit. At the root prompt start visudo:

visudo

In the sample copy of /etc/sudoers below, find the two lines containing POWEROFF. Add these two lines to your sudoers file. The first line defines the command (POWEROFF) which you are creating. The second line designates the user allowed to use the newly created command. Be sure to replace [user-name] with the user�s login name.

# /etc/sudoers

# Host alias specification

# User alias specification

# Cmnd alias specification
Cmnd_Alias   POWEROFF = /sbin/poweroff   

# User privilege specification
root    ALL = (ALL)  ALL
[user-name]   ALL = NOPASSWD:  POWEROFF

Important Note: If you make any mistakes, correct them with the commands at the bottom of the visudo screen only. If you are running visudo in eterm, use the Function and Enter Keys as listed at the bottom. If you are running visudo in gnome-terminal, choices made from the menu bar at the top or with fast keystrokes are frequently erratic -- therefore, save the file and close visudo, using the left mouse button only. Keystrokes are as follows:

2Save > Save > 10Quit

If you have several users, you may want to create a POWEROFF group in sudoers. You can also assign users to the POWEROFF group in the sudoers file. For directions, refer to:

http://www.debian-administration.org/articles/33

3. Add a PowerOFF icon to the IceWM toolbar. Do this as user (not root) by logging in for each of your users and performing the following steps:

(1) At the terminal, as root:

su   [user-name]       [note: do NOT use "su - [user-name]"]
icemc

(2) Then File > Open > Toolbar. Choose the entry on your toolbar AFTER which you want PowerOFF to be installed. Right click on that entry. From the dropdown menu, left click on "Insert Application".

(3) The bottom of icemc screen now provides three lines for your new command. (Do not use quotes.)

_1) On the first line, "Name", enter "PowerOFF".

_2) On the second line, "Icon", enter "PowerOFF".

_3) On the third line, "Exec", enter:

sudo   /sbin/poweroff

(4) Then File > Save; File > Exit.

(5) Restart IceWM by clicking on the IceWM icon at the beginning of the toolbar. Then click Logout > Restart IceWM. Your new PowerOFF icon will appear on the toolbar. Repeat step #3 above for all users.

4. If you want to create a desktop icon for PowerOFF in Gnome, do so in the usual manner, using "sudo /sbin/poweroff" for the command.

****************************************************************************

Fine-Tuning Your LTSP Network to Ignore Routers & Other DHCP Servers

If your network consists of an LTSP server, dedicated LTSP workstations (i.e., running only LTSP), and other computers with STATIC IP's running various other non-LTSP operating system, you have successfully setup a basic LTSP network.

HOWEVER, if your network contains LTSP workstations that also boot another operating system as well as LTSP, computers with DYNAMIC IP addresses, another computer acting as a DHCP server, or a router with DHCP activated, you are NOT finished.

In the second scenario, any of the non-LTSP computers in the network with a dynamic IP address can be assigned an IP address by the LTSP server. Although these other computers cannot complete a successful connection with the LTSP server, each will receive a non-functional IP address on a non-functional subnet.

The only solution for this problem is to assign static IP addresses to ALL non-LTSP computers. My attempts at changing the dhcp port from 67 to 1067 for LTSP were unsuccessful. Although there were reports about this workaround several years ago, it cannot be accomplished as easily today. (This approach was used in Edubuntu as recently as August 2006 and required rewriting scripts and recompiling the kernel.)

Conversely, in the second scenario, it is also possible for an LTSP workstation to be assigned an IP address controlled by the extraneous DHCP server and be unable to successfully logon to the LTSP server. (You need not be concerned with a router acting as a DHCP server because the router responds so slowly: your LTSP server will have already assigned an IP address before the router has had a chance to process the request!)

For this problem there is a workable solution:

LTSP workstation MAC addresses can be used in the static-version of dhcpd.conf to restrict the LTSP server to assigning IP addresses and exporting boot code only to those computers which are listed in the dhcpd.conf file.

The static-version of dhcpd.conf can also contain a specific identification code, the Vendor Class Identifier of "Etherboot," which your workstation can be programed to ask of a DHCP server before it will accept any proffered IP number from that server. Use of this feature prevents your workstation from accepting an IP address from the router or non-LTSP server. The workstation requires a specially modified boot rom image to initiate this extra step during the workstation's boot process.

To institute this extra security step, follow the directions below only after you have demonstrated that your system is setup correctly using dynamic dhcpd.conf.

Step 1. Adding VCI and MAC addresses to dhcpd.conf.

1. Modify dhcpd.conf.

(1) Save your working copy of dhcpd.conf.

cp  dhcpd.conf   dhcpd.conf-working-dynamic

(2) Copy the static version of dhcpd.conf from the Pre-Configured Files section to a new text file, using gedit.

(3) Copy all IP addresses from the working dynamic version to the static version.

(4) Leave or remove "#" from the "next-server" line. See directions in the dhcpd.conf file's header. Change the server IP address to that of your server:

#  next-server                  192.168.2.100;     # <--Change IP

(5) Uncomment the following line:

# option vendor-encapsulated-options 3c:09:45:74:68:65:72:62:6f:6f:74:ff;

(6) Obtain the MAC addresses of each LTSP workstation (see Comments section for directions).

(7) For each of your workstations make a workstation host name entry ("host ws101", "host ws102", etc.), and list the workstation's MAC address after the "hardware ethernet" entry. The same host names must also be entered in the /etc/hosts file.

(8) Save your updated static version as /etc/dhcp3/dhcpd.conf by overwriting the previous version.

(9) Restart the dhcp demon so that your revised version is loaded:

ps   -A                    [find process-# of dhcpd3, e.g. 1043]
kill  dhcpd3-process-#     [e.g., "kill  1043"]
/usr/sbin/dhcpd3 

Step 2. Obtain a new boot rom containing VCI.

(1) Download another copy of the boot rom image you are using (.zdsk, .com) from www.romomatic.org. However, do not download the image immediately.

(2) Instead click on "Configure." On the new screen (version 5.4.2), 18 entries down, find the entry:

REQUIRE_VCI_ETHERBOOT

Place a check in the box.

(3) Select "Get ROM" at the bottom of the page, and download the modified rom image.

(4) Substitute the modified rom image for the rom image you were previously using on the floppy/hard disk on your LTSP workstation. (Follow directions on the romomatic web page for copying the rom image to your floppy or hard disk.)

3. Repeat "Step 2. Obtain a new boot rom" above, obtaining a new boot rom image which is specific for each model of network card in use in your workstations. Install the appropriate rom image into the corresponding workstation.

4. Successfully boot each workstation to confirm that the new entries in dhcpd.conf are correct for each workstation.

****************************************************************************

COMMENTS & NOTES

1. SECURITY PRECAUTIONS.

(1) You may want a fire wall; this minimum install does not include one.

(2) SSH needs to be installed if absolute security of data is desired.

2. MARGINAL NETWORK INTERFACES & HUBS. Component failure will prevent the workstation from connecting to the server. This may result in the boot process halting right after the 'pivot_root' takes place on the workstation. The problem is thought to be a result of packets sent by the server which are damaged on the way to the workstation's CPU.

Hubs and switches may contain certain ports that cause this error while other ports function properly on the same hub or switch. However, in my case it was the two ECS motherboards with built-in NICs (VIA-rhine chipset, VT6103) that caused the halt. I had to turn off the onboard lan and install a separate Rtl-8139 chip network card in each ECS computer to solve the problem. Although the motherboard lans were adequate for surfing the internet, they were inadequate for LTSP networking.

3. ROUTERS. If you are using a router in your network which has DHCP enabled, you need to disable the router's ability to assign IP addresses in the range which includes xxx.xxx.xxx.100 to xxx.xxx.xxx.110, the range used by LTSP. If you do NOT do this, occasionally your LTSP server may try to assign the same IP address that your router has already assigned. Alternatively, when one of the non-LTSP computers on your network boots up, it may be assigned an IP address by your LTSP server instead of the router.

Directions for preventing these problems are found above in the section "Fine-Tuning your LTSP Network".

4. UNIQUE WORKSTATION PARAMETERS. By selecting a workstation entry format which uses the MAC address of each workstation, you can pass specific parameters to each workstation in both the dchcp.conf and lts.conf files.

To obtain the MAC address (not to be confused with IP address) for a workstation, unplug its network cable and allow it to boot from the .zdsk or .com image. The computer will hang and the MAC address will be displayed on the booting workstation's screen.

If you are using ISA network cards, you can also obtain the NIC driver name and IO address and interrupt of the workstation's NIC from the workstation screen using the same process.

5. PARTITIONING & BACKUP. The operating system in which a backup program runs determines how you will partition your hard drive. If you use a linux program for partitioning and then try to backup with a Windows (DOS) program, your backup program may be unable to run because of "errors" on the partitions. And if you try to use a Windows program to enlarge or move a Windows partition which was created by a linux program, you may damage the Windows partition so that it cannot be backed up.

Thus, if you are going to use a linux backup program, partition with a linux program. If using a DOS backup, partition with DOS. If you decide to enlarge/reduce a partition size, it must be done with a program that runs in the SAME operating system (linux, DOS) that you originally partitioned from.

6. ISA & PCI NETWORK CARDS. You will have to do some searching on the rom-o-matic site to find ISA boot images. The image for the common ISA NE2000 chip was not in the current version, 5.4.0. I found it in an older version, 5.3.2, listed as "ne - drivers/net/ns8390".

I was not successful in getting computers with ISA cards to connect properly with the server. The ISA cards were NE2000 compatible cards running at 10 Mbps and did not seem to sync well with the servers's NIC running at 100 Mbps. This may have been a router problem.

If you are using D-Link 530TX+ PCI network cards, the packet drivers on the cdroms and floppies may not work. You will have to download the most recent driver from the manufacturer.

7. SATA HARD DRIVES. With the advent of SATA hard drive the use of a master boot record (MBR) boot manager has become more difficult. For instance, the boot manager I like, OSL-2000 which installs in on MBR, will not install on a SATA drive. I have had to switch to Partition Magic's boot manager which is installed in a DOS partition.

The DOS programs Partition Magic and Drive Image 2002 have become erratic when used with SATA drives or very large drives.

Drive Image run from within Windows XP crashes when it reboots to DOS on a SATA hard to start the backup. The MBR is overwritten in the process and the hard drive is unbootable. (You can recover from this error by using MbrWiz to boot your hard drive to the Windows XP partition.) A Drive Image backup must always be INITIATED from a DOS partition when using it with a SATA hard drive!

Partition Magic, on the other hand, hangs on large hard drives when booted from DOS. But it will run successfully on the same hard drive from within Windows XP.

****************************************************************************

PRE-CONFIGURERED FILES

1. How to copy the Sample Files in this document directly to your Linux installation:

(1) Browse to the LTSP Wiki. Find and open this article.

(2) Highlight the desired file by holding down the left mouse button while moving over the text.

(3) Open a terminal and start gedit.

(4) Paste the copied text by clicking on the middle mouse button.

(5) Save the file with the appropriate name.

This procedure is particularly important for the two versions of dhcpd.conf where misplaced brackets and semicolons will make the file unusable. If you try to type this file manually you will have errors!

2. How to edit the DOS files and insert your own data:

Many of the DOS files shown below have double-line entries: these are indicated by two successive lines, each starting with "rem". The first line identifies the data that goes in the second line; the second line is the data (i.e. the command) itself. In the samples, both lines are "commented out" with "rem" so that they will not be interpreted as commands. This is to prevent confusing errors when you first run the new file. Enter YOUR required data in the second line and remove "rem" at the beginning of that line only.

---

1. DHCPD.CONF

1) Two versions of dhcpd.conf are listed here. Install version #1, dynamic-dhcpd.conf, for dynamic workstations first. It is much easier to trouble-shoot.

2) Once you are up and running, you can switch to version #2, static-dhcpd.conf. It uses MAC addresses to assign static IP's and/or pass specific parameters to each workstation. Remember to rename whichever version you finally use to dhcpd.conf after copying it to the /etc/dhcpd3 directory.

3) Check that the LTSP operating files you are actually using are the same as those listed in the following two versions of dhcpd.conf. Check this by doing a directory listing ("ls -l") of the following two directories. If they are not, change dhcpd.conf to match the versions of the files in your server's tftpboot subdirectories:

/tftpboot/lts/

/tftpboot/lts/2.4.26-ltsp-3/

Version #1 -- dynamic-dhcpd.conf

##########
#
#   dynamic-dhcpd.conf version of /etc/dhcp3/dhcpd.conf
#    *** Rename to dhcpd.conf before using ***
#
#  FOR LTSP WORKSTATIONS WITH DYNAMIC IP ADDRESSES
#
#   (1) assignment of dynamic IP addresses to 10 workstations;
#   (2) workstations assigned addresses xxx.xxx.xxx.101 to xxx.xxx.xxx.110;
#   (3) server assigned IP address xxx.xxx.xxx.100 during Linux 
#       installation.
# 
#     
# How to Edit this File:
#   (1) IP addresses requiring change are marked "Change IP";
#   (2) IP file format = xxx.xxx.xxx.yyy;
#   (3) replace all IP addresses with your IP address;
#   (4) obtain your specific IP address information from dhcpd.conf.sample
#       file created when LTSP was installed;
#   (5) end each line with a ";" except after a parenthesis;
#       keep your "{   }" straight;
#       use "#" to prevent interpretation of text on the line beyond "#".
#
##  Beginning of file


# - In Debian 3.1 SARGE, the "next-server" statement should be commented
#   out; it is not needed and possibly harmful.
# - In Debian TESTING or UNSTABLE, or anything with dhcp3-server >= 3.0.3,
#   the "next-server" statement is needed or Etherboot will walk in 
#   circles saying "No IP address".  To activate, uncomment the line.
# next-server                  192.168.2.100;     # <--Change IP

ddns-update-style            none;
default-lease-time           21600;
max-lease-time               21600;
option subnet-mask           255.255.255.0;
option broadcast-address     192.168.2.255;     # <--Change IP
option routers               192.168.2.1;       # <--Change IP
option domain-name-servers   192.168.2.100;     # <--Change IP
option domain-name           "ltsp";            # <--Accept/Change
option root-path             "192.168.2.100:/opt/ltsp/i386"; # <--Change IP 
option option-128 code 128 = string;
option option-129 code 129 = text;
             
shared-network WORKSTATIONS {
   subnet 192.168.2.0   netmask 255.255.255.0 {          # <--Change IP     
 
     range dynamic-bootp 192.168.2.101   192.168.2.110;  # <--Change 2 IP's 
 
 
     use-host-decl-names         on;
     option log-servers          192.168.2.100;          # <--Change IP
     if substring (option vendor-class-identifier, 0, 9) = "PXEClient"
     {
     filename   "/tftpboot/lts/2.4.26-ltsp-3/pxelinux.0";  #<--Check version
     }
     else
     {

     filename   "/tftpboot/lts/vmlinuz-2.4.26-ltsp-3";  #<--Check version
     }
    }
   }

##  End of file
#
##########

---

Version #2 -- static-dhcpd.conf

##########
#
#    static-dhcpd.conf version of /etc/dhcp3/dhcpd.conf
#    *** Rename to dhcpd.conf before using ***
#
#  FOR LTSP WORKSTATIONS WITH ASSIGNED PERMANENT IP ADDRESSES
#
#   (1) assigns permanent IP addresses to 10 specific workstations;
#   (2) workstation addresses assignable in range of xxx.xxx.xxx.101 to
#       xxx.xxx.xxx.110;
#   (3) server IP address xxx.xxx.xxx.100 assigned during Linux 
#       installation;
#                 
# How to Edit this File:
#   (1) IP addresses requiring updating are marked as "Change IP";
#   (2) IP file format = xxx.xxx.xxx.yyy;
#   (3) replace all IP addresses with IP addresses
#       obtained from your dhcpd.conf.sample file installed by LTSP;
#   (4) assign each workstation a different name;
#   (5) each host workstation must also have an individual MAC address;
#       obtain the MAC address from /var/log/syslog while that specific
#       workstation is attempting to boot;
#   (6) clone additional workstations as needed, assigning each a different
#       IP address between xxx.xxx.xxx.101 and xxx.xxx.xxx.110;
#       Note: each workstation has 2 parentheses "{ }" associated with it!
#   (7) names of the workstations must also be entered in */etc/hosts* file;
#   (8) remember to end each line with ";" except after parenthesis;
#       keep your "{   }" straight;
#       use "#" to prevent interpretation of text on the line beyond 
#       the "#";
#   (9) If you need to pass parameters on the kernel command line to a
#       workstation, you can do it with option-129.  In order for Etherboot
#       to look at option-129, you MUST have option-128 set to a specific
#       value.  The value is a special Etherboot signature of
#       'e4:45:74:68:00:00'.
#
#       Add these two lines to the each host entry that needs special
#       parameters:
#          option option-128     e4:45:74:68:00:00;       # Do NOT change
#          option option-129     "NIC=ne IO=0x300";       # An example
#
##   Beginning of file


# - In Debian 3.1 SARGE, the next-server statement should be commented out;
#   it is not needed and possibly harmful.
# - In Debian TESTING or UNSTABLE, or anything with dhcp3-server >= 3.0.3,
#   the next-server statement is needed or Etherboot will walk in 
#   circles saying "No IP address".  To activate,  uncomment the line.
# next-server                  192.168.2.100;     # <--Change IP


#  Uncomment the following option line if your boot rom contains the
#   modification for using REQUIRE_VCI_ETHERBOOT.  This option initiates
#   the Vendor Class Identifier of "Etherboot":
# option vendor-encapsulated-options 3c:09:45:74:68:65:72:62:6f:6f:74:ff;


ddns-update-style            none;
default-lease-time           21600;
max-lease-time               21600;
option subnet-mask           255.255.255.0;
option broadcast-address     192.168.2.255;     # <--Change IP
option routers               192.168.2.1;       # <--Change IP
option domain-name-servers   192.168.2.100;     # <--Change IP
option domain-name           "ltsp";            # <--Change/Retain
option root-path             "192.168.2.100:/opt/ltsp/i386";  # <--Change IP
option option-128 code 128 = string;
option option-129 code 129 = text;

subnet 192.168.2.0 netmask 255.255.255.0 {       # <--Change IP
    range  192.168.2.101  192.168.2.110;         # <--Change 2 IP's
       use-host-decl-names      on;
       option log-servers       192.168.2.100;   # <--Change IP
    }

    host ws101 {
        fixed-address         192.168.2.101;         # <--Change IP
        hardware ethernet     00:30:bd:1e:d9:e2;     # <--Change MAC
        filename    "/tftpboot/lts/vmlinuz-2.4.26-ltsp-3";  
                                                 #<--Check version
    }

    host ws102 {             
        fixed-address         192.168.2.102;         # <--Change IP
        hardware ethernet     00:0d:dd:a2:a0:25;     # <--Change MAC
        filename    "/tftpboot/lts/vmlinuz-2.4.26-ltsp-3";
                                                  #<--Check version
    }

#
##  End of file
#
##########

---

2. CONFIG.SYS

rem c:\config.sys
[menu]
menuitem=DOS, DOS Boot
menuitem=LINUX, LINUX Boot
menuitem=LTSP, LTSP Boot
menudefault=DOS,10
[LINUX]
rem insert Linux shell command here
[DOS]
stacks=0,0
device=c:\dos\himem.sys
device=c:\dos\emm386.exe  X=C000-C7FF   noems
dos=high,umb
rem ***Insert your own cdrom driver in the next line
rem  devicehigh=c:\dev\vide-cdd.sys  /d:msc000
files=30
[LTSP]

---

3. AUTOEXEC.BAT - minimal version

rem  c:\autoexec.bat (minimal version)

@echo off
goto %config%

:linux
rem  ---------------------------------------------------------------
rem --  Linux will not run with any type of mouse installed, high or low.
rem  ---------------------------------------------------------------
rem ***Insert your own Linux pen version start command in the next line
rem  c:util\slinux.com
goto end

:dos
path=c:\;c:\dos;c:\util;
loadhigh=c:\dos\mscdex.exe /D:MSC000
loadhigh=c:\dos\doskey
rem ***Insert your own mouse driver in the next line
rem  c:\dev\ctmouse
rem ***Insert your own screen blanker in the next line
rem  loadhigh=c:\dev\blank-it   /m   10
cls
echo.
echo.
echo  1)  To Deactivate Screen Saver, move Mouse or hit Space Bar.
echo  2)  Type "DI" to start Disk Image.
echo  3)  Type "PM" to start Partition Magic.
echo.
echo.
rem ***Insert the drive for your CDROM in the next line
rem  echo  Note:  G: = CDROM
goto end

:ltsp

rem  ***LTSP must be run with a "bare" autoexec.bat and config.sys
c:\ltsp\rtl-8139
goto end

:end

---

4. SOURCES.LIST -- Sarge

##########
#

#/etc/apt/sources.list

deb   http://ftp.us.debian.org/debian/   sarge   main   non-free   contrib
deb-src   http://ftp.us.debian.org/debian/   sarge   main   non-free   contrib

deb   http://security.debian.org/   sarge/updates   main   contrib   non-free

#
##########

4. SOURCES.LIST -- Etch

######################
#
#  /etc/apt/sources.list -- ETCH version
 
# deb cdrom:[Debian GNU/Linux testing _Etch_ - Official Snapshot amd64 Binary-1 (20060808)]/ etch main

deb http://ftp.us.debian.org/debian/ etch main non-free contrib
deb-src http://ftp.us.debian.org/debian/ etch main non-free contrib

deb http://security.debian.org/ etch/updates main contrib non-free
deb-src http://security.debian.org/ etch/updates main contrib non-free

#
#########

---

5. LTS.CONF

##########
#
# /opt/ltsp/i386/etc/lts.conf
#
# Config file for the Linux Terminal Server Project (www.ltsp.org)
#

[Default]
     SERVER             = 192.168.2.100   #Insert your server's IP
     XSERVER            = auto
     X_MOUSE_PROTOCOL   = "IMPS/2"
     X_MOUSE_DEVICE     = "/dev/psaux"
     X_MOUSE_RESOLUTION = 400
     X_MOUSE_BUTTONS    = 5
     USE_XFS            = N
     SCREEN_01          = startx

#
###########

---

6. LTSP.BAT

rem  c:\ltsp\ltsp.bat

@echo off
cls
echo.

rem SECTION 1
echo The WORK STATION is loading its packet driver ..........
echo.
rem -- The packet driver for Belkin is in the next line
F5D5000  0x7e
echo.

rem SECTION 2
echo The Work Station will now start the REMOTE SERVER ..........
rem -- The following command must contain the Server network card's MAC #
doswol  00:50:BA:8A:75:8B
echo.

rem SECTION 3
echo The SERVER is now booting.  Hit any key for immediate LOGON ..........
rem  -- The following command starts the count-down clock
wait4  +1:40  /B  /D  /C12
echo.

rem SECTION 4
echo The SERVER and WORK STATION are exchanging files prior to LOGON .........
echo.
rem  -- The ROM image for the Belkin NIC is
rtl-8139

---

7. AUTOEXEC.BAT - deluxe version

rem  c:\autoexec.bat  (deluxe version)

@echo off
goto %config%

:linux
rem  ---------------------------------------------------------------
rem  Linux will not run with any type of mouse installed, high or low
rem  ---------------------------------------------------------------
rem ***Insert your own Linux pen version start command in the next line
rem  c:util\slinux.com
goto end

:dos
path=c:\;c:\dos;c:\util;                           
loadhigh=c:\dos\mscdex.exe  /D:MSC000
loadhigh=c:\dos\doskey
rem ***Insert your own mouse driver in the next line
rem  c:\dev\ctmouse
rem ***Insert your own screen blanker in the next line
rem  loadhigh=c:\dev\blank-it  /m  10
cls
echo.
echo.
echo  1)  To Deactivate Screen Saver, move Mouse or hit Space Bar.
echo  2)  Type "DI" to start Disk Image.
echo  3)  Type "PM" to start Partition Magic.
echo.
echo.
rem ***Insert the drive for your CDROM in the next line
rem  echo  Note:  G: = CDROM
goto end

:ltsp
rem ***LTSP must be run with a "bare" config.sys and autoexec.bat
path=c:\;c:\ltsp;c:\dos;c:\util;
c:\ltsp\ltsp
goto end

:end

---

8. INTERFACES -- Version 8-A -- SARGE

### /etc/network/interfaces -- SARGE version

#
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback

### The primary network interface - dynamic
#auto eth0
#iface eth0 inet dhcp

### The primary network interface - static
auto eth0
iface eth0 inet static

address   192.168.2.100    # IP address of your LTSP server 
netmask   255.255.255.0    # do not change
broadcast 192.168.2.255    # change first 3 triplets of IP address
gateway   192.168.2.1      # Your routers' address-usually ends with 1

#
### end of file

8. INTERFACES -- Version 8-B -- ETCH

###################
#
# /etc/network/interfaces -- ETCH version

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
allow-hotplug eth0
iface  eth0  inet  static
  address   192.168.2.100     # IP address of your LTSP server
  netmask   255.255.255.0     # Do not change
  broadcast   192.168.2.255   # Change first 3 triplets of IP address
  gateway   192.168.2.1       # Your router's address-usually ends with 1

#iface eth0 inet dhcp

#
### end of file

---

Changelog for: How-To Install LTSP 4.1 in Debian 3.1 Sarge & Etch

4 Nov. 2006. LTSP & amd64 notice added.

26 Sept 2006. Remote xserver crashes during workstation boot (due to recent changes in LTSP?) when using Preconfigured lts.conf file. Lts.conf revised to function properly again with optical mouse.

16 Aug 2006. Additional directions added for Etch installation. New section added on preventing workstations from accepting IP addresses from non-LTSP DHCP servers.

1 Feb 2006. Newer routers will not work with DOSWOL default settings. New settings provided. Directions provided for setting up PowerOFF desktop icon to shutdown remote server.

23 Nov 2005. Entire section on deluxe hard drive installation revised.

---