[gPXE-devel] Integrate lighthttpd into etherboot

[Lap Ngo Doan]

Hi Oliver,
Thank for you quick answer.
>>Imho gpxe doesnt suppurt enabling/disabling disk and other bios-settings
excluding >>networking, so this work has to be done additionally. Dont
forget: Every BIOS is its own >>kingdom! You have to do this for every new
Bios again!
Yes, I know I need to do some works. As you know, basically all of works
related to interfacing with hardware (like BIOS firmware provide us) should
be done by lower level (often written by asm or C).
Now I'd like to add a higher level to allow user setting some parameter
over the network on HTTP.
And for prototype version, I know I should reflash Bios again and again.

>>You have anouter problem: At boot time normally the computer hasnt an
ip-address so he has >>to get one. Now you have to know, if the ip-address
hosts the right computer and so on.
We just want do some setting for the board. Can we fixed the address for
device? For example 192.168.1.1 If user want to change some thing on
device, they should connect to the device from that IP address.
>>Addittionally, lighttpd is an overkill (who needs php at boot-time?) and
will imho waste to much >>space, but maybe tinyHTTP will be adequate for
you?
Yes, I only need tinyHTTP.

>>Maybe  (g|i)pxe will communicate better via aoe  (ethernet frames) than
with http, so no ip->>address is needed. In other way, the fork of gpxe,
"ipxe" (www.ipxe.org) has a powerful script >>engine inside, which can
download the needed script _after_ download ipxe, so you can fit >>your
needs into it dynamicly. Maybe this will suffice your needs?
Thank for you suggestion. I will investigate ipxe for more details.

On Mon, Aug 13, 2012 at 5:37 AM, Oliver Rath <rath at mglug.de> wrote:

>  Hi Lap!
>
> Principially this is a good idea.
>
> Am 13.08.2012 11:16, schrieb Lap Ngo Doan:
>
> Hi Oliver,
> Thank for you answer.
>  >>What kind of information  do you want to get from a running
> lighttpd-Server on gpxe?
> Coreboot is a Free Software project aimed at replacing the proprietary
> BIOS (firmware) found in most computers. coreboot performs a little bit of
> hardware initialization and then executes additional boot logic, called a
> payload.
> Unfortunately, coreboot doesn't support user interface to change some
> setting on BIOS (for example: enable/disable disk, boot devices priority...)
>
>
> Imho gpxe doesnt suppurt enabling/disabling disk and other bios-settings
> excluding networking, so this work has to be done additionally. Dont
> forget: Every BIOS is its own kingdom! You have to do this for every new
> Bios again!
>
>
>   I want to get/set some hardware parameters like BIOS provide by adding
> Etherboot as a payload of coreboot.
>
>  >>What do you want to do with this else, which cant be done by a
> webserver on a running linux-system?
> I want to get/set some hardware parameters over the network on HTTP before
> the running linux-system.
> It mean that, this utility is on ROM
>
>
> You have anouter problem: At boot time normally the computer hasnt an
> ip-address so he has to get one. Now you have to know, if the ip-address
> hosts the right computer and so on.
>
> Addittionally, lighttpd is an overkill (who needs php at boot-time?) and
> will imho waste to much space, but maybe tinyHTTP will be adequate for you?
>
> But nevertheless it is a good idea :-)
>
> Maybe  (g|i)pxe will communicate better via aoe  (ethernet frames) than
> with http, so no ip-address is needed. In other way, the fork of gpxe,
> "ipxe" (www.ipxe.org) has a powerful script engine inside, which can
> download the needed script _after_ download ipxe, so you can fit your needs
> into it dynamicly. Maybe this will suffice your needs?
>
>
> Regards,
> Oliver
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://etherboot.org/pipermail/gpxe-devel/attachments/20120813/449da53b/attachment-0001.html>