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 <[EMAIL PROTECTED]> wrote:
>
> >
> > On Feb 1 2008 12:53, Alejandro Riveira Fernández wrote:
> > >>
> > >> # uname -m
> > >> I won't tell you.
> > >> # linux32 uname -m
> > >> i686
> >
On Sat, 9 Feb 2008 21:13:43 +0100 (CET)
Jan Engelhardt <[EMAIL PROTECTED]> 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
> >$
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-b
On Fri 2008-02-01 11:47:29, Rik Bobbaers wrote:
> hi there,
>
> since i'm not on the list... how about:
>
> tail /proc/1/smaps and check the address size...
> on 32 bit: e000-f000 r-xp 00:00 0 [vdso]
>
> on 64 bit: ff60-ff601000 r-xp 00:00 0
El Fri, 1 Feb 2008 01:59:03 +0100 (CET)
Jan Engelhardt <[EMAIL PROTECTED]> escribió:
>
> # 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
>
> Now what? :-)
>
> Well, the answer is simple, a 64-bit kern
hi there,
since i'm not on the list... how about:
tail /proc/1/smaps and check the address size...
on 32 bit: e000-f000 r-xp 00:00 0 [vdso]
on 64 bit: ff60-ff601000 r-xp 00:00 0
[vdso]
there you can clearly see that your address space is do
On Thu, 31 Jan 2008, H. Peter Anvin wrote:
> > Quiz: on a booted system, how do you tell 32bit from 64bit kernel?
> uname -m
I think that the real point here is that there is no general way how to
determine whether the kernel is 32bit or 64bit from full dmesg output,
which could sometimes make
Pavel Machek wrote:
Hi!
Quiz: on a booted system, how do you tell 32bit from 64bit kernel?
A1: zcat /proc/config.gz | grep CONFIG_64
...but config.gz is optional
A2: cat /proc/meminfo | grep High
...but i386 kernel could have highmem disabled
What is _your_ answer? ;-)>
don't strip Ccs, thanks. (and try not to tofu either.)
On Jan 31 2008 17:01, Justin Banks wrote:
>
>uname -a will tell you, though.
No. uname is generally not a reliable source to tell you the bitness (or
more precisely, the arch). It may even happen that you cannot find out
at all if access p
On Thu 2008-01-31 16:46:57, Ray Lee wrote:
> On Jan 31, 2008 4:42 PM, Pavel Machek <[EMAIL PROTECTED]> 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
On Jan 31 2008 16:46, Ray Lee wrote:
>On Jan 31, 2008 4:42 PM, Pavel Machek <[EMAIL PROTECTED]> 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)?
# uname -m
I won't tell you.
# linux32 uname -m
i686
Now what
On Jan 31, 2008 4:42 PM, Pavel Machek <[EMAIL PROTECTED]> 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)?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [E
Hi!
Quiz: on a booted system, how do you tell 32bit from 64bit kernel?
A1: zcat /proc/config.gz | grep CONFIG_64
...but config.gz is optional
A2: cat /proc/meminfo | grep High
...but i386 kernel could have highmem disabled
What is _your_ answer? ;-)>
13 matches
Mail list logo
