mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ingo Oeser <ingo.oeser@informatik.tu-chemnitz.de>
To: ketil@froyn.com
Cc: mas9483@ksu.edu, linux-kernel@vger.kernel.org
Subject: Re: gzipped executables
Date: Tue, 13 Feb 2001 13:09:49 +0100	[thread overview]
Message-ID: <20010213130949.A472@nightmaster.csn.tu-chemnitz.de> (raw)
In-Reply-To: <20010213084031.8598.qmail@www1.nameplanet.com>
In-Reply-To: <20010213084031.8598.qmail@www1.nameplanet.com>; from ketil@froyn.com on Tue, Feb 13, 2001 at 08:40:31AM -0000

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
-- 
10.+11.03.2001 - 3. Chemnitzer LinuxTag <http://www.tu-chemnitz.de/linux/tag>
         <<<<<<<<<<<<       come and join the fun       >>>>>>>>>>>>

  reply	other threads:[~2001-02-13 12:10 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-13  8:40 ketil
2001-02-13 12:09 ` Ingo Oeser [this message]
2001-02-13 13:08   ` Padraig Brady
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=20010213130949.A472@nightmaster.csn.tu-chemnitz.de \
    --to=ingo.oeser@informatik.tu-chemnitz.de \
    --cc=ketil@froyn.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®