why are there different images based on sd card size?
#1
I'm new to this, but have been exploring and experimenting with my new pine64 and also a rpi3 (just ordered a ODROID-C2 to play with as well)

I haven't seen this practice elsewhere. for other distros I have tried there is a single img file and, once you have it flashed, you expand the file system to free up the rest of the card.

Just curious what the advantage is here.

thanks
#2
(07-28-2016, 06:42 AM)checktravis Wrote: I'm new to this, but have been exploring and experimenting with my new pine64 and also a rpi3 (just ordered a ODROID-C2 to play with as well)

I haven't seen this practice elsewhere. for other distros I have tried there is a single img file and, once you have it flashed, you expand the file system to free up the rest of the card.

Just curious what the advantage is here.

thanks

Expanding the file system utilised by the Android image is apparently trickier than your standard Linux image. The PhoenixCard version of the image expands readily enough, but not everyone gets on well with the PhoenixCard software, so there are also offered DD images, which can be burned using the dd command, or with software such as Win32DiskImager, ApplePi Baker or Etcher, depending on the computer you are using to burn the image.

See also this thread: Empty space.

Ideally I suppose the DD Android images would come with a built-in script that automatically expands the filesystem to fill the microSD card. Then only a single minimally-sized image would be needed.
#3
Theoretically the /data partition on the dd images can be expanded since it is behind all the other ones. Practically the partition layout has overlapping definitions as I pointed out in http://forum.pine64.org/showthread.php?tid=1834 . I managed to resize the /data partition to the full size, but you have to use low-level tools like sfdisk since all the more user-friendly ones don't operate on partition tables with overlapping partitions. Maybe this can be somehow fixed in the build config of the Android SDK?

The Phoenixcard images are expanded on the fly to the full card size, but they require a tool that basically runs only on Windows and doesn't always work for everyone...
Come have a chat in the Pine IRC channel >>


Possibly Related Threads…
Thread Author Replies Views Last Post
  Irradium (based on crux linux) riscv64, aarch64 mara 0 740 11-03-2023, 03:10 PM
Last Post: mara
  Maximum size of boot MicroSD for RockPro64 and Pinebook Pro commiecam 0 1,733 08-07-2022, 10:47 AM
Last Post: commiecam
  How to boot from SD card on pinebook pro linux123 3 6,182 12-02-2020, 10:29 AM
Last Post: linux123
  micro sd card won't insert Samuel Venable 2 4,531 09-01-2020, 12:15 AM
Last Post: Samuel Venable
  SD Card boot - trying out OS Baconomics 1 4,437 06-19-2020, 06:58 AM
Last Post: tophneal
  How to boot from the SD card and install to eMMC? ravanh 2 6,543 03-18-2020, 09:42 AM
Last Post: tophneal
  recommended micro sd card ? mronhb 91 214,965 03-03-2020, 11:34 PM
Last Post: siyatalerja
  eMMC card on adapter Malmgren 8 11,405 03-20-2018, 11:14 AM
Last Post: Malmgren
  corrupt microsd card after reboot maxpayne 6 10,227 02-08-2017, 05:42 PM
Last Post: maxpayne
  recommended micro sd card? Gustavo Woltmann 1 3,660 01-03-2017, 11:38 PM
Last Post: MarkHaysHarris777

Forum Jump:


Users browsing this thread: 1 Guest(s)