You pretty much have 5 options. dd, cp, rsync, tar, and cpio. But if you want a really good discussion about whats best, you can google stuff like "unix exchange rsync" and just read everything. I was actually reading a post last night about rsync versus cp I think.
Anyway, it honestly does not get any easier than rsync -a <source> <destination> . . . But I like dd too for variou occations, as well as tar. I've never realy used cpio but have read about it, and cp . . . well it's not up to snuff if you ask me. On Sat, Oct 31, 2015 at 2:32 PM, [email protected] <[email protected]> wrote: > After slapping myself a few times, that's what I ended up doing. dd'ing > would be faster, but I was not comfortable that I'd get the options right. > > Next experiment... > > On Sat, Oct 31, 2015 at 2:35 PM, William Hermans <[email protected]> > wrote: > >> Or even rsync to sdcard . . . >> >> On Sat, Oct 31, 2015 at 1:14 PM, Robert Nelson <[email protected]> >> wrote: >> >>> >>> On Oct 31, 2015 2:41 PM, "[email protected]" <[email protected]> wrote: >>> > >>> > Hi Arsi, that was my backup plan, but that's a *little* bit less >>> efficient than a direct write to the SD card on the BBB. >>> > >>> > I found Robert's 2 year old eMMC-to-SD script on GitHub; wonder if >>> that's still up-to-date. Guess I'll try! >>> >>> It is, but it's a little risky on old rootfs, specially prior to Sep >>> 2014.. As we made major changes to the location of the boot loader and >>> kernel location on disk, that summer. (Since that major change we haven't >>> broken it.) >>> >>> I'd recommend, NFS/rsync backup the boot/root.. Install the 2015-07-28 >>> image, double check the new kernel works for you. (3.8.13 based in that >>> image). Then rsync back just the 'root'.. Double check it still works with >>> your changes.. Then you can use the built in emmc to SD backup across. >>> >>> 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. >>> >> >> -- >> For more options, visit http://beagleboard.org/discuss >> --- >> You received this message because you are subscribed to a topic in the >> Google Groups "BeagleBoard" group. >> To unsubscribe from this topic, visit >> https://groups.google.com/d/topic/beagleboard/8G61AQECz08/unsubscribe. >> To unsubscribe from this group and all its topics, send an email to >> [email protected]. >> For more options, visit https://groups.google.com/d/optout. >> > > -- > 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. > -- 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.
