Syslinux - Sep 2002 - RedHat kickstart with PXELINUX [A small change for pxelinux]

It looks like someone else also has the same problem:

http://www.zytor.com/pipermail/syslinux/2002-September/000848.html

I don't know much about Intel i386 asm. Otherwise, I will send a
patch :-).


H.J.
----- Forwarded message from "H. J. Lu" <hjl at lucon.org> -----
I am using pxelinux to do RedHat kickstart install. I ran into a
problem. Both pxelinux and kickstart use

	filename "xxx"

in /etc/dhcpd.conf for different purposes. Naturally, they won't work
together.  I was wondering if a small change to pxelinux could be made.
That is if the filename got from DHCP ends with a `/', pxelinux will
append "pxelinux.0" to it. That means if

	filename "/tftpboot/"

pxelinux will try "/tftpboot/pxelinux.0".

Thanks.


H.J.
----- End forwarded message -----

H. J. Lu wrote:
> It looks like someone else also has the same problem:
> 
> http://www.zytor.com/pipermail/syslinux/2002-September/000848.html
> 
> I don't know much about Intel i386 asm. Otherwise, I will send a
> patch :-).
> 
> ----- Forwarded message from "H. J. Lu" <hjl at lucon.org>
-----
> I am using pxelinux to do RedHat kickstart install. I ran into a
> problem. Both pxelinux and kickstart use
> 
> 	filename "xxx"
> 
> in /etc/dhcpd.conf for different purposes. Naturally, they won't work
> together.  I was wondering if a small change to pxelinux could be made.
> That is if the filename got from DHCP ends with a `/', pxelinux will
> append "pxelinux.0" to it. That means if
> 
> 	filename "/tftpboot/"
> 
> pxelinux will try "/tftpboot/pxelinux.0".
> 
You wouldn't be able to boot -- this filename isn't used by PXELINUX, 
it's used by the network boot PROM to know what to boot from.

I believe you can override the kickstart filename by providing:

append ks=<directory>

in the PXELINUX config file.

(For what it's worth, the way Kickstart uses the filename is nonstandard.)

	-hpa

Hi,

"H. Peter Anvin" <hpa at zytor.com> schrieb am 26.09.02
20:01:49:
> Anyone happens to know which version of tftp-hpa that was?  atftp is 
> probably better handing huge amounts of clients, but tftp-hpa should 
> definitely handle a lot more than 64.
it does handle a lot more, even when started from inetd. I had no problem
booting >100 clients at one time, and this was with tftp-hpa-0.1x (17?).

Maybe this also depends on the inetd used? Some inetd's limit the number
of started processes ...

Regards,

Josef

______________________________________________________________________________
Jetzt testen fur 1 Euro! Ihr All-in-one-Paket! 
https://digitaledienste.web.de/Club/?mc=021106

H. J. Lu wrote:
> 
> Ok, I used pxe
> 
> http://www.kano.org.uk/projects/pxe/
> 
> I made a few changes and created a rpm. I am enclosing the source rpm
> here. Hope it is ok.
>
Sending large binaries to a mailing list is usually considered 
antisocial.  I suspect it will be caught by the spam filter on the list 
in which case I'll kill it.

	-hpa