This sounds too easy

I can not get the files from the rpm kernel-2.6.9-1.681_FC3.src.rpm.

I use #rpm -ivh kernel-2.6.9-1.681_FC3.src.rpm and it shows the progress bar like it installs. There are no errors everything looks clean. The rpm is installed under the /usr/src directory.
There is nothing installed under the /usr/src/redhat directory. I have searched for the tarballs that I have heard should be produced and none are to be found. I have also searched for the normal tree structures that show up with a kernel package. Where is it putting all these files???

With all of the previous FC releases I have always compiled my kernel with the vanilla kernel from kernel.org so that my radeon will work. However, with FC3 the ATI driver is absolutety worthless, but I can't stand the extra stuff that bogs down the system and the vanilla 2.6.9 kernel has been flaky with FC3. Worked OK with the first FC3 kernel, but after the up2dates (which finally are worthwhile) on the kernel, I have a hard time getting goog streamlined kernels. This is why I raise the white flag and say give me the custom kernel sources.

It seems that FC has downgraded from each version. I know everyone loves the security, but it is operable as root and not as user. I am considering going back to Mandrake but I have had little success with my intel network card after version 9. My other choice that sounds good is debian.

I installed that very package today and it put itself in /usr/src/redhat/SOURCES. I got mine off the mirror at Duke. (mirror.linux.duke.edu)

Maybe the package forgets to create the correct directory tree? Do you have all the usual suspects in the /usr/src/redhat dir? Did you install as root? Directory permissions OK?

I do agree that each FC release seems to be advancing to the rear at an ever increasing rate. If you think about it, RH has no reason to allow the world to have a free product that is better than the one they are trying to sell...

It did not put itself in the ../souces tree.

But, I did download from redhat and not Duke

BTW

How is slackware? I am thinking about giving it a shot.

Slackware is great if you don't need GUI config tools. You are on your own there. It is very much like BSD in the way it initializes and the way it favors stability over marginal features. It has the least helpful documentation, but that cuts both ways. It forces you to learn. Maybe that is what Patrick Volkerding is really trying to accomplish - to make us think for ourselves and to read the fine manuals.

I use RHEL on the desktop, but all my servers are highly modifed SL10 distro's.

Did this the other day and like you was bit mystified, then read soemwhere that all the rpm does when you run it is extract a "Tarball", I think that's right. You then have to copy the "Tarball" to /usr/src or where ever and extract that !!

Sorry can't tell you where it put's it or how to extract it as I'm not @ my PC just now. Might try /var/spool/ something think that's where the rpm's from up2date live.

Not much use I know, but hopefully a pointer.

The RPM package extracts to /usr/src/redhat/SOURCES. You just have to do the following:

cd /usr/src
tar -xjvpf /usr/src/redhat/SOURCES/linux-2.6.9.tar.bz2

Now you have a folder linux-2.6.9 in /usr/src. Make a ln -s linux-2.6.9/ linux and you're done!

As I initially said, it sounds to easy.

As it turns out, the srpm puts tarballs in the /usr/src/redhat/SOURCE directory. I did not initially see this because I viewed it in the gui and not with ls as terminal. I was also surprised to find out that it looks like the official 2.6.9 kernel with the 2.6.10rc patch. All in all, I was able to compile the kernel but I am still wondering how is it a custom kernel when everthing appears to be like kernels that I have compiled right from kernel.org.

Thank you for your input.

paikea

Thanks. I have followed this procedure and I am able to get the /usr/src/linux-2.6.9 folder but when other programs that require the kernel source call it I get the following:

[root@localhost ~]# sh build_26.sh i386
Checking for kernel-source... [ Failed ]

you must install the kernel-source.

[root@localhost ~]#

Any idea why?

I have had some apps that required a symbolic link to the current source tree.

This was solved by creating a symbolic link in the /usr/src directory named linux that points to the current source tree.