[cfgeeks] 64 bit Linux

[Kevin Korb]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

If -m says x86_64 then it is 64 bit.  You aren't going to get a 32bit
system to say that.

The only way a 64 bit system would say something like i686 or i386 is if
uname is running in 32 bit compatibility mode and I can't imagine that
happening without the entire OS running that way too.

Dual core is exactly the same way.

- -- 
~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~
 	Kevin Korb			Phone:    (407) 252-6853
 	Systems Administrator		Internet:
 	FutureQuest, Inc.		Kevin at FutureQuest.net  (work)
 	Orlando, Florida		kmk at sanitarium.net (personal)
 	Web page:			http://www.sanitarium.net/
 	PGP public key available on web site.
~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~

On Thu, 28 Jun 2007, Kevin P. Inscoe wrote:

> Date: Thu, 28 Jun 2007 16:23:19 -0400
> From: Kevin P. Inscoe <kevin at inscoe.org>
> To: Central Florida Geeks <cfgeeks at mail.cfgeeks.org>
> Subject: Re: [cfgeeks] 64 bit Linux
> 
> On Thu Jun 28, 2007 at 04:17:53PM -0400, Kevin Korb wrote:
>>  The stuff you quoted plainly says that x86_64 is 64 bit while i?86 is
>>  32 bit (or a 64bit CPU running in 32 bit mode).  I supose you could
>>  force it to fail by compiling uname as a 32 bit binary and linking it
>>  with the 32 bit compatibility libraries on a 64 bit system+OS but
>>  otherwise it should work.
>
> Ok I guess I am not explaining this well enough.
>
> Does uname -m being X86_64 *always* mean 64 bit? Or another way to put is it
> *always* a valid to assert *only* 64 bit systems will *always* print X86_64
> even Dual Core's?
>
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7-ecc0.1.6 (GNU/Linux)

iD8DBQFGhBn+VKC1jlbQAQcRAvxEAKCnjFBGH10GC2uOzLwmtrvPJv5AAQCfff+Q
gQfMB3ey35s2El6LOyGWKD8=
=l3U5
-----END PGP SIGNATURE-----