Neil Robst <[EMAIL PROTECTED]> writes:

> Thanks for this Max.
> 
> PXELinux can call a different pxelinux.cfg file based upon that the
> client's IP address. Therefore is there something I can put in the
> pxelinux.cfg config file that will pass a parameter name containing the
> unattended.txt file to use to unattended???
> 
> Regards,
> Neil

We have no direct support for this, but it can be done with a little
Perl coding.

The kernel parameters appear in "/proc/cmdline", as for any Linux
system.  So you can look there to find the options passed by PXELINUX.

Also, DHCP option 233 appears in the "unattend=..." line of
/var/run/dhcp.out.  We create this file ourselves in our
udhcpc-script, which runs when the DHCP lease is obtained.  (We
patched the DHCP client to hand us option 233, a number which I picked
after careful meditation and Google searching.)

In your case, I would recommnd using the DHCP option, since that
avoids the need for multiple pxelinux.cfg files.

You need to parse /var/tmp/dhcp.out to obtain the "unattend=..." line,
then parse that line to get the unattend.txt file name, then use
$u->load() to read it.  I realize this is messy, but it should work.

For the next release, I will look into adding a "get_cmdline_param()"
interface to install.pl, which will let you query the kernel command
line and DHCP option 233 directly.  This interface may be difficult to
support under DOS, however.

 - Pat


-------------------------------------------------------
This SF.Net email is sponsored by: Oracle 10g
Get certified on the hottest thing ever to hit the market... Oracle 10g. 
Take an Oracle 10g class now, and we'll give you the exam FREE. 
http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click
_______________________________________________
unattended-info mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/unattended-info

Reply via email to