1 |
On Tue, Oct 07, 2014 at 05:29:11AM +0200, meino.cramer@×××.de wrote: |
2 |
> Hi, |
3 |
> |
4 |
> There are two SDcards of the same brand and model. |
5 |
> The first one cariies a not so current Gentoo Linux. |
6 |
> The second one is empty. |
7 |
> Now the first one is image-copied to the second one with dd, |
8 |
> which copies the contents of the whole device (not the partitions). |
9 |
> |
10 |
> Then the first one is put into my embedded system, boots up and |
11 |
> the normal eix-syn/emerge/compiel is done to update the system (whch |
12 |
> takes a longer time becaus this is an embedded system). |
13 |
> |
14 |
> Will I get a technical identical working and valid copy of the first sdcard onto |
15 |
> the second sdcard if I rsync the relevant partition of the first onto |
16 |
> the second sdcard. |
17 |
> |
18 |
> Or will I produce crap this way? Is this valid Gentoo-wise? |
19 |
> |
20 |
|
21 |
Moin (again), |
22 |
|
23 |
this will work quite well, at least if you take care (I used this way for |
24 |
moving my systems to new drives or even via network to different boxes (in the |
25 |
latter case CFLAGS and kernel config will become important again, as you can |
26 |
imagine)). |
27 |
Ideally you should run rsync with the option to remove files not found on the |
28 |
source drive (otherwise you'll likely clutter the target with stale files |
29 |
(especially documentation but also older library versions). |
30 |
You will also need to change the configs (at least static network & hostname, |
31 |
possibly more) so that both systems don't clash, at least if you plan to run |
32 |
both on the same network. |
33 |
The "rm" option of rsync is potentially dangerous (e.g. you can delete files |
34 |
from home). |
35 |
If you are careful this is a valid way of doing that. Another option that would |
36 |
move quite a bit work from one machine to the other is just building binpkgs on |
37 |
one host and use the other one as binhost. That way (if you use identical |
38 |
/etc/portage dirs) you can quite savely use portage and nonetheless negate the |
39 |
use of compiling (there will still be the load of dependency resplution, |
40 |
extracting etc). |
41 |
|
42 |
WKR |
43 |
Hinnerk |