Reading /cdrom/KNOPPIX/KNOPPIX ...again

[BillS]

Ok; back to the question of delooping the /cdrom/KNOPPIX/KNOPPIX file
Below are my results. On a newly installed 3.3(Nov-19) system reading from
the installation CD. I had no luck What am I missing?
I have added blank lines and comments.

root@bernie:/#mount /cdrom
root@bernie:#/cd /cdrom/KNOPPIX

   <<standard setup to read such as boot.img>>
   << associate /dev/loop0 with the file...>>
root@bernie:/cdrom/KNOPPIX# losetup /dev/loop0 /cdrom/KNOPPIX/KNOPPIX
   << then mount it ..>>
root@bernie:/cdrom/KNOPPIX# mount -t auto /dev/loop0 /mnt/test
mount: block device /dev/loop0 is write-protected, mounting read-only
mount: you must specify the filesystem type

   << what file type to specify ? >>
root@bernie:/cdrom/KNOPPIX# mount -t ext2 /dev/loop0 /mnt/test
mount: block device /dev/loop0 is write-protected, mounting read-only
mount: wrong fs type, bad option, bad superblock on /dev/loop0,
       or too many mounted file systems
    
   << check the loop is still lonked to the file>>
root@bernie:/cdrom/KNOPPIX# losetup -a
/dev/loop0: [0b00]:67584 (/cdrom/KNOPPIX/KNOPPIX) offset 0, no encryption

   << did it happen dispite the messages? >>
root@bernie:/cdrom/KNOPPIX# mount
/dev/hda5 on / type ext3 (rw,errors=remount-ro)
none on /proc type proc (rw)
devpts on /dev/pts type devpts (rw,gid=5,mode=620)
/dev/hda7 on /mnt/hda7 type ext3 (rw)
capifs on /dev/capi type capifs (rw,mode=0666)
/dev/cdrom on /cdrom type iso9660 (ro,noexec,nosuid,nodev)

   << just try anything possible >> 
root@bernie:/cdrom/KNOPPIX# mount  /dev/loop0 /mnt/test
mount: block device /dev/loop0 is write-protected, mounting read-only
mount: you must specify the filesystem type
root@bernie:/cdrom/KNOPPIX# mount  -t ext /dev/loop0 /mnt/test -o ro
mount: fs type ext not supported by kernel
root@bernie:/cdrom/KNOPPIX# mount  -t ext2 /dev/loop0 /mnt/test -o ro
mount: wrong fs type, bad option, bad superblock on /dev/loop0,
       or too many mounted file systems
root@bernie:/cdrom/KNOPPIX# mount  -t ext3 /dev/loop0 /mnt/test -o ro
mount: wrong fs type, bad option, bad superblock on /dev/loop0,
       or too many mounted file systems
root@bernie:/cdrom/KNOPPIX# mount  -t msdos /dev/loop0 /mnt/test -o ro
mount: wrong fs type, bad option, bad superblock on /dev/loop0,
       or too many mounted file systems

   <<check the loop again >>
root@bernie:/cdrom/KNOPPIX# losetup -a
/dev/loop0: [0b00]:67584 (/cdrom/KNOPPIX/KNOPPIX) offset 0, no encryption

   << what sort of file does 'file' say it is? >>
root@bernie:/cdrom/KNOPPIX# file /cdrom/KNOPPIX/KNOPPIX
/cdrom/KNOPPIX/KNOPPIX: Bourne shell script text executable
   << try that >>
root@bernie:/cdrom/KNOPPIX# sh /cdrom/KNOPPIX/KNOPPIX
insmod: cloop.o: No such file or directory
   << was cloop.o removed as part of hdd install?>>
root@bernie:/cdrom/KNOPPIX# find / -name cloop.o -print
/lib/modules/2.4.22-xfs/kernel/drivers/block/cloop.o
   << nope, it is there, why not found ?>>
root@bernie:/cdrom/KNOPPIX#modprobe -l |grep loop
/lib/modules/2.4.22-xfs/kernel/drivers/block/cloop.o
/lib/modules/2.4.22-xfs/kernel/drivers/block/loop.o
/lib/modules/2.4.22-xfs/kernel/drivers/block/loop.o.distrib
/lib/modules/2.4.22-xfs/kernel/drivers/isdn/isdnloop/isdnloop.o

   <<maybe a version problem, check>>
root@bernie:/cdrom/KNOPPIX# head -4 /cdrom//KNOPPIX/KNOPPIX
#!/bin/sh
#V2.0 Format
insmod cloop.o file=$0 && mount -r -t iso9660 /dev/cloop $1
exit $?

   << try the command line embeded in the file >>
root@bernie:/cdrom/KNOPPIX# mount -r -t iso9660 /dev/cloop /cdrom/KNOPPIX/KNOPPIX
mount: /dev/cloop is not a valid block device
root@bernie:/cdrom/KNOPPIX# mount -r -t iso9660 /dev/cloop1 /cdrom/KNOPPIX/KNOPPIX
mount: /dev/cloop1 is not a valid block device
root@bernie:/cdrom/KNOPPIX# ll /dev/cloop1
brw-------    1 root     root     240,   1 Jul 25  2003 /dev/cloop1
root@bernie:/cdrom/KNOPPIX# mount -r -t iso9660 /dev/cloop0 /cdrom/KNOPPIX/KNOPPIX
mount: special device /dev/cloop0 does not exist
    << that was wierd, not a block or does not exist?>>

    << try the type iso9660  >>
root@bernie:/cdrom/KNOPPIX# mount  -t iso9660  /dev/loop0 /mnt/test -o ro
mount: wrong fs type, bad option, bad superblock on /dev/loop0,
       or too many mounted file systems
root@bernie:/cdrom/KNOPPIX#

[baldyeti]

Not sure what you're trying to do, but simply mounting the image was IIRC:

insmod cloop file=/cdrom/KNOPPIX/KNOPPIX
mount -r -o loop /dev/cloop /mountpoint

I may forget something (I am not running knoppix now), but this is explained in a presentation availbale on the knopper site. That document is in German but the slides still help. Also I think cloop v2 allows mounting of several compressed images, but I don't know what the syntax would be in that case.

[windos_no_thanks]

You've asked the same stuff here: http://www.knoppix.net/forum/viewtopic.php?t=7056
Why not go back and re-read it ?

[BillS]

Baldyeti's 2 lines worked. This is the first time that the 'insmod' command didn't return an error. That is why I was using losetup.

I am still puzzled about why it worked, but that is for later study. The listing shows that cloop.o was not found at one point, but already loaded at another.

<<shrug>>

Thanks muches.... now on with the scripts.

BillS

[windos_no_thanks]

Baldyeti's 2 lines worked. This is the first time that the 'insmod' command didn't return an error. That is why I was using losetup.

Losetup does not work with compressed images. Generally I'm starting to think you are trolling since you already claimed you managed to get it (the compressed filesystem) mounted in the previous thread. However, this is interesting :

root@bernie:/cdrom/KNOPPIX# file /cdrom/KNOPPIX/KNOPPIX
/cdrom/KNOPPIX/KNOPPIX: Bourne shell script text executable
<< try that >>
root@bernie:/cdrom/KNOPPIX# sh /cdrom/KNOPPIX/KNOPPIX
insmod: cloop.o: No such file or directory
<< was cloop.o removed as part of hdd install?>>
root@bernie:/cdrom/KNOPPIX# find / -name cloop.o -print
/lib/modules/2.4.22-xfs/kernel/drivers/block/cloop.o
<< nope, it is there, why not found ?>>
root@bernie:/cdrom/KNOPPIX#modprobe -l |grep loop
/lib/modules/2.4.22-xfs/kernel/drivers/block/cloop.o
/lib/modules/2.4.22-xfs/kernel/drivers/block/loop.o
/lib/modules/2.4.22-xfs/kernel/drivers/block/loop.o.distrib
/lib/modules/2.4.22-xfs/kernel/drivers/isdn/isdnloop/isdnloop.o

<<maybe a version problem, check>>
root@bernie:/cdrom/KNOPPIX# head -4 /cdrom//KNOPPIX/KNOPPIX
#!/bin/sh
#V2.0 Format
insmod cloop.o file=$0 && mount -r -t iso9660 /dev/cloop $1
exit $?

Running /cdrom/KNOPPIX/KNOPPIX as a "script" shouldn't work as such because you need to provide the mount point as a parameter but if it (the KNOPPIX file) would have been done correctly it shouldn't have complained when trying to insert the cloop module.
A peek at the man page for insmod tells us what is wrong:

If the module file name is given without directories or extension, insmod will search for the module in some common default directories.

So, the correct third line in the KNOPPIX file would be:

insmod cloop file=$0 && mount -r -t iso9660 /dev/cloop $1

The reason it still works when booting from CD is that the script that mounts the compressed filesystem doesn't use that line but explicitly provides it's own insmod command.
Has anyone told Klaus about this ?
Not a big deal of course since if one follows the instructions it will still work but it would also be very easy to fix.

[BillS]

This is not a troll at all. But do keep in mind that I just started with Linux this past Christmas, and there is a lot yet to be learned.

The other thread you mention involved cloop initialization failures when trying to access the compressed file during CD boot. I wanted to check the files integrety. The solution was the 'head -4' command that showed there were 2 different versions of cloop (1.4 & 2.0) involved. I obtained and built the 2.0 package, installed it (and other apps) per directions and the resulting remastered compressed (with v2.0 compressor) file system had no problems during the CD boot. The key was the v2.0 'create_compressed_fs' being used. I didn't look about for other latent misconfigurations.

The solution was a successful compression during remastering, but I never was able to open the original (11-19-03) KNOPPIX file. I always had to boot from the CD to extract the contets of that KNOPPIX file. As explained below, the cloop V2 installation resulted in both versions of cloop.o being present in the system, not just one.

OK; I said this was a problem for later. Yesterday I was sucessful in delooping the (11-19-03)KNOPPIX file on a systemI I had just built with 3.3-20031119. Today on the 3.3-20030924 based system (augmented with cloop-2.0) it (delooping) failed as it always had.

I had built and installed cloop 2.0 onto this system. the first line of this listing is the system supplied cloop v1.4, the last line is my newly built and installed per instructions.

root@lp1:/# modprobe -l |grep loop
/lib/modules/2.4.22-xfs/kernel/drivers/block/cloop.o
/lib/modules/2.4.22-xfs/kernel/drivers/block/loop.o
/lib/modules/2.4.22-xfs/kernel/drivers/block/loop.o.distrib
/lib/modules/2.4.22-xfs/kernel/drivers/isdn/isdnloop/isdnloop.o
/lib/modules/misc/cloop.o

This arrangement failed due to search order. I 'mv'ed the system supplied module to 'cloop14.o' giving:

root@lp1:/# modprobe -l |grep loop
/lib/modules/2.4.22-xfs/kernel/drivers/block/cloop14.o
/lib/modules/2.4.22-xfs/kernel/drivers/block/loop.o
/lib/modules/2.4.22-xfs/kernel/drivers/block/loop.o.distrib
/lib/modules/2.4.22-xfs/kernel/drivers/isdn/isdnloop/isdnloop.o
/lib/modules/misc/cloop.o

Now it works (with 2003119 v2) , because the v2 cloop is loaded.

An subsequent attempt (after approp. 'umount'ing) give a message about clooping already existing, but does work with a v1.4 looped file.

root@lp1:/# mount /cdrom
root@lp1:/# insmod cloop file=/cdrom/KNOPPIX/KNOPPIX
Using /lib/modules/misc/cloop.o
insmod: a module named cloop already exists
root@lp1:/# mount -r -o loop /dev/cloop /mnt/test
root@lp1:/# ls /mnt/test
bin cdrom etc home lib none proc sbin usr vmlinuz
boot dev floppy initrd mnt opt root tmp var

The cloop-2.0 documentation doesn't mention replacement or search order. In fact, the 'depmod -a' seems to be an error since '-a' is not a documented option. And this command only looks is a predefined path which does not seem to include the new directory that the instructions directed us to create.

Mystery solved

BillS

[Hasse]

This one worked for me:

insmod cloop file=/cdrom/KNOPPIX/KNOPPIX
mount -o ro /dev/cloop /mnt/test

Many ways to achive the same task