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."
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."
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.********* sig: If you don't like the law, get filthy stinking rich, and buy a better one.
success story
There are quite a few internet cafe packages out there, and there might even be one on sourceforge; combined with linux, I could not think of a better solution for a library, especially when the payment system is used administrate (and ensure that all patrons of your library have equal access).
Sounds like a great project, good luck!
success story here, sorry
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."
l
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.shtm
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
My MythTV HowTo
Some people already referenced to distros you can use.. so I don't have to do that anymore.
:-)
.. (thank god spyware didn't exist back then, I don't want to imagine how bad it would be now :-))
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,
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)
Learn about pinball machines on www.flippers.be
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.
Richard Steven Hack - This sig is TOO GODDAMN SHORT TO DO ANYTHING USEFUL WITH! MORONS!
I would use Knoppix.
That's got everything you need on it - it's a full, live-on-CD version of Linux, and it's completely free. Boot off it, glue the CD-drives shut, and you're good. You'd need small hard drives for it, naturally, and quite a bit of memory (~512MB should do fine), but that'd do _very_ nicely for a workstation - KDE, OpenOffice, Mozilla, and a bunch of other things that make a workstation a workstation.
Striking fear in the authors of godawful fanfiction, I am here, appearing in darkness, Tuxedo Jack!
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.
"!"
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.
Daily Shenanigans
...just use the EZLink internet terminals from Pantheon.. if Adam west endorses it.. it must be good!!! :(
It works.
If you've attended the Apple stores they have Macs sitting around for people to interact with and even though a good deal of the interaction is unsupervised, nothing destructive happens with the box and life is relatively good.
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.
phatlipmojo writes "I'm a librarian ..."
Funny. When I was a kid librarians were named Ann, Phyllis, or Doris.
"[T]he single essential element on which all discoveries will be dependent is human freedom." -- Barry Goldwater
There are plenty of resources for thin client computing in a library environment.
s /caseStudy.asp?storyID=13818
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/caseStudie
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!
At my university (http://www.kuleuven.be/) the library uses Sun terminals. Searching for books can be done online from your dorm or from one of the netscape browsers running on the Sun thingies.
The Sun computers look very sharp, are very small and are all accompanied by a LCD display. They run some sort of Linux-Unix like OS.
There is also StarOffice installed on all computers so you can type something and mail it to yourself
The books themselves have RFID tags on them (or something like that, the building knows when you take a book) and you have to enter/leave by using your University ID card
You do realize that a thin client is not a slimline desktop, don't you?
A thin client is one with little or no computing power... Just a screen, keyboard and mouse, give or take...
A slimline desktop is one where you "pay more to have all that computing power stuffed into a smaller case."
OTOH, maybe IHBT.
"Go to CNN [for a] spell-checked, fact-checked summary" -- CmdrTaco
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?
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!
My pics.
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!
If you're not living on the edge, you're just taking up space!
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.
Panurge has posted for the last time. Thanks for the positive moderations.
2) install mandrake linux official 10.0 on it
3) install ltsp 4.1 http://www.ltsp.org/ on top of it
4) get a load of old PC hardware (everything up from pentium goes, all you need is a non s3-grahic card and one spare pci-bus)
5) rid the PCs with all moving parts (leave the fans though...)
6) get pxe-booting network cards for the clients (100mbit is fine, via-rhine for example)
7) fire up.
if you want to do it with new hardware, just buy some via epia+case combos =)
Mail me for more details - I can also do the actual job if being paid =)
++K
<[letter kay][at][number seventy seven][dot][finnish TLD]>
The world has trolled you.
Renember when we used to call thin clients "dumb terminals"?
Then they seemed to be uncool.
Now they call them "smart displays". Still uncool mostly.
I have to connections to Tarantella in any way, and I dislike Windows, but I must admit that this is a very good option.
Never eat more than you can lift -- Miss Piggy
http://k12ltsp.org/
K-12 Linux Terminal Server Project
Perfect for what you're looking for and already in use in various schools and libraries.
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.
AccountKiller
If you're looking for thin clients at the library, I'd suggest keeping lending lots of books on diet and exercise.
He who laughs last is stuck in a time dilation bubble.
There is a morphix derivative that is a pure kiosk style Firefox. Currently I am trying to remaster it a bit, not doing so well, but that is me and how little time I have put into it, and thae fact that I want it locked down hard. Oh - here look toward the bottom for the firefox iso.
Sera
Slashdot, where armchair scientists get shouted down and armchair theologians get modded up.
There is no justification for ever installing full-blown PCs in this kind of environment. (No, I don't work for or with these guys, I just have way more experience than I ever wanted administering extensive networks of independent PCs in environments where the cumulative equivalent of VT's Big Mac was brought to bear on tasks that cumulatively required roughly a dual P4). Web browsing, word processing and the like require almost no processing power. Unless your users are creating/editing/transcoding audio or video, compiling elaborate programs, or doing deep data searches on local data, the computing power is wasted.
Not to mention the time wasted on cleaning up after clueless users (in a properly configured thin client environment users are only users, not manipulators, of the core operating environment), keeping up with the latest patches, x number of software/OS "up"grades instead of one (and the requisite hardware upgrades - two, three years down the road, instead of replacing a library full of obsolete machines, you replace one, and keep your clients),... I could go on, but /. comments aren't supposed to be books, so I'll stop.
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.
Don't forget to pick hardware that won't require lots of care. My suggestion is to get one of those VIA fanless jobbers and net boot it. That way, there's no fans do die, no hard drive to die, and no noise to disturbe library patrons.
And why would IE for Windows be necessary (or even desirable)?
If a standards compliant browser (Firefox, Opera, Safari, IE for mac, IE for Windows (almost)) can't browse your web pages, you have a problem with the web pages, not with the browser.
Perhaps it's time to step back and question those assumptions, after all, they're not even at the building/buying stage. Choosing IE for Windows is basically choosing windows, which as you point out, makes the question almost a non-question - they may as well go back to continual problems trying to keep the systems up, up to date and hardened, which is precisely what the poster wanted to avoid.
I have some experience of setting up Netbootet Macs. Prior to 10.3 it was hell, but now it works nicely. If you can afford it, buy some iMac TFT's and remove the harddrives.
:)
With NetBoot you can add software to all machines on the fly and the new Apple Remote Desktop 2 has loads of features, including VNC support so you can monitor the machines from your PDA while you relax on the beach.
It's also easy to set the machines in kiosk mode where they, say, only can access a web browser - or whatever you want your visitors to use.
Sun Rays are dead silent (no moving parts), very low power (20W) which also saves you on air-con, last forever, require no maintenance on the client side, are very secure (air traffic control for Air Force One is run off a network of Sun Rays) and easy to setup.
Version 3.0 of the server software also runs on Linux. V3 is also bandwidth efficient enough that you can deploy over broadband or a group over 10Mb Ethernet.
As for how much they cost, on modern hardware the main thing to bear in mind is the amount of main memory you have. Sun have a sizing guide to help. For lightweight usage, eg a library, they suggest you can run 40 clients off a server with 4GB of main memory.
So 40x Sun Ray 1g = $359 * 40 = $14.4K (re-use monitors from your existing systems). On server side, a Sun Fire v20z with 2x Opteron 250s and 4GB of memory is $7k, though you could get a model with slower CPUs and pay for more memory. As a library, you should be able to get an educational discount too.
I have read a lot of different definitions of what 'thin clients' are in this thread. Actually, they are all right and wrong. 'Thin client' has quite a few definitions and the definition that applies to you depends on your appliction. For this application, I think we can assume that 'thin client' means a computer without a natively installed OS. In reality, what you want is a standard run of the mill PC for each terminal. There is no need to get exotic towards either end of the spectrum.
For arguments sake, lets assume you want 5 terminals throughout your library. If money were no object, I would order 5 standard PCs from your favorite computer manufacturer (this could be a big dog like Dell or HP or a local computer store.) The only things you want to pay special attention to are warranties. Get the best warranty you can get your hands on. Not to be an advertisement for Dell, but they do have a nice 4year/4hour on site warranty. Once you call in a hardware problem, within 4 hours there will be a tech there to work on it and they'll do this for 4 years. That's hard to beat. One nice thing about buying a standard PC instead of one designed to be the minimum thin client configuration is that if you change your mind later, you can always use a non-thin client solution. I would also consider buying an extra PC. Depending on how busy your terminals will be, you may not get enough time on one of them to update your deploy image. You will need to do things like perform virus scan updates and apply security patches and bug fixes. If taking over a terminal every once in a while is no bigge, don't worry about the extra PC.
Once you have your 5 terminals you should set them up with the standard OS and software you intend to support. I see a lot of Linux suggestions here and Linux could very easily pull it off. But, for a public library, Windows will easily work as well. It is really up to you and which OS you want to support. Whatever you do, make sure you have Mozilla, an office suite, and a virus scanner. If you run Linux, this should be Open Office and if you run Windows, it should be open office AND Microsoft Office. Once you have decided that, I think the idea of bootstrapping over the network is a good idea, but there are other options. Wether you choose Linux or Windows XP, both are capable of firewalling and you should definitely use that feature on the clients and it probably wouldn't hurt to have a firewall protecting your entire building too. But that's just my paranoia kicking in.
First, the drawbacks of net bootstrapping. If you do this, you will either be loading an entire OS and it's apps onto the client hard drive which would take a long time and every reboot of the machine would have that minimum as a downtime. Or, you could just load the base OS onto the machine and have all the apps installed on a server via a mapped drive. This would require less downtime at boot, but your network and server become single points of failure for your clients and you would have long application load times. I would recommend a daily reboot. If you do this when the library opens, then the downtime is not a problem. I would snag the whole OS over the network. This way, regardless of who walks in and out of your library, at least once a day you have cleaned up their messes and you will only have to maintain a single deploy image for all of your terminals. Also, if a computer has trouble and you are too busy to spend time troubleshooting or if you're out and a non-techy person is there, all that is needed is a reboot to take care of the problem.
There are a couple of things to keep in mind. I assume your computer will be capable of searching some sort of database to let patrons search for books and what not. If this is so, you might also want to consider having the terminals have their own databases that snag a copy of the database data from the server at boot time. Every 15 minutes or 30 minutes or so, the clients can request updates. This way, you still only have to u
A word like that is called a 'portmanteau' word. It's got a nice story behind it; like 'chortle', it is one of the many words that Lewis Carrol, author of Alice in Wonderland, added to the language.
See Wikipedia and this site for more details.
I love the English language...
While not specifically for libraries check out
http://www.k12ltsp.org
We currently use it at work on the Tech Floor, and it runs great... I can't remember the last time I replaced a hard drive in a machine.. oh wait I haven't... cause they all run off the server =) BLAH! Nightmare when each machine ran seperately.. replace hard drives, format, etc.
The articles:
0 209 0 08
http://os.newsforge.com/print.pl?sid=04/05/03/152
http://www.libraryplanet.com/2004/05/lumixis
http://www.schoollibraryjournal.com/article/CA406
are about a distro based on "Linux From Scratch" that was specificly created for public access terminal use in a library. It has been deployed and is loved by everyone, the public and library management included. I have not used it myself, I heard about it at a user's group meeting. You might want to contact the author and get a copy. ljsalazar(at)comcast.net The project website http://www.lumixtech.com/ seems to be down.
I am a Network Administrator for a medium size city Library. We currently use Dell's with XP and all the 'bell's and whistle'...including the essential Deep Freeze. I am looking at Terminal Services with either Linux or MS. Wyse Technologies (formally Netier) does offer thin clients and if I remember right they can offer terminal service through these. From my experience Linux IS morse secure but you will have a greater learning curve if not phobia from patrons..and staff alike! Good Luck! Richard-
A library I worked with a couple of years back used windows with a restore-on-reboot card. They'd get hit with a virus, or some other bad thing would happen to a system, but they could bring the system back to a known state by turning it off and back on.
Not the be-all answer (no fun if you have to restart XXX times a day) but in conjunction with not-too-frequent patching (weekly?) and a decent anti-virus package it can be good.
Also handy for getting rid of content/screen savers/other unwholesome content that a user might download.
(I'm not a fan of windows, just relaying an experience)
http://www.juzt-reboot.com/
http://www.hddguarder.com/
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.
-- I thought I was wrong once, but I was mistaken
All that I can say is avoid software from Dynix. Our local Hamilton Public Library, usually a superb outfit, just moved all of their catalogues to Dynix systems and it has been a total disaster.
The terminals in the library are very, very slow to respond, and for the first month the search funtion only worked about 10% of the time.
Talk to them before buying Dynix to find out what went so wrong.
Three Squirrels
Yes but if you instead get 40 little epia boxes with no disk just a CF card, and a server its much cheaper. If you recycle old PC's as thin clients it gets very cheap indeed
Sorry this is not directly related to Thin Clients for libraries, but I had to mention it anyhow Koha - Open Source Library System http://www.koha.org/ It is an excelent open source library management system that should recieve more attention
I've set up this kind of system for a number of local non-profits specifically because they don't have an IT department. It works great. After you set it up it just works. If a client starts acting funny, you just restart it and it gets a brand new copy of software. You can configure how much access users have to software. You can make different rules for different users or different computers if necessary. It's really stable. The ones that I have running right now are up from security patch to security patch. Also, each Netboot server can handle up to 50 clients. So with an education discount, a G5 with the OSX Server and 50 eMacs will run you about $40,000.
Mandrake Terminal Server available since, I think, 9.0. If you're running audio, video or just lots of screens, go for "diskless fat client" mode rather than "thin client" mode; NFS + Linux's caching makes the network bandwidth much nicer that way, and lots of things like plugging in USB thumbs, cameras or PDAs are easier to manage.
If you want to charge for it, I've cobbled up an infrastructure based on Ruby and PostgreSQL which seems to work fine. It'll be released soon (weeks) under the name "lincaf" (GPL, natch). It will probably learn how to be coin-op within a few weeks as well.
You can actually use the Kiosk tool with any KDE from 3.2.0, and most of the setting effects from it (by hand-editing config files) from KDE 3.0. The Kiosk structure allows you to default changes back to a system config file, so you can make changes for all users (or all in a group) post facto.
What I did for lincaf was set up a template user, tell useradd to borrow that filetree, then do a pass over it with a few lines of Ruby to re-sanitise config files and the like.
Got time? Spend some of it coding or testing
I replaced such a system with Linux. Unless you lock the MS-Windows browsers down to the point of total uselessness (especially MSIE), there's always a way to slip a crack in under the radar. Every gap you close leaves another ten.
/bin/false as a shell, mounting the guest-users' $HOME with noexec, and tightening the screws on a handful of KDE's Kiosk Admin config items ended all of that instantly, and so far permanently.
Using Linux,
Got time? Spend some of it coding or testing
I work for a rather large library system in the Houston area (25 different locations, and I'm in the CO), so I'd like to touch on a few points in your post.
:)
So you don't want Windows, but you want IE, Word, Excel and Powerpoint?
I don't believe she said she didn't want Windows, but rather she was unafraid of a non-Windows alternative.
I'd personally try to push you away from supporting a lot of apps outside of just plain-jane internet access.
That would be suicide! At least in my library system. You see, a lot of the time people come into the library to use the computers because *they dont have one*. What this means is that they use computers for all sorts of things, from doing term papers on Word and using our printers to print them. Some come in and work on a spreadsheet for something they are working on at home. Powerpoint? Sure! Why not? What if they need to do a presentation for a class, or for their own business, and they'd like the resources of a library system at their backs while doing research on it. Again, people come to the library to use the computers for all sorts of reasons, and it would be quite presumptuous of us if we thought they only need Internet access.
My point is, the library is where information is collected with the tools to utilize all of it. Not just Internet access. Heck, we even provide free 'Computer Use' classes that teach people from the nearby trailor parks how to browse the web, or click with a mouse.
Hope this helps clear up a few things.
++Om
Go here: http://h18004.www1.hp.com/products/thinclients/ind ex_t5000.html
HP makes Windows and Linux thin clients - all fully supported. This is not something I've tried, but I agree that thin client is the way to go in this situation (low user needs and high maintenance worries). You might think about sticking with windows since so many people know how to use it - hard to say. On the other hand, linux is better in so many ways ($$$ and stability/susceptibility to viruses). Go with Linux and all will be well. Have one windows machine in the corner 'just in case'.
After a few initial glitches at my CyberCafe, LTSP-based thin clients ran flawlessly thereafter. Our main troubles were in printers jamming. Although we mainly ran KDE/Linux systems, even Windows Terminal Server ran more reliably (in a GNU/Linux-protected network using rdesktop on the clients).
My advice (inclusive of some flamebait) is the following:
*. First, if you need/want help contact the WSU Lug or me (smutz) on the #wsulug irc channel on freenode.net
1. Use LTSP (add a separate Windows Terminal Server and rdesktop, if you need Windows)
2. Gentoo, SuSE and Mandrake seemed to work best for various reasons. Gentoo is the very best, but takes a lot more work to get configured.
3. Use ReiserFS (but not on RedHat). Never mind all the anti-reiser FUD. I've been using Reiser for years on sometimes as many as 30 servers, six in one area with power outages at least once every two weeks. Reiser really is badly broken on RedHat, but has honestly been vastly more reliable than Ext3. I am running mostly Reiser but Ext3 on a few systems and the Ext3 systems are periodically corrupted after power outages or cable kicks...sometimes irrecoverably. We've repeatedly unplugged our Reiser-based systems and never had any corruption, except for a physical disk error, a bad disk controller, and an overheated system (due to a dead fan).
4. Do not standardize on Mozilla!! It is by a huge margin, the number one crashing and account-disabling application we've used in the Cafe. The latest versions of Konqueror can replace it very handily if you put a lot of work into configuration: installing all the Netscape pluggins and setting it to say it's Internet Explorer (latest version). On the other hand, FireFox (light version of Mozilla) is reasonably stable and works great without much work into it. Konqueror has the advantage that, when it does crash, it doesn't lock up the whole user account, as does Mozilla or Firefox. Konqueror just closes as where Mozilla-based browsers (like FireFox require superuser intervention to kill it and let the user keep working) The latest versions of Konqueror have pretty much done away with the last rendering problems and stability is pretty good. Remember: Even Mozilla only locks up one user account, and doesn't effect other users. With LTSP, you can just hit reset and login as a different user..
5. If you are going to let people do word processing, set OpenOffice to automatically save as Microsoft Word format. It'll save you and your users TONS of headaches...because they never remember, if you tell them... And get rid of KOffice.. As much as I like it, people really do need MS Office compatibility and it doesn't reasonably offer that, yet. And, make sure you install Microsoft Fonts and/or set the default font to something Microsoft Word has that is similar.. I forget what we are using...sorry.
I'd love to offer more help but don't want to post my contact info in an open forum. You can find me and others who know of me on the wsulug IRC channel on freenode.net
Matthew C. Tedder
eMacs (or any recent Mac for that matter) also support NetBoot. Basically, this lets you use a Mac as a thin client. Each Mac will boot from an OS image on a server (Apple XServe) which would allow easy administration. The cost: a little more expensive than standalones or true thin clients, but not horribly so.
Best of all, it's easy. OS X and OS X server are easy to learn for non-techies.
The Mac OS, as mentioned above, also supports Word, Excel, PowerPoint, etc. Event IE, though its a little out of date.