Quote:
Originally Posted by EternalCyclist
...
Why do I have to mount it via /dev/loop?
What about simply doing "mount -o offset=1075838976 /dev/mmcblk0p4 /somehwere" ?
|
I was thinking this as well. In my mntusb.params
(from my Select Boot thread) I run /mnt/us/RUNME.sh at startup after I directly mount /mnt/us using an offset and no loop mount. It works fine. As far as I know, no (automatic) loop mount is used (unless I am misunderstanding something here).
Quote:
Originally Posted by eureka
...
You could mount with your command. With losetup loop device is chosen by you, and with your command loop device is chosen by mount tool. It's the sole difference, AFAIK.
|
But his command did not include "mount -o loop", and without the "loop", are you sure it is the same as losetup?
I thought that loop mounting was for mounting an image file as a block device, rather than raw partitions. If I am wrong in my thinking here, please enlighten me. Thanks...
EDIT: WikiPedia seems to agree with me:
http://en.wikipedia.org/wiki/Loop_device
Quote:
|
In Unix-like operating systems, a loop device, vnd (vnode disk), or lofi (loopback file interface) is a pseudo-device that makes a file accessible as a block device.
|
And as I see it, the whole point of your exercise is to mount a raw partition that you created instead of mounting an image file, to avoid problems experienced with out-of-memory errors while using loop mounts. Remind me again, WHY are we loop mounting here?