public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Dale <rdalek1967@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user]  Network failed and weird error message
Date: Mon, 14 Oct 2013 10:18:38 -0500	[thread overview]
Message-ID: <525C0B4E.8020708@gmail.com> (raw)
In-Reply-To: <201310140823.30110.michaelkintzios@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1185 bytes --]

Mick wrote:
> On Sunday 13 Oct 2013 22:49:41 Dale wrote:
>> I don't overclock so I'm not worried about that.  I did it once with a
>> old Abit mobo with a AMD 2500+ CPU but it just didn't make much
difference.
>
> O/C = higher costs.  You need higher frequency memory, bigger CPU/case
coolers
> and potentially a bigger PSU.  If your budget is constrained then buy
> memory/cooler/PSU that will run with default settings.  The 10%
performance
> improvement that a modern CPU may give you when O/C is not really
worth the
> hassle.


I got plenty of all that for sure.  My P/S is much to large.  The CPU
cooler is plain huge for the CPU I got.  I don't know what the memory
could do but I just run it at stock speeds.

When I build a rig, I try to buiild it like a tank.  The military type
tank. I try to build to last at least 7 or 8 years maybe 9.  I'm sort of
disappointed if this mobo is going out already.  It's way to early for
my liking.  I think it is only like 3 years old.  My old Abit was about
8 years old and it was working fine, just slowly.  ;-)

Dale

:-)  :-)

-- 
I am only responsible for what I said ... Not for what you understood or
how you interpreted my words!


[-- Attachment #2: Type: text/html, Size: 1710 bytes --]

  reply	other threads:[~2013-10-14 15:18 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-04 16:09 [gentoo-user] Network failed and weird error message Dale
2013-10-04 19:35 ` Alan McKinnon
2013-10-04 20:19   ` Dale
2013-10-05  8:54     ` Alan McKinnon
2013-10-05 10:06       ` Dale
2013-10-05 13:41         ` Bruce Hill
2013-10-06 18:36       ` Dale
2013-10-06 18:55         ` Alan McKinnon
2013-10-06 19:24           ` Dale
2013-10-06 19:52             ` Dale
2013-10-06 19:59             ` Neil Bothwick
2013-10-06 20:31               ` Dale
2013-10-06 20:55                 ` Frank Steinmetzger
2013-10-07  0:11                   ` Dale
2013-10-07  8:08                     ` Neil Bothwick
2013-10-06 21:07             ` Alan McKinnon
2013-10-06 22:39               ` Neil Bothwick
2013-10-07  0:36               ` Dale
2013-10-06 21:42         ` Bruce Hill
2013-10-07  0:28           ` Dale
2013-10-07  8:06             ` Neil Bothwick
2013-10-07 14:17               ` Dale
2013-10-04 21:52   ` Walter Dnes
2013-10-05  9:04     ` Alan McKinnon
2013-10-05 10:13       ` Dale
2013-10-05 13:37         ` Alan McKinnon
2013-10-06 18:38           ` Dale
2013-10-13 12:26             ` Dale
2013-10-13 17:31               ` Mick
2013-10-13 21:49                 ` Dale
2013-10-14  7:23                   ` Mick
2013-10-14 15:18                     ` Dale [this message]
2013-10-14 11:03                   ` OT - RAM disks - WAS " Tanstaafl
2013-10-14 12:08                     ` Dale
2013-10-15  5:53                     ` Pandu Poluan
2013-10-07  2:29 ` Dale

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=525C0B4E.8020708@gmail.com \
    --to=rdalek1967@gmail.com \
    --cc=gentoo-user@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