Actually, I think figuring out how to load from multiboot (install bootimg, write item) is just as easy as figuring out how to do it from uboot. Both require a similarly limited and basic set of instructions, HOWEVER, I don't think as simple of an instruction set exists. When I've finished my current project(s) (write localization for Russian for Sleep Analyzer; create my custom clock plugin for Advanced Clock Plugin; try to become useful at python enough to write patches for, and support, Advanced Power, Advanced Power Monitor, and Advanced Interface Switcher), I will do my best to write up such guides, and provide easy-to-use .debs for each OS (NITDroid and MeeGo), as well as see if I can figure out RobbieThe1st's backupmenu and uboot enough to figure out how to make a uboot-only version.

This does not mean get your hopes up - but it does mean that if no one else gets it done reasonably soon, I will make a sincere effort to do so.

RobbieThe1st: Sorry I kinda dropped out from this thread from back before you even implemented SSH in BackupMenu. I greatly appreciate your work, even if I personally haven't used it yet. I've just been busy. But I will be catching up on this thread relatively soon. Really glad to see your latest post being pro-uboot and showing support for a uboot port.

One1002: UBoot supports any OS, pretty much. Literally, just about any OS you can think of, if it can load on the N900, uboot can load it, from MMC, from SD card, from rootfs, over SSH through USB or something, just about anywhere. The only thing is it's not built from the ground up to be user friendly, so selection isn't AS simple as using the arrow keys to select a different OS. Also, you need mkimage if you want to take a not-yet-made-for-uboot kernel image, and convert it from a zImage to a uImage. However, I just took the mkimage binary from the Debian Lenny packages for armel architecture, stuck it on the N900 at /sbin/ and it works just fine.

Speaking of which, RobbieThe1st, any chance you can include the fiasco-flasher (admittedly a Nokia binary, only distributed in the PR1.0 kernel, and not really free to distribute - may need to file a request or bug report for that), the regular on-board-the-N900 'flasher', and mkimage within the backupmenu? This would let people reflash kernels and/or make them from within backupmenu if they'd like, saving the need to use a computer for N900 revival even if the N900 won't load to any of the kernels.