From: Marcus Meissner <meissner@suse.de>
To: Andi Kleen <ak@suse.de>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
Thomas Glanzmann <sithglan@stud.uni-erlangen.de>,
linux-kernel@vger.kernel.org
Subject: Re: AMD64: 64 bit kernel 32 bit userland - some pending questions
Date: Tue, 6 Jun 2006 13:56:39 +0200 [thread overview]
Message-ID: <20060606115639.GC17753@suse.de> (raw)
In-Reply-To: <200606061355.04334.ak@suse.de>
On Tue, Jun 06, 2006 at 01:55:04PM +0200, Andi Kleen wrote:
> On Tuesday 06 June 2006 13:51, Rafael J. Wysocki wrote:
> > On Tuesday 06 June 2006 12:42, Andi Kleen wrote:
> > > Thomas Glanzmann <sithglan@stud.uni-erlangen.de> writes:
> > >
> > > > Hello everyone,
> > > > I would like to use an AMD64 Opteron System with a 64 bit Linux Kernel,
> > > > but a 32 bit userland (Debian Sarge). I have a few questions about this:
> > >
> > > The main caveat is that iptables and ipsec need 64bit executables
> > > to be set up. The rest should work.
> >
> > Recently I've had a problem running wine with a 16-bit windows application
> > on a 64-bit kernel. I guess it's a wine's problem, then?
>
> At some point it worked - i ran 16bit solitaire and some other programs,
> but it's not regularly tested. When it works on a 32bit kernel with
> the same wine version it should work on the 64bit kernel too. If not
> it's likely a kernel bug.
It should work fine.
If not, what is the actual bug/error message? :)
Ciao, Marcus
next prev parent reply other threads:[~2006-06-06 11:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-06 9:34 AMD64: 64 bit kernel 32 bit userland - some pending questions Thomas Glanzmann
2006-06-06 10:42 ` Andi Kleen
2006-06-06 10:49 ` Thomas Glanzmann
2006-06-06 11:51 ` Rafael J. Wysocki
2006-06-06 11:55 ` Andi Kleen
2006-06-06 11:56 ` Marcus Meissner [this message]
2006-06-06 12:11 ` Rafael J. Wysocki
-- strict thread matches above, loose matches on Subject: below --
2006-06-07 3:11 Albert Cahalan
2006-06-07 4:08 ` H. Peter Anvin
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=20060606115639.GC17753@suse.de \
--to=meissner@suse.de \
--cc=ak@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rjw@sisk.pl \
--cc=sithglan@stud.uni-erlangen.de \
/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