Thomas, Exact thing I'm working on right now. Are you trying to get ACL support as well??
Right now I'm at the point where I can get the utilties upgraded, then ipl into the new kernel (finally). Here's the order I used: Upgraded gettext - 0.11.2 Upgraded binutils - 2.12.90.0.4 w/DW patch Upgraded gcc - 3.1 w/DW patch Upgraded glibc - 2.2.5 w/DW patch Upgraded modutils - 2.4.7 patched and installed kernel I've gotten some really good responses from this list on this topic so make sure you read over the last month thoroughly. I received this advice from Bernhard Kaindl: " to compile the 2.4.17 for S/390, you don't need to upgrade your glibc to 2.2.5. gcc-3.1 alone is enough and even 2.95.3 would do it, 3.1 is only on that pages because that's the combination tested by the Developers. The only thing you need are the new new-tools from one of the two 2.4.17 streams, the s390-tools from the non-may2002 stream is even enough if you don't need the new OSA features." HTH Josh -----Original Message----- From: Geyer, Thomas L. [mailto:[EMAIL PROTECTED]] Sent: Wednesday, July 03, 2002 9:47 AM To: [EMAIL PROTECTED] Subject: 2.4.17 Upgrade Problem I am trying to upgrade my SLES 2.4.7 kernel to 2.4.17. I have followed the procedure in the HOW-TO from linuxvm.org and in the Linux on zSeries and S390: Systems Management Redbook. When I try to boot the new kernel I get the following errors: Parallelizing fsck version 1.19a (13-Jul-2000)" fsck.ext2: No such file or directory while trying to open /dev/dasdb1"" (null): " The superblock could not be read or does not describe a correct ext2" filesystem. If the device is valid and it really contains an ext2" filesystem (and not swap or ufs or something else), then the superblock" is corrupt, and you might try running e2fsck with an alternate superblock:" e2fsck -b 8193 <device>" " fsck.ext2 /dev/dasdb1 failed (status 8)! Run it manually!" "7"[1A""[80C"[10D"[1;31mfailed"[m""8" fsck failed. Please repair manually and reboot. The root" file system is currently mounted read-only. To remount it" read-write do:" " bash# mount -n -o remount,rw /" " Attention: Only CONTROL-D will reboot the system in this" maintanance mode. shutdown or reboot will not work." " I have tried the upgrade numerous times with the same errors at boot time. Where have I gone wrong? I am trying to get to kernel 2.4.17 "May 2002 stream". I may be confused to the order one should do the following upgrades. I was planning to do them in the following order: 1. kernel 2. OCO modules 3. tool-chain 4. utilities 5. debug tools This information I got from the following web page: http://www10.software.ibm.com/developerworks/opensource/linux390/current2_4_ 17-may2002.shtml Does the above order matter? Are my assumptions incorrect? Any help, hints or suggestions would be of help. Thanks. Thomas L. Geyer Email:[EMAIL PROTECTED] Phone:(330) 471-2073 Fax:(330) 471-4034 ********************************************************************** This message and any attachments are intended for the individual or entity named above. If you are not the intended recipient, please do not forward, copy, print, use or disclose this communication to others; also please notify the sender by replying to this message, and then delete it from your system. The Timken Company **********************************************************************
