View Single Post
Old 10-31-2012, 11:29 PM   #16
EternalCyclist
Member
EternalCyclist for a long time would go to bed early.EternalCyclist for a long time would go to bed early.EternalCyclist for a long time would go to bed early.EternalCyclist for a long time would go to bed early.EternalCyclist for a long time would go to bed early.EternalCyclist for a long time would go to bed early.EternalCyclist for a long time would go to bed early.EternalCyclist for a long time would go to bed early.EternalCyclist for a long time would go to bed early.EternalCyclist for a long time would go to bed early.EternalCyclist for a long time would go to bed early.
 
Posts: 17
Karma: 17948
Join Date: Oct 2012
Device: KT
@eureka: Thank you. I will try this method on my K4 later.

When you mount the new ext3 partition you do not use the entries of the partitiontable in mmcblk0p4. This means there is a discrepancy between that partition table and the actual start of the ext3 partition?

This calculated offset could be written into the partition table on mmcblk0p4, so that mounting the ext3 partition on the host can be done without the offset option?

Why do I have to mount it via /dev/loop?
What about simply doing "mount -o offset=1075838976 /dev/mmcblk0p4 /somehwere" ?
EternalCyclist is offline   Reply With Quote