Peter Rundle wrote:
>
> Your dhcpd.conf file needs to look like this:-
>
> if substring (option vendor-class-identifier, 0, 9) = "PXEClient"
> {
> filename "/tftpboot/lts/eb-5.0.3-eepro100.pxe";
> }
> else if substring (option vendor-class-identifier, 0, 9) = "Etherboot"
> {
> filename "/tftpboot/lts/vmlinuz.all";
> }
>
> With PXE booting the system goes to the dhcp server and tftp server
> twice, once to get the eitherboot code (which is otherwise on the
> floppy or burnt into the eprom), and a second time to get the
> kernel.
Why do you use etherboot at all?
PXE does all you need, at least with the LTSP-2.09pre3 kernel and initrd
package:
I myself boot LTSP using "pxelinux" the following way:
Just configure "pxelinux" from "syslinux" (use freshmeat.net to find it)
to boot the kernel and the new initrd.
Nothing more.
Just this.
Boots fine, and does not need etherboot!
The whole setup needs:
1. dhcpd configured to load "pxelinux" binary
2. pxelinux.cfg configured to load kernel and initrd.
3. kernel from kernel package
4. initrd build from initrd package.
I'm working here with an AOpen MX3S mainboard, pxe in BIOS.
No disk, no floppy, no cdrom, but still booting LTSP(2.09pre3).
So long,
J�rgen
_____________________________________________________________________
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
