From: Ian Soboroff <isoboroff@acm.org>
To: linux-kernel@vger.kernel.org
Subject: Re: Automatic download of kernel rpms
Date: Wed, 09 Nov 2005 08:34:55 -0500 [thread overview]
Message-ID: <9cfd5lagd1c.fsf@rogue.ncsl.nist.gov> (raw)
In-Reply-To: <Pine.LNX.4.61.0511080910001.3265@chaos.analogic.com> (linux-os@analogic.com's message of "Tue, 8 Nov 2005 09:13:54 -0500")
"linux-os \(Dick Johnson\)" <linux-os@analogic.com> writes:
> On Tue, 8 Nov 2005, Alan Cox wrote:
>
>> On Maw, 2005-11-08 at 08:33 -0500, Gene Heskett wrote:
>>> Generally, no. The exact reason is that rpms are a vendor item, and no
>>> fixed relation to the kernel.org tarballs.
>>
>> "make rpm" should build an RPM package from them but you will still need
>> to get the configuration correct before doing this.
>>
>
> Alan can verify that Red Hat Fedora puts the ".config" file in
> /boot as /boot/config-`uname -r`. This can be copied to the
> new kernel tree as ".config" and `make oldconfig` should get
> you a kernel configured very close to the one provided with
> the distribution.
Note that Fedora (and RHEL) kernels modularize nearly everything and
need an initrd to boot. The kernel's "make rpm" does not make the
initrd for you (or fix up your grub.conf, IIRC). So, the sequence is:
(unpack kernel)
cp /boot/config-`uname -r` .config
make oldconfig
(answer questions about new stuff)
make rpm
rpm -ivh <the-new-rpm>
mkinitrd /boot/initrd-<ver> <ver>
(edit grub.conf or what have you)
Ian
prev parent reply other threads:[~2005-11-09 13:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-08 6:29 li nux
2005-11-08 13:33 ` Gene Heskett
2005-11-08 14:18 ` Alan Cox
2005-11-08 14:13 ` linux-os (Dick Johnson)
2005-11-09 13:34 ` Ian Soboroff [this message]
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=9cfd5lagd1c.fsf@rogue.ncsl.nist.gov \
--to=isoboroff@acm.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®