View Single Post
Old 03-11-2012, 07:08 PM   #3
geekmaster
bit basher & pixel pusher
geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.
 
geekmaster's Avatar
 
Posts: 5,698
Karma: 7581655
Join Date: Nov 2011
Location: A young man living in an old man's body.
Device: Too many.
Quote:
Originally Posted by ixtab View Post
...
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.
geekmaster is online now   Reply With Quote