Darn it, I forgot the most important thing, and I have no way to test this to make sure it is 100% accurate - right now.
You need to backup the MBR in the case of a single partition setup. something like this: http://www.cyberciti.biz/faq/howto-copy-mbr/ However, I'm not 100% sure how large the MBR is or how to check. I'm mostly sure Robert has this set to 1M but am not 100% positive. But if it is . . . dd if=/pathto/sdcard of=/some/path/mbr.bak bs=1024 count=1 This would be done sometime prior to using fdisk / sfdisk to create a new partiton setup on the sdcard. Then once you have created a new partition with fdisk / sfdisk you would . . . dd if=/some/path/mbr.bak of=/pathto/sdcard bs=446 count=1 Crap I hope you haven't started on this yet. Tell you what give me a few hours, and I can test this all myself and have exact steps when done. On Thu, Jun 11, 2015 at 11:58 AM, William Hermans <[email protected]> wrote: > OK, a few caveats I noticed about that article. > > First, you'd be mounting the sdcard on a mount point created by yourself. > such as: > > sudo mkdir /media/rootfs/ > sudo mount /pathto/sdcard /media/rootfs > > Second, once the sdcard is mounted, you will have to cd into the topmost > directory such as: > > cd /media/rootfs > > Once here, if you run ls you should see your basc rootfs directory > structure. Once that is confirmed . . . > > makedir ~/backup > sudo tar -zcvf ~/backup/rootfs.tar.gz . > > NOTE: the dot after the full tar command. It is necessary to tell tar what > to do, and in this case, tar the entire current directory structure. > > Anyway, you can probably figure out how to use fdisk / sfdisk to create a > partition the size you want. As well as using makefs.ext4 or whichever > filesystem type you want on that partition. But make sure while in fdisk > you mark the boot partition as *boot* > > Once all that is done . . . > sudo mount /pathto/sdcard /media/rootfs > sudo tar xzvf ~/backup/rootfs.tar.gz -C ~/media/rootfs > > And that should be it. If for some reason it does not boot, put the sdcard > back into your running Linux machine, run fdisk on it, and double check to > make sure the boot partition *is* maked as active boot. This has tripped me > up a few times myself, often enough to where I usually double check with > fdisk before I take it out of the working Linux system I'm using to begin > with. > > > > > On Thu, Jun 11, 2015 at 11:13 AM, William Hermans <[email protected]> > wrote: > >> errr, ooops, you must make sure the boot partition is marked as active >> boot with fdisk. >> >> On Thu, Jun 11, 2015 at 11:11 AM, William Hermans <[email protected]> >> wrote: >> >>> Yes. By using tar, and the "imaged" partition(s) would have to be >>> "offline". >>> Meaning you would have to put the sdcard into a system that was already >>> running Linux. Here is the gist of things: >>> http://www.aboutdebian.com/tar-backup.htm >>> >>> So anyway, once you have a rootfs backup, you'd have to use fdisk, or >>> sfdisk to create a new partition(s), then makefs to create the file >>> system(s) type that you wanted. Finally, tar the image onto the new >>> filesystem. >>> >>> On Thu, Jun 11, 2015 at 8:39 AM, William Pretty Security < >>> [email protected]> wrote: >>> >>>> Not to worry. >>>> >>>> I do have one question though. >>>> >>>> >>>> >>>> My actual image size is usually about 3GB, however I can only find 8GB >>>> uSD cards. >>>> >>>> I tried just formatting half of the card (4GB) but I still get an 8GB >>>> image, using the ‘standard’ imaging tools. >>>> >>>> Is there some way I can Image just the boot partition and the roofs? >>>> >>>> >>>> >>>> Thanks; >>>> >>>> Bill >>>> >>>> >>>> >>>> *From:* [email protected] [mailto: >>>> [email protected]] *On Behalf Of *William Hermans >>>> *Sent:* Thursday, June 11, 2015 12:26 AM >>>> >>>> *To:* [email protected] >>>> *Subject:* Re: [beagleboard] Displaying GPS Data ? >>>> >>>> >>>> >>>> William, >>>> >>>> Sorry, the only notes I could find are rather incomplete, and I could >>>> not find the puTTY log sessions I used to have on my old laptop. I could >>>> piece together a couple of txt note files I kept that are sort of exact >>>> steps I used to create the whole setup. More or less. >>>> >>>> Something to consider though. I do not use the any of the "official" >>>> images for my own "production" images. I have kind of a what some may >>>> consider a "convoluted" setup. I use two images, both of which are NFS >>>> rootfs;s. One for development, and one for "production". The development >>>> image I use to install all necessary development tools such as gcc, >>>> build-esential, checkinstall, etc. On which I built my own version of >>>> nodejs( 0.10.29 if memory serves ). When then I created a Nodejs *deb >>>> package to install on the "production" image. >>>> >>>> My production image is pretty much just RCN's bare-fs rootfs, with a >>>> minimal set of what I consider necessary tools installed. openssh-server, >>>> psutils, ntpdate, etc. The whole thing including Nodejs sits( again, if >>>> memory serves ) at around 95M total size in flash though . . . which is why >>>> my setup is so convoluted . . . >>>> >>>> Anyway, if you're interested, let me know, and I will try to get you >>>> something as complete / accurate as possible. >>>> >>>> >>>> >>>> On Wed, Jun 10, 2015 at 1:53 PM, William Hermans <[email protected]> >>>> wrote: >>>> >>>> complete code for the Nodejs app >>>> >>>> index.js >>>> http://pastebin.com/w4PiZ23t >>>> >>>> index.html >>>> http://pastebin.com/vbDx1KG0 >>>> >>>> package.json: >>>> http://pastebin.com/u4vc0w8x >>>> >>>> It's a rather simple app, but it could be as complicated as one would >>>> like. I pastebin'd package.json so you would know which versions of >>>> express, and socket.io I used. Which can be pretty important if you're >>>> new to nodejs like I was when I first wrote this app . . . I also have >>>> noted somewhere but I'll have to dig for them, it's been several months >>>> since I learned / wrote this, and javascript / nodejs is not really one of >>>> my strong points . . . >>>> >>>> >>>> >>>> >>>> >>>> On Wed, Jun 10, 2015 at 1:32 PM, William Pretty Security < >>>> [email protected]> wrote: >>>> >>>> Thanks. That would be GREAT !! >>>> >>>> >>>> >>>> *From:* [email protected] [mailto: >>>> [email protected]] *On Behalf Of *William Hermans >>>> *Sent:* Wednesday, June 10, 2015 3:51 PM >>>> *To:* [email protected] >>>> *Subject:* Re: [beagleboard] Displaying GPS Data ? >>>> >>>> >>>> >>>> I did the same thing with a TEMPer v1.4 USB thermometer dongle. Running >>>> the application through Nodejs, and then parsing the output in a callback. >>>> Let me see if I can find my code, or notes. >>>> >>>> >>>> >>>> On Wed, Jun 10, 2015 at 12:45 PM, William Hermans <[email protected]> >>>> wrote: >>>> >>>> Nodejs + child_process.exec to run the GPS executable, and then in a >>>> callback parse the output. Then do with it as you wish. Something like >>>> this: >>>> >>>> http://www.dzone.com/snippets/execute-unix-command-nodejs >>>> >>>> In that example though the person is just printing the output of pwd to >>>> stdout, etc. But the concept is the same-ish. >>>> >>>> >>>> >>>> On Wed, Jun 10, 2015 at 12:25 PM, William Pretty Security < >>>> [email protected]> wrote: >>>> >>>> Hello Group; >>>> >>>> >>>> >>>> I have a webpage server running on a BBB. This page currently serves >>>> (streams) video from my robot. >>>> >>>> I would like to also display the Lat/Long from the onboard GPS. >>>> >>>> >>>> >>>> I have CGPS installed and working. It writes text to the console. >>>> >>>> What I would like to know is how to send this text to a text box or >>>> whatever on the web page. >>>> >>>> I’m thinking node.js + java script? >>>> >>>> >>>> >>>> Thanks; >>>> >>>> >>>> >>>> Bill >>>> >>>> >>>> >>>> "All that is necessary for the triumph of evil is that good men do >>>> nothing" Edmond Burke *(1729 - 1797)* >>>> >>>> >>>> http://www.packtpub.com/building-a-home-security-system-with-beaglebone/book >>>> >>>> http://ca.linkedin.com/pub/bill-pretty/2b/b07/602 >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> -- >>>> 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. >>>> >>>> No virus found in this message. >>>> Checked by AVG - www.avg.com >>>> Version: 2015.0.5961 / Virus Database: 4355/9986 - Release Date: >>>> 06/10/15 >>>> ------------------------------ >>>> >>>> No virus found in this message. >>>> Checked by AVG - www.avg.com >>>> Version: 2015.0.5961 / Virus Database: 4355/9986 - Release Date: >>>> 06/10/15 >>>> >>>> -- >>>> 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. >>>> >>>> No virus found in this message. >>>> Checked by AVG - www.avg.com >>>> Version: 2015.0.5961 / Virus Database: 4355/9991 - Release Date: >>>> 06/10/15 >>>> >>>> ------------------------------ >>>> >>>> No virus found in this message. >>>> Checked by AVG - www.avg.com >>>> Version: 2015.0.5961 / Virus Database: 4355/9986 - Release Date: >>>> 06/10/15 >>>> >>>> -- >>>> 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.
