I am in the same boat as you. We want to boot a GNU-Linux OS in order to
run a Citrix ICA client that will connect to our Metaframe servers. Our
choice for nics is the Intel Pro 100 S, we started buying them for our heavy
clients. I am using the PXE feature of these nics (they don't have a place
for an eeprom) to boot off the network. Se have various subnets separated
by Cisco switches.
> > After reading it over, though, I'm not sure that it's the best/most
> > efficient way of making PXE clients work with LTSP? What I mean is, it
> > looks like the author patched something together that works by using PXE
to
> > load up and launch etherboot code. That, in turn, connects to the LTSP
> > server using the more conventional, non-PXE method. I don't see why I
can't
> > just boot directly from PXE protocol and skip the step of loading
etherboot
> > code?
There is link from the contrib page to
http://people.redhat.com/alikins/ltsp/. This page seems somewhat outdated,
although some of the info is good. You can find Pxelinux at
http://syslinux.zytor.com/. That is what we are using right now. We didn't
have to use the PXE server that you talk about in another e-mail. Rather
than putting a kernel or etherboot image in DHCP file option, we just put
/path/pxelinux.0. Pxelinux then will look for a config file in /the
directory where it found pxelinux.0/pxelinux.cfg/default or the hexadecimal
representation of the IP. In the config file you can give it options much
like those of lilo. This is explained better at the syslinux site.
Although I compiled my kernel with DHCP support, it doesn't seem to get
DHCP info when it boots. I did not check the log to see more info. I used
the IPAPPEND 1 option to pass the ip info from pxe to the kernel. Does
anyone know how or if you can pass the hostname to the kernel as an append?
> > No, I fully understand that either Windows 2000 or Linux DHCP server can
> > issue either dynamic or static IP addresses. The only reason I'm
interested
> > in issuing dynamic IPs to the LTSP clients is for ease of
administration. I
> > don't like having to manually set up a MAC address to IP address
> > relationship in a config file on the LTSP server for each one of the
clients
> > I set up. (Not only that, but if someone moves a client from one
location
Our test situation is using a linux DHCP 2.0 server right now. But before
it goes production we will integrate it with the 2000 DHCP. Our
configuration should be very simple on 2000 because we are not using vci
options or any "if" statements in DHCP as mentioned in the pxe.howto.htm.
Later if you want I could send you our config files.
_____________________________________________________________________
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.openprojects.net
