Messages in this thread | | | Date | Fri, 29 Jan 1999 00:50:42 -0500 | From | Mark Swanson <> | Subject | 2.1.127-2.2.1 large file bug. |
| |
Hello,
System: Linux 2.2.1 (seen since 2.1.127). redhat-5.1, glibc upgrade to 2.0.7. gcc upgrade to 2.8.1, ASUS *dual* (SMP enabled) P100, 64MB RAM, aic7xxx. Upgraded all libraries/utils mentioned in the 2.2.1 Changes file - except the on that got cracked.
The system rocks in almost every way. It runs db2, Solid, and tons of C++ and Java apps perfectly. There is only one problem and I can do it 100% of the time:
1. cp linux-2.2.0.tar.gz /tmp 2. tar xvfz linux-2.2.0.tar.gz 3. Wait 1.5 hrs for it to untar.
cp works blazingly fast, gcc doesn't wait for anything. Nothing else I throw at it fails or even delays a smidgeon. Can *anyone* else acknowledge this symptom or am I the only one in the world having this problem? Must I use GCC-2.7.2.3? (I require 2.8.1 for Mico - CORBA).
You could say, "Don't untar large files.". But it worked in 2.1.126! Recompiling tar didn't help, BTW.
ALSO: Rebooting the SMP box fails. It just hangs. The last time it rebooted properly was in 2.1.125. 126 and onwards fails - even with reboot=warm and reboot=bios as a kernel parameter in LILO. any suggestions here would be great too.
Didn't know where else to post this...
-- 1999 - The year of the penguin.
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
| |