Linux.com

Feature: Linux

Expert shares secrets to saving thousands with K12LTSP

By Bruce Byfield on January 25, 2007 (8:00:00 AM)

Share    Print    Comments   

The K12 Linux Terminal Server Project (K12LTSP) is a thin client distribution designed for use in schools. Recently, I was invited by Robert Arkiletian, a K12LTSP contributor, to see the software in action in his computer lab at Eric Hamber Secondary School in Vancouver, Canada. We talked about the system requirements for a K12LTSP installation, investigated the available software, and discussed the success of Arkiletian's own lab, which has saved his school thousands of dollars in hardware costs.

Masterminded by Eric Harrison, an employee of the Multnomah Education Service District in Portland, Oregon, K12LTSP is available in both Fedora Core and CentOS-based editions. The distribution is in widespread use throughout North America and parts of Europe, and, together with Edubuntu and Skole Linux, is generally considered one of the leading educational versions of GNU/Linux.

Arkiletian's lab consists of a single server and 30 clients. The lab's size makes it less complex than some K12LTSP installations that are deployed school-wide, but still large enough to make it a representative case study.

Setup and installation

K12LTSP uses the Anaconda installer, and can be used as a workstation distribution. Unsurprisingly, however, installing the software as a thin client is more complicated. The K12LTSP site gives a listing of hardware requirements for servers and clients, but Arkiletian stresses that these are minimums. Based on his experience over the last three years, he lists recommended requirements that are generally more demanding.

For the server, Arkiletian favors a dual processor, so that a runaway process can be killed without disrupting a class in session. He also advises two SCSI hard drives, although he allows that some of the recent SATA drives might be fast enough and reliable enough to be suitable replacements. Either way, he suggests that the hard drives be set up to mirror each other in a RAID 1 array. The server should have 100MB of RAM per client, rounded upwards -- twice what the K12LTSP site suggests -- in order to accommodate the use of memory-hungry programs such as OpenOffice.org. It also requires two Ethernet cards: one to create a private network on a hub for the clients, and one to connect to the rest of the network.

For client machines, clock speed is relatively unimportant, although anything less than a 100MHz Pentium is likely to have an ISA bus and require manual configuration. Nor is more than 4MB of memory on the video card needed in a typical class. What is important is RAM. Arkiletian finds that the 64MB listed on the K1LTSP site sometimes results in hard disk thrashing. He recommends doubling that, as well as using a light window manager such as IceWM instead of GNOME or KDE. In addition, clients need a 100Base-T Ethernet card. Older client machines may also need USB ports so that students can use memory sticks.

Software selection

In the latest version, K12LTSP's packages are based on Fedora Core 6, with additions from Fedora Extras. The packages include standard free software for desktops, including Firefox and OpenOffice.org, which Arkiletian describes as the programs most widely used in his school outside of computer classes.

However, the distribution also includes its own unique touches, often in the form of scripts for specific purposes, such as integrating with other operating systems or restoring the default desktop on the clients, and are probably unknown to most teachers beforehand except, in some cases, as an icon on the desktop.

From the end user's perspective, the most obvious difference between this operating system and less specialized distros is the extensive range of educational software K12LTSP provides, such as Tuxtype, gPeriodic, and Celestia, the 3-D space simulator. In the latest version, the list of educational software has grown so long that it is divided into two sections -- one for kindergarten to grade five, and one for grades six and above.

For teachers, the outstanding feature of K1LTSP is Fl_TeacherTool. Written by Arkiletian, Fl_TeacherTool allows teachers to interact with client machines via VNC. At a glance, teachers can see what clients are in use, and what processes each is running. By clicking the Monitor button, they can see the desktops of other clients on their own machine. If a student is doing something he shouldn't, the Control button lets teachers take control of the student's desktop.

In addition, Fl_TeacherTool has several controls specifically for teaching. With the Distribution function, teachers can send files to students. Broadcast is even more powerful, sending copies of whatever the teacher is working on directly to one or more students' desktops so that they can follow along, and eliminating the need for a white board or handouts. Broadcast is especially useful in detailed work such as computer programming, where students need to pay close attention to what is happening.

The main drawback of Fl_TeacherTool is its use of the Fl toolkit rather than more widely used GTK or Qt. Yet, despite the name, Fl_TeacherTool is not just for teachers; potentially, it could be used by any administrator who needs to interact with users.

Advantages and disadvantages

After running his K12LTSP lab for nearly three years, Arkiletian sees distinct advantages to client/server computing. Because it uses thin clients, maintenance is low. Software does not have to be installed on each client -- although the option is available -- and clients can be swapped out easily when they fail. "It turns clients into an appliance," Arkiletian says.

More importantly, running K12LTSP gives new life to old labs. Some of the machines in Arkiletian's lab are seven or eight years old, and still in service long after their use as workstations is past. Not only are they kept out of landfills, but running them is a major cost-saver. Even with memory upgrades to client machines and a state-of-the-art server, Arkiletian estimates that his lab cost only $4,000 to set up -- about a tenth the cost of buying replacement workstations. More recently, the money that his lab has saved over the years has allowed his school to invest in a new Mac OS X lab, giving students a chance to explore a variety of different computing environments.

At the same time, Arkiletian admits that K12LTSP labs have their limitations. They are suited only to standard computing. For memory-intensive activities such as animation, they are impractical regardless of how much RAM is in the servers and clients, because the memory swapping is too frequent. However, for the average class, the environmental, economic, and pedagogical arguments that can be made in favor of K12LTSP are exactly the sort that can persuade school boards to experiment with free software.

Bruce Byfield is a computer journalist who writes regularly for NewsForge, Linux.com, and IT Manager's Journal.

Bruce Byfield is a computer journalist who writes regularly for Linux.com.

Share    Print    Comments   

Comments

on Expert shares secrets to saving thousands with K12LTSP

Note: Comments are owned by the poster. We are not responsible for their content.

New Version has Spotlighting

Posted by: Anonymous Coward on January 26, 2007 05:32 AM
The latest version of Fl_TeacherTool has a feature called Spotlighting. It allows a selected student to control a Broadcast. Hence, individual students can be called upon to display their ability while being watched by their peers. Great for programming classes.

Robert Arkiletian

#

Also a CentOS version with long-term support

Posted by: Anonymous Coward on January 26, 2007 07:37 AM
I see Robert all the time on the K12LTSP list (hi!).

There are two versions of K12LTSP--the Fedora version, described in the article, and the CentOS (or "EL", for "Enterprise Linux") version. At home, I run the CentOS version of K12LTSP on a dual-AthlonMP 1.2GHz machine. My terminals are Pentium-166's from 1997 and have 32 to 64MB DRAM and regular ol' 3Com 3C905x 10/100 NIC's in them. Sound is handled by SoundBlaster 16 and AWE-32 cards. Video is anything from Diamond Stealth64 to Matrox Millenium G400. I installed MPlayer to get the WMV and QuickTime stuff going, for those who need that. Everything *Just Works.*

The nice thing about the CentOS version is that I don't have to upgrade my K12LTSP server to the next Fedora release every 6 months to a year. In some environments, that can be a real blessing.

#

ref conf

Posted by: Anonymous Coward on January 26, 2007 10:51 AM
post hardware and sofware tutorials on curriki.org?

#

The Client horsepower can be clustered as well?

Posted by: Anonymous Coward on January 26, 2007 11:39 AM
There was nothing in the article about being able to cluster the client PC's horse power with the servers?

Is this possible?

StartCom Linux's multi-media version uses Fedora as well, and it uses the ability to cluster out of the gate, so to speak.

If possible with K12LTSP, then is there info about this available?

This spring's release of Edubuntu should be interesting as they are still working out making that LTSP release up to somewhere near and even PAR with the K12LTSP Fedora version (getting close but not there yet, by this spring maybe)?

For all LTSP installs, FireFox is an obscene RAM hog, and the folks at Mozilla really should clue into a need for a lighter MULTI-USER friendly version for these LTSP releases. For now, it might be wise to look at other browsers and forget about Mozilla's browsers for LTSP installs.

#

OpenOffice.org another RAM oinker

Posted by: Anonymous Coward on January 30, 2007 10:52 AM
OpenOffice.org is the other memory pig. Both it and Firefox could stand to use much less DRAM. The thing is, Firefox is necessary from a mind-share point of view (it's also proved very popular on MS Windows), and OpenOffice.org is needed for technical reasons (MS Office proprietary file formats). So we really do need both programs.

However, in LTSP environments, remember that we get to take advantage of shared libraries, etc. So, for one user, OpenOffice.org might suck up 100MB, but subsequent users will use much less per user.

I agree, though, a Web browser shouldn't use that much DRAM in the first place. That's why I now use Konqueror most of the time.<nobr> <wbr></nobr>:-)

#

fltk a drawback?

Posted by: Anonymous Coward on January 26, 2007 12:32 PM
Even though FLTK it is not as popular as GTK or Qt, FLTK it is much more memory efficient, fast and with less dependencies than those more popular toolkits. Granted, it doesn't look as nice as them, or does all that they do but it does what it does pretty well.

Besides, popularity of a toolkit should never be used as a measure of quality as the author seem to imply. Any good programmer worth its salt uses the best tool for the job regardless of how popular it is: If the tool doesn't requires all the bell and whistles of Qt/GTK and may be used on slow machines with very little memory (As computers are in many schools) then using GTK/Qt is overkill.

#

Re:fltk a drawback?

Posted by: Anonymous Coward on January 26, 2007 04:17 PM
I completely agree with the previous poster about FLTK. What a silly thing to say by the author. In my own experience, the popularity of a product is rarely a measure for its quality.

Btw, FLTK has scheming, so the user can decide to make it look very much like Gtk, or somewhat Aqua-isch, or even implement their own scheme.

#

Re:fltk a drawback?

Posted by: Anonymous Coward on January 29, 2007 06:01 AM
Last time I've checked, fltk couldn't handle BiDi (right-to-left written) languages, a nogo for many countries (Arabic, Hebrew and Farsi for example).

#

Re:fltk a drawback?

Posted by: nanday on January 27, 2007 01:51 AM
When I called fltk a drawback, I was thinking only in terms of the acceptance of any tool that uses it. Many users are reluctant to install another toolkit, especially when it's only needed for a single program.

- Bruce Byfield (nanday)

#

What about PXE?

Posted by: Anonymous Coward on January 26, 2007 07:32 PM
I don't know much about thin-client terminals and stuff, but what about using PXE ?

#

Re:What about PXE? = See LTSP.org links here:

Posted by: Anonymous Coward on January 27, 2007 02:20 AM
All of these LTSP distros are going to be under the same mutual team. The LTSP folks help out the K12LTSP folks, and also there is mutual workings going on between those two and edubuntu as well.

PXE and Etherboot are both able to use LTSP.
see: <a href="http://www.ltsp.org/" title="ltsp.org">http://www.ltsp.org/</a ltsp.org>
<a href="http://wiki.ltsp.org/twiki/bin/view/Ltsp/WebHome" title="ltsp.org">http://wiki.ltsp.org/twiki/bin/view/Ltsp/WebHome</a ltsp.org>
<a href="http://wiki.ltsp.org/twiki/bin/view/Ltsp/PXE" title="ltsp.org">http://wiki.ltsp.org/twiki/bin/view/Ltsp/PXE</a ltsp.org>

PXE will be the future as it has some more interesting feature abilities... (of course not all really older PCs can do PXE, so there is Etherboot)!

In fact, Edubuntu's 1st real version had only PXE as a client boot option, and has since been trying to clean up and make better a Etherboot option as well. per - <a href="http://www.edubuntu.org/GettingStarted" title="edubuntu.org">http://www.edubuntu.org/GettingStarted</a edubuntu.org>
Quote from page:
"The minimum requirements for a thin client computer is a Pentium II with 48MB RAM and a 2MB display card. Recommended specifications is at least a Pentium II/300 with 64MB RAM and a 4MB display card. You will also need a method to boot over the network. Most newer motherboards (and network cards) have built-in PXE software that allows you to boot from the network. If it doesn't, you can create a network boot floppy or CD from <a href="http://rom-o-matic.net./" title="rom-o-matic.net.">http://rom-o-matic.net./</a rom-o-matic.net.> Keep in mind that you need to enable PXE emulation when creating the boot media"

#

With fat/powerful clients, try DRBL

Posted by: Anonymous Coward on January 29, 2007 02:51 PM
For memory-intensive activities such as animation, if you have powerful/fat clients, maybe you can try DRBL:
<a href="http://drbl.sf.net/" title="sf.net">http://drbl.sf.net/</a sf.net>

#

This story has been archived. Comments can no longer be posted.



 
Tableless layout Validate XHTML 1.0 Strict Validate CSS Powered by Xaraya