<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: What is the risk of using old kernel after updating to 2.4.20 kernel RPM? in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/what-is-the-risk-of-using-old-kernel-after-updating-to-2-4-20/m-p/3028281#M5778</link>
    <description>hi&lt;BR /&gt;&lt;BR /&gt;if u are able to boot the kernel with an older version guess there are no isses. u can just leave it like that make the older version your default kernel version.&lt;BR /&gt;&lt;BR /&gt;did u also upgrade any other depots along with this kernel. i think it will not be that way.&lt;BR /&gt;&lt;BR /&gt;and until some one manually adds the kernel-* rpms, by default redhat doesnt update the kernel rpms automatically. so it is u are someone else with root access on this box has done this. first remove that.&lt;BR /&gt;&lt;BR /&gt;cheers&lt;BR /&gt;-balaji</description>
    <pubDate>Mon, 21 Jul 2003 14:27:51 GMT</pubDate>
    <dc:creator>Balaji N</dc:creator>
    <dc:date>2003-07-21T14:27:51Z</dc:date>
    <item>
      <title>What is the risk of using old kernel after updating to 2.4.20 kernel RPM?</title>
      <link>https://community.hpe.com/t5/operating-system-linux/what-is-the-risk-of-using-old-kernel-after-updating-to-2-4-20/m-p/3028276#M5773</link>
      <description>I just used up2date and Red Hat Network to update the kernel RPM from 2.4.7 to 2.4.20 but the new kernel panics because it won't work with the AIC-7770 SCSI driver. I can boot the old 2.4.7 kernel successfully. What is the risk of just booting and running on the old 2.4.7 kernel? Do I need to remove the 2.4.20 kernel RPM?&lt;BR /&gt;&lt;BR /&gt;Thanks for your reply,&lt;BR /&gt;&lt;BR /&gt;Paul Mancillas</description>
      <pubDate>Mon, 21 Jul 2003 03:14:43 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/what-is-the-risk-of-using-old-kernel-after-updating-to-2-4-20/m-p/3028276#M5773</guid>
      <dc:creator>Paul Mancillas</dc:creator>
      <dc:date>2003-07-21T03:14:43Z</dc:date>
    </item>
    <item>
      <title>Re: What is the risk of using old kernel after updating to 2.4.20 kernel RPM?</title>
      <link>https://community.hpe.com/t5/operating-system-linux/what-is-the-risk-of-using-old-kernel-after-updating-to-2-4-20/m-p/3028277#M5774</link>
      <description>The risk is low but significant.&lt;BR /&gt;&lt;BR /&gt;Due to the way I layed out my production web server, it won't boot after kernel upgrades.  I'm using raid 1 mirroring and have two ide drives hung off the same controller.&lt;BR /&gt;&lt;BR /&gt;I'm planning on changing that.&lt;BR /&gt;&lt;BR /&gt;The nice thing is that if the machine won't boot you can always boot off the old kernel&lt;BR /&gt;&lt;BR /&gt;When the machine comes up after boot, you see a startup menu and just arrow down to the prior kernel and boot.&lt;BR /&gt;&lt;BR /&gt;There is a file called /boot/grub/grub.conf&lt;BR /&gt;&lt;BR /&gt;This lets you switch back to the old kernel as the automatic boot device.&lt;BR /&gt;&lt;BR /&gt;The loaded kernels are listed in order and start with zero.&lt;BR /&gt;&lt;BR /&gt;So the upgrade has a low risk and a built in backup plan.&lt;BR /&gt;&lt;BR /&gt;SEP</description>
      <pubDate>Mon, 21 Jul 2003 03:36:58 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/what-is-the-risk-of-using-old-kernel-after-updating-to-2-4-20/m-p/3028277#M5774</guid>
      <dc:creator>Steven E. Protter</dc:creator>
      <dc:date>2003-07-21T03:36:58Z</dc:date>
    </item>
    <item>
      <title>Re: What is the risk of using old kernel after updating to 2.4.20 kernel RPM?</title>
      <link>https://community.hpe.com/t5/operating-system-linux/what-is-the-risk-of-using-old-kernel-after-updating-to-2-4-20/m-p/3028278#M5775</link>
      <description>&lt;BR /&gt;If your hardware is supported by an old kernel and not by a kernel update i guess you should write a bug report in the Redhat bugzilla.&lt;BR /&gt;Hopefully someone will fix it and you will be able to upgrade to a 2.4.20+ when it appears.&lt;BR /&gt;&lt;BR /&gt;In terms of risk all the kernel changes are metioned in the errata of the kernel package. (if i remember correctly versions prior to 2.4.8 risk  a spinlock causing ext3 corruption on SMP systems, the rest of the upgrades are (local user) security realted).&lt;BR /&gt;&lt;BR /&gt;Cheers&lt;BR /&gt;Cristi</description>
      <pubDate>Mon, 21 Jul 2003 05:22:09 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/what-is-the-risk-of-using-old-kernel-after-updating-to-2-4-20/m-p/3028278#M5775</guid>
      <dc:creator>Cristian Draghici_1</dc:creator>
      <dc:date>2003-07-21T05:22:09Z</dc:date>
    </item>
    <item>
      <title>Re: What is the risk of using old kernel after updating to 2.4.20 kernel RPM?</title>
      <link>https://community.hpe.com/t5/operating-system-linux/what-is-the-risk-of-using-old-kernel-after-updating-to-2-4-20/m-p/3028279#M5776</link>
      <description>Well,&lt;BR /&gt;&lt;BR /&gt;There is a security issue in your kernel version, that make anyone able to use a buffer overflow on your kernel and such gain root privileges.&lt;BR /&gt;&lt;BR /&gt;This can be done locally or remotely.&lt;BR /&gt;&lt;BR /&gt;But, up to now, there is no known proof of concept, that is to say that a script kiddy wishing to experiment this on machines over the Internet can't find an easy program that would do this for him or her.&lt;BR /&gt;&lt;BR /&gt;That is to say that if your machine is a personnal machine, connected from time to time, you have almost 0 risk.&lt;BR /&gt;&lt;BR /&gt;If your machine is a web server connected continuously, then you should recompile the new kernel to suit with your SCSI driver.&lt;BR /&gt;&lt;BR /&gt;If you choose to keep old kernel, then, as SEP said, remove in /boot all that concerns 2.4.20, remove reference in /boot/grub/grub.conf, and remove directory related to 2.4.20 in /usr/src.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;hth.&lt;BR /&gt;&lt;BR /&gt;J</description>
      <pubDate>Mon, 21 Jul 2003 05:48:48 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/what-is-the-risk-of-using-old-kernel-after-updating-to-2-4-20/m-p/3028279#M5776</guid>
      <dc:creator>Jerome Henry</dc:creator>
      <dc:date>2003-07-21T05:48:48Z</dc:date>
    </item>
    <item>
      <title>Re: What is the risk of using old kernel after updating to 2.4.20 kernel RPM?</title>
      <link>https://community.hpe.com/t5/operating-system-linux/what-is-the-risk-of-using-old-kernel-after-updating-to-2-4-20/m-p/3028280#M5777</link>
      <description>Hello!&lt;BR /&gt;&lt;BR /&gt;The risk is exists that the rpm of kernel 2.4.20 replace some files that old kernel&lt;BR /&gt;need.&lt;BR /&gt;Because the use of rpm the kernel 2.4.20&lt;BR /&gt;depend on some other rpms like glibc 2.3&lt;BR /&gt;and new rpm so it could also have problems with the old kernel.&lt;BR /&gt;&lt;BR /&gt;Caesar</description>
      <pubDate>Mon, 21 Jul 2003 06:20:02 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/what-is-the-risk-of-using-old-kernel-after-updating-to-2-4-20/m-p/3028280#M5777</guid>
      <dc:creator>Caesar_3</dc:creator>
      <dc:date>2003-07-21T06:20:02Z</dc:date>
    </item>
    <item>
      <title>Re: What is the risk of using old kernel after updating to 2.4.20 kernel RPM?</title>
      <link>https://community.hpe.com/t5/operating-system-linux/what-is-the-risk-of-using-old-kernel-after-updating-to-2-4-20/m-p/3028281#M5778</link>
      <description>hi&lt;BR /&gt;&lt;BR /&gt;if u are able to boot the kernel with an older version guess there are no isses. u can just leave it like that make the older version your default kernel version.&lt;BR /&gt;&lt;BR /&gt;did u also upgrade any other depots along with this kernel. i think it will not be that way.&lt;BR /&gt;&lt;BR /&gt;and until some one manually adds the kernel-* rpms, by default redhat doesnt update the kernel rpms automatically. so it is u are someone else with root access on this box has done this. first remove that.&lt;BR /&gt;&lt;BR /&gt;cheers&lt;BR /&gt;-balaji</description>
      <pubDate>Mon, 21 Jul 2003 14:27:51 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/what-is-the-risk-of-using-old-kernel-after-updating-to-2-4-20/m-p/3028281#M5778</guid>
      <dc:creator>Balaji N</dc:creator>
      <dc:date>2003-07-21T14:27:51Z</dc:date>
    </item>
  </channel>
</rss>

