Slashdot Mirror
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."
Get tha fuckin puck down, eh? No high stickin! T. Horton would have a shit-fit with that sorta crap, eh? Jeeze. My Touque's all in a fuckin twist now, eh, ya lame ass hoser fuck! Go Canucks! Ahhhh ferget it...buncha bums. It's like the fuckin Greek army on furlough! Campbell's an asswad! BC still lays a beatin' on Albortia! Take care, Eh?
Ohhhh! A friggin Klein-slave moddin a coaster down, Eh? Well, I got a 10-knuckle sammich for a fruit like yerself! Holy Jeeze! A fuck-over like dat comes along but once in a long while! Suck a nut, Eh?
Havent seen these in a while!
Welcome back!
Stupid narrow minded partisam politics. Call me once you've taken the red pill.
Democrats and Republicans only disagree about how to enslave you
And you aren't karma whoring?
WTF? Have the lunatics found slashdot or did I accidentally set to -1?
BSD culminated in previously thought And executes a Discuusion I'm
engineering project Here, please do of th3 founders of of programming of the old going numbers. The loss believe their
...the lunatics find YOU!