public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: Jim Roland <jroland@roland.net>
Cc: "J. Dow" <jdow@earthlink.net>, linux-kernel@vger.kernel.org
Subject: Re: RedHat kernel RPM 2.2.16
Date: Wed, 07 Feb 2001 08:37:45 +0000	[thread overview]
Message-ID: <16718.981535065@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.05.10102062344490.31995-100000@ns.roland.net>
In-Reply-To: <Pine.LNX.4.05.10102062344490.31995-100000@ns.roland.net>


jroland@roland.net said:
>  FWIW, the rpm -i did unpack the kernel to the /usr/src/redhat/SOURCES
> directory, however, I had to manually untar the sources to /usr/src to
> get my kernel, move over the appropriate .config file, and manually
> run the patches to patch the sources.  Forcing RPM to be very
> talkative (via -vv) gave me a bunch of "action unknown" errors, and
> the rpm's install scripts did not execute.  This occurs on an RH7
> system as well.  Seems to be something wrong with RH's kernel rpm? 

Install the kernel-source binary RPM, which contains the build tree already 
extracted and set up as you desire, instead of the master SRPM which 
contains build instructions for all the kernel versions.

i.e. kernel-source-2.2.16-3.i386.rpm, not kernel-2.2.16-3.src.rpm

--
dwmw2


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

  reply	other threads:[~2001-02-07  8:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <0b2801c090c6$3e1a76e0$0a25a8c0@wizardess.wiz>
2001-02-07  5:50 ` RedHat kernel RPM 2.2.16 Jim Roland
2001-02-07  8:37   ` David Woodhouse [this message]
2001-02-08  3:09     ` Jim Roland
2001-02-07  9:39   ` Alan Cox
2001-02-07  5:03 Jim Roland

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=16718.981535065@redhat.com \
    --to=dwmw2@infradead.org \
    --cc=jdow@earthlink.net \
    --cc=jroland@roland.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