Dude.
You're right.
It's not on purpose, but is a side effect of the part of the read_local_cfg function that tries to determine if we should look for a local.cfg file on the local hard disk.
But, I think I should break this out into a seperate function now. Behavior won't change, but the code will be a mite cleaner.
Cheers!
Thus spake Jerry G. DeLapp ([EMAIL PROTECTED]):
On Monday 24 May 2004 03:36 pm, Brian Elliott Finley wrote:si_imagename si_this si_that si_theother
This would allow someone at the syslinux "boot:" prompt, to type in:
boot: systemimager si_imagename=my_image
The /etc/init.d/rcS would then parse these out, and set the miscellaneous si variables appropriately.
The requested use: "I want to choose my master autoinstall script at boot time ($IMAGENAME.master)."
What say you?
Doesn't it already do that? I know I boot images all the time without DHCP like this:
boot: kernel initrd=initrd.img root=/dev/ram HOSTNAME=blah.localdomain DEVICE=whatever IPADDR=whatever ad nauseum.
The minimal set necessary is HOSTNAME DEVICE IPADDR NETMASK BROADCAST IMAGESERVER.
I'm almost certain that anything you can put in a local.cfg file can be passed on the command line, including IMAGENAME.
--
------------------------------------------------------
Brian Elliott Finley Argonne, MCS Division Mobile: 630.631.6621 Office: 630.252.4742
gpg --keyserver wwwkeys.pgp.net --recv-keys 10F8EE52
------------------------------------------------------
-------------------------------------------------------
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
_______________________________________________
Sisuite-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/sisuite-devel
