From owner-freebsd-questions Tue Jun 3 16:11:10 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA29892 for questions-outgoing; Tue, 3 Jun 1997 16:11:10 -0700 (PDT) Received: from adam.adonai.net ([205.182.92.2]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA29880 for ; Tue, 3 Jun 1997 16:11:01 -0700 (PDT) Received: from localhost (leec@localhost) by adam.adonai.net (8.8.5/8.7.3) with SMTP id SAA03075; Tue, 3 Jun 1997 18:12:17 -0500 (CDT) Date: Tue, 3 Jun 1997 18:12:17 -0500 (CDT) From: "Lee Crites (AEI)" To: "Sexton, Robert" cc: freebsd-questions@hub.freebsd.org Subject: Re: Shared Source Tree In-Reply-To: <4F1AF95B0187397C@mg01a.mhs.squared.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-questions@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk =>Is it possible under 2.2 to NFS-share a source tree? =>I found a discussion of this 18 months ago where Jordan said that every =>host needs it's own /usr/src. I'm hoping this has changed, because =>I'd really like to maintain only one tree with cvsup. => =>I did try to Readonly mount the existing 2.2 tree via NFS, but make =>world died about halfway through with a write error. I'm not sure how others do it, but I got some help from a local guru (thanks, Richard) on this very matter. FreeBSD comes with a nice little program hidden under the X subdirectories someplace called lndir. This utility makes a link clone of your subdirectory tree. So, I put my real source code in a different directory, like /pub/FreeBSD/source/2.x.x, then run lndir under /usr/src. (I can't remember the complete syntax off the top of my head.) Anyway, this made an image of the real source code, via symlinks, under /usr/src. Make world didn't know -- or seem to care. When I start bringing more machines on-line, I will keep all of the source on a single machine and use something like NFS to access it from each one. Also, this will allow me to keep multiple versions of the os with impunity. When I've got the newest version loaded and running, I can just lndir to the new tree and build/install, no sweat. That, in fact, is how I initially upgraded from 2.1.5 to 2.2. Some might not consider it the best solution, but from my perspective it works, so I'm happy... Lee