Talk:Cloop
From Wikipedia, the free encyclopedia
[edit] The disadvantages section
I removed this, because it is demonstrably false:
- The cloop kernel module only allows one compressed image at a time to be active.
Although you are only allowed to specify one compressed image on the insmod cloop.o command line, you can use the losetup utility to activate multiple compressed images.
I'm not sure how true the remaining two entries are.
Also, is there any reason to have a "disadvantages" section but no "advantages" section? It seems kind of out-of-place. 4.255.44.24 17:17, 1 October 2005 (UTC)
[edit] New version of software and new file format?
The description on this page, information on the linked pages, and information that can be found by search the web seems to describe an old version of cloop. For example, cloop 2.04-118 that comes with OpenSuSE 10.3 behaves very different:
- multiple images can be allowed by creating additional device nodes (mknod /dev/cloop$I b 240 $I, I=0,...,7, and losetup, see also discussion section above)
- create_compressed_fs does not hold the compressed data in (virtual) memory if the image is a regular file. Instead, it starts outputting data immediately (tested with a 55 GB image file). This also means that the file format must have changed since the index cannot be written at the start of the output anymore (stdout is not seekable). Jowagner (talk • contribs) 17 January 2008 (UTC)