Thank you for your help. I was unaware of UUID(s) and the first thing I 
find is that you should use UUIDs instead of /dev/...

I will do a bit more work on UUIDs and try figure out the machinations of 
uEnv.txt and /etc/fstab and try figure out the final details myself. I will 
post for posterity whatever I discover works so the next noob won't waste 
so much of your valuable time.

Thanks again.

Brian

On Tuesday, January 7, 2014 9:51:24 PM UTC-5, RobertCNelson wrote:
>
> On Tue, Jan 7, 2014 at 8:41 PM, Brian Piccioni 
> <[email protected]<javascript:>> 
> wrote: 
> > Please bear with me. 
> > 
> > When I log into the source system it says 
> > Welcome to Ubuntu 13.04 (GNU/Linux 3.8.13-bone21 armv7l), which is a 
> 3.8.13 
> > Kernel (?). 
>
> Oh, that was 7 months ago... let's just call it "old" and therefor 
> "broken".. 
>
> > 
> > When I made the copy I had burned this image to a microSD 
> > 
> > Angstrom-Cloud9-IDE-GNOME-eglibc-ipk-v2012.12-beaglebone-2013.08.21 
> > 
> > Based on your comment, I inserted a spare microSD into the destination 
> BBB 
> > it works (apparently) perfectly. (!!!!) 
> > 
> > THANK YOU! 
> > 
> > Now, if I update the Kernel on the source BBB, then recreate the source 
> and 
> > copy it to the destination should it behave properly even without a 
> microSD? 
> > 
> > This is not absolutely critical because my application will pretty much 
> > always have a microSD card installed, however, if the microSD were 
> defective 
> > or not installed properly, etc., the original BBB could at least tell me 
> > while the copies would not. 
>
> Use an UUID instead of a raw /dev/mmcblk name in your bootloader 
> (uEnv.txt) and /etc/fstab then you won't have to worry about that.. 
>
> Regards, 
>
> -- 
> Robert Nelson 
> http://www.rcn-ee.com/ 
>

-- 
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/groups/opt_out.

Reply via email to