public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Daniel da Veiga" <danieldaveiga@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] move instalation from one system to another one.
Date: Thu, 31 Jul 2008 14:07:19 -0300	[thread overview]
Message-ID: <342e1090807311007n43d09f42vc5d7c6fe885a858a@mail.gmail.com> (raw)
In-Reply-To: <20080731181202.87e69a0b.nicolas.s-dev@laposte.net>

On Thu, Jul 31, 2008 at 1:12 PM, Nicolas Sebrecht
<nicolas.s-dev@laposte.net> wrote:
>
> Sebastian Günther a écrit:
>
>> If you want such functionality, use Debian or Ubuntu.
>
> Or just use the good C*FLAGS and kernel options.
>

Nicolas is right, you can (at your own risk, of course) do a migration
like this, so "DON'T" is not really the only option, and changing
distros is NOT an option in most cases. Gentoo is perfectly capable of
that.

Change flags in make.conf for generic compatible ones, compile a new
kernel (I used genkernel for the migration, and compiled a specific
kernel for the new machine later), emerge -e world and transfer the
system (I used rsync, and had to deal with some network issues),
everything worked (after some fine tunning for the new hardware) for
me. Sometimes the effort is worth, it was my case, YMMV. It takes a
little while (for me, the migration itself took a Sunday afternoon,
like 6 hours), but you can still use your system while emerge does its
work, and while the new kernel compiles. Its less time than a normal
install from the ground up (with the whole configuration process, X,
Window Manager, etc). After the migration, change flags again, and let
emerge do its magic, while you can keep working.

PS: I kept my old system as a backup for a few weeks.

PS2: I had an old Athlon XP 1.2GHz and migrated the whole system to a
Core Duo 2.8GHz, as you may imagine, both machines were COMPLETELY
different, but still I kept all my preferences, packages, files, all
of it. An year before the migration, the Athlon XP was running a
CHOST=i386 and I changed it to i686 with success. Gentoo is sometimes
just magical.

-- 
Daniel da Veiga



  reply	other threads:[~2008-07-31 17:07 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-30  8:55 [gentoo-user] move instalation from one system to another one Platoali
2008-07-30 10:34 ` Sebastian Günther
2008-07-31  0:13   ` Adam Carter
2008-07-31 16:12   ` Nicolas Sebrecht
2008-07-31 17:07     ` Daniel da Veiga [this message]
2008-07-31 17:15       ` [gentoo-user] " Nikos Chantziaras
2008-07-31 18:40         ` Daniel da Veiga
2008-07-31 18:50         ` Nicolas Sebrecht
2008-07-31 19:05           ` Stroller
2008-07-31 20:25             ` Daniel da Veiga
2008-07-31 22:09               ` Volker Armin Hemmann
2008-07-31 23:22                 ` Daniel da Veiga
2008-07-31 23:30                 ` ABCD
2008-08-01  9:53                   ` Volker Armin Hemmann
2008-08-04  6:30                     ` Platoali

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=342e1090807311007n43d09f42vc5d7c6fe885a858a@mail.gmail.com \
    --to=danieldaveiga@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