From: "linux-os \(Dick Johnson\)" <linux-os@analogic.com>
To: "Alan Cox" <alan@lxorguk.ukuu.org.uk>
Cc: "Gene Heskett" <gene.heskett@verizon.net>,
"Linux kernel" <linux-kernel@vger.kernel.org>
Subject: Re: Automatic download of kernel rpms
Date: Tue, 8 Nov 2005 09:13:54 -0500 [thread overview]
Message-ID: <Pine.LNX.4.61.0511080910001.3265@chaos.analogic.com> (raw)
In-Reply-To: <1131459503.25192.42.camel@localhost.localdomain>
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.
Cheers,
Dick Johnson
Penguin : Linux version 2.6.13.4 on an i686 machine (5589.55 BogoMips).
Warning : 98.36% of all statistics are fiction.
.
****************************************************************
The information transmitted in this message is confidential and may be privileged. Any review, retransmission, dissemination, or other use of this information by persons or entities other than the intended recipient is prohibited. If you are not the intended recipient, please notify Analogic Corporation immediately - by replying to this message or by sending an email to DeliveryErrors@analogic.com - and destroy all copies of this information, including any attachments, without reading or disclosing them.
Thank you.
next prev parent reply other threads:[~2005-11-08 14:13 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) [this message]
2005-11-09 13:34 ` Ian Soboroff
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=Pine.LNX.4.61.0511080910001.3265@chaos.analogic.com \
--to=linux-os@analogic.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=gene.heskett@verizon.net \
--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®