[gPXE] Help me design a way to boot one of many predefined OSes with a short, single command
Tal Aloni
tal.aloni.il at gmail.com
Thu Feb 4 13:44:53 EST 2010
Hi everyone,
as a software developer, I occasionally test software that is tied to specific hardware, and since I have to test the software under many operating systems, you might imagine that gPXE is by far, the best way to do it.
as a result, for the past year, I found myself entering those long chain-commands.
recently, during a long test session, I've decided that I'm going to find a faster way to do it.
it turns out that there is more than one way to achieve my goal,
I want to develop something that would be helpful to more than just me, please help me decide which of the various options is fitting to this project and would be the most helpful, if you have additional ideas, please let me know.
approach #1:
currently, gPXE execute only the first embedded image, we can use additional embedded images (scripts), one to load each OS, and manually execute them when needed.
changes required to gPXE:
1. ability to load and execute an embedded image in a single command (two commands are required today, as chain does not work on embedded images)
note:
gPXE always executes the first embedded image, so it's recommended that the first image would contains the command autoboot.
(if Ctrl-B has not been pressed, that's the script that would be executed)
cons:
it's necessary to keep an image up to date with many embedded scripts,
the user would have to rebuild the image every time an OS has been added.
we can make it easier by extending rom-o-matic, and define syntax that allows to add multiple scripts.
approach #2:
use the first embedded image to set variables containing the necessary commands, and then enter the variables in the command line.
changes required to gPXE:
1. show the Ctrl-B dialog for a second time (after the embedded image have been executed)
2. ability to set variables contains more than one word (complete commands)
3. ability to autoboot after embedded image execution. (in case it only used to set variables)
cons:
- the Ctrl-B will only be usable for our purpose the second time it will be shown
- some people may (?) want to skip autoboot after embedded image execution failed, this won't be possible anymore.
I would be glad to hear any opinion,
you are also welcome to ask me questions,
Thanks,
Tal
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://etherboot.org/pipermail/gpxe/attachments/20100204/719c0306/attachment.html
More information about the gPXE
mailing list