public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jakub Jelinek <jakub@redhat.com>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: Jeff Garzik <jgarzik@pobox.com>, Adrian Bunk <bunk@fs.tum.de>,
	Andrew Morton <akpm@osdl.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [2.6 patch] disallow modular BINFMT_ELF
Date: Mon, 17 Nov 2003 08:08:06 -0500	[thread overview]
Message-ID: <20031117130806.GC6288@devserv.devel.redhat.com> (raw)
In-Reply-To: <m1vfpjol6w.fsf@ebiederm.dsl.xmission.com>

On Sun, Nov 16, 2003 at 06:09:11PM -0700, Eric W. Biederman wrote:
> Jeff Garzik <jgarzik@pobox.com> writes:
> 
> > Adrian Bunk wrote:
> > > modular BINFMT_ELF gives unresolved symbols in 2.4 .
> > > modular BINFMT_ELF gives the following unresolved symbols in 2.6:
> > 
> > 
> > Interesting.  this causes me to wonder if we should bother making BINFMT_ELF an
> > 
> > option at all...
> 
> We have platforms uClinux for which ELF is not the preferred format so we
> should at least be able to compile it out.

Similarly on bi-arch supporting platforms, CONFIG_BINFMT_ELF controls
64-bit ELF support which one might want to disable and only use
CONFIG_BINFMT_ELF32 (or other config option which controls 32-bit ELF
support).

	Jakub

  reply	other threads:[~2003-11-17 13:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-15 23:26 [2.6 patch] disallow modular BINFMT_ELF Adrian Bunk
2003-11-15 23:48 ` Jeff Garzik
2003-11-15 23:53   ` Martin Hicks
2003-11-17  1:09   ` Eric W. Biederman
2003-11-17 13:08     ` Jakub Jelinek [this message]
2003-11-17  9:25   ` Christoph Hellwig
2003-11-17  9:26   ` Christoph Hellwig

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=20031117130806.GC6288@devserv.devel.redhat.com \
    --to=jakub@redhat.com \
    --cc=akpm@osdl.org \
    --cc=bunk@fs.tum.de \
    --cc=ebiederm@xmission.com \
    --cc=jgarzik@pobox.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox