Redhat Kernel updates catuion

[Jeffrey Silverman]

I am thinking about installing the RedHat kernel updates up from

2.4.20-8

to

2.4.20-20.9

Whate caveats and cautions should I know about? What might I break? Am I
worrying too much?

I am going to use up2date to do this. Or should I download the kernel and
install it as a second kernel instead of upgrading the current kernel? (I
know that this is the recommended procedure when *compiling* a new kernel).

Thanks
--
Jeffrey D. Silverman | jeffrey AT jhu DOT edu
Johns Hopkins University | Baltimore, MD
Website | http://www.wse.jhu.edu/newtnotes/

[Vwakes]

On Wed, 24 Sep 2003 Jeffrey Silverman wrote:

>I am going to use up2date to do this. Or should I download the kernel
>and install it as a second kernel instead of upgrading the current
>kernel?

IIUC, up2date downloads the specified kernel rpm and does a "rpm -i" and
not "rpm -U" which would be a problem. So you can use 'up2date'.

V.

[Paul Lutus]

Jeffrey Silverman wrote:

> I am thinking about installing the RedHat kernel updates up from
>
> 2.4.20-8
>
> to
>
> 2.4.20-20.9
>
> Whate caveats and cautions should I know about?

You mean, besides "don't throw away your old kernel"?

I just made this change, and I discovered I had to get the PCMCIA source and
compile it along with the kernel source for my laptops. Apart from this, no
big difficulties.

> What might I break? Am I
> worrying too much?
>
> I am going to use up2date to do this. Or should I download the kernel and
> install it as a second kernel instead of upgrading the current kernel?

IMHO you should get the source and compile it as a second kernel.

--
Paul Lutus
http://www.arachnoid.com

[Lenard]

On Wed, 24 Sep 2003 15:11:33 -0400, Jeffrey Silverman typed:

> I am thinking about installing the RedHat kernel updates up from
>
> 2.4.20-8
>
> to
>
> 2.4.20-20.9
>
> Whate caveats and cautions should I know about? What might I break? Am
> I worrying too much?

Upgrading a release kernel (correctly) is not a problem, you will not
break anything (99.99% sure) and yes your worrying to much.


> I am going to use up2date to do this. Or should I download the kernel
> and install it as a second kernel instead of upgrading the current
> kernel? (I know that this is the recommended procedure when *compiling*
> a new kernel).

It's best to install the new kernel and keep the current kernel.

rpm -ivh <file_name>

FYI: Unless you want the RPM file you do not need to download it to
install it. As root from the console or xterm session type something like;

rpm -ivh ftp://updates.redhat.com/9/en/os/i686/kernel-2.4.20-20.9.i686.rpm

Modify to match your actual system processor hint: uname -p


--
SCO + RICO Act = Justice

[rowan]

Jeffrey Silverman wrote:
> I am thinking about installing the RedHat kernel updates up from
>
> 2.4.20-8
>
> to
>
> 2.4.20-20.9
>
> Whate caveats and cautions should I know about? What might I break? Am I
> worrying too much?
>
> I am going to use up2date to do this. Or should I download the kernel and
> install it as a second kernel instead of upgrading the current kernel? (I
> know that this is the recommended procedure when *compiling* a new kernel).
>
> Thanks

Jeffrey, without knowing specifically what you're running on your machine you're asking a question that can't
be answered. Up2date will bring down and install the latest, most times making that the default for the next
boot. If you find that something is broken after you boot the new kernel your boot loader, GRUB or LILO,
typically has a menu selection for you to step back to the prior version at which point you can edit
/etc/grub.conf or etc/lilo.conf to change the default to boot the prior kernel. NOTE if you're using LILO you
have to issue the lilo command after editing the lilo.conf.

[Jeffrey Silverman]

On Wed, 24 Sep 2003 15:11:33 -0400, Jeffrey Silverman wrote:

> I am thinking about installing the RedHat kernel updates up from
>
> 2.4.20-8
>
> to
>
> 2.4.20-20.9
>
> Whate caveats and cautions should I know about? What might I break? Am I
> worrying too much?
>
> I am going to use up2date to do this. Or should I download the kernel and
> install it as a second kernel instead of upgrading the current kernel? (I
> know that this is the recommended procedure when *compiling* a new
> kernel).
>
> Thanks

Thank you for all the replies. One caveat not mentioned that I discovered
on upgrade was that my NVIDIA drivers do not work under the new kernel.
But there really is no way any of y'alls could know that I have an NVidia
chip in dat dere mah-sheen.

So, to fix, I booted into old kernel, used web browser, browsed to
nvidia.com, downloaded nvidia-xxx-xxx.run (their driver package) rebooted
into *new* kernel, init 3'ed, ran nvidia's package, which was very nice
and automatically compiled new drivers for me (I'm assuming that the
kernel source need be installed for this, which it was).

init 5

all stations go!

<thinkingOutLoud>
I wonder if the average n00b could figure that stuff out. It has taken me
a while to get to the point where all those steps I just spelled out are
automatic-like.
</thinkingOutLoud>
--
Jeffrey D. Silverman | jeffrey AT jhu DOT edu
Johns Hopkins University | Baltimore, MD
Website | http://www.wse.jhu.edu/newtnotes/

[Vwakes]

On Wed, 24 Sep 2003 Jeffrey Silverman wrote:
>
><thinkingOutLoud> I wonder if the average n00b could figure that stuff
>out. It has taken me a while to get to the point where all those steps
>I just spelled out are automatic-like. </thinkingOutLoud>

Big deal? Only caveat here is a n00b knows how to read/understand
English and has the ability to google search the posts like this.

Or just imagine how you would have done that without the above. So it's
only the time.

V.

[Jeffrey Silverman]

On Wed, 24 Sep 2003 14:51:47 -0700, Vwakes wrote:

> On Wed, 24 Sep 2003 Jeffrey Silverman wrote:
>>
>><thinkingOutLoud> I wonder if the average n00b could figure that stuff
>>out. It has taken me a while to get to the point where all those steps
>>I just spelled out are automatic-like. </thinkingOutLoud>
>
> Big deal? Only caveat here is a n00b knows how to read/understand
> English and has the ability to google search the posts like this.
>
> Or just imagine how you would have done that without the above. So it's
> only the time.
>
> V.

Yeah, well, just <thinkingOutLoud>
--
Jeffrey D. Silverman | jeffrey AT jhu DOT edu
Johns Hopkins University | Baltimore, MD
Website | http://www.wse.jhu.edu/newtnotes/

[JimL]

Why is my hardware platform different from my machine and processor?

[root@tyanbox root]# uname -p
i586
[root@tyanbox root]# uname -i
i386
[root@tyanbox root]# uname -m
i586

Did I screw up?

JimL






On Wed, 24 Sep 2003 19:27:15 GMT, Lenard <lenard@127.0.0.1> wrote:

>On Wed, 24 Sep 2003 15:11:33 -0400, Jeffrey Silverman typed:
>
>> I am thinking about installing the RedHat kernel updates up from
>>
>> 2.4.20-8
>>
>> to
>>
>> 2.4.20-20.9
>>
>> Whate caveats and cautions should I know about? What might I break? Am
>> I worrying too much?
>
>Upgrading a release kernel (correctly) is not a problem, you will not
>break anything (99.99% sure) and yes your worrying to much.
>
>
>> I am going to use up2date to do this. Or should I download the kernel
>> and install it as a second kernel instead of upgrading the current
>> kernel? (I know that this is the recommended procedure when *compiling*
>> a new kernel).
>
>It's best to install the new kernel and keep the current kernel.
>
>rpm -ivh <file_name>
>
>FYI: Unless you want the RPM file you do not need to download it to
>install it. As root from the console or xterm session type something like;
>
>rpm -ivh ftp://updates.redhat.com/9/en/os/i686/kernel-2.4.20-20.9.i686.rpm
>
>Modify to match your actual system processor hint: uname -p

[JimL]

On Wed, 24 Sep 2003 23:49:49 -0400, "Jeffrey Silverman"
<jeffrey@jhu.edu> wrote:

>On Wed, 24 Sep 2003 14:51:47 -0700, Vwakes wrote:
>
>> On Wed, 24 Sep 2003 Jeffrey Silverman wrote:
>>>
>>><thinkingOutLoud> I wonder if the average n00b could figure that stuff
>>>out. It has taken me a while to get to the point where all those steps
>>>I just spelled out are automatic-like. </thinkingOutLoud>
>>
>> Big deal? Only caveat here is a n00b knows how to read/understand
>> English and has the ability to google search the posts like this.
>>
>> Or just imagine how you would have done that without the above. So it's
>> only the time.
>>
>> V.
>
>Yeah, well, just <thinkingOutLoud>

I've taught at the college level and I can assure you that 90 percent
of the population does NOT have the ability to figure that stuff out.
Not even close.

That's exactly why God made windows.

JimL

[Lenard]

On Thu, 25 Sep 2003 06:24:26 -0500, JimL typed:

>
> Why is my hardware platform different from my machine and processor?

It's not, your platform type is i386 (x86) as opposed to any of the other
linux platforms like alpha, s390, mips or x86_64 for example.

>
> [root@tyanbox root]# uname -p
> i586
> [root@tyanbox root]# uname -i
> i386
> [root@tyanbox root]# uname -m
> i586
>
> Did I screw up?

No


--
SCO + RICO Act = Justice

[Vwakes]

On Thu, 25 Sep 2003 JimL wrote:

> I've taught at the college level and I can assure you that 90 percent
>of the population does NOT have the ability to figure that stuff out.
>Not even close.

100% of anything won't be able to figure any stuff out with that
attitude.

And we were talking abt an average n00b, whatever that supposed to mean,
perhaps a 30 to 60 day struggle with Linux?. And not about those ppl who
needs things like "Video Professor" to tickle their 'brain' in using an
OS. And definetely not kids < 10 and all the senior citizens and with
some exceptions in the both the cases.

> That's exactly why God made windows.

What's wrong with you ppl? Always bringing up God for the all the wrong
reasons ;-) Lucky He/She didn't hear this!

V.

[J.O. Aho]

Jeffrey Silverman wrote:
> I am thinking about installing the RedHat kernel updates up from
>
> 2.4.20-8
>
> to
>
> 2.4.20-20.9
>
> Whate caveats and cautions should I know about? What might I break? Am I
> worrying too much?
>
> I am going to use up2date to do this. Or should I download the kernel and
> install it as a second kernel instead of upgrading the current kernel? (I
> know that this is the recommended procedure when *compiling* a new kernel).

1. Download the sourceRPM manually
2. Rebuild the sourceRPM as an i386 version first before you rebuild it for
your CPU (if you have something else than i386/i486).

Problems can be that you will need the RH9 glibc too, at least without it you
won't get the maximum bennefit of the kernel.


//Aho

[J.O. Aho]

Jeffrey Silverman wrote:

> <thinkingOutLoud>
> I wonder if the average n00b could figure that stuff out. It has taken me
> a while to get to the point where all those steps I just spelled out are
> automatic-like.
> </thinkingOutLoud>

If they have had a nvidia driver installed, then they would have solved it
too, sooner or later.


//Aho

[Jeffrey Silverman]

On Thu, 25 Sep 2003 07:21:19 -0700, Vwakes wrote:

<snip!>
> OS. And definetely not kids < 10 and all the senior citizens and with some
> exceptions in the both the cases.
<snip!>

Actually, I can think of a number of kids < 10 who would be very good at
figuring out how to use their computer. I was one of those, once, long
ago. (not as long as some!) Not too sure about the seniors (that's
pensioners to you English chaps!), though.

--
Jeffrey D. Silverman | jeffrey AT jhu DOT edu
Johns Hopkins University | Baltimore, MD
Website | http://www.wse.jhu.edu/newtnotes/

[jeem]

JimL wrote:
> Why is my hardware platform different from my machine and processor?
>
> [root@tyanbox root]# uname -p
> i586
> [root@tyanbox root]# uname -i
> i386
> [root@tyanbox root]# uname -m
> i586
>
> Did I screw up?
>
> JimL
>
>
>
>
>
>
> On Wed, 24 Sep 2003 19:27:15 GMT, Lenard <lenard@127.0.0.1> wrote:
>
>
>>On Wed, 24 Sep 2003 15:11:33 -0400, Jeffrey Silverman typed:
>>
>>
>>>I am thinking about installing the RedHat kernel updates up from
>>>
>>> 2.4.20-8
>>>
>>>to
>>>
>>> 2.4.20-20.9
>>>
>>>Whate caveats and cautions should I know about? What might I break? Am
>>>I worrying too much?
>>
>>Upgrading a release kernel (correctly) is not a problem, you will not
>>break anything (99.99% sure) and yes your worrying to much.
>>
>>
>>
>>>I am going to use up2date to do this. Or should I download the kernel
>>>and install it as a second kernel instead of upgrading the current
>>>kernel? (I know that this is the recommended procedure when *compiling*
>>>a new kernel).
>>
>>It's best to install the new kernel and keep the current kernel.
>>
>>rpm -ivh <file_name>
>>
>>FYI: Unless you want the RPM file you do not need to download it to
>>install it. As root from the console or xterm session type something like;
>>
>>rpm -ivh ftp://updates.redhat.com/9/en/os/i686/kernel-2.4.20-20.9.i686.rpm
>>
>>Modify to match your actual system processor hint: uname -p
>
>
I get i686, i386, i686. It seems like the same type thing. I wouldn't worry.
Jeem

[Vwakes]

On Thu, 25 Sep 2003 jeem wrote:
>JimL wrote:
>
>> Why is my hardware platform different from my machine and processor?
>>
>> [root@tyanbox root]# uname -p
>> i586
>> [root@tyanbox root]# uname -i
>> i386
>> [root@tyanbox root]# uname -m
>> i586
>>
>> Did I screw up?
>>
>I get i686, i386, i686. It seems like the same type thing. I wouldn't
>worry. Jeem

Pls place your response directly below the previous posters text you are
replying to. What's the point in blindly following something without
understanding it's rationale? Read up:

http://mailformat.dan.info/quoting/bottom-posting.html

V.