[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

RE: [K12OSN] k12 ltsp thick clients

Title: Message
I'm doing this now
Chris Bacigalupo,
Technical Coordinator
Harbor City International School
332 W. Mich. St. Ste. 300 
Duluth, MN 55802
tel. (218) 722.7574
cel. (218) 428.1264
-----Original Message-----
From: k12osn-admin redhat com [mailto:k12osn-admin redhat com] On Behalf Of Tim Thorpe
Sent: Saturday, October 04, 2003 18:31
To: k12osn redhat com
Subject: [K12OSN] k12 ltsp thick clients

As part of graduation at my high school we as seniors are required to do a senior project. A group of us have decided to attempt a thick client Linux solution for our school using a tech lab as a test bed. I (the lead researcher in the project) ran across K12LTSP which seems like a ballpark solution to our challenge. Most of our boxes are strut boxes with all sorts of random NICs and parts in them we are approaching this with the mindset that we have a zero budget and must use what we have.  I guess what it comes down to is that were looking for a bit of guidance and perhaps a rough roadmap on where we might need to look for information pertaining to what we want to do.


Our idea is to get a thin client working the way we want and move up to a thick client. Our idea of thick clients is part of Linux is installed on the HD’s of the nodes enough to get it to a boot point where it can pull its brain from the server, and download and run the applications from the server locally. Where upgrading consists of updating the files on the server. Very much like a thin client solution however utilizing the hard drives already in the machines, also the idea of a floppy at each work station is begging to get ripped off at our school, and not all nics are bootable.


Any guidance would be appreciated.


Tim Thorpe

North Salem High School

Salem, OR



I've stopped 10,542 spam messages. You can too!
One month FREE spam protection at www.cloudmark.com
Cloudmark SpamNet - Join the fight against spam!


Attachment: image001.gif
Description: Binary data

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]