public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Dale <dalek1967@bellsouth.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Hardware upgrade and Gentoo
Date: Wed, 18 Jul 2007 14:19:26 -0500	[thread overview]
Message-ID: <469E67BE.2060000@bellsouth.net> (raw)
In-Reply-To: <200707182037.34064.volker.armin.hemmann@tu-clausthal.de>

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

Volker Armin Hemmann wrote:
> On Mittwoch, 18. Juli 2007, Daniel da Veiga wrote:
>   
>> On 7/18/07, Alex Schuster <wonko@wonkology.org> wrote:
>>     
>>> Another method, which I would use, would be to change your CFLAGS to what
>>> you would like for the new processor, but use mtune= instead of march=.
>>> This will also optimize for the cpu, but the code will run on any x86
>>> CPU. emerge world --emptytree to re-compile everything, then switch your
>>> hardware. This will give you flexibility, at the cost of lesser
>>> optimization. Depends on how you use your system, most applications will
>>> not show a noticeable speed ddifference I guess.
>>> You could also change to march= later, when the system ist up, and
>>> re-compile everything again to get full optimization.
>>>       
>> Oh, that's good to know, I guess that's the best option, since after
>> the system is up and running I can do whatever optimizations it needs,
>> as long as I'm able to boot and work with it in the new hardware.
>>
>> Tonight I'll start the (long and boring) process of recompiling the
>> whole stuff with "-mtune" instead of "-march".
>>
>> Thanks to all that replied so far... Maybe more suggestions comming?!
>>     
>
> instead of two emerge --emptytree it would be faster to just nuke the 
> installation....
>   

I agree.  Just back up /etc, make a copy of your world file and any
other config files you may need and start from scratch.  At least then
you KNOW for sure where you started from and that something didn't get
missed somewhere.

Oh, don't forget /home either.

Dale

:-)  :-)  :-)

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

  reply	other threads:[~2007-07-18 19:32 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-18 16:51 [gentoo-user] Hardware upgrade and Gentoo Daniel da Veiga
2007-07-18 17:08 ` Joshua Doll
2007-07-18 17:49 ` Alex Schuster
2007-07-18 18:02   ` Daniel da Veiga
2007-07-18 18:37     ` Volker Armin Hemmann
2007-07-18 19:19       ` Dale [this message]
2007-07-18 19:38         ` Daniel da Veiga
2007-07-18 20:20           ` Mick
2007-07-18 20:35       ` Neil Bothwick
2007-07-18 20:13   ` Mike Williams
2007-07-18 20:39   ` Neil Bothwick
2007-07-18 21:36     ` Daniel da Veiga

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=469E67BE.2060000@bellsouth.net \
    --to=dalek1967@bellsouth.net \
    --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