Am Sonntag, 27. Juni 2004 13:23 schrieb [EMAIL PROTECTED]:
> (1) Is it possible to load the client software onto an HP t5500 thin client
> (diskless) NC. The web states HP is giving LTSP its full support and that
> the t5500 can be used as a client. How do I load the Linux boot image onto
> the NC - I cannot seem to find any documentation on how this is done. I
> normally flash these devices with CE.NET using either a parallel cable or
> FTP update. I have no idea however on flashing the RAM disks in these NC's
> with LTSP boot images.
I hope that boxes support PXE. That means, at every system boot, you load the
linux kernel and initial ramdisk via network, by means of etherboot or
pxelinux. Both should be possible. If that box does not support network
booting, that's a bit more complicated though. Check the BIOS setting,
perhaps press F12 on booting etc.
> (2) How do I properley uninstall the LTSP on my server once I have
> installed it. I want to re-install it but when I run its configuration
> script it will not 're-add' the config files etc. I have uninstalled the
> RPMS but I dont think this has deleted the config files and folders that
> LTSP installed.
As the only LTSP specific stuff is in /opt/ltsp, you can just
rm -rf /opt/ltsp
to remove that (and perhaps delete /etc/lts.conf, if it exists).
The rest is put together by tweaking standard daemons' config files, which
you, in doubt, will have to undo by hand (but there's no need to, usually).
> (3) Has anyone got any advice for me on setting up the network addresses,
> DHCP entries and my network address rage etc. in the LTSP config files.
> Also how does DHCP work with LTSP - my Linux box (on which LTSP is loaded)
> is not a DHCP server. Is this a problem? Our DHCP servers on our local
> network are Windows NT machines. I could setup the Linux box as a DHCP
> server if required but I dont reallyyyyyyy want to.
If the box netboots, it will need a dhcp server that knows "what goes on",
where the boot image resides etc. It's probably a good idea to have, at least
in the beginning, a second network card in your linux LTSP server to which
only the terminal(s) is/are wired. There are ways around, but for learning it
all, it's much easier to go this way.
You'll need a separate address range for this new network then, so choose any
10.x.y.*/255.255.255.0 that's not currently in use in your organisation, or
any 192.168.x.*/255.255.255.0. Then setup your dhcp server on the linux box
(you'll need one now) to only play with the new network (by giving it only
the one interface to listen on).
> Any help will be greatly appreciated. If I can get this system working it
> could mean a big step towards our company utilising Linux solutions to meet
> our terminal server needs in the future.
In case you run into specific trouble (like dhcp setup, tftp trouble etc), I
recommend also checking if there's some help to be caught in the #ltsp
channel on irc.freenode.org - there's not always someone on to help you, but
most times you'll find advice there.
You'll also notice that there's been much topics on the mailing list - the
archives (I think on gmane.org) could have information to a topic where you
just "can't find the key to press" :-)
Regards & hth
Anselm
-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 -
digital self defense, top technical experts, no vendor pitches,
unmatched networking opportunities. Visit www.blackhat.com
_____________________________________________________________________
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
