Problem w/ Unleashed too many files in image.gz [solved]

Using applications, configuring, problems
Post Reply
Message
Author
User avatar
papaschtroumpf
Posts: 250
Joined: Fri 17 Jun 2005, 04:23

Problem w/ Unleashed too many files in image.gz [solved]

#1 Post by papaschtroumpf »

Image

trying to build my own puppy with firefox and icewm and I get the error message above.
Is it telling me I have too many packages or that the disk I'm working from is too small? I have 650M left on that disk so I'm guessing that's not the problem?
it tells me to press enter if no errors, but wat if I have errors? start over?
Last edited by papaschtroumpf on Fri 24 Jun 2005, 03:42, edited 1 time in total.
Mandriva LE 2005 user and puppy newbie

Mathiasdm
Posts: 100
Joined: Thu 05 May 2005, 07:52

#2 Post by Mathiasdm »

I had that problem too.
I think it's because you have to clean out the subdirectories in your puppy-unleashed directory first (if you've done a remaster before).

I could be wrong, of course ;-)

User avatar
BarryK
Puppy Master
Posts: 9392
Joined: Mon 09 May 2005, 09:23
Location: Perth, Western Australia
Contact:

#3 Post by BarryK »

That's the trickiest part of using Unleashed.
It means you have too many files in image.gz.

image.gz when uncompressed is a 11264K bytes ext2 filesystem.
This loads into a ramdisk at initial bootup, /dev/ram0.
The kernel is compiled for 11264K ramdisks.

You have two choices.

1.
image.gz is all the directories and files OTHER than /usr, so you can
either delete some files, or compress some files using upx.

2.
Do what the script says and make the kernel ramdisk bigger,
ramdisk_size=12288 for example, for a 12M ramdisk.
To do this, you have to edit "createpuppy" script -- look down to
where it writes to isolinux.cfg and place "ramdisk_size=12288"
somewhere, for example before the "PFILE=" entry.

Option 2 would be the easiest probably.

Mathiasdm
Posts: 100
Joined: Thu 05 May 2005, 07:52

#4 Post by Mathiasdm »

Are there any special consequences with Option 2?

User avatar
papaschtroumpf
Posts: 250
Joined: Fri 17 Jun 2005, 04:23

#5 Post by papaschtroumpf »

If I wanted to use upx, I assume that all I need to do is run upx and the executable files in the /packages sub-directories?

EDIT: saw in the readme that you compress it after the fact in the post-install script. I guess I might do the same.

I'm thinking about adding a dummy package that would be there solely for the purpose of running a post install script. How is the order of the packages determined?
EDIT: looks like it's in the order they are listed in the package file (alphabetical). Another way to do this is to change the createpuppy script to cat my own stuff at the end of the collated pinstall.sh (something like customize.sh).

Is there a way to know you're over the limit without going through the entire "processing keywords" step that occurs before it fails?
Mandriva LE 2005 user and puppy newbie

User avatar
papaschtroumpf
Posts: 250
Joined: Fri 17 Jun 2005, 04:23

#6 Post by papaschtroumpf »

BarryK wrote: image.gz is all the directories and files OTHER than /usr, so you can
either delete some files, or compress some files using upx.
I'm missing something about this.

I removed bluefish, scribus, most games, the 3 vector graphics program, fvvm95, jwm and maybe a few other things and simply added my icewm package.
That package is 1020K but only 20 bytes of it are in /etc, the rest of it is in /usr so it would mean that the packages I removed didn't use more than 20 bytes altogether outside of /usr?
Mandriva LE 2005 user and puppy newbie

User avatar
BarryK
Puppy Master
Posts: 9392
Joined: Mon 09 May 2005, 09:23
Location: Perth, Western Australia
Contact:

#7 Post by BarryK »

It is very easy to see the size of the files that will go into image.gz
-- it is the folder "rootfs-complete"
after you have run the createpuppy script, there it is.

You can try "du -k" to see how much space rootfs-complete occupies, but it is not an accurate measure of how much space it will actually occupy. :?
:wink:

You can see upx in action in some of the pinstall.sh scripts -- awk/gawk for example, i think also the e2fsprogs package.

User avatar
papaschtroumpf
Posts: 250
Joined: Fri 17 Jun 2005, 04:23

#8 Post by papaschtroumpf »

I'm I supposed to be able to build an ISO from freshly downloaded puppy-unleashed.1.0.3.tgz and pupget_packages-1 and pressing ENTER for every question in the buildscript?

i.e. is the "default" build list too big to fit? I have been assuming that it's not but for some reason I still get the error above.

I will re-download the packages in case I corrupted something.

I can't confirm my scripts in the pther post work for sure because I'm unabel to build an iso, even without using my scripts.
Mandriva LE 2005 user and puppy newbie

User avatar
papaschtroumpf
Posts: 250
Joined: Fri 17 Jun 2005, 04:23

#9 Post by papaschtroumpf »

no dice, these are the steps I followed:

reboot computer and biit from 1.0.3 liveCD
selection option 2 no HD
wget -r ftp://ibiblio.org/pub/linux/distributio ... packages-1
wget ftp://ibiblio.org/pub/linux/distributio ... 0.3.tar.gz

(also got md5sum, not shwon here)

sync
tar -zxf puppy-unleashed-core-1.0.3.tar.gz
sync
cd puppy-unleashed/packages
cp /mnt/linux2/puppy/ibiblio.org/pub/linux/distributions/puppylinux/pupget_packages-1/* .
./expandtarballs.sh
sync
cd ..
./createpuppy

/dev/hda3 which is on /mnt/linux2 has 2715556 Kbytes available (19% used) so I pressed ENTER
when the ppackage selection came up I clicked OK without changing anything
ignored the warning about possible needed packages and pressed enter
building rootfs-complete...
press enter to choose default kernel (2.4.27)
pressed enter to bypass dependencies check
press enter to satr processing the pinstall.sh
press enter to accept 103 as the version
takes its sweet time to build index.html.....
waited for me to press enter after the fvwm95 menu building and sat there all night (we need a no prompt build option)
ENTER
ENTER to start building image.gz and usr_cramfs
ENTER to NOT do 1 big file

---> KABOOOM!

Image


du rootfs-complete returns 13256
Mandriva LE 2005 user and puppy newbie

User avatar
BarryK
Puppy Master
Posts: 9392
Joined: Mon 09 May 2005, 09:23
Location: Perth, Western Australia
Contact:

#10 Post by BarryK »

The default build works.
Others have done it.

Are you sure that rootfs-complete directory is in a partition with lots of free space?

Try booting Puppy live-CD normally, so that there is a pup001 file.
-- what reason would you have for not doing that?

User avatar
papaschtroumpf
Posts: 250
Joined: Fri 17 Jun 2005, 04:23

#11 Post by papaschtroumpf »

df now returns 2637384 available on /dev/hda3 (mounted on /mnt/linux2) or 21% used

That's a difference of 78172 Kbytes from what was reported at the start of the ./createpuppy script

I'm at a loss here..
Mandriva LE 2005 user and puppy newbie

User avatar
papaschtroumpf
Posts: 250
Joined: Fri 17 Jun 2005, 04:23

#12 Post by papaschtroumpf »

BarryK wrote: image.gz when uncompressed is a 11264K bytes ext2 filesystem.
This loads into a ramdisk at initial bootup, /dev/ram0.
The kernel is compiled for 11264K ramdisks.
df reports that /dev/loop2 (the rootfs-tmp2) is 10903 1K blocks. Are you saying it should report 11264?

what's the easiest way to compare the contents of my rootfs-complete with someone that has completed the build successfully to see what is different?

would the fact that I booted in option 2 have anything to do with it (grasping at straws here).

Also I lied, /dev/hda3 is an ext3 partition, not ext2 does it matter?
Mandriva LE 2005 user and puppy newbie

User avatar
papaschtroumpf
Posts: 250
Joined: Fri 17 Jun 2005, 04:23

#13 Post by papaschtroumpf »

Tried it again with option 1 at boot, but still won't work.

somebody help!
Mandriva LE 2005 user and puppy newbie

schlammi

#14 Post by schlammi »

I had exactly the same problem than papschtroumpf. I donwloaded teh original puppy-unleashed tarball and my first build was to large.

I stopped the ./createpuppyscript after the errors and used upx to shrink down some files in /bin and /sbin. Then I started the script again and it made a nice .iso File.


But unfortunately my puppy doesn`t boot up right. It stops with kernel panic, when it tries to start the init process. Any ideas?

User avatar
papaschtroumpf
Posts: 250
Joined: Fri 17 Jun 2005, 04:23

#15 Post by papaschtroumpf »

it will make a nice iso file if you allow the script to continue when there are errors, of course the iso doesn't work...

The script should probably abort on its own, I'll add this to my todo list since I have already made some changes to some of the build scripts. Of course those changes are on hold until I can get puppy unleashed to compile out of the box first.
Mandriva LE 2005 user and puppy newbie

User avatar
BarryK
Puppy Master
Posts: 9392
Joined: Mon 09 May 2005, 09:23
Location: Perth, Western Australia
Contact:

#16 Post by BarryK »

ext2, ext3, reiserfs, that's irrelevant. If the partition has at least 550M free space after expanding Unleashed core and downloading all the packages, then it's fine.
packages.txt is the same one used to create puppy 1.0.3.

As you commented, some files are created in /tmp.
Maybe if you have created one puppy-unleashed folder, worked in it, then created another puppy-unleashed folder, all in the same session, perhaps there is some undesirable interaction.
When you reboot, /tmp is wiped.

When you get to that point in the script that reports not enough space, you could continue, you'll just end up with a incorrect iso. Or, ctrl-c to quit.
If you type ctrl-c to exit the script, then "df" command to find out if your /mnt/linux2 is full.

Though, exiting the script at that point will leave /dev/loop2 in existence,
you will have to "umount rootfs-tmp2".

User avatar
papaschtroumpf
Posts: 250
Joined: Fri 17 Jun 2005, 04:23

#17 Post by papaschtroumpf »

yes, I can't see how the host filesystem could be relevant but I'm grasping at straws here.
In the previous post with the large picture, I made sure to do a reboot to clear /temp and whatever else might have been "tainted"

as I reported in the previous post, df returns 2637384 available on /dev/hda3 (mounted on /mnt/linux2) or 21% used after I hit ctrl-c after the errors.

yes /dev/loop2 is still mounted and df reports that it's 100% full at 10903 1K blocks (should it be 11264?)

now I usually reboot and delete the entire puppy-unleashed directory before starting over, so that would take card of unmounting /dev/loop2 (because of the reboot) and freeing the space allocated for it (deleting unleashed) right?

I'm also running under virtual PC but I can;t see how this could be relevant either. I've ran linux and puppy under virtual PC without ever running into a problem like this.
Mandriva LE 2005 user and puppy newbie

GuestToo
Puppy Master
Posts: 4083
Joined: Wed 04 May 2005, 18:11

#18 Post by GuestToo »

i just tried Unleashed 1.0.3

clean install, downloaded using my dotpup

i used all the default options

it couldn't make image.gz because rootfs-tmp2/ was too small

i looked for files that shouldn't be in rootfs-tmp1 - rootfs-tmp2 ... i noticed that bash (all 633k) was in /bin

i think bash should be in /usr/bin and there should be a symlink in /bin to /usr/bin/bash

if you look in packages/bash-3.0/, bash is in bin/
i think it should be in usr/bin/, and a symlink should be in bin/

what i did was, i created a new dir in packages/bash-3.0/ called usr/
i moved bin/ to usr/
i made a dir bin/ and put a symlink to /usr/bin/bash in it (make sure the symlink is to /usr/bin/bash, not to the bash file in packages/bash-3.0/usr/bin/ )

so the bash package contains these 2 files:
packages/bash-3.0/usr/bin/bash
packages/bash-3.0/bin/bash

and packages/bash-3.0/bin/bash is a symlink to /usr/bin/bash
(right click the packages/bash-3.0/bin/ dir, click Open Xterm Here, and type
ln -s /usr/bin/bash bash )

i ran createpuppy again, and it seemed to work ok ... it put a symlink to /usr/bin/bash in rootfs-tmp2/bin/ , it didn't show any out-of-space errors, and it seemed to build the iso ok

User avatar
papaschtroumpf
Posts: 250
Joined: Fri 17 Jun 2005, 04:23

#19 Post by papaschtroumpf »

thanks for looking into it GuestToo! I was going nuts, especially since it takes over an hour to build on my machine (I didn't want to use the faster scripts I posted just in case they somehow messed things up)

I'll make the changes.

The unleashed pcakge should probably get updated.
Mandriva LE 2005 user and puppy newbie

User avatar
papaschtroumpf
Posts: 250
Joined: Fri 17 Jun 2005, 04:23

#20 Post by papaschtroumpf »

Thanks! it worked!
Mandriva LE 2005 user and puppy newbie

Post Reply