SCIENTIFIC-LINUX-USERS Archives

December 2009

SCIENTIFIC-LINUX-USERS@LISTSERV.FNAL.GOV

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Alan Bartlett <[log in to unmask]>
Reply To:
Alan Bartlett <[log in to unmask]>
Date:
Wed, 16 Dec 2009 17:03:19 +0000
Content-Type:
text/plain
Parts/Attachments:
text/plain (27 lines)
2009/12/16 Jim Green <[log in to unmask]>:

> I'm trying to set up an SL5 client for a kerberos/LDAP/NFS4 server.  I'm getting
> a kernel panic on the client in certain situations (writing to a file
> which I do not
> own but do have group write permissions) and from the oops I think that this
> is a kernel bug fixed in 2.6.20.  Sadly, yum shows me only 2.6.18 kernels and
> the problem persists on the most recent (2.6.18-164.6.1.el15)
>
> So to my question : How can one install a kernel >= 2.6.20 on SL5 ?
> I couldn't find SL rpms/srpms and googling for the experience of others
> wanting to do this turns up little useful info.

Jim,

Please read TUV's policy on backporting [1].

You should also realise it is not the mainline kernel-2.6.18 but is
kernel-2.6.18-164.6.1.el5 with somewhere in the order of 2000 patches
applied to the original mainline kernel. The "EXTRAVERSION" of
"-164.6.1.el5" makes all the difference.

Regards,
Alan.

[1] http://www.redhat.com/security/updates/backporting/

ATOM RSS1 RSS2