I would think you should be able to use Kpackage (I haven't actually tried it). You may have to read the how-to, specifically the section on X Session Configuration to get it to work right. Really in this case the command line works well.
There's a way to know the size of the iso file I'll build ?
Can I use a grafical editor to add and remove packages (it would be more fast than using apt-get) ?
I would think you should be able to use Kpackage (I haven't actually tried it). You may have to read the how-to, specifically the section on X Session Configuration to get it to work right. Really in this case the command line works well.
Can you find out the ISO size before you build it?
Simple answer: No
Complex answer: It can be estimated.
The cloop compression method compresses approximately 1830MB into 695MB which is a 62% reduction in size. You must first exit the chroot and if /proc is mounted to the chroot, then unmount /proc. Then run the command to give you a total file space usage for the build areaIn my opinion, if the size is greater than 1840MB then it will be too big for a standard 700MB CD ISO image.Code:du -h --max-depth=1 /path/to/Knoppix/remaster/build/area/
I just made a DVD and Midnight Commander shows it to be 2059MB and KNOPPIX image is 2047MB (if you divide it by 1024, you see that it is very near max. 2 gig limit for one cloop image). 'Making compressed fs' showed this to be 4895MB and 78322 blocks.Originally Posted by UnderScore
As you can easily count, compression ratio is in my case about 42% of uncompressed files. In my CDs compression has been about 38-40 %. So it's not always the same as also Undescore said.
You can try to count what compression would be by checking the size of your remaster:
-tapsa-Code:du -ms remaster/
Hi tr,
I'd like to have some more info about the 2gig limit for cloop images - I was completely unaware of it, is it mentioned anywhere?
Is it because the DVD filesystem cannot store files bigger than 2 gig or is this a problem for cloop itself?
Actually, I'm looking for a method to compress partition image files that are much bigger and might come out as 5-8Gig or bigger when compressed. If cloop has a limit of 2Gig, it's out in any case.
Cheers
Dirk
I think you have misunderstood the whole thing. Klaus Knopper explais it in tread http://lists.debian.org/debian-knopp.../msg00015.html:Originally Posted by DirkS
-tapsa-Code:Short explanation: The ISO filesystem, which is still used for the DVD for compatibility reasons, has a maximum file size limitation of 2 GB. So, in order to use a compressed image of more than 2GB in size, you have to use TWO (or more) cloop images instead (cloop can handle up to 8 simultaneous images by default), and then just join them with unionfs. The /linuxrc inside minirt.gz does this.
Thanks for the info. Since my problem is about compressing existing images, the ability to join them with unionfs will not help me.Originally Posted by tr
Anyway, as it is now, the cloop images are "limited" in size by the amount of RAM that I have available. (I wonder why it was built this way... gzip can compress images that are much larger than the available RAM...)
Cheers
Dirk
Extron RGB-160XI Analog Computer Video 60-378-01
$187.06
Vintage 1960s Donner Model 3000 Analog Computer ~ MUSEUM PIECE Extremely Rare
$4000.00
NEC Multisync II JC-1402HMA VGA EGA CGA Analog TTL Computer Monitor Vintage 1988
$699.99
NEW Aquarius+ Computer Signature Edition - 8Bit Retro System
$239.00
Apple Macintosh SE/30 M5119 Computer 8MB RAM Recapped Working *See Description*
$450.00
Landen Computer. Circa 1898. the Rapid Computer Company. With Original Case.
$425.00
IBM Modem Saver Phone Line Tester
$7.99
Burr Brown Analog Computer parts Circuit boards w Helipot Potentiometers 1631a
$85.00
Wooting Two HE Mechanical Keyboard Analog Linear Lekker Switches
$299.99
Sony Trinitron CPD-1304 9 PIN Analog Vintage CRT Monitor - Great for Retro PC
$475.30