Linux Terminal Server Project
System requirements for an LTSP network vary depending on the number of concurrent diskless workstations accessing the server and the applications they will be running. The two most important things to consider here are the server's available memory and the speed of the network. Even though a 10Mb network can handle a large number of diskless workstations running console-based applications, a faster (100Mb) network is required if the workstations are to run remote X sessions and productivity applications like StarOffice. The minimum server configuration for an LTSP network is a Pentium-class computer with at least 64MB RAM and a 2GB hard drive. On the workstation side, a 486 or K5 computer with 16MB RAM and a 1MB video card (for X) can get the work done.
The whole LTSP network operation depends on the good condition of network cards, hubs and cabling to run properly and smoothly. Please be sure to check them prior to any installation.
LTSP tools currently run on the following Linux distributions:
Red Hat 6.0, 6.1, 6.2 and 7.0
SuSE 6.2, 6.3, 6.4, 7.1 and 7.2-beta
Debian 2.0, 2.1 and 2.2
Caldera eDesktop 2.3, 2.4 and eServer 2.3
All the software and documentation needed to run an LTSP network can be obtained from the download section of their web site, http://www.ltsp.org/. The necessary precompiled packages come in both RPM and TGZ formats. Remember to read the documentation before attempting to install the software and scripts.
The Quick Installation requires that your installation meets the following criteria:
You are installing on a Red Hat 6.0, 6.1, 6.2 or 7.0-based system or a Mandrake 7.2-based system.
The server will have an IP address of 192.168.0.254.
The workstations will have addresses in the range of 192.168.0.1 through 192.168.0.253.
Applications will run on the server, displaying output on the workstations.
You are using DHCP.
Download the LTSP RPM packages from the LTSP download site, http://www.ltsp.org/.
lts_core-2.xx-xx.i386.rpm—the Core LTSP package, which contains the root filesystem, configuration utilities and documentation for the workstations.
lts_kernel_xxxx-2.xx-xx.i386.rpm—precompiled kernels for diskless booting. Choose the appropriate kernel for the network card of the diskless workstation.
lts_xxxx-2.xx-xx.i386.rpm—precompiled X servers. Choose the appropriate X server for the video card of the diskless workstation.
Verify that dhcpd is installed on the server. Run the following command:
rpm -qa | grep dhcp
It should report a line like:
dhcp-2.0-5If it doesn't, then you need to load the DHCP RPM from the Red Hat installation CD.
Once the installation of the above packages is complete, you need to move to the /tftpboot/lts/templates directory. Several files there will configure the system files on your server. Each one of these files is responsible for one system file. Take a look at those files, and make sure you agree with what they are going to do. They can potentially make your system vulnerable to intrusion. You may wish to make changes to the system files manually. If you want to do it automatically, then run the ltsp_initialize command:
cd /tftpboot/lts/templates ./ltsp_initialize
Copy the /etc/dhcpd.conf.example file to /etc/dhcpd.conf. Modify the dhcpd.conf file to include the MAC address of the network card in the workstation. Then, add the following line to the /etc/hosts file:
192.168.0.1 ws001You should next edit the /tftpboot/lts/ltsroot/etc/lts.conf file to make sure the entries are correct for the workstation. Then reboot the server and turn on the workstation. You should get a graphical login prompt on the workstation. You can log in using any user ID available on the server.
As you can see, installation of an LTSP network is straightforward, and it can be up and running in a few minutes. Don't forget to follow the instructions carefully, and if you have any difficulties, read the troubleshooting section of the documentation. The project's mailing list is also a good source for solving problems, finding out about new software developments and learning from other users' experiences.
Practical Task Scheduling Deployment
July 20, 2016 12:00 pm CDT
One of the best things about the UNIX environment (aside from being stable and efficient) is the vast array of software tools available to help you do your job. Traditionally, a UNIX tool does only one thing, but does that one thing very well. For example, grep is very easy to use and can search vast amounts of data quickly. The find tool can find a particular file or files based on all kinds of criteria. It's pretty easy to string these tools together to build even more powerful tools, such as a tool that finds all of the .log files in the /home directory and searches each one for a particular entry. This erector-set mentality allows UNIX system administrators to seem to always have the right tool for the job.
Cron traditionally has been considered another such a tool for job scheduling, but is it enough? This webinar considers that very question. The first part builds on a previous Geek Guide, Beyond Cron, and briefly describes how to know when it might be time to consider upgrading your job scheduling infrastructure. The second part presents an actual planning and implementation framework.
Join Linux Journal's Mike Diehl and Pat Cameron of Help Systems.
Free to Linux Journal readers.Register Now!
- SUSE LLC's SUSE Manager
- My +1 Sword of Productivity
- Managing Linux Using Puppet
- Non-Linux FOSS: Caffeine!
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- Tech Tip: Really Simple HTTP Server with Python
- Doing for User Space What We Did for Kernel Space
- Rogue Wave Software's Zend Server
- Parsing an RSS News Feed with a Bash Script
- SuperTuxKart 0.9.2 Released
With all the industry talk about the benefits of Linux on Power and all the performance advantages offered by its open architecture, you may be considering a move in that direction. If you are thinking about analytics, big data and cloud computing, you would be right to evaluate Power. The idea of using commodity x86 hardware and replacing it every three years is an outdated cost model. It doesn’t consider the total cost of ownership, and it doesn’t consider the advantage of real processing power, high-availability and multithreading like a demon.
This ebook takes a look at some of the practical applications of the Linux on Power platform and ways you might bring all the performance power of this open architecture to bear for your organization. There are no smoke and mirrors here—just hard, cold, empirical evidence provided by independent sources. I also consider some innovative ways Linux on Power will be used in the future.Get the Guide