Upgrading kernel 2.2.12 to kernel 2.2.16, keeping same options

Upgrading kernel 2.2.12 to kernel 2.2.16, keeping same options

Post by mike » Sun, 14 Jan 2001 01:53:29



Hi,
    I was told that kernel 2.2.16 is more secure than 2.2.12, which
was part of my Redhat 6.1 distribution.
    I would like to upgrade in a way that all the options that were
built into the origional kernel that came with Redhat 6.1
remains the same. I don't know what those options are?
    How to accomplish the task?

                                                        Thanks
                                                                    Mike

 
 
 

Upgrading kernel 2.2.12 to kernel 2.2.16, keeping same options

Post by Stephen Cornel » Sun, 14 Jan 2001 02:37:50



>     I was told that kernel 2.2.16 is more secure than 2.2.12, which
> was part of my Redhat 6.1 distribution.
>     I would like to upgrade in a way that all the options that were
> built into the origional kernel that came with Redhat 6.1
> remains the same. I don't know what those options are?
>     How to accomplish the task?

Easiest solution: use the kernel RPMs on Red Hat's FTP site
(updates.redhat.com).  You can find links to them from the Web site,
where the upgrade is listed under the `security advisories' pages.
The options may not be identical to the old 6.1 kernel (after all, the
new kernel probably has several new features enabled), but you
shouldn't lose any functionality.  Be sure to follow the instructions
on the web pages on how to upgrade the kernel.  While you're at it, it
would be a good idea to upgrade other packages in your distribution
that have security advisories against them; several packages are
vulnerable to remote root exploits unless upgraded.

If you insist on compiling your own kernel, you can install the
kernel-sources-2.2.12 rpm from your old distro.  This contains a file
/usr/src/linux-2.2.12/.config (notice the dot), which contains the Red
Hat 6.1 default kernel configuration.  Copy this to the new kernel
source tree /usr/src/linux-2.2.16, and configure the kernel using
`make oldconfig' rather than the usual `make config' (or make xconfig or
whatever).  This should then only ask you about how to configure the
new features of the kernel.  The rest of the procedure for compilation
and installation of a kernel is also documented on the Red Hat web
pages.

HTH,
Stephen.
--

University of Cambridge, Zoology Department, Downing Street, CAMBRIDGE CB2 3EJ

 
 
 

Upgrading kernel 2.2.12 to kernel 2.2.16, keeping same options

Post by Karen Rosi » Sun, 14 Jan 2001 22:19:34



> Hi,
>     I was told that kernel 2.2.16 is more secure than 2.2.12, which
> was part of my Redhat 6.1 distribution.
>     I would like to upgrade in a way that all the options that were
> built into the origional kernel that came with Redhat 6.1
> remains the same. I don't know what those options are?
>     How to accomplish the task?

>                                                         Thanks
>                                                                     Mike

Go to www.aduva.com

Download Aduva Manager and then perform the Kernel Update.

Before it will update you're kernel it will tell you what changes are
needed (if any are needed). It won't do anything without your approval.

Try it. It might solve your problem in the easy way.

cheerio,

Karen

 
 
 

1. Help: Failed Modules When Upgrading from 2.2.12smp to 2.2.16smp

I installed the new RPM's for 2.2.16 and built an SMP version of it
using,

make xconfig

make MAKE="make -j2" bzImage
make MAKE="make -j2" modules
make modules_install

Then I copied my bzImage to /boot/vmlinuz-2.2.16-3.
Then, I created an initrd image with

mkinitrd /boot/initrd-2.2.16-3.img

and a boot floppy with

mkbootdisk 2.2.16-3

Unfortunately, not everything comes up fine after rebooting. I get a
whole host of unresolved symbol errors when the kernel is trying to load
the loadable device drivers. Specifically, neither the joystick.o,
parport.o, nor sound.o modules will load properly. All of them produce
the same errors...something like, "undefined symbol _global_cli,
_global_start, ..".

I also get a bunch of unresolved symbol errors from other modules.

Despite this, at leat my Ethernet TCP/IP connection is working and
everything else is work. What am I doing wrong this time? I've done this
many times and never had problems like this. Am I missing something in
my system? Did something change significantly between the 2.2.12 and
2.2.16 releases that would cause this problem?

By the way, none of the kernel build procedures that I've seen in RedHat
manuals, or anywhere else, specifically talk about the "System.map". Do
I have to do anything with this file.

Also, the kernel used to be smart enought, that if I called my kernel
2.2.16-3smp.i586 that it would look for modules in

/lib/modules/2.2.16-3smp.i586

At least it seemed to do that in 2.2.12. The kernel doesn't appear to do
this for 2.2.16. It insists on looking for modules in 2.2.16-3.

Please respond via e-mail.

--
Bruce W. Bigby/Technical Specialist (Software Engineer)
Xerox Corporation - 300-12S/145, 800 Phillips Road, Webster, NY 14580

///////////////////////////////////////////////////////////////////
All of the opinions in this e-mail message are my own and do not
represent the opinions or policies of my employer, unless I have
explicitly stated so.
///////////////////////////////////////////////////////////////////

2. me and my Gravis...

3. DMESG: SMP motherboard not detected (knl: 2.2.12 2.2.15 2.2.16)

4. Problem with inetd since installing Pentium board

5. 2.2.12 -> 2.2.16

6. packages: @newdepend semantics?

7. Multicast on 2.2.12 - 2.2.16

8. driver for Aver PCImager card needed

9. Kernel 2.2.16 "kernel panic, no init found", kernel 2.2.12, no problem

10. need help with kernel patching 2.2.16 -> 2.2.16-1

11. OPTi 16 Sound Card Configuration under RH5.2 & kernel 2.2.12

12. Kernel 2.2.12 refuses to compile after upgrades to GCC, make, and glibc

13. Problem with 'mkinitrd' while upgrading kernel to 2.2.12