From owner-freebsd-chat Fri May 22 09:45:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA21925 for freebsd-chat-outgoing; Fri, 22 May 1998 09:45:43 -0700 (PDT) (envelope-from owner-freebsd-chat@FreeBSD.ORG) Received: from violet.csi.cam.ac.uk (exim@violet.csi.cam.ac.uk [131.111.8.58]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA21877 for ; Fri, 22 May 1998 09:45:28 -0700 (PDT) (envelope-from bjc23@hermes.cam.ac.uk) Received: from bjc23.trin.cam.ac.uk ([131.111.212.250]) by violet.csi.cam.ac.uk with smtp (Exim 1.92 #1) id 0ycuwL-0005Ex-00; Fri, 22 May 1998 17:45:05 +0100 Date: Fri, 22 May 1998 17:45:07 +0100 (BST) From: Ben Cohen X-Sender: bjc23@bjc23.trin.cam.ac.uk Reply-To: bjc23@hermes.cam.ac.uk To: Stuart Henderson cc: chat@FreeBSD.ORG Subject: Re: Why installing ports on a computer? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-chat@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, 22 May 1998, Ben Cohen wrote: > > > Do ftp.*.freebsd.org support NFS mounting? If they do (or were > > > adjusted so that they did), then when necessary it would presumably be > > > possible to NFS mount the latest set of ports over /usr/ports. > > > > the ports collection usually builds in /usr/ports/*/*/work/.. > > Oh, I didn't think of that.... But would mount_union solve that? If I understand it correctly, then the build could be local, the rest of the ports stuff on ftp.*.freebsd.org via mount_nfs, and everything else would be OK. If the installation was using CD instead of NFS, mount_union could be done in the same way. Depending on exactly how mount_union works (I've never used it) it could even be used over an installed ports tree to collect new ports (though perhaps not updated ones?) I don't know what the advantages and disadvantages of mount_union are, but maybe this would solve the above problem and software wouldn't have to be rewritten (much). Ben. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-chat" in the body of the message