From: Rusty Russell <rusty@rustcorp.com.au>
To: Tomas Szepe <szepe@pinerecords.com>
Cc: Bas Mevissen <ml@basmevissen.nl>
Cc: Gerardo Exequiel Pozzi <vmlinuz386@yahoo.com.ar>,
linux-kernel@vger.kernel.org
Subject: Re: module-init-tools don't support gzipped modules.
Date: Thu, 31 Jul 2003 02:46:23 +1000 [thread overview]
Message-ID: <20030730183635.0B82D2C097@lists.samba.org> (raw)
In-Reply-To: Your message of "Wed, 30 Jul 2003 12:15:18 +0200." <20030730101518.GL4279@louise.pinerecords.com>
In message <20030730101518.GL4279@louise.pinerecords.com> you write:
> > [ml@basmevissen.nl]
> >
> > >The possibility of compressing the modules is interesting, like for
> > >example in cases of construction of small systems or initrd.
> >
> > In both cases, you might use a compressed file system. Maybe you better
> > try to save memory and disk space by compressing less critical stuff
> > than kernel modules.
>
> It's a valid feature request nonetheless.
I agree, but I believe almost anything is a valid feature request.
I don't want to require zlib, though. The modutils I have (Debian)
doesn't support it, either.
It's fairly trivial patch, which probably is best as an add-on (which
I think RH do?
Rusty.
--
Anyone who quotes me in their sig is an idiot. -- Rusty Russell.
next prev parent reply other threads:[~2003-07-30 18:36 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 [this message]
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
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=20030730183635.0B82D2C097@lists.samba.org \
--to=rusty@rustcorp.com.au \
--cc=ml@basmevissen.nl \
--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).