From: Joseph V Moss <jmoss@ichips.intel.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] Re: PROPOSED: 32/64 bit coexistance
Date: Tue, 18 Sep 2001 21:05:12 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590698805221@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590698805199@msgid-missing>
> >>>>> On Tue, 18 Sep 2001 18:57:15 +0200, Christoph Hellwig <hch@ns.caldera.de> said:
>
> Christoph> It does. On Linux-ABI I use e.g. /emul/osr5, /emul/uw7
> Christoph> and /emul/svr4. Id suggest using /emul/<opsys> for
> Christoph> emulations of another operating system for the same
> Christoph> architecture, /emul/<arch>-<opsys> for non-native.
>
> Christoph> Windows should go into /emul/win64 and /emul/ia32-win32.
>
> Sounds reasonable. /emul/ia32-linux should be it, then.
I'm not so sure. Should the architecture name be 'ia32'? The linux kernel
and other things have normally referred to it as 'i386' (or any of i[3456]86 in
some cases).
Personally, I'd prefer the 'ia32' name, if for no other reason than to avoid
the problems associated with my parenthetical remark in the last paragraph.
next prev parent reply other threads:[~2001-09-18 21:05 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
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 [this message]
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-105590698805221@msgid-missing \
--to=jmoss@ichips.intel.com \
--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