public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@suse.cz>
To: Matt Stegman <mas9483@ksu.edu>, linux-kernel@vger.kernel.org
Subject: Re: gzipped executables
Date: Wed, 14 Feb 2001 20:22:20 +0100	[thread overview]
Message-ID: <20010214202220.A304@bug.ucw.cz> (raw)
In-Reply-To: <Pine.GSO.4.21L.0102122251040.24003-100000@unix2.cc.ksu.edu>
In-Reply-To: <Pine.GSO.4.21L.0102122251040.24003-100000@unix2.cc.ksu.edu>; from Matt Stegman on Mon, Feb 12, 2001 at 11:09:39PM -0600

Hi!

> Is there any kernel patch that would allow Linux to properly recognize,
> and execute gzipped executables?
> 
> I know I could use binfmt_misc to run a wrapper script:
> 
>     decompress to /tmp/prog.decompressed
>     execute /tmp/prog.decompressed
>     rm /tmp/prog.decompressed
> 
> But that's not as clean, secure, or fast as the kernel transparently
> decompressing & executing.  Is there a better way to do this?

You could do this with uservfs(.sourceforge.net):

ln -s /overlay/path/.../executable.gz#ugz executable

and let uservfs do it for you. It will essentially do what you
described, but it will work on any file.
								Pavel

-- 
I'm pavel@ucw.cz. "In my country we have almost anarchy and I don't care."
Panos Katsaloulis describing me w.r.t. patents at discuss@linmodems.org

  parent reply	other threads:[~2001-02-17 13:35 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-13  5:09 gzipped executables Matt Stegman
2001-02-13 21:09 ` Mike Castle
2001-02-14 19:22 ` Pavel Machek [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-02-13  8:40 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

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=20010214202220.A304@bug.ucw.cz \
    --to=pavel@suse.cz \
    --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