1 |
On Thu, Jul 31, 2008 at 1:12 PM, Nicolas Sebrecht |
2 |
<nicolas.s-dev@×××××××.net> wrote: |
3 |
> |
4 |
> Sebastian Günther a écrit: |
5 |
> |
6 |
>> If you want such functionality, use Debian or Ubuntu. |
7 |
> |
8 |
> Or just use the good C*FLAGS and kernel options. |
9 |
> |
10 |
|
11 |
Nicolas is right, you can (at your own risk, of course) do a migration |
12 |
like this, so "DON'T" is not really the only option, and changing |
13 |
distros is NOT an option in most cases. Gentoo is perfectly capable of |
14 |
that. |
15 |
|
16 |
Change flags in make.conf for generic compatible ones, compile a new |
17 |
kernel (I used genkernel for the migration, and compiled a specific |
18 |
kernel for the new machine later), emerge -e world and transfer the |
19 |
system (I used rsync, and had to deal with some network issues), |
20 |
everything worked (after some fine tunning for the new hardware) for |
21 |
me. Sometimes the effort is worth, it was my case, YMMV. It takes a |
22 |
little while (for me, the migration itself took a Sunday afternoon, |
23 |
like 6 hours), but you can still use your system while emerge does its |
24 |
work, and while the new kernel compiles. Its less time than a normal |
25 |
install from the ground up (with the whole configuration process, X, |
26 |
Window Manager, etc). After the migration, change flags again, and let |
27 |
emerge do its magic, while you can keep working. |
28 |
|
29 |
PS: I kept my old system as a backup for a few weeks. |
30 |
|
31 |
PS2: I had an old Athlon XP 1.2GHz and migrated the whole system to a |
32 |
Core Duo 2.8GHz, as you may imagine, both machines were COMPLETELY |
33 |
different, but still I kept all my preferences, packages, files, all |
34 |
of it. An year before the migration, the Athlon XP was running a |
35 |
CHOST=i386 and I changed it to i686 with success. Gentoo is sometimes |
36 |
just magical. |
37 |
|
38 |
-- |
39 |
Daniel da Veiga |