Quote:
Originally Posted by ixtab
...
It's pretty much exactly the same method as used here, except that you're treating the device as a disk rather than as a partition (i.e., run fdisk /dev/loop0, rather than mkfs.ext3) |
I have done plenty of loop mounts (usually with "mount -o loop"). It just seemed odd to me here that these startup script output messages report that it "successfully wrote" a partition table inside mmcblk0p4, and using /dev/mmcblk0p4p1, which is not in /dev/mmc*.
BTW, these messages are created when "/bin/sh /etc/rcS.d/S50diags start" starts up.