public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@ns.caldera.de>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] Re: PROPOSED: 32/64 bit coexistance
Date: Tue, 18 Sep 2001 16:57:15 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590698805212@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590698805199@msgid-missing>

On Tue, Sep 18, 2001 at 09:33:11AM -0700, David Mosberger wrote:
> I think LSB is correct in suggesting /libXX for the native code model
> and "something" else for emulated code models.  /opt/emu32 is clearly
> a silly name though: it mixes up the data model and the code model
> again.  For the IA-64 Linux project, we're currently using
> /emul/ia32-linux for the IA-32 subsystem.  (If there is strong
> objection and good reasons to reject the "/emul" prefix, I suppose we
> could use /opt/emu/ia32-linux/ instead.)

Don't put it in /opt.  For something like a binray emulator /opt
is just silly.

Currently mips and sparc use /usr/gnemul/<opsys>, Linux-ABI for ix86
uses /emul/<opsys>.  I'd suggest going for one of those, possibly
the latter (:)).

> A related question is whether /emul/ is reserved for "same OS"
> emulation.  E.g., where would a Windows emulator go?  If /emul/ only
> ever contains Linux emulators, then we could change the prefix to
> /emul/ia32/ but, from a user perspective, I think it would be
> preferable if /emul/ were allowed to contain foreign OS emulators as
> well.

It does.  On Linux-ABI I use e.g. /emul/osr5, /emul/uw7 and /emul/svr4.
Id suggest using /emul/<opsys> for emulations of another operating
system for the same architecture, /emul/<arch>-<opsys> for non-native.

Windows should go into /emul/win64 and /emul/ia32-win32.

	Christoph

-- 
Whip me.  Beat me.  Make me maintain AIX.


  parent reply	other threads:[~2001-09-18 16:57 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-18  8:34 [Linux-ia64] Re: PROPOSED: 32/64 bit coexistance Andreas Jaeger
2001-09-18  9:00 ` Theodore Tso
2001-09-18  9:21 ` Luigi Genoni
2001-09-18  9:39 ` Jakub Jelinek
2001-09-18 10:06 ` Jakub Jelinek
2001-09-18 16:33 ` David Mosberger
2001-09-18 16:57 ` Christoph Hellwig [this message]
2001-09-18 17:22 ` David Mosberger
2001-09-18 17:50 ` Andreas Jaeger
2001-09-18 19:33 ` David Mosberger
2001-09-18 20:07 ` Andreas Jaeger
2001-09-18 20:25 ` Christoph Hellwig
2001-09-18 20:47 ` David Mosberger
2001-09-18 20:53 ` David Mosberger
2001-09-18 21:05 ` Joseph V Moss
2001-09-19  6:02 ` Jakub Jelinek
2001-09-19 21:43 ` David Mosberger

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=marc-linux-ia64-105590698805212@msgid-missing \
    --to=hch@ns.caldera.de \
    --cc=linux-ia64@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