From: Peter Humphrey <peter@humphrey.ukfsn.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Hoping someone can help explain distcc to me
Date: Sun, 21 Aug 2011 17:27:57 +0100 [thread overview]
Message-ID: <201108211727.57834.peter@humphrey.ukfsn.org> (raw)
In-Reply-To: <1522485.Prk91GPbbn@eve>
On Sunday 21 August 2011 14:53:15 Joost Roeleveld wrote:
> That would help as I'm planning on setting this up myself as well for my
> netbook.
Right. I have two Konsoles open on my workstation, which is the compilation host. In one I "su -" and in the
other I "ssh serv" (this is the client Atom box, which among other things runs http-replicator to serve the
portage tree to the LAN). Naming is going to get confusing if I'm not careful, so I'll refer to the ssh session as
"Atom" and the compilation host as "Host". Then my steps are:
Host: # /etc/init.d/atom start (this is the script I showed yesterday)
# linux32 chroot /mnt/atom /bin/bash
# env-update && . /etc/profile
Atom: $ sudo emerge --sync && sudo eix-update
Host: # emerge --sync && emerge -auvD -j 5 --changed-use --keep-going world
Atom: $ sudo emerge -auDkv --jobs=3 --changed-use --with-bdeps y --keep-going world
Host: (various clean-up operations such as depclean, eclean and localepurge)
# exit
# /etc/init.d/atom stop
Atom: (similar cleaning up)
$ exit
That's it as far as I remember.
> Is there a way to automate the steps inside the chroot without having to
> have a script inside the chroot?
I'd be reluctant to try to automate it any more than this. It's about as simple to use as can be and as I want it.
I've set up aliases for most of those long commands to save my wrists, and of course command-line recall is
wonderful. The task that takes longest is portage on the Atom calculating what packages it needs to emerge
from.
I try not to forget to copy any USE-flag changes etc between the Atom and the chroot, but of course I'm no
more than human.
--
Rgds
Peter Linux Counter 5290, 1994-04-23
next prev parent reply other threads:[~2011-08-21 16:30 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-20 22:56 [gentoo-user] Hoping someone can help explain distcc to me Paul Hartman
2011-08-21 0:35 ` Peter Humphrey
2011-08-21 1:08 ` Paul Hartman
2011-08-21 1:58 ` Peter Humphrey
2011-08-21 2:46 ` Dale
2011-08-21 3:04 ` Matthew Finkel
2011-08-21 9:41 ` Peter Humphrey
2011-08-21 13:53 ` Joost Roeleveld
2011-08-21 16:27 ` Peter Humphrey [this message]
2011-08-21 17:42 ` Neil Bothwick
2011-08-24 11:04 ` Dale
2011-08-21 1:34 ` victor romanchuk
2011-08-21 10:38 ` Alex Schuster
2011-08-21 14:39 ` victor romanchuk
2011-08-22 20:41 ` Alex Schuster
2011-08-22 22:36 ` Bill Longman
2011-08-22 22:41 ` Bill Longman
2011-08-22 19:47 ` [gentoo-user] " Paul Hartman
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=201108211727.57834.peter@humphrey.ukfsn.org \
--to=peter@humphrey.ukfsn.org \
--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