devdoc:devdoc_create_image

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
Last revision Both sides next revision
devdoc:devdoc_create_image [2010/08/23 11:43]
droemel
devdoc:devdoc_create_image [2022/05/21 10:50]
mkeuter
Line 1: Line 1:
-====== Create an image ======+====== Create a Flash 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 ''./scripts/build'', do:
  
-After running ''toolchain/build'', do:+  ./scripts/astlinux-makeimage -z 256 256 0
  
-  ./makerunnix.sh -A -z 3998 192 1856+This creates an astlinux-xxx.img.gz file with a single FAT16 partition of 256MB.
  
-in this case, 3998 is what my 4GB card has in usable space in MB.  192MB is the size of my VFAT partition.+Burn this image to a CF or USB flash drive:
  
-192MB is the size of the VFAT partition Images are slightly less than 60MB, so 192 is enough room for 3 images.+  zcat astlinux-xxx.img.gz | dd of=/dev/sdc bs=64k
  
-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. +(if ''/dev/sdc'' is where my system detects the CF... Be very careful to get ''of='' correct...)
- +
-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: If you hadn't used the -z flag, then it would just be:
  
-  dd if=astlinux-trunk-4337.img of=/dev/sdc bs=64k+  dd if=astlinux-xxx.img of=/dev/sdc bs=64k
  
 to burn this image onto a CF. to burn this image onto a CF.
Line 33: Line 22:
 Wait until the 'busy' light on your CF reader stops blinking.  Just to be sure, do: Wait until the 'busy' light on your CF reader stops blinking.  Just to be sure, do:
  
-sync +  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 follow **[[userdoc:new-install|New Installation]]** to complete the process.
  
-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.+\\ 
  
 +\\ 
  
 +!!Note:!! The above ''./scripts/astlinux-makeimage'' part does NOT work in a virtual machine, which runs as an LXC container (e.g. in Proxmox). You'll need a "real" VM for this.
  • devdoc/devdoc_create_image.txt
  • Last modified: 2022/05/21 10:53
  • by mkeuter