Tyson D Sawyer <[EMAIL PROTECTED]> writes: A couple of comments.
> I need to better organize the boot and update process so that we can do upgrades > to these robots without ever leaving one unbootable as it costs several hundred > dollars to open one of these things up and reseal it if we have to really > bootstrap it again. I currently have two independent copies of LinuxBIOS on the supermicro p4dc6. A fallback and a normal image. The switching is accomplished entirely in software, and I automatically return to the fallback if the boot does not succeed. In a production environment I never expect to update the fallback image. You might find a better way or this might be an example you want to clone. > Those are the high level goals I need to achieve for the project. The more > tangible TODO for achieving this are: > > - Look at linux booting linux instead of the linuxbios command line for choosing > > kernels and filesystems that I use now. A second option is to do something like src/standalone/lbbl which is a simple ELF executable reusing code from LinuxBIOS but allowing you to implement your current strategy. With it being two seperate executables the LinuxBIOS core won't succumb to bootloader feature creap so it isn't a problem. > Was that more information than you needed? ;-) Useful. Eric
