From: Dan Stromberg <dstromberglists@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Building a kernel-source RPM (not a kernel RPM)?
Date: Wed, 12 Sep 2007 10:31:03 -0700 [thread overview]
Message-ID: <pan.2007.09.12.17.30.59.597440@gmail.com> (raw)
In-Reply-To: 1189616966.31502.75.camel@tara.firmix.at
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!
next prev parent reply other threads:[~2007-09-12 17:31 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-12 16:13 Building a kernel-source RPM (not a kernel RPM)? Dan Stromberg
2007-09-12 16:49 ` Dan Stromberg
2007-09-12 17:05 ` Sam Ravnborg
2007-09-12 17:11 ` Bernd Petrovitsch
2007-09-12 17:51 ` Sam Ravnborg
2007-09-12 18:10 ` Bernd Petrovitsch
2007-09-12 18:16 ` Sam Ravnborg
2007-09-12 18:23 ` Bernd Petrovitsch
2007-09-12 20:23 ` Jan Engelhardt
2007-09-12 21:05 ` linux-os (Dick Johnson)
2007-09-12 17:09 ` Bernd Petrovitsch
2007-09-12 17:31 ` Dan Stromberg [this message]
2007-09-12 18:03 ` Bernd Petrovitsch
2007-09-12 19:46 ` Thorsten Leemhuis
2007-09-12 20:03 ` Sam Ravnborg
2007-09-13 17:09 ` Thorsten Leemhuis
2007-09-13 17:22 ` Sam Ravnborg
2007-09-13 17:26 ` Thorsten Leemhuis
2007-09-12 18:03 ` Jan Engelhardt
2007-09-13 16:09 ` Chuck Ebbert
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=pan.2007.09.12.17.30.59.597440@gmail.com \
--to=dstromberglists@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.