You need patches linux-2.4.7-s390-3.tar.gz and linux-2.4.7-s390-4.tar.gz
from
http://www10.software.ibm.com/developerworks/opensource/linux390/current2_4.shtml#64-kernel
Saying goes: Great minds think alike - I say: Great minds think for
themselves!
Carlos A. Ordonez
IBM Corporation
Server Consolidation
|---------+--------------------------->
| | "Wolfe, Gordon |
| | W" |
| | <gordon.w.wolfe@|
| | boeing.com> |
| | Sent by: Linux |
| | on 390 Port |
| | <[EMAIL PROTECTED]|
| | RIST.EDU> |
| | |
| | |
| | 03/05/2002 06:31|
| | PM |
| | Please respond |
| | to Linux on 390 |
| | Port |
| | |
|---------+--------------------------->
>-------------------------------------------------------------------------------------------------------------------------------|
|
|
| To: [EMAIL PROTECTED]
|
| cc:
|
| From:
|
| Subject: Re: SLES 7 BETA 2.4.7 Kernel Bug
|
|
|
>-------------------------------------------------------------------------------------------------------------------------------|
This is the problem with beta software. The reason it's called "beta" is
that it's still in test. You have to take what you get. My company has an
absolute prohibition against using any form of beta code in production for
this very reason.
We have a subscription, license, and maintenance agreement with SuSE on
SLES7 2.4.7. The same bug existed on the commercially-distributed
production code too. We just found it a few days ago. If you have a
maintenance agreement with SuSE, you can get into the password-protected
maintenance site and download the rather substantial (about 12 megs) fix.
There was a message that came across the list on February 26th (sorry, I
don't have the message) that I think said the problem was with one of the
IBM modules. Another way around this problem might be to download the
latest patches for 2.4.7 from IBM Developerworks and apply them to the
kernel source and rebuild the kernel. This may or may not work because
SuSE
puts additional patches on the kernel that may cause IBM's patches not to
apply. If you're really good at kernel source code and reading diff files
you might be able to fix this if it occurs.
"Never trust any computer you can lift."
Gordon Wolfe, Ph.D. (425)865-5940
VM Technical Services, The Boeing Company
> ----------
> From: Monteleone
> Reply To: Linux on 390 Port
> Sent: Monday, March 4, 2002 11:59 PM
> To: [EMAIL PROTECTED]
> Subject: SLES 7 BETA 2.4.7 Kernel Bug
>
> Hello everybody,
> I'm currently testing this version and I get the 'Kernel bug fcntl.c
> 417'.
> I understood that there is a kernel replacement for users in maintenance
> mode.
> What happen for the other?
> Is there a way to bypass this problem or should i have to subscribe?
> Thanks for your responses.
> Best Regards,
>
>
> G�rard MONTELEONE
> Ing�nieur Syst�me & R�seau
> * 04.95.23.68.09 / 06.87.72.70.32
> [EMAIL PROTECTED]
> S.I.T.E.C zi du Vazzio
> 20090 AJACCIO Cedex
>
>
>
