I'm using busybox 0.60.2 statically compiled with uClibc in a script being run by busybox ash.
gunzip -c is returning a value of 153 in attempting to decompress a valid archive. gunzip -t on the same archive immediately previous in the script returns a value of 0. These archives are compressed with -9 and decompress fully and correctly in a different context. According to GNU gunzip docs, gunzip is only supposed to return 0, 1, or 2. No error messages are produced by gunzip when it generates this error code of 153, and no messages are produced by ash either. This same error code (153) is being returned by mkfs.minix in another script in the same startup process. No error messages are produced, and the messages that ARE produced are normal and expected messages. Here is the context: CONTEXT 1 Using a 1.68M floppy with Linux 2.2.20 and syslinux 1.64 boots fine, and all archives decompress fine. Everything works as expected. CONTEXT 2 Using a 1.44M floppy with Linux 2.4.16 and syslinux 1.60 has problems. It boots into Linux fine, attempts to load modules (which are not ready, so it fails - not a big deal), and then mkfs.minix fails, and then the second disk (a 1.68M floppy) is inserted and read. This disk is the same one that is used to boot under CONTEXT 1. QUESTIONS 1. What does the error code of 153 from gunzip mean? It's not a GNU compatable code... 2. What does the error code of 153 from mkfs.minix mean? 3. Do I need to recompile busybox under Linux 2.4.16 to make this work? I think it was compiled under 2.2.15... 4. Why do other busybox binaries seem to work fine? My Linux distribution uses busybox extensively, and nothing else is returning 153 that I can tell... I use chmod, chown, ash, test, rm, mv, cp, ... 75 apps or more... -- David Douthitt UNIX Systems Administrator HP-UX, Unixware, Linux [EMAIL PROTECTED] _______________________________________________ Leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
