From: Rusty Russell <rusty@rustcorp.com.au>
To: Willy Tarreau <willy@w.ods.org>
Cc: Rusty Russell <rusty@rustcorp.com.au>, linux-kernel@vger.kernel.org
Subject: Re: module-init-tools don't support gzipped modules.
Date: Fri, 01 Aug 2003 16:30:44 +1000 [thread overview]
Message-ID: <20030801064916.3F45B2C2B2@lists.samba.org> (raw)
In-Reply-To: Your message of "Thu, 31 Jul 2003 16:33:50 +0200." <20030731143350.GA30865@alpha.home.local>
In message <20030731143350.GA30865@alpha.home.local> you write:
> On Thu, Jul 31, 2003 at 11:06:35AM +1000, Keith Owens wrote:
> > On Thu, 31 Jul 2003 02:46:23 +1000,
> > Rusty Russell <rusty@rustcorp.com.au> wrote:
> > >I don't want to require zlib, though. The modutils I have (Debian)
> > >doesn't support it, either.
> >
> > Really? modutils 2.4: ./configure --enable-zlib
>
> Ok, here is a patch against module-init-tools-0.9.13-pre that I ported from
> modutils. I haven't tested it yet since I don't have any 2.6 kernel right here.
> But at least it compiles with and without zlib.
OK, I'll work from this patch: I'll probably pull out a separate
"snarf file" function and use that for all these cases, to ensure
there's only one #ifdef though.
Thanks!
Rusty.
--
Anyone who quotes me in their sig is an idiot. -- Rusty Russell.
next prev parent reply other threads:[~2003-08-01 6:49 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-30 9:22 module-init-tools don't support gzipped modules Gerardo Exequiel Pozzi
2003-07-30 10:10 ` Bas Mevissen
2003-07-30 10:15 ` Tomas Szepe
2003-07-30 16:46 ` Rusty Russell
2003-07-30 19:11 ` Bill Nottingham
2003-07-31 1:06 ` Keith Owens
2003-07-31 9:19 ` Tomas Szepe
2003-07-31 9:52 ` Pawel Kot
2003-07-31 9:57 ` Tomas Szepe
2003-08-01 7:13 ` Gerardo Exequiel Pozzi
2003-07-31 14:33 ` Willy Tarreau
2003-08-01 6:30 ` Rusty Russell [this message]
2003-08-01 7:14 ` Gerardo Exequiel Pozzi
2003-07-31 9:17 ` Tomas Szepe
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=20030801064916.3F45B2C2B2@lists.samba.org \
--to=rusty@rustcorp.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=willy@w.ods.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;
as well as URLs for NNTP newsgroup(s).