devdoc:devdoc_create_image

This is an old revision of the document!


Create an image

Use “dmesg” to figure out the size of the CF when you insert it into your build system.

You'll need the size of the CF in megabytes. A 4GB CF isn't 4096MB long, due to overhead from housekeeping, emulation, and geometry. So you'll need the exact number (or round down if you're not sure).

After running toolchain/build, do:

./makerunnix.sh -A -z 3998 192 1856

in this case, 3998 is what my 4GB card has in usable space in MB. 192MB is the size of my VFAT partition.

192MB is the size of the VFAT partition. Images are slightly less than 60MB, so 192 is enough room for 3 images.

1856MB is the size of ASTURW partition, which includes (for me) log files, voice mail, etc. In this case, I'm using roughly half the card and leaving the rest unused.

The -A argument tells it to partition, format, and label the ASTURW filesystem. I'll still need to run genunion once I've booted up this image.

The -z argument means to compress the image (since the ASTURW partition will be large but empty) to save space on my hard drive (since at any given time, I might have a dozen images).

When this completes, I can do:

zcat astlinux-trunk-4337.img.gz | dd of=/dev/sdc bs=64k

(if /dev/sdc is where my system detects the CF… again, use the info from dmesg to figure out where this is. Be very careful… we're not hunting wabbits.)

If you hadn't used the -z flag, then it would just be:

dd if=astlinux-trunk-4337.img of=/dev/sdc bs=64k

to burn this image onto a CF.

Wait until the 'busy' light on your CF reader stops blinking. Just to be sure, do:

sync

and then to verify the image, do:

sudo fdisk -l -u /dev/sdc

to confirm it was written correctly.

At this point, you may remove your CF and install it into your target system, power up… boot, and run “genunion” to complete the process.

This article is written by Philip.

  • devdoc/devdoc_create_image.1282582031.txt.gz
  • Last modified: 2010/08/23 11:47
  • by droemel