[SOLVED] How to understand size of iso created by MultiPup cd/dvd Creator?
Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
There is less than 24 hours left to vote in the 2015 LinuxQuestions.org Members Choice Awards. Click here to go to the polls. Vote now and make sure your voice is heard!
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
How to understand size of iso created by MultiPup cd/dvd Creator?
I was creating an iso containing some Puppies for burning a cd using MultiPup &, in my total MBs (added by hand) it gave me around 666 MB but right before making the iso image the utility reported about a 63 MB iso size.
I asked this question in the proper thread at the murga forum but haven't received an answer there, yet. So, I thought that many persons using this forum should have used that utility by this moment with success & may know how to interpret this outcome & how to proceed.
When you burn this image to a cd, do you get a working iso? 63M seems kind of smallish for puppy but it might be that it is just the changes after compression. Then add that amount to the puppy distro.
Not sure exactly what you have but most of the live cd's use a way to compress data. The thing you get is some few files and one or more large files that is really a compressed file system. Knoppix was one of the first to use one or more of the tricks to put more on a live cd that I knew of. Others have used similar deals well before that. A normal cd might hold up to 3G of software in a compressed state.
I've moved outside the mounted partition (root) everything iso. Augmented with this my memory a lot, nonetheless, after running MultiPup again & right before making the image I checked the sizes & noticed the following:
1) When checking the iso file size by pressing on 5th button, counting from the top on MultiPup main screen, it shows 615M from standard isos & 51M from Alien (DSL);
2) When pressing the 6th button on the same screen (Click to create your iso image) it reports that the total size is 538M (a substantial decrease in size);
3) I checked the taskbar icon for memory availability before creating the image & it again is showing a slab in red but after clicking on it shows 780M;
I really can't make sense of what I'm experiencing with this MultiPup thing!
Note: The version I'm using for the DSL isn't the one I see in one of the MultiPup screens, I''m using dsl-4.4.10-initrd.iso. Could this make such a huge diference in the outcome?
I was examining my partition sizes with GParted & found that the sda2 & linux-swap partitions are locked, so I can't resize or move them around. In the other hand, it occurred to me after seeing that sda3 has 314MB free space (as reported by right-clicking on the part & selecting Properties) & 392.87MB as reported by GParted, that if I can put & boot DSL from there & it comes with a working GParted app the sda2 & swap partitions might be onlocked & would permit me to resize, merge with an empty little part besides it & other goodies that I need to do with them.
If I have sda2 as my main partition with all the grub folders/files & a folder for each frugally installed puppy & a couple of other folders for certain d/ls, would it finally get locked after a potential OS on sda3 is up or the locked one should be sda3?
Posting in the DSL forum a question for doing this...
Yesterday, I read carefully the instructions that MultiPup gives in relation to the DSL alien that was tested (DSL4.2.5) & d/l it & ckecked the md5sum OK & used it to make the iso file: it worked fine in terms of sizes reported vs. expected.
I burnt the iso file with 'Burniso2cd' from PL528.005 & it ckecked out OK. When I tried to boot with it the VAIO it wasn't possible for me to do it because I don't see anything in the external screen until puppy is awaken; the onboard screen is faulty (useless).
I tried it later on the HP laptop, making sure to depress Esc right after the first splash screen to select the boot device. The problem here was that it showed me that the cd led was lighted or flickering but it reverted immediately to the PXE boot option. I tried it many times & rechecked the BIOS settings a few times too but to no avail.
Finally, I decided to boot the HP with the DSL2.5.* in the Flash Drive & it worked OK. Even though this's an old version I like it very much but the BonEcho version of FF it's running needs urgently a flash plugin (at least ver. 9 or higher) as the messages I saw while visiting many pages. Even the Yahoo homepage needs it, not to mention my favorite web-radio staion.
Does anybody here knows enough of DSL for advising me as to how to update the browser or installing the necessary plugin or both?