11-11-2023, 06:26 PM
What's the difference between writing to the eMMC module or SD with "flasher" or "etcher" software , vs. writing to the device with dd of=/dev/rld0 or of=/dev/mmcblk2 ?
I have this idea that the OS knows how to flash and etch these devices, and we might be able to treat them like any random access block device, and in fact it appears that people out there are doing exactly that. Possibly the flasher result would be significantly more compact or something?
Conversely, I'd like to be able to copy raw eMMC to SD - for example, boot from a 128Gb SD and dd and compress the 64Gb eMMC. That could then be reinstalled to recover to that state at the time of the copy.
Thanks for any insight into this.
I have this idea that the OS knows how to flash and etch these devices, and we might be able to treat them like any random access block device, and in fact it appears that people out there are doing exactly that. Possibly the flasher result would be significantly more compact or something?
Conversely, I'd like to be able to copy raw eMMC to SD - for example, boot from a 128Gb SD and dd and compress the 64Gb eMMC. That could then be reinstalled to recover to that state at the time of the copy.
Thanks for any insight into this.
