Matt;
What you are suggesting is doable, but first ask
yourself:
Why not full LTSP?
LTSP has tremendous advantages over distributions
that are stored in the client device. The primary
advantage is that you don't have to perform updates
on each terminal. Updates are performed on the
server. All terminals immediately get the updates,
since they are accessed over NFS rather than from
storage on the terminal.
If you *have to* have a stand-alone O/S and runtime
(ie "embedded"), I'd suggest you look into a
distribution with those goals, like:
http://diet-pc.sourceforge.net/
Hope this helps,
Tom
> I'd like some assistance in formulating my plan of attack for a
> thin client project I'd like to implement using LTSP. Here's what I
> need to accomplish:
>
> 1) Boot diskless thin client kernel from:
> A) Disk-On-Chip Flash card if kernel image present
> B) if no kernel image on DOC, use DHCP to contact TFTP
> server to download kernel and copy to DOC
> 2) As the client is diskless I'd like to run the OS from either
> a RAMDISK or a temp file system in RAM
> 3) Load X and a RDP client to access MS Term server.
--
----------------------------------------------------------------------
Thomas L. Griffing Red Hat Certified Engineer
Pondus Solutions, Inc. [EMAIL PROTECTED]
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_____________________________________________________________________
Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto:
https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
For additional LTSP help, try #ltsp channel on irc.freenode.net
