From owner-freebsd-questions Fri Apr 28 20:10: 8 2000 Delivered-To: freebsd-questions@freebsd.org Received: from mercury.campbell-mithun.com (Mercury.campbell-mithun.com [192.159.32.151]) by hub.freebsd.org (Postfix) with ESMTP id 82B6D37C02C for ; Fri, 28 Apr 2000 20:10:04 -0700 (PDT) (envelope-from swb@accord.grasslake.net) Received: from accord.grasslake.net (accord.grasslake.net [206.11.249.240]) by mercury.campbell-mithun.com (8.9.1a/8.9.1) with ESMTP id WAA04336; Fri, 28 Apr 2000 22:10:02 -0500 Received: from localhost (swb@localhost) by accord.grasslake.net (8.9.3/8.9.3) with ESMTP id WAA33365; Fri, 28 Apr 2000 22:09:45 -0500 (CDT) (envelope-from swb@accord.grasslake.net) Date: Fri, 28 Apr 2000 22:09:44 -0500 (CDT) From: Shawn Barnhart To: cjclark@home.com Cc: freebsd-questions@FreeBSD.ORG Subject: Re: Local FTP install & local cvs? In-Reply-To: <20000428224229.B25309@cc942873-a.ewndsr1.nj.home.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 28 Apr 2000, Crist J. Clark wrote: > The standard install floppies download compiled and archived code in > the from the x.x-RELEASE directories on the FreeBSD ftp sites. They do > not download from "source." The easiest way to have a local > release ready for installation from floppy over ftp is to take a > FreeBSD CDROM, mount it on a machine, and make the CD accessible over > ftp. If you don't have the CDROM, download a full copy of the > x.x-RELEASE tree from a ftp site. And if you _really_ want to be cool, > build from source and make your own release locally. This seems trivial, in a sense. Are there any docs on where it starts to look for files in the tree? My past experience with something similar (RH Linux about 4 releases ago) was that there was zero documentation on where the fsck'n installer started looking for files. Some like to assume the same dir structure from the top on down, meaning creating pub/foo/blurfl/X.X-RELEASE. > I also have one machine dedicated to serving source (2.2.8, 3.4, 4.0, > and PAO) and the ports tree for the others (I have about 6 FreeBSD > machines at the location). This is easy. Just CVSup on the server as > instructed in the many guides and examples and just make the tree NFS > mountable. The same goes for allowing access to an obj-tree over NFS. Explain this further. The cvsup part is simple, I do that all the time (over and over). Is really a matter of just NFS exporting /usr/src? What I'd like to be able to do is use cvsup on the slave machine, but point it at the master machine. My machines aren't all on the same local LAN or even in the same part of the country. Having to NFS mount a source tree and use it remotely (which is what I think you were suggesting) isn't practical, but having them cvsup from an internal machine would be. Even having machines on the same LAN cvsup from an internal machine would be great -- there isn't a single cvsupX.freebsd.org machine less than 15 hops from me, and two are 19. > I am not aware of any cookbook docs for doing these two things in one > place. The hardest part about setting up the ftp installs is getting > the ftp serving configured. There are many docs about that, see > ftpd(8) for a start. Getting the source served has two parts: (1) > getting CVSup going and (2) setting up the NFS. Each is documented in > the Handbook and in manpages in several places. Oh, exports(5) and ftpd(8) are familiar enough. I can probably sort out the install bit. Being my own CVS master for slaves is probably going to require much more knowledge about CVS than I have (which is kind of like saying the Jupiter is much bigger than Earth). To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message