19/08/2003 Eugene Coetzee (document best viewed in the vi text editor) First things first: ------------------ - Prepare your Slackware distribution with full graphical (x-windows) support - The author didn't test this script with anything else other than Slackware 8.0 (Linux kernel 2.2.19) and ltsp_core-3.0.9 - The author (by his own confession) doesn't really know how to use a mouse properly - the assumption is that you are using a console environment to do the installation and know how to use a command line text editor like vi - This write-up is not intended to replace the existing instructions for installation - you need to follow them religiously using the install.sh and slackware.sh scripts supplied with this tarball Basics ------ - You need the following packages from http://sourceforge.net/projects/ltsp 1. ltsp_core-3.0.9-i386.tgz 2. ltsp_kernel-3.0.9-i386.tgz 3. ltsp_x_core-3.0.4-i386.tgz 4. ltsp_x_fonts-3.0.0-i386.tgz - There is very useful documentation available from http://www.ltsp.org - in particular the full HTML documentation entitled "LTSP - linux Terminal Server project - v3.0" - Everything starts off with ltsp_core-3.0.9-i386.tgz where the supplied slackware.sh script must be added to the unpacked root directory: ltsp_core does all the basic setup work and is the only package that needs to be modified - You need to modify the supplied install.sh script (for ltsp_core) or use the one supplied with this tarball Modifying install.sh -------------------- install.sh reads the slackware version from /etc/slackware-version and then executes the appropiate slackware.sh script using a soft link The included install.sh should work fine. Soft linking slackware-8.0.0.sh -------------------------------- ln -s slackware-8.0.0.sh slackware.sh (in the unpacked ltsp_core directory) slackware.sh ------------- slackware.sh does the magic by creating a set of template scripts that are executed as a last step of the installation I hacked the original redhate.sh script for this purpose so read through the slackware.sh script to get an idea of what the script does. Affected system files --------------------- The main difference between distros are the location of system files and the way that startup scripts /etc/rc.d/* are executed. In the case of Redhat versus Slackware the biggest differences are the path to files kdmrc and syslog.conf. There is also no update-inetd or chkconfig commands to automatically update startup scripts under Slackware. The following system files are either modified or created. /etc/X11/xdm/Xaccess /etc/x11/xdm/Xservers /etc/X11/xdm/Xsetup_workstation /etc/X11/xdm/xdm-config /etc/X11/gdm/gdm.conf /etc/X11/gdm/init/Default (symbolic link to Xsetup_workstation) /opt/kde/share/config/kdmrc /etc/dhcpd.conf.example (must be manually renamed to /etc/hdpcd.conf later) /etc/exports /etc/hosts.allow /etc/inetd.conf /etc/inittab /etc/syslog.conf It is highly recommended that you BACKUP these files BEFORE you attempt the installation. Things that must be done manually after running ltsp_initialise --------------------------------------------------------------- So you have run install.sh and ltsp_initialise (in this order) The following stuff wasn't worth automating and must be verified/modified using a text editor (sorry :{ Make sure that the following symbolic link exists: /etc/X11/gdm/Init/Default -> ../../xdm/Xsetup_workstation In file /etc/rc.d/rc.inet2 check for lines: /sbin/rpc.portmap /etc/rc.d/rc.nfsd start In file /etc/inetd.conf check for line: tftp dgram udp wait nobody /usr/sbin/tcpd in.tftpd If everything else fails... --------------------------- I have included examples of the files "as is" on my system so that you can compare and perhaps correct problems. See the examples directory. TODO ---- Go to sleep now. Contact ------- You can send me comments, suggestions and bug reports at but I would appreciate if you could fix things yourself.