From: Padraig Brady <Padraig@AnteFacto.com>
To: mas9483@ksu.edu
Cc: linux-kernel@vger.kernel.org
Subject: Re: gzipped executables
Date: Tue, 13 Feb 2001 13:08:17 +0000 [thread overview]
Message-ID: <3A8931C1.4090601@AnteFacto.com> (raw)
In-Reply-To: <20010213084031.8598.qmail@www1.nameplanet.com> <20010213130949.A472@nightmaster.csn.tu-chemnitz.de>
You might consider UPX (http://upx.tsx.org)
Very cool. The beta version supports compressing the kernel
and "direct-to-memory" compression. I think it still
has the disadvantage of not sharing segments between many
instances of the same program. Is there any way of fixing
this? (probably would have to hack a bit with the loader?)
For a general solution I would look @ changing the filesystem
so that particular files (not just executables) can be compressed/
decompressed transparently. (I.E. for ext2 implement `chattr +c`).
Padraig.
Ingo Oeser wrote:
> On Tue, Feb 13, 2001 at 08:40:31AM -0000, ketil@froyn.com wrote:
>
>> On Mon, 12 Feb 2001 23:09:39 -0600 (CST) Matt Stegman <mas9483@ksu.edu> wrote:
>>
>>> Is there any kernel patch that would allow Linux to properly recognize,
>>> and execute gzipped executables?
>>
>> Perhaps you could put it in the filesystem. Look at the
>> "chattr" manpage, which shows how this is meant to work with
>> ext2. It seems not to have been implemented yet. This way you
>> could also compress any files, not just executables.
>
>
> A nice way already implemented in 2.4.x is cramfs. Many embedded
> people (like me) use it to fill up their flash disks.
>
> Look at linux/Documentation/filesystems/cramfs.txt for more info.
>
> Regards
>
> Ingo Oeser
next prev parent reply other threads:[~2001-02-13 13:08 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 [this message]
2001-02-13 13:58 ` Matt Stegman
2001-02-13 14:09 ` Xavier Bestel
-- 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=3A8931C1.4090601@AnteFacto.com \
--to=padraig@antefacto.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.