Hi Connie,

It's always been that way.  As far back as RedHat 7.  Beyond that, I don't
know because I used to use Slackware.  If you look at the
glibc-kernheaders version number, you'll see they don't even match the
initial kernel that comes with that distribution.  Not your fault.
RedHat's been doing this since I started using RedHat many moons ago.


Ken

PS. Btw, when is RedHat Enterprise going to the 2.6 kernel?  I had to put
Fedora Core 2 on a new laptop.  Much to my dislike.  But I needed some new
drivers.

On Tue, 28 Sep 2004, csieh wrote:

> Ken,
>
> On Tue, 28 Sep 2004, Ken Teh wrote:
>
> > Hi Alan,
> >
> > I know this problem.  I fix it manually all the time.  This is what you
> > do:
>
> So why do you have to do this?  What broke it?
>
> -Connie Sieh
> >
> > If you do
> >
> > rpm -qf /usr/include/asm
> > rpm -qf /usr/include/linux
> >
> > you will see that they belong to the rpm glibc-kernheaders.  I always do
> > the following:
> >
> > cd /usr/include
> > mv asm asm.glibc-kernheaders
> > ln -sf /usr/src/linux-2.4/include/asm asm
> > mv linux linux.gblic-kernheaders
> > ln -sf /usr/src/linux-2.4/include/linux linux
> >
> > Then,
> >
> > cd /usr/src/linux-2.4/include
> > ln -sf asm-i386 asm
> >
> > These last 2 steps are necessary if the asm link is not there.
> > /usr/src/linux-2.4 is itself a link.  Be sure it is pointing to the correct
> > kernel tree.
> >
> > There are actually a few more /usr/include directories that correspond to
> > subdirectories in /usr/src/linux-2.4/include.  If you need to use the kernel
> > tree's headers instead of /usr/include, then you need to mv and ln them as
> > well.  I would be very careful with the net/ subdirectory.  I suspect the
> > one in /usr/include is used in applications development, so it should not be
> > mv'ed.
> >
> > Cheers!
> >
> > Ken
> >
> > On Tue, 28 Sep 2004, Alan J. Flavell wrote:
> >
> > > On Tue, 28 Sep 2004, csieh wrote:
> > >
> > > > What do you mean by kernel development rpms.
> > >
> > > I mean that when I did the original 301 install, I went to the custom
> > > selection and I checked the box for the kernel development group.
> > > This was chiefly so that I could build kernel-modules (I wasn't really
> > > planning on building custom kernels, but you never know...)
> > >
> > > > I assume you mean kernel-source .  Did you have kernel-source
> > > > installed before and do you have it installed now.
> > >
> > > That's right.  (I've responded to Troy now, and I'll report on
> > > anything useful that comes up).
> > >
> > > many thanks.
> > >
> >
>