"Mark W. Knecht" wrote:

>    Now, my goal was to do a kernel build from source, and I downloaded a
> non-source package (kernel-2.2.16-22.i686.rpm). I couldn't find a SRPM
> of -22, so I downloaded kernel-2.2.16-3.src.rpm. I think Larry said he was
> running this kernel. I'm hoping this really is source for the kernel...

Most RPM-based distros will, when building from the .src.rpm, create
something like the following list of RPMs:

kernel-version-revision.arch.rpm
kernel-headers-version-revision.arch.rpm
kernel-source-version-revision.arch.rpm
(and sometimes)
kernel-pcmcia-cs-version-revision.arch.rpm
kernel-doc-version-revision.arch.rpm
...etc...

If you download and install the kernel-source-2.2.16-22.i686.rpm (if
there is one), it should put the source to their kernel (with all of the
patches applied) in /usr/src/ -- if you get the kernel-2.2.16-22.src.rpm
you'll spend 3 days compiling, since they typically build an SMP kernel,
and a regular kernel, etc.

...but, if you do decide to use a .src.rpm for a kernel:

>    I attempted to run rpm, and it looks like it's running, but I can't find
> the source on my system. (Assuming that it really got written somewhere...)
> There's no directory under /usr/src for 2.2.16-3. I used:
> 
>    rpm -ivh kernel-2.2.16-3.src.rpm

these get put into the RPM source directory; on redhat that's
/usr/src/redhat/, on mandrake it's /usr/src/RPM/, on suse, it's
/usr/src/packages/ (I think), etc.  It's different for every distro.

>    Where does rpm put this stuff? I'm sure there must be a way to get rpm to
> tell me what it does?
> 
>    Off to find my copy of Maximum RPM.

Good idea.  ;)  Kernel source RPMs are usually the most convoluted ones
you'll find, hundreds of patches, very long spec files, etc.  You'll
probably need to dig through /usr/src/redhat/SPECS/kernel.spec (or
equivalent) if you really want to do this.  :)
_______________________________________________
Win4Lin-users mailing list
[EMAIL PROTECTED]
https://lists.netraverse.com/mailman/listinfo/win4lin-users

Reply via email to