But before going farther, the configuration that I want is:
1. boot-image on SD (losetup, etc).
2. home in the boot-image OR load cardfs to /
There's not enough space to load the cardfs to /
I successfully got the Hentges image into the boot-image with no trouble, but in trying to load cardfs, I got the option of: cf, card or /home/. The problem with home of course is that it is back on the internal flash.
Why is that a problem? With the poodle set up this way you can boot anything you want off the SD-card... or remove it and still have a system that works. With the ability to do this you can change one or all of the multiple boot images on your SD-card you want... imho it's a nice feature for testing other images.
Greg
[div align=\"right\"][a href=\"index.php?act=findpost&pid=91899\"][{POST_SNAPBACK}][/a][/div]
I guess I didn't mention that / would be on the image too - like standard "root on SD"
Yes Greg - swapping out images without the cardfs is a very legitmate way to use it of course - but I am looking to swap "entire" images - and even more importantly back them up.
An even more optimal situation, in some cases, would be to mount the "/home/" and/or "/" in another "ext image" file. This would allow easy swapout of any of the three in testing.
I am not really concerned about that though - unless it would make upgrading from 3.5.3 to 3.5.4, for example, easier.
If I am still not making myself clear, the desire after booting (with altboot) is to be running entirely off the image(s) on the SD card except for tempfs, etc and real RAM, of course. This would allow me on a daily basis, for example, to pop out the SD card, back up the image to a CD/DVD RW, and put it back in. So I have EVERYTHING backed up - like I would do with Acronis on my laptop. So if my SD card did fry, just copy the backup image onto a new one, plop it in and proceed. I have saved myself on my laptop(s) twice this way when hard drives died.
If I am missing something here - please correct me.