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: [gentoo-user] New mobo change
Date: Mon, 14 Oct 2013 22:50:32 -0500	[thread overview]
Message-ID: <525CBB88.3070202@gmail.com> (raw)

Howdy,

I ordered the new mobo as much as I needed to wait.  The mobo is the
same brand but a different chipset and a couple other things are
different.  I have already built a kernel for those changes.  I plan to
put everything on the old mobo on the new mobo.  That includes the CPU. 
I'm pretty sure this will not be needed but want to ask to be sure.  Do
I need to do a emerge -e world or should it "just work" like it is? 
Since the CPU is going to be the exact same CPU, I'm thinking it is not
needed.  I do have march=native set in make.conf. 

Thoughts?  Thanks.

Dale

:-)  :-) 

P. S.  I think this is the most I have ever spent on a mobo.  $120.00
with shipping.

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



             reply	other threads:[~2013-10-15  3:50 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-15  3:50 Dale [this message]
2013-10-15  5:38 ` [gentoo-user] New mobo change Pandu Poluan
2013-10-15  7:49   ` Dale
2013-10-15 15:02     ` Bruce Hill
2013-10-17 21:40 ` [gentoo-user] " Dale
2013-10-17 23:57   ` walt
2013-10-18  0:14     ` Bruce Hill
2013-10-18  3:29       ` Dale
2013-10-18  0:12   ` Bruce Hill
2013-10-18  3:33     ` Dale
2013-10-18 15:52       ` J. Roeleveld
2013-10-18 16:46         ` Pandu Poluan
2013-10-18  2:43   ` Walter Dnes
2013-10-18  3:54     ` Dale
2013-10-19 23:38       ` Volker Armin Hemmann
2013-10-20  5:39         ` Dale
2013-10-20  9:20           ` Volker Armin Hemmann
2013-10-20 21:19 ` Dale
2013-10-20 23:09   ` Edward M
2013-10-20 23:52     ` Dale
2013-10-21  1:27       ` William Kenworthy
2013-10-21  3:09         ` Dale
2013-10-21  3:38           ` William Kenworthy
2013-10-21  3:54             ` Dale
2013-10-21  4:27               ` Dale
2013-10-21  5:52                 ` J. Roeleveld
2013-10-21  9:18                   ` Dale
2013-10-21  6:07                 ` Edward M
2013-10-21  9:13                   ` Dale
2013-10-21 19:24                     ` Daniel Frey
2013-10-21 20:47                       ` Dale
2013-10-21 22:10                     ` Edward M
2013-10-21 23:24                       ` Dale
2013-10-21 15:07               ` Frank Steinmetzger
2013-10-21 17:45                 ` Dale
2013-10-21 23:35                   ` Neil Bothwick
2013-10-21 23:57                     ` Dale
2013-10-22  7:50                       ` Neil Bothwick
2013-10-22  9:04                         ` Dale
2013-10-22  9:20                           ` Neil Bothwick
2013-10-22 10:52                             ` Dale
2013-10-22 10:55                               ` Neil Bothwick
2013-10-22 11:09                                 ` Dale
2013-10-22 14:14                           ` Bruce Hill
2013-10-22 19:31                             ` Dale
2013-10-22 21:14                           ` Edward M
2013-10-22 21:34                             ` 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=525CBB88.3070202@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