To: linux-kernel@vger.kernel.org
From: Dan Stromberg <dstromberglists@gmail.com>
Subject: Re: Building a kernel-source RPM (not a kernel RPM)?
Date: Wed, 12 Sep 2007 10:31:03 -0700
Message-ID: <pan.2007.09.12.17.30.59.597440@gmail.com>
References: <pan.2007.09.12.16.13.41.195991@gmail.com> <1189616966.31502.75.camel@tara.firmix.at>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7BIT
User-Agent: Pan/0.14.2 (This is not a psychotic episode. It's a cleansing moment of clarity.)
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 2660
Lines: 67

On Wed, 12 Sep 2007 19:09:26 +0200, Bernd Petrovitsch wrote:

> On Wed, 2007-09-12 at 09:13 -0700, Dan Stromberg wrote:
>> I sent this to kernel newbies first, and while I got one response there,
>> it answered a different question than the one I was asking...
> 
> Are you sure?

Yes, I'm sure.  The answer over there was "you don't want to do that.  Do
this instead.

>> I'm on a SuSE system.
>> 
>> I'm working on automating the install of said system, but it needs a
>> Linus kernel - 2.6.21.7 specifically, and it needs kernel source too so
>> that we can build modules in the field as needed.
> 
> Find a kernel-source.*.src.rpm or kernel-*.src.rpm or whatever SuSE uses
> for
> nameing convention and reverse engineer the .spec file.
> Fedora BTW abandoned kernel-source* and they have now a website with a
> description
> how to produce a configured kernel source tree (e.g. for out-of-tree
> modules).

So this is as smooth as producing kernel-source RPM's gets?

I might be better off sticking with a .tar.bz2 and repointing symlinks.

>> I see you can make an rpm of a bootable kernel with "make rpm".
> 
> Well, then there must be a .spec file somewhere which just wants to be
> extended.

I'm not sure this is going to be any easier to automate, if that's what's
required.

>> Is there a streamlined way of building a corresponding kernel-source
>> RPM?  Or do people pretty much all just dump the source in /usr/src, and
> 
> Yes, you put all the steps you do by hand into the .spec file. That's
> it.

I may just stick them in a bash script and forget about the RPM.  Or are
there other packages that are going to be cranky, dependencywise, if I
ignore the RPM?

>> manually update symlinks as needed?  If the latter, what symlinks need
>> to be updated?
> 
> Actually nowadays usually there no "sym-link updating" anymore necessary

On OpenSuSE 10.2, there appears to be:

# find / /home -xdev -ls | egrep -- '-> /usr/src/linux'
215641    0 lrwxrwxrwx   1 root     root           26 Sep 11 17:50 /lib/modules/2.6.18.2-34-default/source -> /usr/src/linux-2.6.18.2-34
213786    0 lrwxrwxrwx   1 root     root           45 Sep 11 17:50 /lib/modules/2.6.18.2-34-default/build -> /usr/src/linux-2.6.18.2-34-obj/x86_64/default

> just put the correct ones in /lib/modules/$(uname -r)/ and the full name
> in
> /boot/grub/menu.lst.

Which correct "ones"?  Sometimes pronouns aren't shortcuts :)

Thanks!


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/