[NTLUG:Discuss] Kernel

[terry]

kbrannen at gte.net wrote:

> Patrick Parks wrote:
>
>> Cool, thanks for the reply.
>>
>>
>>> the System.map file is not generally used for much either. I 'think' 
>>> that his is used for debugging. You need it if you debug something. 
>>> When you do a compile yourself, a System.map file is created. I copy 
>>> this to my /boot directory and add a -x.x.x. version number to it
>>
>>
>>
>> do you soft link this also? ln -s System.map System.map-x.x.x?
>
>
> No, you want to copy it.  If you don't, and then you later come back 
> and make a new kernel, you've "lost" your data 
> (System.map-old-kernel-info) haven't you. :-)
>
>>
>> I have seen some references to recompiling the Kernel using RPM, is this
>> recommended, and what is the difference in doing it this way vs   the
>> old way?
>
>
> You got me there.  I always thought the new kernel rpms just dumped 
> new source into /usr/src/linux for you to compile, but now that I 
> think about it, I'm not sure I've ever let up2date give me a new kernel.
>
> HTH,
> Kevin
>
I think they could do it either way, but RedHat's up2date apparently 
downloads a kernel rpm that installs itself.  I say that from experience 
because I did it a couple months ago on my cousin's RedHat (8.0) box and 
after I was done, it left me with a new fully functional kernel and even 
added the entry in grub's menu.lst for it and all I had to do was change 
to default to the new one instead of the old one.

I just tried it on a new RH8 box I have here, (the $199 ThizLinux Fry's 
special), and it failed twice, (so far), saying that the rpm failed some 
sort of authentication verification, so I have yet to duplicate the 
process.  (I'm on dialup here so it's very slow  process.)

-- 
Registered Linux User #188099
<><