Quote:
Originally Posted by geekmaster
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*.
|
The "p1-p4" suffixes could simply be an artifact of whichever program output the message when it modified the "disk" /dev/mmcblk0p4.
BTW, the nomenclature is unusual for Linux, it looks more like what you see on BSD systems.
That said, think of it as fdisk running on some device (/dev/sample0, assuming that's a valid one) . While you're modifying the partition table, you would "write" to partitions /dev/sample0p1 etc. and possibly log messages accordingly, even if these devices only come to life once the partition table was written and the kernel reloaded it.
Hope this was understandable
