From: Bill Davidsen <davidsen@tmr.com>
To: Alex Davis <alex14641@yahoo.com>,
Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: most linux friendly motherboard chipset
Date: Sat, 28 Oct 2006 19:05:45 -0400 [thread overview]
Message-ID: <4543E249.8070203@tmr.com> (raw)
In-Reply-To: <20061027233223.15380.qmail@web50210.mail.yahoo.com>
Alex Davis wrote:
> I'm preparing to build a brand new 64-bit machine, I am currently leaning toward AMD 64x2.
> I've read that NVidia, along with (silent) data corruption issues, can be a bit of a pain
> to get working under Linux. Anyone have any experience with ULi, ATI, or SiS?
>
> Note: I'm not entirely ruling out Intel.
I have had good luck with ASUS boards, the Intel chipset, and either the
provided graphics or ATI (I don't like the binary nVidia drivers). I am
just ordering one this weekend, and I'm going with the cheap PentiumD
930 CPU because the quad core units will be out in the spring, and I can
go with that without tying up money in a fast CPU now.
The Core2Duo is faster than AMD (today), has the hardware VM support,
has 64 bit. And most of my clients are running Intel, which is some
consideration regarding support expertise.
--
Bill Davidsen <davidsen@tmr.com>
Obscure bug of 2004: BASH BUFFER OVERFLOW - if bash is being run by a
normal user and is setuid root, with the "vi" line edit mode selected,
and the character set is "big5," an off-by-one errors occurs during
wildcard (glob) expansion.
prev parent reply other threads:[~2006-10-28 23:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-27 23:32 most linux friendly motherboard chipset Alex Davis
2006-10-28 11:49 ` Christoph Hellwig
2006-10-28 23:05 ` Bill Davidsen [this message]
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=4543E249.8070203@tmr.com \
--to=davidsen@tmr.com \
--cc=alex14641@yahoo.com \
--cc=linux-kernel@vger.kernel.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