All of lore.kernel.org
 help / color / mirror / Atom feed
From: Al Viro <viro@ZenIV.linux.org.uk>
To: Chad Brewbaker <crb002@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: dlopen() and ELF alternatives
Date: Sat, 14 May 2016 18:25:02 +0100	[thread overview]
Message-ID: <20160514172502.GA14480@ZenIV.linux.org.uk> (raw)
In-Reply-To: <CAMMYZ9Am1uMjSwATvWsRpHhDGXcqtO26GXRwi26DTVtEPRwr0w@mail.gmail.com>

On Sat, May 14, 2016 at 11:41:54AM -0500, Chad Brewbaker wrote:
> In 2016 we are still relying on flat file databases to store binaries.

This is not a discussion club; cut the rethorics if you want to be taken
seriously.  You sound as if the only problem you have is that format is
insufficiently buzzword-compliant; if that's the case, nobody is going to
give a damn, obviously.  If you *do* have more specific problem, have
a courtesy to describe it...

> I am looking for prior attempts at alternative interfaces to dlopen(), and
> alternative formats for object files.

There had been a plenty of object file formats; take a look at libbfd for a
sample of that panopticum.

      reply	other threads:[~2016-05-14 17:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-14 16:41 dlopen() and ELF alternatives Chad Brewbaker
2016-05-14 17:25 ` Al Viro [this message]

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=20160514172502.GA14480@ZenIV.linux.org.uk \
    --to=viro@zeniv.linux.org.uk \
    --cc=crb002@gmail.com \
    --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.