Hello, I'd need the SD image I prepared for the xM to be supplied to people without them changing a single bit in it. Also, this avoids write failure with power supply failures and increases the life of the SD. >From my understanding this can be done by mounting the rootfs as read-only at some point in the boot and writing any change to the RAM without making them persistent. But I'm not expert in the bootstrap process with Linux.
The only similar case I know in detail so far is with Ubuntu 10.10 https://ccrma.stanford.edu/~eberdahl/satellite/ and it has two uInitrd images for boot, one with aufs enable and the other without. They only differ in a couple of scripts and if one wants changes to be persistents it is enough to mv files in the boot partition in order for the bootloader to pick the right one. Now, I'm using debian and the rcn-ee builds. Here the boot partition is different it uses initrd.img and zImage. I'm not sure what to do here since it is a different boot method. Are there any suggestions on how to reach my goal? Any simple solution, even performed with an init script after bootstrap would be fine as a starter. Regards -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
