From: "Walter Dnes" <waltdnes@waltdnes.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] An alternative to http-replicator
Date: Sat, 10 Jun 2006 22:43:03 -0400 [thread overview]
Message-ID: <20060611024303.GA26116@waltdnes.org> (raw)
In-Reply-To: <448A6201.6090900@cs.umn.edu>
On Sat, Jun 10, 2006 at 01:09:05AM -0500, Jeremy Olexa wrote
> Much simplier:
> http://gentoo-wiki.com/HOWTO_Using_a_shared_portage_via_NFS
My approach requires 2 emerges (boa and rsyncd) and their config files
on the server plus inserting the server as the preferred mirror in 2
lines in /etc/make.conf on the client(s).
NFS requires building NFS server support on the server (reboot
required) and NFS client support on the client(s) plus setting up lines
in the associated config files. It also requires enabling and running
portmapper on port 111 (the linux version of Windows' port 139) on the
server and punching a few holes in iptables. For details see...
http://gentoo-wiki.com/HOWTO_Share_Directories_via_NFS
In terms of programs to configure and run, it's a wash. But I'll
pick http security (especially boa) over portmap/nfs security any day.
rsync and nfs both work for "emerge --sync" because we know that those
files are supposed to be *ABSOLUTELY* identical for all machines at any
given time. Unless your server has *EVERY PACKAGE THAT EVERY CLIENT
NEEDS*, you run into a problem when emerging packages. If a required
tarball isn't present, emerge downloads the missing file (tarball, etc)
to the distfiles directory. But, but, but... the clients' distfiles
directories are nfs mounts on the server. That implies that *THE
CLIENTS WILL NEED WRITE PERMISSION ON THE SERVER*!!!!
My approach is to make *LOCAL* copies on the client from mirrors. The
local server just happens to be the first mirror on the list. If it
doesn't have a required file, no problem, check the next mirror in the
list. The clients never have to write on the local server.
--
Walter Dnes <waltdnes@waltdnes.org> In linux /sbin/init is Job #1
My musings on technology and security at http://tech_sec.blog.ca
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2006-06-11 2:50 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-10 3:31 [gentoo-user] An alternative to http-replicator Walter Dnes
2006-06-10 4:43 ` Anielkis Herrera Gonzalez
2006-06-10 5:00 ` Michael Weyershäuser
2006-06-10 5:09 ` Teresa and Dale
2006-06-10 8:45 ` Neil Bothwick
2006-06-11 2:37 ` William Kenworthy
2006-06-12 23:17 ` Neil Bothwick
2006-06-10 6:09 ` Jeremy Olexa
2006-06-10 9:02 ` Michael Weyershäuser
2006-06-10 10:25 ` Mick
2006-06-11 1:41 ` Bob Sanders
2006-06-11 2:00 ` Teresa and Dale
2006-06-10 14:59 ` Jeremy Olexa
2006-06-10 17:19 ` Andrew Frink
2006-06-10 18:21 ` Uwe Thiem
2006-06-11 2:43 ` Walter Dnes [this message]
2006-06-11 3:06 ` Bob Sanders
2006-06-11 8:18 ` Mick
2006-06-12 2:24 ` Walter Dnes
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=20060611024303.GA26116@waltdnes.org \
--to=waltdnes@waltdnes.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