Do you have loop compile in the kernel? If you compile it as a module, do a modprobe loop. Try that command again.
On Wed, 2003-06-04 at 18:35, Brian Reichholf wrote: > i have a bin file, and wanted to extract one file from it, > so i emerged bin2iso and converted it to an iso file (at least so i > hoped) > > strangely enough the result was: <filename>-01.iso and <filename>-02.iso > (the bin is an image of an SVCD) > > i wasn't that surprised though and just though `what the hell' and > wanted to mount the <filename>-02.iso as a loopback device... > > so here goes: > > $ mount -o loop -t iso9660 /path/to/file.iso /mnt/iso > mount: wrong fs type, bad option, bad superblock on /dev/loop0 > or too many mounted filesystems > > i doubt it is the latter (too many filesystems) as i only have 10 > mounted filesystems (including tmpfs that is) and i have no problem to > mount another network drive. i do have loopback support compiled into > the kernel (not as module) and seeing as the svcd-bin is inteded to be > burned to a cdr, i should be right to assume that the filetype is > iso9660.. what am i doing wrong??? > > help is appreciated > > cheers, > -bri > > > -- > [EMAIL PROTECTED] mailing list >
signature.asc
Description: This is a digitally signed message part
