Gentoo Archives: gentoo-user

From: Grant <emailgrant@×××××.com>
To: Gentoo mailing list <gentoo-user@l.g.o>
Subject: Re: [gentoo-user] Managing multiple systems with identical hardware
Date: Tue, 01 Oct 2013 06:55:08
Message-Id: CAN0CFw05qwFxi280v1An1uJp8tqHTmkzHTo2hWthgUpbTLtAGw@mail.gmail.com
In Reply to: Re: [gentoo-user] Managing multiple systems with identical hardware by Neil Bothwick
1 >> > I'm soaking up a lot of your time (again). I'll return with any real
2 >> > Gentoo questions I run into and to run down the final plan before I
3 >> > execute it. Thanks so much for your help. Not sure what I'd do
4 >> > without you. :)
5 >>
6 >> I'm sure Neil would step in if I'm hit by a bus
7 >> He'd say the same things, and use about 1/4 of the words it takes me ;-)
8 >
9 > So far in this thread, I've managed about 0/4 of the words you've used...
10 > Oh damn!
11 >
12 > But yes, a build host and adding --usepkg=y to EMERGE_DEFAULT_OPTS in
13 > make.conf gives a massive speed increase. Run the build host in an easily
14 > recovered environment, like a VM, and you don't even have to monitor the
15 > world update on it, just run a script in the early hours that does emerge
16 > --sync && emerge -uXX @world and check your mailbox for errors before
17 > running emerge on the "clients". The use clusterssh or dsh to update them
18 > all at once.
19
20 I'm hoping to update everything on my own laptop before I have the
21 laptop clients update. If I install everything on my own laptop that
22 any of the clients have installed, I should be able to avoid any
23 update trouble on the clients. clusterssh or dsh sounds like a good
24 method for updating the clients. Basically, once I update everything
25 on my laptop and it looks good, I want to be able to send the clients
26 a signal to update as well.
27
28 - Grant