| 1 |
On Thu, 26 Jul 2012 18:09:26 +0100, Peter Humphrey wrote: |
| 2 |
|
| 3 |
> Just to expand that, I followed Neil's advice when setting my boxes up. |
| 4 |
> I have an atom box as LAN server and an i5 workstation. I have a script |
| 5 |
> which I run on the workstation to mount all the necessary directories |
| 6 |
> on the chroot, including nfs-mounting the atom's /usr/portage/packages |
| 7 |
> dir. Then I chroot into the 32-bit system as described in the |
| 8 |
> installation handbook, env-update && . /etc/profile and away I go. |
| 9 |
> |
| 10 |
> Then, on the atom, I emerge -kuaDvN world to install from the packages |
| 11 |
> I've just built. |
| 12 |
> |
| 13 |
> The only thing to be careful of is keeping the atom box and the chroot |
| 14 |
> identical. /var/lib/portage/world and /etc/portage/ must be identical. |
| 15 |
|
| 16 |
I use a script that rsyncs these, sets up the chroot mounts and then |
| 17 |
chroots. The only part it doesn't take care of is keeping the relevant |
| 18 |
parts of make.conf in sync (because some parts of the file must be |
| 19 |
different). |
| 20 |
|
| 21 |
> Also /usr/src/linux/.config and /boot/ . |
| 22 |
|
| 23 |
/boot doesn't need to be synced, /usr/src/linux only needs to be synced if |
| 24 |
you are building kernel modules, but I build those natively (I also |
| 25 |
compile kernels natively). |
| 26 |
|
| 27 |
I really should get around to documenting this on the wiki sometimw. |
| 28 |
|
| 29 |
|
| 30 |
-- |
| 31 |
Neil Bothwick |
| 32 |
|
| 33 |
Distrust any enterprise that requires new clothes. - Henry David Thoreau |
| 34 |
(1817-1862) |
Archives