| 1 |
On Sun, 3 Apr 2011 14:55:39 +0100, Peter Humphrey wrote: |
| 2 |
|
| 3 |
> > Yes. the script that I use to start up and enter the chroot for each |
| 4 |
> > system not only does the usual mounting of /dev/ and /proc in the |
| 5 |
> > chroot, it also rsyncs /etc/portage and /var/lib/portage/world* with |
| 6 |
> > the real target. Make.conf has to be maintained manually, because |
| 7 |
> > there are settings in the two that need to be different, although I |
| 8 |
> > suppose I could split out the common settings, USE, CHOST etc, into a |
| 9 |
> > separate file and source that. |
| 10 |
> |
| 11 |
> In my case the chroot is identical in structure to the real target, |
| 12 |
> apart from the number of cores, so I can copy make.conf into the chroot |
| 13 |
> without risk. |
| 14 |
|
| 15 |
You probably don't want EMERGE_DEFAULT_OPTS="--usepkg" in the chroot's |
| 16 |
make.conf. |
| 17 |
|
| 18 |
I also turn off the ELOG* functions in the chroot, as the emails it sends |
| 19 |
contain the wrong hostname, leading to much confusion. |
| 20 |
|
| 21 |
|
| 22 |
-- |
| 23 |
Neil Bothwick |
| 24 |
|
| 25 |
/ For security reasons, all text in this mail |
| 26 |
is double-rot13 encrypted. / |
Archives