[ This is veering off topic for LTSP, apologies. ]
> Just one question from the non-Etherboot expert:
> Could you load a kernel and an initrd?
Etherboot knows how to load nbi formatted images, so the work is done by
mknbi, which can also e.g. embed kernel parameters.
> How about the network dr
> > Just configure "pxelinux" from "syslinux" (use freshmeat.net to find it)
> > to boot the kernel and the new initrd.
>
> Exactly: you use pxelinux *instead* of Etherboot, which is perfectly OK,
> but contradicts your previous statement.
Ok. You are right. I just "ignored" the fact that "pxeli
Why we need a PXE HOWTO. :)
> Why do you use etherboot at all?
* I may just prefer Etherboot, e.g. if I already have a working
Etherboot config for other machines.
* Mostly C, so it can be easily developed by more people.
* My goal is to flash Etherboot into my boot roms and replace PXE.
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"
>{
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.al
dear friends,
now the ws in not booting
with pxe, i can ran the ws with floppy i can run, if i
tried to boot the ws through pxe booting means, it
says "boot file not found" error.just i attached my
detailed conf files,
please help me.
In pxe server, dhcpd daemon is disabled by ntsy
