View Single Post
Old 03-11-2012, 07:17 PM   #4
ixtab
(offline)
ixtab ought to be getting tired of karma fortunes by now.ixtab ought to be getting tired of karma fortunes by now.ixtab ought to be getting tired of karma fortunes by now.ixtab ought to be getting tired of karma fortunes by now.ixtab ought to be getting tired of karma fortunes by now.ixtab ought to be getting tired of karma fortunes by now.ixtab ought to be getting tired of karma fortunes by now.ixtab ought to be getting tired of karma fortunes by now.ixtab ought to be getting tired of karma fortunes by now.ixtab ought to be getting tired of karma fortunes by now.ixtab ought to be getting tired of karma fortunes by now.
 
ixtab's Avatar
 
Posts: 2,903
Karma: 6677485
Join Date: Dec 2011
Device: K3, K4, K5, KPW, KPW2
Quote:
Originally Posted by geekmaster View Post
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
ixtab is offline   Reply With Quote