On Sat 09 Aug 2014 at 02:44:31 +1000, Zenaan Harkness wrote: > On 8/9/14, Martin McCormick <mar...@x.it.okstate.edu> wrote: > > Zenaan Harkness writes: > >> I think you meant "-o loop" rather than "-ro loop". > >> > >> > first to see what would happen and it appeared to work but ls > >> > /mnt throws an I/O error as does any operation on /mnt until one > >> > umounts /mnt. > >> > >> If the above don't fix it, copy and paste the output of > >> your mount command (include the command). We might > >> spot something you're not seeing. > > > > Very possible and many thanks. I'll give your suggestion > > a try. > >> > >> Good luck, > > > > Thanks. I think I am close but let's see what we get. > > No probs. > > Please "reply all" (in general) especially if you are seeking > further feedback/ questions (of course).
Giving the information asked for would also have helped. > Also, you can try "man losetup", if you want to do things more > manually, but "mount -o loop" should be your first port of call. > Here are some random notes (re losetup) I have from years ago: > # first create a new loop device > mknod /dev/loop/300 b 7 300 > # then assign your loop file to new loop device > losetup /dev/loop/300 your_loop_file.dat > # and finally mount the loop device instead of the file > mount /dev/loop/300 /your_mount_directory/ > # if you then need to unmount, use > umount /your_mount_directory/ > losetup -d /dev/loop/300 mount -ro loop FreeBSD-9.1-RELEASE-amd64-bootonly.iso /mnt works here. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140808174400.ga19...@copernicus.demon.co.uk
