Date: Sun, 19 Nov 2000 15:24:01 -0800 (PST) From: Matt Dillon <dillon@earth.backplane.com> To: "Louis A. Mamakos" <louie@TransSys.COM> Cc: Warner Losh <imp@village.org>, James <j@evilcode.com>, stable@FreeBSD.ORG Subject: Re: cd /usr/ports; make clean Message-ID: <200011192324.eAJNO1891133@earth.backplane.com> References: <20001118231633.A85206@evilcode.com> <200011190635.eAJ6ZRS94516@grumpy.dyndns.org> <20001118230305.A83848@evilcode.com> <20001119151138.A7434@bsdvm.jtjang.idv.tw> <200011192202.eAJM2cG03593@billy-club.village.org> <200011192239.eAJMdDa90818@earth.backplane.com> <200011192308.eAJN8q714360@whizzo.transsys.com>
next in thread | previous in thread | raw e-mail | index | archive | help
:
:
:> Since I export /usr/ports read-only, I never put my work directories
:> in the ports hierarchy itself. I set /etc/make.conf to:
:>
:> WRKDIRPREFIX= /var/tmp
:
:Hey, this is very cool! This should be listed in /etc/defaults/make.conf.
:And I guess that you have a symlink for /usr/ports/distfiles too?
:
:louie
Yes. /usr/ports/distfiles is a symlink to /usr/ports.distfiles on the
NFS server. I then mkdir /usr/ports.distfiles on the NFS server.
The client configuration depends on the client:
* client has local-disk /usr, simply mkdir /usr/ports.distfiles. done.
* client is diskless, simply do a mount_mfs on /usr/ports.distfiles.
(make it big, assuming you have sufficient swap).
etc.
Works wonderfully. Without it building ports on workstations is
a mess.
It would be even better if the ports system could look in two places
for distfiles ... so I could build up local repository on the NFS
server that clients would use directly, and still allow clients
to download distributions into local directories when the NFS server
doesn't have the request.
I do the same thing for /usr/src and /usr/obj.
/usr/src read only NFS export
/usr/obj read only NFS export
/usr/ports read only NFS export
This beats dup'ing the entire ports and source hierarchy on every box,
and makes building the world and installing on workstations with
local disks trivial. You build the world on the server,
then simply 'make installworld' on each workstation. Same thing with
kernels... build on the server, install from each workstation.
It's easy to automate, too, and no-risk of exposure since the NFS exports
are read-only (you could be paranoid and run the mounts through IPSEC
links too if you wanted, but I usually don't bother).
-Matt
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200011192324.eAJNO1891133>