Puppy Linux Discussion Forum

[papaschtroumpf]

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?

[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

[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]

Are there any special consequences with Option 2?

[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?

[papaschtroumpf]

[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.


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

[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.

[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/distributions/puppylinux/pupget_packages-1
wget ftp://ibiblio.org/pub/linux/distributions/puppylinux/puppy-unleashed-core-1.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!




du rootfs-complete returns 13256

[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?

[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..

[papaschtroumpf]

[papaschtroumpf]

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

somebody help!

[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?

[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.