Link to home
Start Free TrialLog in
Avatar of lconnell
lconnell

asked on

Linux Live Kit gzip error

Hi all,

I have created a custom build of slackware 14.1 x86_64 using the latest Linux Live Kit.

When I run the ./build script, right after creating the initramfs, I get an error -> gzip: stdin: unexpected end of file.

This results in a corrupt .img file at the end of the build script. I can't find in the build scripts where this is happening.  Can someone shed some light here?

thanks!
Avatar of Mazdajai
Mazdajai
Flag of United States of America image

What is the build script looks like? Have you try to untar the file by hand? It complains about your standard input file from gzip compression.
Avatar of jlevie
jlevie

There may not be an explicit use of gzip anywhere in the build scripts. The error can come from something else that uses gzip to upack a package. The most likely cause of the error is a damaged source package.
Avatar of lconnell

ASKER

Here is the complete set of scripts: https://github.com/Tomas-M/linux-live

It's failing when trying to unzip the ko.gz modules in the temp directory.

find $INITRAMFS -name "*.ko.gz" | xargs gunzip
+ xargs gunzip
+ find /tmp/kiosk-initramfs-9314 -name '*.ko.gz'

gzip: stdin: unexpected end of file
Manually execute gunzip on each of the .ko.gz files are replace any corrupt ones. Then run the build scripts.
You should verify the files as jlevie suggested, or tighten down the file names  under the find command. This may able to reduce the errors.
Oddly I don't see any of those files.  This is frustrating. I tried even on a slack 14.0 distro and I get the same thing. I am not getting any support from linuxquestions or slax.org.
It complains  $INITRAMFS is not a valid gz file. Have you try to remake the img with the following?

find . -print | cpio -o -H newc 2>/dev/null | gzip -f --best >$INITRAMFS.img

Open in new window


If you post your entire build script, we might be able to help. But slax.org would be a better place as this seems to be a distro specific question.
You are going to have to track back through the build script to find where the .ko.gz packages come from.
ASKER CERTIFIED SOLUTION
Avatar of lconnell
lconnell

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
In the future you can add -print option on the find command. It prints the path of the current working file on the screen for better debugging.
I had to rebuild the isolinux binary.