From: Dominik Westner <lists@logicunited.com>
To: Michael Monsen <gentoo@themonsens.org>
Cc: <gentoo-user@gentoo.org>, <gentoo-dev@gentoo.org>
Subject: Re: [gentoo-dev] Re: [gentoo-user] Upgrade, course of action.
Date: Fri, 23 Aug 2002 20:20:47 +0200 [thread overview]
Message-ID: <0B841092-B6C5-11D6-B181-000393823B30@logicunited.com> (raw)
In-Reply-To: <iqocmu0ojfqunsjsrq48nfj5bsu3jhrn07@4ax.com>
It should work out of the box for the Athlon. You might need to do the
usual stuff when you get new hardware, compile new kernel ... ;-)
If you want to have a Athlon optimizied system (should be worth when
using gcc-3.x ... at least people tell me), you can have a look at:
http://gentoo.zhware.net/fuq.html
which mentions a couple of methods how to recompile your whole system.
Btw. I use the following for my Athlon XP 1800:
CHOST="i686-pc-linux-gnu"
CFLAGS="-march=athlon-xp -mmmx -msse -m3dnow -mfpmath=sse
-fomit-frame-pointer -O3 -Wall -pipe"
CXXFLAGS="-march=athlon-xp -mmmx -msse -m3dnow -mfpmath=sse
-fomit-frame-pointer -O3 -Wall -pipe"
with gcc-3.2.
Greetings
Dominik
On Freitag, August 23, 2002, at 06:31 PM, Michael Monsen wrote:
> While visiting the prison at D'Ni on Fri, 23 Aug 2002 04:22:49 -0500
> (CDT), "Gregg" <gregg@sc.am> was overheard saying to the guard:
>
>> I run a server, it hosts 127 websites. Has many users for various
>> other
>> things. It is currently on a celeron 600 overclocked to 675, with 256
>> megs of ram. The motherboard supports celeron and pII. It is
>> beginning
>> to choke. It is time to upgrade the motherboard, cpu and ram. Since
>> this
>> is an old setup (celeron and old mobo) what do I need to do when
>> replacing
>> them. Everything is obviously compiled for it. I have not changed
>> any of
>> my flags in the configuration files. So it is all just i686 in the
>> c*flags. I want to go up to an athlon 2200. So, what do I need to
>> consider before switching them out, what do I need to do afterword .
>> This
>> is a 1.3b_test system with all the latest updates (except gcc 3.2, I am
>> still on 3.1.1)
>
> I'm new to the list and Gentoo, but I would think that your new Athlon
> would run the i686 binaries without trouble at all. If I were in your
> position I'd do the hardware upgrade and then after the upgrade, change
> the flags to Athlon optimizations. As you upgrade packages your system
> will slowly convert over to Athlon-specific binaries.
>
> Somebody please correct me if I'm wrong!
> _______________________________________________
> gentoo-dev mailing list
> gentoo-dev@gentoo.org
> http://lists.gentoo.org/mailman/listinfo/gentoo-dev
next prev parent reply other threads:[~2002-08-26 12:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-23 9:22 [gentoo-dev] Upgrade, course of action Gregg
2002-08-23 16:30 ` [gentoo-dev] Re: [gentoo-user] " Michael Monsen
2002-08-23 16:31 ` Michael Monsen
2002-08-23 18:20 ` Dominik Westner [this message]
2002-08-23 19:30 ` [gentoo-dev] " Alexander Gretencord
2002-08-23 20:45 ` Gregg
2002-08-24 1:25 ` Charles Lacour
2002-08-24 5:24 ` Gregg
2002-08-24 6:41 ` [gentoo-dev] " Paul
2002-08-24 8:03 ` [gentoo-dev] " Thomas M. Beaudry
2002-08-24 11:59 ` Alexander Gretencord
2002-08-25 0:28 ` Gregg
2002-08-25 4:58 ` Thomas M. Beaudry
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=0B841092-B6C5-11D6-B181-000393823B30@logicunited.com \
--to=lists@logicunited.com \
--cc=gentoo-dev@gentoo.org \
--cc=gentoo-user@gentoo.org \
--cc=gentoo@themonsens.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