Hello all,
I have purchased a new MB and processor. I will be transitioning from a
regular Athlon to an Athlon64. Since I am not upgrading my hard drives, I
plan to upgrade the OS as follows:
1. Boot from the latest Gentoo live CD.
2. chroot
3. emerge --update --deep --newuse world
4. rebuild the
--- "Budd, Tracy" <[EMAIL PROTECTED]> wrote:
> Hello all,
>
> I have purchased a new MB and processor. I will be
> transitioning from a
> regular Athlon to an Athlon64. Since I am not
> upgrading my hard drives, I
> plan to upgrade the OS as follows:
>
> 1. Boot from the latest Gentoo live CD.
>
If you want a 64 bit userland then you should start
over with an AMD64 stage.
So you mean that whenever the hardware platform changes are
so substantial (as in this case), one should install the system
from scratch?
Please, bear with me, I'm a new Gentoo user, even though I've
been using Linux f
Correct me if I'm wrong, but if you boot from the livecd, chroot and
emerge the system using the new config (AMD64), recompile your kernel
to the new processor and configure the boot loader, you're able to get
your new system to work with the old configuration and the new
architeture.
Of course, t
--- Antonino Sabetta <[EMAIL PROTECTED]>
wrote:
> > If you want a 64 bit userland then you should
> start
> > over with an AMD64 stage.
>
> So you mean that whenever the hardware platform
> changes are
> so substantial (as in this case), one should install
> the system
> from scratch?
> Please, b
By "new config (AMD64)" do you mean change
CHOST=i686-pc-linux-gnu to CHOST=x86_64-pc-linux-gnu ?
Sounds like a bad idea.
--- Daniel da Veiga <[EMAIL PROTECTED]> wrote:
> Correct me if I'm wrong, but if you boot from the
> livecd, chroot and
> emerge the system using the new config (AMD64),
> re
Athlon64 processors can execute 32 bits instructions. But you can't
use 32 bits executables with 64 bits libraries (or contrary), and this
will append while recompiling your system (when a library used by
emerge or gcc will be recompiled), so it should fail at any time. I
think it can be done, resp
a little easier.
Thanks for the input.
-tracy
-Original Message-
From: Zac Medico [mailto:[EMAIL PROTECTED]
Sent: Wednesday, May 25, 2005 3:32 PM
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Hardware upgrade procedure question
By "new config (AMD64)" do you mea
On Wednesday 25 May 2005 21.31, Zac Medico wrote:
> By "new config (AMD64)" do you mean change
> CHOST=i686-pc-linux-gnu to CHOST=x86_64-pc-linux-gnu ?
> Sounds like a bad idea.
Yes, sounds indeed like a bad idea. Just back up your /home, /etc and other
config files etc. Format old system and ma
--- "Budd, Tracy" <[EMAIL PROTECTED]> wrote:
> Hmm.
>
> While admittedly extreme, shouldn't setting the new
> architecture work, if
> you recompile the entire system? Is this one of
> those
> should-work-in-theory-but-
> don't-try-this-at-home kind of things? I know there
> are some packages, li
--- Emmanuel Durin <[EMAIL PROTECTED]> wrote:
> Athlon64 processors can execute 32 bits
> instructions. But you can't
> use 32 bits executables with 64 bits libraries (or
> contrary), and this
> will append while recompiling your system (when a
> library used by
> emerge or gcc will be recompiled
: [gentoo-user] Hardware upgrade procedure question
--- Emmanuel Durin <[EMAIL PROTECTED]> wrote:
> Athlon64 processors can execute 32 bits instructions. But you can't
> use 32 bits executables with 64 bits libraries (or contrary), and this
> will append while recompiling
On Wed, 25 May 2005 10:27:14 -0400
"Budd, Tracy" <[EMAIL PROTECTED]> wrote:
>
> Did I miss anything?
>
Here is what I did when I did the upgrade -
- Boot LiveCD
- mount the partitions
- cd /mnt/gentoo
- move etc/fstab, etc/conf.d/net, etc/passwd, etc/group, and o
--- Bob Sanders <[EMAIL PROTECTED]> wrote:
> - Then delete directories - bin, sbin, lib, sys,
> etc, opt.
http://www.gentoo.org/proj/en/base/amd64/technotes.xml?part=2&chap=4#doc_chap3
You could recycle the old directories as a 32-bit
chroot environment. That could come in handy if you
w
14 matches
Mail list logo
