public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Arjan van de Ven <arjanv@redhat.com>
To: Andrey Borzenkov <arvidjaar@mail.ru>
Cc: Sam Ravnborg <sam@ravnborg.org>,
	Alistair J Strachan <alistair@devzero.co.uk>,
	Arjan van de Ven <arjanv@redhat.com>,
	linux-kernel@vger.kernel.org,
	Kai Germaschewski <kai@tp1.ruhr-uni-bochum.de>
Subject: Re: [RFC] KBUILD 2.5 issues/regressions
Date: Sun, 9 Nov 2003 11:22:27 +0100	[thread overview]
Message-ID: <20031109112227.A22580@devserv.devel.redhat.com> (raw)
In-Reply-To: <200311091312.56115.arvidjaar@mail.ru>; from arvidjaar@mail.ru on Sun, Nov 09, 2003 at 01:12:56PM +0300

On Sun, Nov 09, 2003 at 01:12:56PM +0300, Andrey Borzenkov wrote:
> 
> sure. But distributor already has shipped all the modules as part of kernel 
> package. Given the number of different kernels in Mandrake currently shipping 
> yet another copy of binary modules for kernel sources would easily fill up 
> the whole CD alone.

in addition at least for the rpm's I'm working on, it's no
longer kernel-source you need or can use for building external modules
against.

  reply	other threads:[~2003-11-09 10:22 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-05  7:10 [RFC] KBUILD 2.5 issues/regressions "Andrey Borzenkov" 
2003-11-05  9:23 ` Arjan van de Ven
2003-11-05 13:39   ` David Woodhouse
2003-11-06 17:23 ` Sam Ravnborg
2003-11-06 23:21   ` Ian Kent
2003-11-09 10:12   ` Andrey Borzenkov
2003-11-09 10:22     ` Arjan van de Ven [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-07-11 17:57 Alistair J Strachan
2003-07-11 17:40 Alistair J Strachan
2003-07-11 17:47 ` Arjan van de Ven
     [not found] ` <200307111856.53635.alistair@devzero.co.uk>
     [not found]   ` <20030711180134.H19709@devserv.devel.redhat.com>
2003-07-11 18:06     ` Alistair J Strachan

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=20031109112227.A22580@devserv.devel.redhat.com \
    --to=arjanv@redhat.com \
    --cc=alistair@devzero.co.uk \
    --cc=arvidjaar@mail.ru \
    --cc=kai@tp1.ruhr-uni-bochum.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sam@ravnborg.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