Re: moving ports to another file system
On Mon, 29 Nov 2004 00:03:33 -0600 Dan Nelson [EMAIL PROTECTED] wrote: In the last episode (Nov 28), Kevin Smith said: After installation and setting up of my BSD system for a while, I've come to realize that I probably should have organized my disk a bit differently and I have a smaller root file system then I would have liked. I may have also created a separate /usr file system, but I have /usr in the root file system. 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. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: moving ports to another file system
In the last episode (Nov 29), Vulpes Velox said: On Mon, 29 Nov 2004 00:03:33 -0600 Dan Nelson [EMAIL PROTECTED] 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 [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
moving ports to another file system
After installation and setting up of my BSD system for a while, I've come to realize that I probably should have organized my disk a bit differently and I have a smaller root file system then I would have liked. I may have also created a separate /usr file system, but I have /usr in the root file system. 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. -K ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: moving ports to another file system
In the last episode (Nov 28), Kevin Smith said: After installation and setting up of my BSD system for a while, I've come to realize that I probably should have organized my disk a bit differently and I have a smaller root file system then I would have liked. I may have also created a separate /usr file system, but I have /usr in the root file system. 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). -- Dan Nelson [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
