From: Xavier Bestel <xavier.bestel@free.fr>
To: Matt Stegman <mas9483@ksu.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: gzipped executables
Date: 13 Feb 2001 15:09:27 +0100 [thread overview]
Message-ID: <200102131409.PAA26445@microsoft.com> (raw)
In-Reply-To: <Pine.GSO.4.21L.0102130758280.4752-100000@unix2.cc.ksu.edu>
Le 13 Feb 2001 07:58:56 -0600, Matt Stegman a écrit :
> Hello,
>
> Anything in 2.4 isn't an option right now. I'm using, and am really happy
> with, the ext3 journalling patch. I'm not planning on a 2.4 upgrade until
> ext3 has been ported. Damn shame I don't have the skill to do that
> myself...
>
> ext2 compression would be great. First off, though, I'm already using the
> ext3 patch. Would ext2 compression be compatible, and take effect for
> ext3 (ext3 support is a separate option in the kernel from ext2)? Also, I
> can't even get to the ext2 compression page
> http://e2compr.memalpha.cx/e2compr/.
>
> UPX looks interesting; I'll have to check it out in depth. Thanks, all!
>
> -Matt
If you're really adventurous, I've once done a patch for uClinux to
enable a compressed (gzip) executable format (not ELF, way lighter). It
should be at http://aplionet.aplio.fr/uclinux (the kernel loader is
linux/fs/binfmt_flat.c, the tools to generate the execs are in
tools/elf2flt)
Xav
next prev parent reply other threads:[~2001-02-13 14:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-13 8:40 gzipped executables ketil
2001-02-13 12:09 ` Ingo Oeser
2001-02-13 13:08 ` Padraig Brady
2001-02-13 13:58 ` Matt Stegman
2001-02-13 14:09 ` Xavier Bestel [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-02-13 5:09 Matt Stegman
2001-02-13 21:09 ` Mike Castle
2001-02-14 19:22 ` Pavel Machek
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=200102131409.PAA26445@microsoft.com \
--to=xavier.bestel@free.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=mas9483@ksu.edu \
/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