I am just curious..
So I wanted to see how the partitions are being used (with fdisk) on the RuneAudio image:
-----------------------------------------------------------------------------------------------
Disk /dev/mmcblk0: 29.8 GiB, 32010928128 bytes, 62521344 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x00005f47
Device Boot Start End Sectors Size Id Type
/dev/mmcblk0p1 2048 206847 204800 100M c W95 FAT32 (LBA)
/dev/mmcblk0p2 206848 4401151 4194304 2G 83 Linux
-----------------------------------------------------------------------------------------------
I see that most of my space from the SD is unallocated..
So what I was pondering about at first, as I start playing with RPi is the SD card life concept, and one of my potential paths was to do DIY and convert everything over to RAM disk, and read-only root (while in normal operation), and could use remount rw to save stuff back, etc.. And of course Frank mentioned about potential for using the arch-linux version at some point, as it has means to minimize SD card writes.
Well that was last week's thought (however, may still take one of those paths in the long run as I play around).
This week I had been pondering about how the lifespan would be to use a very large SD card, as it would take advantage of the flash 'wear leveling' concept, so I ran the above to check the layout: fdisk /dev/mmcblk0 ...to get an idea about if I can take advantage of wear leveling and notice that most of the space is unallocated.
So I was wondering, does the wear leveling use any given cell on the flash to make writes, regardless of the partition layout? I know on traditional SSD drives this is the case (all partitions are virtualized), but just wondering if this is also the case with SD card flash since they may not have as complex of a logic controller chip.
Any thoughts on this?