LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Arjan van de Ven <arjan@infradead.org>
Cc: "Jan Engelhardt" <jengelh@computergmbh.de>,
	"Alejandro Riveira Fernández" <ariveira@gmail.com>,
	"Ray Lee" <ray-lk@madrabbit.org>,
	"kernel list" <linux-kernel@vger.kernel.org>,
	jikos@suse.cz
Subject: Re: how to tell i386 from x86-64 kernel
Date: Sun, 10 Feb 2008 01:27:15 +0000	[thread overview]
Message-ID: <20080210012714.GA4618@ucw.cz> (raw)
In-Reply-To: <20080209143430.193131d8@laptopd505.fenrus.org>

On Sat 2008-02-09 14:34:30, Arjan van de Ven wrote:
> On Sat, 9 Feb 2008 21:13:43 +0100 (CET)
> Jan Engelhardt <jengelh@computergmbh.de> wrote:
> 
> > 
> > On Feb 1 2008 12:53, Alejandro Riveira Fernández wrote:
> > >> 
> > >> # uname -m
> > >> I won't tell you.
> > >> # linux32 uname -m
> > >> i686
> > >
> > > Ubuntu 7.10 64 bit userland 2.6.24
> > >
> > >$ uname -m
> > >x86_64
> > >$ linux32 uname -m
> > >i686
> > 
> > What I am saying is that uname(2) does not reliably tell you whether
> > you have a 64-bit kernel underneath unless you have other sources of 
> > information.
> 
> that's sort of a rabbit-and-the-frog problem. The 32 bit emulator tries to
> look EXACTLY like the 32 bit kernel, and it really should.
> If someone wants a method to detect even that... we would really want
> to know the exact usecase.. because very likely it's the wrong answer
> to some other problem ;-)

dmesg should really really tell you 32 vs. 64 bit, at the first line
where it prints versions... so you easily know what you are dealing
with when someone sends a bugreport.

							Pavel

-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

  reply	other threads:[~2008-02-10  1:27 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-01  0:42 Pavel Machek
2008-02-01  0:46 ` Ray Lee
2008-02-01  0:59   ` Jan Engelhardt
2008-02-01 11:53     ` Alejandro Riveira Fernández
2008-02-09 20:13       ` Jan Engelhardt
2008-02-09 22:34         ` Arjan van de Ven
2008-02-10  1:27           ` Pavel Machek [this message]
2008-02-01  1:03   ` Pavel Machek
2008-02-01  4:51 ` H. Peter Anvin
2008-02-01 10:07   ` Jiri Kosina
     [not found] <960D0E79B4E503448AD14B5E40A5C1C7BB54CE@USX1.corp.bb>
2008-02-01  1:37 ` Jan Engelhardt
2008-02-01 10:47 Rik Bobbaers
2008-02-02 11:06 ` Pavel Machek

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=20080210012714.GA4618@ucw.cz \
    --to=pavel@ucw.cz \
    --cc=ariveira@gmail.com \
    --cc=arjan@infradead.org \
    --cc=jengelh@computergmbh.de \
    --cc=jikos@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ray-lk@madrabbit.org \
    --subject='Re: how to tell i386 from x86-64 kernel' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).