On Tue, Feb 9, 2010 at 6:16 AM, Shao Miller <[email protected]>wrote:
> Luca wrote: > >> Hi all, >> I wanted to pass some parameters to gPXE, when it starts. As I do not >> want to rebuild the gPXE image every time with a new script... >> > > Would the InitRD+CmdLine feature be useful to you? > http://etherboot.org/share/sha0/gpxe/src/bin/gpxe.lkrn > This gPXE build is a "Linux kernel"-format binary which you can load with > any bootloader capable of loading Linux kernels (bzImage). You can pass a > gPXE script as an initrd and this gPXE will find it. > > For GRUB, that might look like: > > title Load gPXE > kernel /gpxe.lkrn > initrd my_script.gpxe > > So if I got it right, I would keep using the same gPXE image and I would just change the gpxe script at every boot. Problem is that script is generated by a central entity just before a workstation is gPXE booted so I can't store the script on the workstation, I need gPXE to contact a remote server and get it. I don't know if that's useful to you or not. Can be handy with QEmu without > constantly rebuilding gPXE. > > # qemu -kernel gpxe.lkrn -initrd my_script -hda /dev/null > > Disclaimer: All claims and opinions are solely those of myself and do not > and should not be perceived as representing the Etherboot nor the gPXE > projects in any way. Thank you for your understanding. > > - Shao Miller > > >
_______________________________________________ gPXE mailing list [email protected] http://etherboot.org/mailman/listinfo/gpxe
