Thin Client Solutions For Libraries?

phatlipmojo writes "I'm a librarian in the process of opening a brand new small public library from the ground up (literally; we don't even have a building yet). The library director and I are considering our options for public computing terminals. Having experienced the frustration of dealing with Dell machines running Windows XP on a daily basis, we're trying to consider other options, and we've been talking about maybe using thin clients. Have any of you used or worked in a library (or similar environment) that uses thin client stations for public computing? What are your impressions? What are the perks and what are the drawbacks?" "I'm hoping that using thin clients could save us daily time troubleshooting bluescreens^H^H^H^H^H^H^H^H^H^H^H computer glitches, allow us a greater degree of uniformity on the public terminals, save us the trouble and expense of putting Anti-virus software, Fortres, and Deep Freeze (or other such utilities) on each machine, and make our machines more difficult for black hat types to mess up on purpose. I'm also hoping we'll be able to offer web access (IE and Mozilla, hopefully. IE at a minimum), Word, Excel, and Powerpoint. And have floppy drives. Plus, it would really comfort me not to pump several hundred dollars per machine into a monopolist's coffers for an OS we're just going to debilitate anyway.

We're in the odd (for a public library) position of money not really being a significant factor in the decision. So, for those thin-client-lovers among you if cost weren't a factor, would you still prefer them to full-fledged PCs?

The other factor here is the tech skills required, because our IT department is me. As librarians go, I'm pretty tech-savvy, but as Slashdotters go, I'm pretty much a luser. So homebrew Linux solutions are really out (plus, vendor support is important for selling ideas like this to the municipal government), but systems requiring basic-to-intermediate networking and troubleshooting skills are in, and I'm not afraid of non-Windows OSes."

Comments

Not a luser!

[Hanzie]

..I'm pretty much a luser...

Mmmmm. That word 'luser'. I don't think it means what you think it means....

You're a public librarian. Thank god for you and your kind.

hanzie.

Re:Not a luser!

[cliffy2000]

To quote Wikipedia: "In hackish, the word luser takes on a broader meaning, referring to any normal user (i.e. not a guru), especially one who is also a loser (luser and loser are pronouced the same)"
So she's okay.

Re:Not a luser!

[WIAKywbfatw]

She? Who said that phatlipmojo was a she? Not all librarians are women, you know.

Looks like we could do with losing the stereotypes about librarians as well as the stereotypes about CS students.

Re:Not a luser!

[pomakis]

he? Who said that phatlipmojo was a she? Not all librarians are women, you know.

Wouldn't the use of "he" be just as presumptuous? The English language has flaws, and this is one of them. Since English has no third-person-singular gender-unspecific pronouns, speakers and writers of the english language have only six choices when referring to somebody whose gender isn't known:

• Use "he/she". This can get very awkward (especially when spoken). E.g.: "Someone across the street bought a newspaper, and then he/she put it over his/her head so that he/she wouldn't get his/her hair wet."
• Use "they". This is technically wrong because it's a plural pronoun, so in can lead to ambiguity and confusion. However, it's becoming increasingly common. E.g.: "Someone across the street bought a newspaper, and then they put it over their head so that they wouldn't get their hair wet."
• Use new gender-unspecific pronouns and hope that they'll be understood and catch on. E.g.: "Someone across the street bought a newspaper, and then ey put it over eir head so that ey wouldn't get eir hair wet.". See http://www.aetherlumina.com/gnp/ for more information on such pronouns.
• Always assume male. This was common and correct practice in bygone days, but I don't think it's reasonable nowadays.
• Guess at a gender. This is a variation of the previous point, and is not only more fair, but more likely to be correct. In this case, the person in question is a librarian, and there are more female librarians than male librarians, so why not initially guess "she" rather than "he"? It's more likely to be correct.
• Avoid the use of pronouns altogether. I think that this option is entirely unreasonable. E.g.: "Someone across the street bought a newspaper, and then that person put it over that person's head so that that person wouldn't get that person's hair wet."

LTSP for Public Libraries

[js7a]

LTSP for Libraries HOWTO

success story

Re:LTSP for Public Libraries

[Aber_Bryn]

I've been working at the National Library of Wales developing an LTSP based system for our new Readers Room. We had decided to replace the old full WinNT desktops with LTSP stations served off a 1u Intel Xeon Server running Redhat 9 (for the trial system). I'm currently in the process of setting up the servers for the deployment version (Redhat Advanced Server on the same hardware).
I personally found the LTSP for Libraries HowTo very useful, after reading it and a day's worth of work in it - our system happily serves Firefox to the terminals.
You should bear in mind though that serving applications like Office to each terminal will mean quite a lot of your bandwidth being taken up. If its running on the same physical network as the rest of your machines (which it *really* shoudn't be imho) then your staff are going to start complaining.
As for security concerns... provided the terminals arent served with an XTerm and you restrict the user logged in only to their home directory, firewall off the server and isolate it from the rest of your network (consider sticking it on a seperate V-LAN to the rest of your network) and keep the machine up to date. Then it will most likely be as safe as any other machine on your network.

Bryn

corrected link

[js7a]

success story here, sorry

From an old Newsforge article-

[thewldisntenuff]

As Auger recently wrote in an article for Library Journal: "Our two Linux luminaries, Michael Ricksecker (network specialist) and Luis Salazar (network engineer), created a kernel and resulting user desktop that closely mimic not only the look and feel of a Windows desktop and browser but lack the unnecessary bells and whistles that come with a standard Windows installation."

Using LFS as a starting point, Luis and Mike were able to build a minimal Linux kernel that included only the functionality required by the "kiosk style" machines. They added the Gnome desktop environment, the Mozilla browser, and OpenOffice.org to complete the picture. They call the new distribution "Lumix."

Anywho, give that a try --

Article From Newsforge-
http://www.newsforge.com/os/04/05/03/1520209.shtml

LumixTech (link from article doesn't work...give this a try or google it)
http://www.lumixtech.com/

Good luck with your new library!

-thewldisntenuff

Re:From an old Newsforge article-

[Spy Hunter]

KDE now provides a "Kiosk mode" that is designed to make this kind of locked-down desktop easy to achieve on any distribution with KDE. Here's a recent article on the subject, and here's the project homepage, and here's the KDE guide for sysadmins, which has lots of information useful to KDE server admins.

Re:From an old Newsforge article-

[atomic-penguin]

Here is the slashdot link:
http://it.slashdot.org/article.pl?sid=04/05 /05/144 1249&tid=103&tid=106

There is no publicly available cd image of this. You have to contact the authors to get a copy.

I was going to try this out in one of the computer labs at school. I even contacted one of the author's and got no reply.

Instead I just did it myself. We had some crappy 200 and 300 Mhz machines for this.

1. I loaded a bare slackware system with network support.

2. Put mozilla firefox on the systems.

3. Unzip the browser.jar for mozilla (Java Archive, compatible with zip).

4. Hand edit the browser.xul file to disable unwanted features (save to disk, bookmarks, preferences).

5. Zip the new browser.xul into browser.jar.

It might sound like a lot of work involved, but there are tutorials on kiosking a browser available via google. It took me two hours at the most to get mozilla locked down and kiosked.

The hardest thing I had to do was get mozilla to start up in place of a logon manager. Because I tried it a few ways and ended up with nasty infinite loops that don't play nice with init. Beside the point, because you probably want something other than just browser access in your library. What I ended up with was a nice locked down browser in fullscreen mode and nothing else. Which was the original goal to have browser kiosk. Extremely easy to modify mozilla to fit your needs. One alternative I have seen is a 10 headed server (1 server, and 10 screens, keyboards and mice). A turnkey solution with applications loaded, exactly what you are looking for. The downside is a price ranging in tens of thousands, depending on what optional packages you want added.

linux..

[DZign]

Some people already referenced to distros you can use.. so I don't have to do that anymore.

But as I have some personal experience with this here's my post :-)

Back in the day when I was studying at university a friend and I both worked a few hours a week in the uni library. They had the same problems you're describing, only on win95 then..
The computers available could be used to surf and telnet to the library system to search books.
Almost every week windows had to be re-installed,
usually because someone messed up some settings, or there was a virus on it, .. (thank god spyware didn't exist back then, I don't want to imagine how bad it would be now :-))

In the end we just installed linux. The login screen clearly said 'log in as 'guest' with password 'guest' and would then boot X with 2 nice large icons: Netscape and a telnet window to the library catalog. Nothing else was possible.

For the next 6 months the year lasted, we didn't have to do any maintenance anymore on these systems..

(bonus for us: we used it as email server too to get personal email out of the uni-system and having a box to telnet from was nice to.. hmm.. experiment a bit)

Re:linux..

[Lumpy]

There is another step you can do if ou want to control the access and or monitor use.

look on freshmeat for some of the cybercafe management systems. you can allocate time to a user and it will shut them down at the end of the alloted time. if your library is not busy, this is not needed, but some libraries are very busy and instead of having the librarians police the stations, you can have the computers police them for you so those waiting to use them will get their time at the terminal.

It worked great for us at a company demonstration of broadband. we had people waiting to "feel the future" so I set up the linux boxes to only allow 15 minutes per user. it worked great and it eliminated the leaches sitting there for 5 hours hogging the access terminals.

I Assume You Are Intending To Use an ILS?

[Master of Transhuman]

If so, go here for the Koha Integrated Library System - an open-source ILS used by several libraries in New Zealand and elsewhere.

Also go here for the Open Source For Libraries Web site which has links to numerous open source library systems and tools. Including a story on how Arizona State University West moved entirely to Linux as the underlying OS for their library.

Between those two sources, you should find plenty to check out.

Sun Rays

[trisweb]

I know you said that money is less important, but Sun Rays still might be out of your league. I have no idea what they go for.

Sun Rays are the epitomy of the thin client. I mean, they really are thin. Only like 2 inches thin. They run off a Solaris central server, and have no hard disk or much of a CPU. I use them all the time in my CS lab at UC Berkeley.

I'm commenting more on the general aspect of the thin client than these specifically, because I think something else might suit your needs better. So let me just say that in a lab of 30 sunrays, they always seemed slow. But then you (probably) don't have freshmen writing C programs with memory leaks and infinite loops that clog the pipes. If you had a moderate number running off a decent server, I'm sure they'd be fine for just about anything you do. Solaris is a pretty standard UNIX environment; you can offer Gnome and KDE and such, and all the applications you described, and they'll work fine as long as people don't expect 3D games.

But I'd consider alternatives. It all depends on how many systems you want to offer. If it were 5-10 systems, I'd just get cheap PCs and install RedHat or other linux, or an old version of Windows. Then keep a disk image handy so you can wipe them whenever you want. But if you need a lot of workstations, then a thin client might be more economical. Work it out and see.

Re:Sun Rays

[WebCrapper]

I recently did a study on Sun Rays and think I can share some data...

For 40 Sun Thin Clients with 1 Server: $74,935 (for Library use, you can probably add up to 60 Thin Clients on one server due to usage)

For 40 Dells (with required antivirus and Ghost):$76,307.28 (with small business discount)

Upside of thin clients is - no work locally, its all on the server. Good technical support (they answered our test call within 2 minutes) will help out with any issues you can't take care of.

If you want an 8 page report on the pro's and cons between the average windows workstations and thin clients (as well as 3 PC manufacturers compared to Sun's Thin clients), feel free to email me.

Re:Sun Rays

[WebCrapper]

I did a report on your average computer vs the Sun Rays:

Dell: P4 2.8GHz, 512 memory, 20G HD (5400 rpm), 24x CD, Win 2k, Ultrasharp 19inch Flat panel that is height adjustable, standard keyboard, wheel mouse, bottom line external speakers, DVI-VGA video adapter, mouse pad, no floppy, no consumer anti-virus software, no Microsoft Office offered.

Cost: $1,797 per unit

Required Software: 40 licenses each of Norton Anti-Virus ($3,219.65) and Ghost (1,207.63), Corp Editions.

Full cost: $76,307.28 for first initial order

Support: A test call to their support line prompted advertisements for spyware removal programs, antivirus programs, network hardware to up sell customers as well as the standard "Your call is important to us." The call lasted 17 minutes before giving up the test call.

Sun Thin Clients:
Configuration Details: The SUN thin clients are, effectively, modern dumb terminals. There is no local processing, everything is done on the server side. A representative would need to insert their smart card, used as a username and password, into the thin client and their session would be brought up immediately, right where they left off before. This enables "hot desking", which means a representative can get up from one terminal, walk across the building and sit down at another terminal and begin working where they left off - zero configuration. The thin client works off of a central server, called a SUN Fire, that can house anywhere from 1 to 80 clients, depending on server type and load. These are normally very fast machines that have their memory maxed out.

The Server runs the only copy of Solaris, so there is only 1 upgrade point and since it
runs Solaris, it is impervious to roughly 99.9% of the viruses that attack computers. A major benefit is that the SUN Fire server requires, roughly, one System Administrator for 2000 thin clients.

The Sun Ray 1G Thin Clients do have audio in and out jacks, giving representatives to listen to music over the network. This would require a CD collection somewhere, a network storage server dedicated to music, etc.

Cost: $359 per unit + SUN Fire server ($12,995 - $29,490) + 19 inch monitors ($1,100 each)

Required Software: None. The SUN Fire server has licenses for 20 to 40 users using Solaris with Gnome, a Windows like operating system as well as other software package like StarOffice (a Unix/Linux version of MicroSoft Office) and GAIM, a Unix/Linux version of AOL Instant Messenger.

Required Hardware: The Sun Thin Clients require a monitor. While Sun offers 19inch LCD displays for $1,100 each, the Thin Clients do support any monitor that supports Display Identification Standard (DDC) ver. 1.2 or 2.1. There is more documentation on monitor needs on Sun's website. Other 19-inch monitors that appear to support the standard are priced at $800 to $1,100. I have also noticed that the Sun Monitor appears to support higher frequency ranges (60-80Hz) vs the low end competition. This can help reduce eyestrain for those that can see monitors flickering at anything below 70Hz, such as myself. The Sun monitors also support 1920x1200 with 24 bit color (2d rendering, no 3d).

Full cost: $74,935 for first initial order

Support: A test call to their support line was greeted with a simplistic menu. After the menu prompt was picked, a "Southern type" SUN technician greeted the caller after a short wait. Total call time to live rep: 2 minutes.

Since the library isn't going to actually use them like we would, you can probably run around 60 per server since it would just be a browser and maybe a terminal window.

Basically, after spending about a week on the issue of workstations for a call center environment, we found that the Sun Ray Thin Clients came out on top and we'll be deploying them ASAP. Hope this helps.

Re:Sun Rays

[W. Justice Black]

ObDisclaimer: I work for the Linux Server Group at Sun.

I have also worked rather intimately with a few thin client technologies over the years, including SunRay, X Terminals (NCD, e.g.), and WinTerminals with WinFrame (NT 3.5) or MetaFrame (NT4/2k). I run a few SunRay servers today, and have run a 75-user cluster of Win/MetaFrame machines in the past. All of these solutions have their plusses (in fact, terminal services is the one Windows technology I like)...

There are, however, bits of your specific set of issues that point me at the SunRay for you:

1. Bandwidth to the clients are not an issue, so no need for the bandwidth saving that ICA gives you (ICA is really quite good over dial-up, e.g.), so that leaves:
2. Windows compatibility. Since you don't seem to care about running Windows apps, all solutions are on more-or-less even footing.

If you've got some coin and are willing to spend a little on systems, I'd recommend the SunRay because:

1. Sessions tied to smart cards. Folks can log in, and wander anywhere in the library with their session tied to (e.g.) their library card. For folks doing combination book/internet research, this is awesome. Folks that haven't tried yet are really missing out.
2. Soon, you won't be tied to Solaris/SPARC anymore. Sun has announced a port of the SunRay software to Linux, so you may well be able to reuse your existing server hardware. In fact, the beta is available for download here.

It never ceases to amaze me how many PC techs I know complain about crawling under desks or removing 25 lbs of personal effects to fetch a system so they can swap a dead drive or similar. When I tell them that thin client technology can guarantee them never having to crawl under a desk again (barring wiring or serious catastrophe), they definitely stop worrying about nonexistant 3D performance. Thin-client is an awesome way to go--you might not spend that much less on the machines, but maintenance and client upgrade costs go to zero.

The downside is no Windows (excepting via e.g. VMWare, Wine, etc.). OTOH, even on Windows Terminal Services you have programs that aren't really written to be run by multiple users on the same machine (even Office gave us fits at times with entries in HKLM instead of HKCU). It's gotten better over the years, though...

Short version: Even if you don't go SunRay, save yourself a lot of headache and go with a thin client.

Re:Sun Rays

[trisweb]

This seems blown up slightly -- A library (IMHO) does not need a 2.8GHz 512MB system. What are people going to do? 3D animation? raytracing? Doom III?

I think a better estimate would be a 1.4 GHz AMD Athlon XP system with 256MB RAM and the bare min for hard disk and other. The monitor you chose also inflated the price a bit. You can get decent 15" monitors these days (either LCD panel, or Trinitron CRT for more savings) for under $300.

And the software costs for the PCs are horribly inflated as well -- first of all, screw Windows. Install a basic Linux environment on them; there go your unnecessary Norton licenses. Use Gnome (or KDE), Firefox, OpenOffice, and a terminal for the Library and you're all set. If you're going to do a price comparison, at least bring the PCs up to the same level as the UNIX sunrays.

Cost per unit: about $600-$800
Total cost: around $30,000

Hmm, significantly less. I don't know if it's just me, but it seems convenient that the sunrays beat out the PCs by only about two grand. Maybe for a call center environment you need the extra horsepower on your PCs (which is ironic, because you chose sunrays instead) but I doubt it. Aside from maintenance and support, the PCs are definately cheaper for the library.

Re:Sun Rays

[mleopold]

I work in the Computer Science Department at the University of Copenhagen (DIKU) and our undergrad and grad student labs are made up of SunRay stations (I guess about 120 of them or so). They are run by 3 fairly slow SunFireV440 and require a number of application servers that can handle the load - in our case that is a pile of cheap Linux-boxes. With an LTSP solution you might be able to get by with fewer application servers as LTSP is able run applications locally.

The setup performs well for most tasks that our studens perform: browsing, compiling, emacs, lyx, etc. However getting audio from the application on a different server through the network into the V440 and finally to the earphone plug on the terminal is a challenge - and ofen more than the SunRay servers can handle.

They require very little attendance from the administrator - except for hardware failures everything can be handled remotely.

I don't know which prices you used for you calculations, but Sun just announced that SunRay software should be on the way for Linux which should bring the price on the servers down substancially.

Money Not a Factor - Use Citrix

[azadism]

If you have the money for Citrix, they provide a great thin-client on option where with the hardware you can put Linux on the client and have put straight into Citrix. 99.99% of the users will never know the difference.

Re:Perhaps use Internet Cafe Software

[Anonymous Coward]

there might even be one on sourceforge

OpenKiosk

Quotes from the webpage:
"OpenKiosk is an open-source multi-platform kiosk system designed for use in libraries, ..."
"With this delivery, OpenKiosk 1.0 is finally drawing to its completion..."

Thinstation

[Errtu76]

Thinstation is a 'distro' that i'm currently using at work (a hospital). It can be used to connect to Citrix, RDP, VNC, Unix, Telnet/SSH, or (with the help of fluxbox/icewm) as a lightweight standalone linux workstation (with an optional FireFox package). The people on the mailinglist are VERY helpful as well, so you don't need to worry about support when you've a problem.

I can really recommend it as a thinclient solution.

Hmmm...

[Combuchan]

phatlipmojo writes "I'm a librarian ..."

Funny. When I was a kid librarians were named Ann, Phyllis, or Doris.

Thin Client Resources

[Anonymous Coward]

There are plenty of resources for thin client computing in a library environment.

I would start by checking out the case studies that are listed at citrix.com. One immediately comes to mind: http://www.citrix.com/site/aboutCitrix/caseStudies /caseStudy.asp?storyID=13818

Incidentally, the man in question here runs a little site by the name of http://www.thethin.net/. It is hands down, the number one resource for thin client solutions on the web. Join the list and listen in for a while, I guarantee you'll learn more about terminal server and thin clients during the first week on this list than you will learn in any classroom.

Good luck to you!

IE requirement?

[tepples]

I'm also hoping we'll be able to offer web access (IE and Mozilla, hopefully. IE at a minimum)

How much would the administration be willing to budge on the IE requirement?

ComputerBank have done this in an Aus Library

[tpgp]

The great mob of volunteers down at Computerbank (a charitable organisation that refurbishes used PCs to run linux and be donated to community groups & individuals) have implemented a thin client system running linux at the Footscray Library in Melbourne, Australia.

Done for virtually no money- and plenty of the users prefer the interface to the more complicated windows systems running along side it!

Read their white paper and (if in Melbourne) go down to the Footscray Library (56 Paisley St, Footscray) and check it out!

Real answers...

[wcdw]

Lots of people talking about 'how-to', but nobody really answering your question. Typical slashdot...

The advantages of thin clients in this type of environment are many. It's almost impossible for a user to screw up what is effectively nothing but a terminal.

Downsides would include the need for a more expensive server on the back-end, as all the horsepower now has to reside in one place. Also, when the server dies, _everybody_ dies.

And if you use commodity hardware for the thin client, it can be harder to lock things down on the client end. General rule of thumb is NO drives of any kind with the client configured to boot across the network.

Many people have suggested the SunRay, and it's hard to argue with that - it's one of the first thin clients that's really usable (IMHO).

http://www.theboyz.biz/ Computer parts & more!

eMacs

[panurge]

If you have the room. Their downsides (very heavy single box solution) become virtues when the general public is concerned. They are hard to move, hard to steal, and - this is very important - can withstand abuse like an LCD can't. The keyboards are robust, you canuse ordinary cheap USB mice, the screen is bright and clear.
The design, with all the vents at the back, makes it hard for kids to try dropping paperclips and so on inside.

The only thing missing is the floppy drive, and I'd question whether that really is "missing". There are several workrounds if someone really needs floppy access.

SunRays are a good idea in more controlled environments but, at the end of the day, you still need physical terminals for the users. Terminals designed for use in uncontrolled environments tend to be expensive and not particularly state of the art as far as display type goes. I still think that most people still underestimate how well the eMac is designed for its environment.

requirements are contradictory and a bit confusing

[Vellmont]

I'm also hoping we'll be able to offer web access (IE and Mozilla, hopefully. IE at a minimum), Word, Excel, and Powerpoint....

it would really comfort me not to pump several hundred dollars per machine into a monopolist's coffers for an OS we're just going to debilitate anyway


So you don't want Windows, but you want IE, Word, Excel and Powerpoint? I think MacOS has the office programs, but unless you want to run the ancient IE5, you're SOL.

I'd personally try to push you away from supporting a lot of apps outside of just plain-jane internet access. Supporting the apps is going to be a pain in the ass, and people are going to be taking up lots of time writing term papers, etc when others just want to check their email.

I really think you need to step back and look at what you really _need_ the system to do. From the details you've provided it doesn't seem like you really have a good grasp about what you want to provide, what your maintenance requirements are, etc.

Thin client is a nice buzz-word, but it doesn't have a huge amount of meaning. Does each client have a HD, or only minimal boot-roms? What about if the central server goes down, any thin-client won't be able to restart.

Hire someone that actually can help you with these problems and analyze the requirements, do research, etc. Slashdot can provide you with very raw information, but it really sounds like you need someone with more tech experience to analyze your situation.

Re:How about a nice friendly Mac?

[hcdejong]

And maybe use NetBoot for centralized administration, which should make it easy to reset the clients to a default state.

15", 17" versions too

[daBass]

Don't forget Sun has Sun Ray clients with either a 15" LCD or 17" CRT in an all in one design too at $1049 and $659(!) respectively. That's a big savings on 40 of these and for a library more than adequate

The smart card is not a requirement either. You can simply log in (as guest if you like), you just don't get your hot desking. This brings the possibilty of giving regular users a real account with some space for documents as well and it keeps their settings. Guest logins are trivial to revert to "standard state" every time they are logged off too.

You don't get IE but that only disables a small amount of websites that due to their stupid reliance on IE don't deserve your custom anyway.

Re:Personally...

[Anonymous Coward]

It's not so bad a suggestion as it seems..

Knoppix supports being a terminal client by a simple LILO-command. For better effect, just remaster the original Knoppix to adjust this and some locale data, and the rest would be up to the server, which can be eg. Knoppix or Debian HD-install.

It's a really fast way to setup thin-clients for sure. Of course, it's a little dirty too, and if you want NX-support, you'd probably have to do some more work. It would be worth it though and REALLY cost-effective. Imagine all you have to do to setup a new client is burn a new CD-R or quick HD-install of Knoppix (the compressed type which is identical to the CD-ROM)?

Myself, I'd find a similar project to base the work on though.

Done That - 7 Times and Counting!

[ELBnet]

I have created a customized LTSP installation for libraries that is currently running in 7 public libraries. The system provides Web browsing and an Office Suite with timed sessions, print management, use statistics, floppy disk access, filtering (or not!). You can see one example install here

The system is completely GPL, requires no special hardware and I am currently working on an automated install system to make installation easier. If you are interested I can give you the email addresses of the directors that are using the system if you contact me: pete at elbnet.com.