Thanks for your reply.
"John Summerfield" <[EMAIL PROTECTED]> writes:
> Are they there?
> [summer@dugite summer]$ ls /dev/loop?
> brw-rw---- 1 root 7, 0 May 6 1998 /dev/loop0
> brw-rw---- 1 root 7, 1 May 6 1998 /dev/loop1
> brw-rw---- 1 root 7, 2 May 6 1998 /dev/loop2
> brw-rw---- 1 root 7, 3 May 6 1998 /dev/loop3
> brw-rw---- 1 root 7, 4 May 6 1998 /dev/loop4
> brw-rw---- 1 root 7, 5 May 6 1998 /dev/loop5
> brw-rw---- 1 root 7, 6 May 6 1998 /dev/loop6
> brw-rw---- 1 root 7, 7 May 6 1998 /dev/loop7
> [summer@dugite summer]$
Yep. (I actually included a listing of my 16 loop device files at the
end of my original posting.)
> Dores dmesg sho wsomething like this (I'm on 2.4.0)
> [summer@possum Documentation]$ dmesg | grep -i loop
> loop: enabling 8 loop devices
> loop: enabling 8 loop devices
I have the same. (Though the messages are appearing after boot time btw.)
> Here's what happened here when I mounted an ISO image:
> [root@possum /root]# mount -o loop ~summer/MODISK.ISO /mnt/floppy/
> [root@possum /root]# lsmod
> Module Size Used by
> loop 7392 2 (autoclean)
> [root@possum /root]# dmesg | tail
:
> loop: enabling 8 loop devices
> ISO 9660 Extensions: Microsoft Joliet Level 1
> ISO 9660 Extensions: RRIP_1991A
I could do
% sudo mount ~/src/.tar/boot.img /mnt/floppy -o loop
% lsmod loop | grep loop
loop 8640 2 (autoclean)
without any problems.
So loop devices seem to be working ok, but not "losetup".
What does
# losetup /dev/loop0
give you?
Jens
_______________________________________________
Redhat-devel-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-devel-list
