On Fri, 19 Nov 1999, Charles Galpin wrote:
> The short version:
> 1. What are the differences between Red Hat's kernel-source rpm and a
> tarball of the same rev? They clearly apply some patches which are not in
> the tarball.
> 2. Are there any downsides to using the tarball and not applying whatever
> patches RH has added?
I guess not. Even more if it's a newer version.
> Well, it turns out RH has applied some patches that make John Hardin's
> patches get rejected. So on my laptop (6.1 too), I got the latest kernel
> 2.2.13 and patched it successfully, and built it. Oh, I was using the
> excellent buildkernel script, and with the exception of having to manually
> update the System.map link (can someone tell me how to make the correct
> System.map be used regardless of the image you boot from?) everything
> looks good.
I have lots of version of kernels and load them without haveing to touch
the symlink. just copy the System.map in the boot dir adding a
-<version> at the end.
example: System.map-2.2.13
> But before I go and do this on my gateway, I want to make sure that I'm
> not shooting myself in the foot doing it this way.
>
> One of the things I have noticed that bothers me is that I have the 2.2.12
> kernel-headers rpm installed which seems to haev things dependent on it.
> Isn't it a bad idea to have the kernel built from a tarball, yet have
> older headers lying around that other rpms might be using? I'm thinking
> specifically of when building source rpms that may need them?
Nop!!! When you compile, the compiler follows the link, thats why yuou
have to change the symlink /usr/src/linux and make it point at the
directory with the current version you are using.
"La gente que usa VB, solo Ve lo Basico"
-----------------------------------------------------------------
Martín Marqués email: [EMAIL PROTECTED]
Santa Fe - Argentina http://math.unl.edu.ar/~martin/
Administrador de sistemas en math.unl.edu.ar
-----------------------------------------------------------------
--
To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
as the Subject.
