-
cloop 0.68 and Red Hat 7.3 problem compilation
Hi all,
I want to try the cloop module under RedHat 7.3, but when i try to compile the module i have the following error:
# make KERNEL_DIR=/usr/src/linux-2.4.18-3/
cc -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -s -I. -fno-strict-aliasing -fno-common -fomit-frame-pointer -mpreferred-stack-boundary=2 -march=i386 -D__KERNEL__ -DMODULE -I/usr/src/linux-2.4.18-3//include -DMODVERSIONS -include /usr/src/linux-2.4.18-3//include/linux/modversions.h compressed_loop.c -c -o compressed_loop.o
compressed_loop.c: In function `clo_read_from_file':
compressed_loop.c:279: too few arguments to function `do_generic_file_read_R4e76ab37'
make: *** [compressed_loop.o] Error 1
Is there anybody out there with the same problem?
Thanks in advance.
-
i have read the file compressed_loop.c and the Makefile,
i have rebuilt the module with this option -DREDHAT_KERNEL
but when i load the module i have this error:
kernel: cloop: Welcome to cloop v0.68
kernel: cloop: out of kernel mem for offsets
What's the problem?
Thanks in advance and excuse me for my english.
-
Senior Member
registered user
it could really mean out of memory. cloop stored a 4 byte offset for each 'uncompressed block' of the original device. So in the case of knoppix which I believe is compressed from some 2G(?) image divided in 64K block, it would be 30000x4(8?) memory allocated for the offsets.
Another possibility is that you tell it to mount something that is not a clooped image and it will go wild as there isn't any signature in the image.
-
hi,
if i do :
mkisofs -r /tmp|create_compressed_fs - 1024 > iso.compressed
insmod cloop file=iso.compressed
i have this error
kernel: cloop: Welcome to cloop v0.68
kernel: cloop: out of kernel mem for offsets
Instead if i do
mkisofs -r /tmp|create_compressed_fs - 65536 > iso.compressed
insmod cloop file=iso.compressed
kernel: cloop: Welcome to cloop v0.68
kernel: cloop: iso.compressed: 903 blocks, 65536 bytes/block, largest block is 65562 bytes.
kernel: cloop: loaded (max 1 devices)
Why?
1024 is a multiple of 512.
-
Senior Member
registered user
As I said, each block needs 4(or 8 ?) bytes to store the offset(and they got loaded all in-memory when you insmod cloop.o) and if you use a block size of 1024(1K), a 600M file will have 600x1K offsets. Lots of memory used. Stick to 64K block.
-
ok
Thanks........
Regards.
Lucky.
Similar Threads
-
By lrathle in forum Customising & Remastering
Replies: 2
Last Post: 09-05-2004, 05:47 PM
-
By BlakeB395 in forum Customising & Remastering
Replies: 0
Last Post: 05-27-2004, 10:57 AM
-
By bcalder in forum General Support
Replies: 5
Last Post: 03-15-2004, 09:42 PM
-
By sabel in forum Customising & Remastering
Replies: 2
Last Post: 12-01-2003, 09:15 PM
-
By arkaine23 in forum Customising & Remastering
Replies: 2
Last Post: 07-08-2003, 05:57 PM
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules

Samsung PC4-2666V 16GB 2Rx8 RAM DDR4 2666MHz M471A2K43CB1-CTD
$59.99

Samsung Galaxy S10 10.9" FE 128GB WiFi Tablet SM-X520NZACXAR S-Pen Keyboard 2025
$299.00

Samsung Chomrebook XE350XBA-K02US LCD Screen FHD Display 15.6" XE350XBA-K03US
$51.77

Samsung - Galaxy Tab A11+ - 11" 128GB - Wi-Fi - Gray - Brand new
$235.59

Samsung JC95-01514A Cover-Side Roller T2 Compatible
$39.00

Samsung JC93-01078A Transfer Roller T2
$89.00

Samsung DVI to DVI Cable 6 ft Digital Video Interface Audio Video NEW
$30.89

Kids Case for Samsung Galaxy Tab A9+/A9 plus 11 Inch 2023 Case, with Strap, Shoc
$27.99

Samsung Galaxy Tab Active 3/ 64 gig/WIFI
$85.00

Samsung 24" S3 Essential IPS 100Hz Monitor | Sealed | Fast shipping
$55.00