Date: Mon, 29 Nov 2004 12:08:55 -0600 From: Dan Nelson <dnelson@allantgroup.com> To: Vulpes Velox <v.velox@vvelox.net> Cc: freebsd-questions@freebsd.org Subject: Re: moving ports to another file system Message-ID: <20041129180854.GG5518@dan.emsphone.com> In-Reply-To: <20041129115236.1519bbb6@vixen42.24-119-122-191.cpe.cableone.net> References: <41AAB892.70707@adelphia.net> <20041129060333.GB5518@dan.emsphone.com> <20041129115236.1519bbb6@vixen42.24-119-122-191.cpe.cableone.net>
next in thread | previous in thread | raw e-mail | index | archive | help
In the last episode (Nov 29), Vulpes Velox said: > On Mon, 29 Nov 2004 00:03:33 -0600 Dan Nelson <dnelson@allantgroup.com> wrote: > > In the last episode (Nov 28), Kevin Smith said: > > > The /usr/ports can take up a lot of space and I'm wondering if > > > there are limitations to having ports live in a another files > > > system with a symbolic link from /usr/ports to a ports directory > > > in another file system. > > > > No limitations at all. You can even symlink it over NFS to another > > machine if you want (set WRKDIRPREFIX to a local path in > > /etc/make.conf though, to speed up builds). > > If one is going to be using NFS for it, I don't see any reason not to > just mount it right to /usr/ports instead of messing with symbolic > linking. The symlink lets amd do the work of mounting the filesystem, that's all. -- Dan Nelson dnelson@allantgroup.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20041129180854.GG5518>