All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: "Ryan C. Gordon" <icculus@icculus.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC][PATCH 1/2] binfmt_elf: FatELF support in the binary loader.
Date: Fri, 23 Oct 2009 15:16:20 -0700	[thread overview]
Message-ID: <4AE22B34.7090103@goop.org> (raw)
In-Reply-To: <alpine.DEB.2.00.0910200034500.18342@andre.icculuslan>

On 10/19/09 21:43, Ryan C. Gordon wrote:
> I'm not sure the added flexibility is worth the extra complications. 
> FatELF solves a specific problem: merging multiple ELF targets into one 
> file, the most compelling use-case being to glue x86_64 and i686 binaries 
> together.
>
> What you're describing would definitely be the route I'd have chosen if, 
> say, a.out files were still in widespread use and actively competed with 
> ELF for mindshare.
>   

It would be nice to have something that would conceptually work for
other architectures with other executable file formats.  Granted ELF is
most common, but its far from the only one.

A generic approach would allow the last-option fallback executable to be
a shell/python/perl script which could do something useful (like display
a useful message).

>> That is, what you have here, but without hacking up binfmt_elf more.
>>     
> I like to think of it as art, like a chef carving a fine piece of meat. :)
>   

Well, its really a bit diseased, with lots of gristly bits and a few
unexpected tubes sticking out the side.

    J

  reply	other threads:[~2009-10-23 22:16 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-19 14:39 [RFC][PATCH 1/2] binfmt_elf: FatELF support in the binary loader Ryan C. Gordon
2009-10-20  0:12 ` Jeremy Fitzhardinge
2009-10-20  4:43   ` Ryan C. Gordon
2009-10-23 22:16     ` Jeremy Fitzhardinge [this message]
2009-10-24  0:25       ` Ryan C. Gordon
2009-10-21  8:08 ` Ryan C. Gordon
2009-10-22  7:31 ` Nicholas Miell
2009-10-22  9:22   ` Ryan C. Gordon

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=4AE22B34.7090103@goop.org \
    --to=jeremy@goop.org \
    --cc=icculus@icculus.org \
    --cc=linux-kernel@vger.kernel.org \
    /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.