From: Pawel Kot <pkot@linuxnews.pl>
To: Tomas Szepe <szepe@pinerecords.com>
Cc: Keith Owens <kaos@ocs.com.au>,
Rusty Russell <rusty@rustcorp.com.au>,
<linux-kernel@vger.kernel.org>
Subject: Re: module-init-tools don't support gzipped modules.
Date: Thu, 31 Jul 2003 11:52:28 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.33.0307311149110.11927-100000@urtica.linuxnews.pl> (raw)
In-Reply-To: <20030731091909.GK12849@louise.pinerecords.com>
On Thu, 31 Jul 2003, Tomas Szepe wrote:
> > [kaos@ocs.com.au]
> >
> > 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
>
> Keith, I believe Rusty meant the standard Debian package had binaries
> compiled w/o '--enable-zlib'.
>
> (And so has Slackware btw.)
Slackware since 8.0 uses compression for the kernel modules by
default and uses --enable-zlib for modutils.
See:
ftp://ftp.slackware.com/pub/slackware/slackware-9.0/source/a/modutils/modutils.SlackBuild
pkot
--
mailto:pkot@linuxnews.pl :: mailto:pkot@slackware.pl
http://kt.linuxnews.pl/ :: Kernel Traffic po polsku
next prev parent reply other threads:[~2003-07-31 9:52 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 [this message]
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
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=Pine.LNX.4.33.0307311149110.11927-100000@urtica.linuxnews.pl \
--to=pkot@linuxnews.pl \
--cc=kaos@ocs.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
--cc=szepe@pinerecords.com \
/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).