From: Lie Ryan <lie.1296@gmail.com>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] Re: intel processors x gentoo
Date: Fri, 29 Oct 2010 07:38:03 +1100 [thread overview]
Message-ID: <AANLkTimcAE2AtGYHfzrEcKZmggiZ8RhkBiAbSUOX80x=@mail.gmail.com> (raw)
In-Reply-To: <pan.2010.10.28.03.51.20@cox.net>
[-- Attachment #1: Type: text/plain, Size: 2122 bytes --]
(Sorry for the top post, this brain dead email software in my mobile phone
do not even allow me to remove the quoted message)
I was under the assunpthat I7 was a 32bit cpu, and I was unaw
On 28 Oct 2010 15:03, "Duncan" <1i5t5.duncan@cox.net> wrote:
Lie Ryan posted on Thu, 28 Oct 2010 06:20:45 +1100 as excerpted:
> On 09/29/10 03:03, Zhu Sha Zang wrote:
>> I have some machines running gentoo and every machine...
Why not?
That statement implies that you don't either don't understand what
keywords are all about, or you don't understand what that specific keyword
means.
If the statement is taken in the one context, if he's running the 64-bit
x86 instruction set, on Gentoo, the keyword for it is amd64, regardless of
who (AMD, Intel, Via...) makes the chip it's running on. For one thing,
Gentoo's support for that instruction set originated before anyone else
had picked it up, and AMD called it AMD64.[1]
That's why this list is the gentoo/amd64 list as well, because that's what
Gentoo calls the arch/instruction-set, regardless of who creates the
hardware.
Unless of course you're arguing that he likely wants ~amd64 instead,
which /is/ something that could be argued (I run ~amd64 on my 64-bit
machine and ~x86 on my 32-bit-only Atom netbook...). But that's going to
require a /lot/ more than a simple "I doubt you would want that" in
reference to the stable version, to back up /that/ argument, to the point
I can't see anyone logically making the claim you made in that context,
either.
----
[1] For another, AMD originated it, and that's what they call it, so it
can be argued that is it's "proper" name, even if generically, x86_64 also
often used (as it is for the kernel, but due to the _ it's harder to
type), or x64 (which is confusing for a few reasons, not the least of
which is that 64 is less than 86, but it's the newer and arguably "better"
instruction set, but I do think MS uses it), or by Intel as em64t or some
such.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
[-- Attachment #2: Type: text/html, Size: 2630 bytes --]
next prev parent reply other threads:[~2010-10-28 21:04 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-28 17:03 [gentoo-amd64] intel processors x gentoo Zhu Sha Zang
2010-09-28 18:30 ` [gentoo-amd64] " Nikos Chantziaras
2010-09-28 20:18 ` Duncan
2010-09-28 18:31 ` [gentoo-amd64] " Agostino Sarubbo
2010-09-28 18:50 ` James Ausmus
2010-09-28 18:52 ` Frank Peters
2010-09-28 18:55 ` Fernando Boaglio
2010-09-28 19:37 ` Zhu Sha Zang
2010-09-28 22:15 ` malc
2010-09-29 14:24 ` Zhu Sha Zang
2010-10-27 19:20 ` [gentoo-amd64] " Lie Ryan
2010-10-28 3:51 ` Duncan
2010-10-28 20:38 ` Lie Ryan [this message]
[not found] ` <AANLkTi=E4Jbi_Ud985dXddHoE6peGoyEy1ckBAxyLKay@mail.gmail.com>
2010-10-28 20:49 ` Lie Ryan
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='AANLkTimcAE2AtGYHfzrEcKZmggiZ8RhkBiAbSUOX80x=@mail.gmail.com' \
--to=lie.1296@gmail.com \
--cc=gentoo-amd64@lists.gentoo.org \
/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