From: Neil Bothwick <neil@digimed.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Howzat!
Date: Mon, 18 Apr 2011 22:56:09 +0100 [thread overview]
Message-ID: <20110418225609.0e47a40e@digimed.co.uk> (raw)
In-Reply-To: <4DAC4FF4.4000002@binarywings.net>
[-- Attachment #1: Type: text/plain, Size: 1116 bytes --]
On Mon, 18 Apr 2011 16:51:32 +0200, Florian Philipp wrote:
> In the setup Neil proposes, every client mounts an NFS share from your
> server and uses that as its DISTDIR (where it stores the downloaded
> files). For downloading files, the clients access the normal public
> Gentoo mirrors but because all clients share the same directory, files
> that some client has already downloaded are also available for every
> other client. Therefore they will not be downloaded twice.
Exactly.
> The only possible problem with this approach is that two clients might
> attempt to download the same file at the same time. Just make sure to
> start your updates at different times to avoid this.
I believe this is no longer an issue as portage now uses file locks over
NFS. I don't know if it does the same with CIFS shares, I've never tried
it.
Incidentally, my cron script that runs emerge --sync follows it with
emerge-uDNf world, so the files are already in $DISTDIR when I want to
update.
--
Neil Bothwick
"I am a Cub Ranger. We dib dib dib for the One. We dob dob dob for the
One."
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2011-04-18 22:08 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-18 1:28 [gentoo-user] Howzat! Peter Humphrey
2011-04-18 1:44 ` Dale
2011-04-18 4:53 ` Joshua Murphy
2011-04-18 7:52 ` Florian Philipp
2011-04-18 8:12 ` Neil Bothwick
2011-04-18 9:32 ` Florian Philipp
2011-04-19 22:40 ` Kfir Lavi
2011-04-19 22:54 ` Dale
2011-04-20 7:33 ` Joost Roeleveld
2011-04-20 8:42 ` Dale
2011-04-20 9:25 ` Joost Roeleveld
2011-04-20 9:49 ` Pandu Poluan
2011-04-20 10:24 ` Joost Roeleveld
2011-04-21 5:41 ` Pandu Poluan
2011-04-21 15:49 ` Paul Hartman
2011-04-20 12:37 ` Joost Roeleveld
2011-04-20 13:16 ` Alan McKinnon
2011-04-20 13:41 ` Joost Roeleveld
2011-04-20 20:06 ` Alan McKinnon
2011-04-20 21:38 ` Mick
2011-04-18 11:22 ` Peter Humphrey
2011-04-18 12:44 ` Neil Bothwick
2011-04-18 14:35 ` Peter Humphrey
2011-04-18 14:51 ` Florian Philipp
2011-04-18 15:48 ` Peter Humphrey
2011-04-18 15:59 ` Peter Humphrey
2011-04-18 21:56 ` Neil Bothwick [this message]
2011-04-19 5:34 ` Thanasis
2011-04-19 6:57 ` Joost Roeleveld
2011-04-19 8:04 ` Neil Bothwick
2011-04-19 12:07 ` Thanasis
2011-04-20 13:33 ` Neil Bothwick
2011-04-20 21:23 ` Thanasis
2011-04-20 22:01 ` Neil Bothwick
2011-04-21 7:44 ` Thanasis
2011-04-21 8:03 ` Neil Bothwick
2011-04-21 8:15 ` Thanasis
2011-04-21 10:57 ` Thanasis
2011-04-21 13:26 ` Neil Bothwick
2011-04-21 14:45 ` Thanasis
2011-04-21 22:09 ` Neil Bothwick
2011-04-22 5:05 ` Thanasis
2011-04-22 7:14 ` Neil Bothwick
2011-04-22 8:12 ` Thanasis
2011-04-22 13:00 ` Neil Bothwick
2011-04-22 15:26 ` Thanasis
2011-04-22 18:46 ` Neil Bothwick
2011-04-21 13:41 ` Mark Knecht
2011-04-21 22:42 ` Neil Bothwick
2011-04-22 0:38 ` Mark Knecht
2011-04-19 12:40 ` Joost Roeleveld
2011-04-20 10:40 ` Thanasis
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=20110418225609.0e47a40e@digimed.co.uk \
--to=neil@digimed.co.uk \
--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