having trouble mounting disk image on loopback device 2313
On Sun, 09 Jul 2006 23:30:17 -0700, iforone
losetup -o 32256dev-loop1 test.file mountdev-loop1mnt-vhda1
losetup -o 49351680dev-loop2 test.file mountdev-loop2mnt-vhda2
On a real hard disk, there are separate devices for parbreastions. In my way of thinking, devices are mounted. I think about it this way:
1. A device and and mount point are linked together by the mount command. 2. At a minimum, these conditions must be met for a mount command to succeed: a. The device must exist b. The mount point must exist c. The device must contain a filesystem recognizable by the kernel.
On Tue, 11 Jul 2006 02:59:08 GMT, Steven Jones staggered into the Black Sun and said: OK, that's weird. What happens if you leave it mounted? If it's plugged in all the time, is there...
There are other considerations (such as user permissions, etc.), but I think the above is the fundamental. It is also possible to write directly to the device without using a filesystem and without mounting it (raw I-O). But you are correct- when a device is mounted, it implies the a filesystem is being used, not raw I-O to the device, so it could be just a matter of how to visualize the work done by the mount command.
On 10 Jul 2006, in the Usenet newsgroup comp.os.linux.embedded in article newsgroup comp.os.linux.misc in article newsgroup comp.os.linux.x in article Please don't post the same article to multiple groups, especially when it's...
I forgot to show the mount command after using losetup. I also made a typo for one of the offset values. I have fixed both errors above.
Other mount options can be specified for the filesystem, etc. can be used. The simple form usually works for me because mount can usually determine the filesystem type before mounting it.
-- Douglas Mayne
On Mon, 10 Jul 2006 21:13:38 -0500, Dances With Crows Thanks for your feedback. The only thing that I do is unmount it. It remains plugged in...
Linux groups from Newsgroups