Hi,
After playing around with lbmenu, I came up with the following idea to select payloads in a clean way.
1a, linuxbios parses the payload number cmos position, and starts the selected payload
or
1b, linuxbios loads a payload (lbmenu), and passes control to it
2, lbmenu parses the lar 3, the user selects which payload to run 4, lbmenu writes the payloads number (position in lar) to a cmos variable and gives back control (point 1a)
Imho it is better to have always the 1a, way running, but we have to be sure the cmos contains a valid value.
Of course with this method payload selection can be repeated as much times as we want in a single run.
-- Alex
On 9/8/07, Alex Beregszaszi alex@rtfs.hu wrote:
Hi,
After playing around with lbmenu, I came up with the following idea to select payloads in a clean way.
1a, linuxbios parses the payload number cmos position, and starts the selected payload
or, if it is out of range, an emergency payload :-)
Imho it is better to have always the 1a, way running, but we have to be sure the cmos contains a valid value.
we want an unattended boot ability.
I hope to try lbmenu out soon.
ron
On 08/09/07 11:36 -0700, ron minnich wrote:
On 9/8/07, Alex Beregszaszi alex@rtfs.hu wrote:
Hi,
After playing around with lbmenu, I came up with the following idea to select payloads in a clean way.
1a, linuxbios parses the payload number cmos position, and starts the selected payload
or, if it is out of range, an emergency payload :-)
Imho it is better to have always the 1a, way running, but we have to be sure the cmos contains a valid value.
we want an unattended boot ability.
Absolutely, if the number isn't at all sane, then we just freak out and load payload 0 by default. Also, the payload number should have some magic bits on it to ensure that what we see is intentional, Like make the top nibble 0xa or something (assuming that we can affort 8 bits of CMOS space, and that we'll only have 16 payloads). Anyway, you get my point.
Jordan
-
Alex Beregszaszi -
Jordan Crouse -
ron minnich