From: Matthias Schniedermeyer <ms@citd.de>
To: "Shaun R." <mailinglists@unix-scripts.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 64bit kernel, 32bit OS?
Date: Thu, 10 Jul 2008 09:20:37 +0200 [thread overview]
Message-ID: <20080710072037.GA10883@citd.de> (raw)
In-Reply-To: <g53keq$vq1$1@ger.gmane.org>
On 09.07.2008 17:16, Shaun R. wrote:
> If i where to run a 32bit OS on a 64bit kernel would there be any
> problems with that? I'm not trying to convert the OS to 64bit, just
> would rather not have to build multiple kernels if i dont have too. I'm
> talking x86_32 and x86_64 btw too.
I guess you mean 32bit userspace with a 64bit kernel.
And that's no problem as long as "CONFIG_IA32_EMULATION" is set
The option is in the menu: Executable file formats / Emulations
and is called: IA32 Emulation
Bis denn
--
Real Programmers consider "what you see is what you get" to be just as
bad a concept in Text Editors as it is in women. No, the Real Programmer
wants a "you asked for it, you got it" text editor -- complicated,
cryptic, powerful, unforgiving, dangerous.
next prev parent reply other threads:[~2008-07-10 7:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-10 0:16 64bit kernel, 32bit OS? Shaun R.
2008-07-10 7:20 ` Matthias Schniedermeyer [this message]
2008-07-10 8:18 ` Jiri Slaby
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=20080710072037.GA10883@citd.de \
--to=ms@citd.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mailinglists@unix-scripts.com \
/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