LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Ray Lee <ray-lk@madrabbit.org>
Cc: kernel list <linux-kernel@vger.kernel.org>, jikos@suse.cz
Subject: Re: how to tell i386 from x86-64 kernel
Date: Fri, 1 Feb 2008 02:03:19 +0100	[thread overview]
Message-ID: <20080201010319.GA5112@elf.ucw.cz> (raw)
In-Reply-To: <2c0942db0801311646s40368a89r537a7d576ba57981@mail.gmail.com>

On Thu 2008-01-31 16:46:57, Ray Lee wrote:
> On Jan 31, 2008 4:42 PM, Pavel Machek <pavel@ucw.cz> wrote:
> > Quiz: on a booted system, how do you tell 32bit from 64bit kernel?
> 
> Uhm, is this a trick question? What's wrong with uname(2)?

No, it is a tricky question. You are right, uname -a tells me. Sorry.

Still, it would be nice to print it as a first message of dmesg, so
that it automatically gets included with problem reports... on
easy-to-see place.

								Pavel

Linux version 2.6.24-rc8 (pavel@amd) (gcc version 4.1.3 20071209 (prerelease) (Debian 4.1.2-18)) #65 SMP Thu Jan 31 00:02:37 CET 2008
BIOS-provided physical RAM map:


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

  parent reply	other threads:[~2008-02-01  1:03 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
2008-02-01  1:03   ` Pavel Machek [this message]
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=20080201010319.GA5112@elf.ucw.cz \
    --to=pavel@ucw.cz \
    --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).