Hello James,

Wednesday, December 18, 2002, 6:19:41 PM, you wrote:

JTRJ> Hello,

JTRJ> I've successfully installed the LTSP software and I currently have one Redhat 
8.0 based server and one X-Terminal.

JTRJ> The X-Terminal is a Pentium 200, with no hard disk (just floppy & CDROM) and a 
3c905b NIC. It also has an AWE64 soundcard.

JTRJ> What I'd like to be able to do is have each machine be able to use their 
floppy/cdrom/audio/(possibly Zip/Jazz) devices, yet remain (hard)diskless. Is this 
possible? I've read in the ltsp
JTRJ> contrib section about using ftp and automount to do this, but it seems more like 
an ugly hack for my purposes.

There is an approach like NBD (Network block devices). I set it up
after howto from the net and it still runs, but I'm not into it right
now. Search for NBD on the ltsp pages.

JTRJ> For example, I'd like to be able to have a user insert an audio cd and have it 
play on their workstation only. 

local-apps, then use some command-line (or X) cd-player controlling
software? I hope that's not to hard to do. Never did myself though.

JTRJ> I am also curious about the local X-Terminal. For example, how can I get access 
to it's root filesystem after a user has logged in? (I'd like to see a /proc 
filesystem for example). 

You could compile a static telnetd (that needs no libraries) and put
it inside /opt/ltsp/i386. Then chain it somehoe into the terminal
start scripts, and telnet to that workstation when it is up.

Don't forget to remove it once you are done.

JTRJ> I've noticed that the X-Terminal always has a hostname of "wks001" or something 
like that, where is pulling this hostname from?

>From dhcp. You remember reading something about
host ws001 {
     fixed-address 1.2.3.4;
     hardware ethernet 00:11:17:54:f2:22;
}
entries inside dhcpd.conf?

It can be done more luxuriously for numerous clients, see my posting
from about 5 minutes ago to the topic "[Ltsp-discuss] dhcpd"

HTH

Anselm                            mailto:[EMAIL PROTECTED]

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

Reply via email to