There are some cases where a remote ports tree is a good thing to have around. For example, it can save bandwidth by downloading dist files only once and using them across all clients, when you need to know that all hosts using the tree have the same version of packages (good in development environment or large network), or even when the client doesn't have enough space for ports tree, distfiles, or the compile itself (NanoBSD!)

I personally use this method for my NanoBSD boxes. These installs are usually on small flash cards that (1) don't have room for the ports tree/build and (2) would kill my solid state drives with all the rewrites. Using ports allows me to fine-tune applications instead of being a slave to preconfigured binaries...which is a very good thing on an embedded board.

Since you are a FreeBSD geek (don't lie!) and already have an existing FreeBSD system, we will just use that port tree and emulate it being on another media device. There is no magic here, but NFS can be picky!

NFS

Pretty much anyone that has been around any unix variant has heard of NFS. The FreeBSD handbook outlines it very well.

In short, it lets you mount a remote directory as if it was on your system. This is exactly what we need to emulate the ports tree.

In our topology, we need a NFS server (with the ports system on it in our case) and our client will be out NanoBSD box.

Server

Ports Tree

First of all, make sure you have the ports tree installed. If you are not sure, ls the /usr/ports directory.

• # ls /usr/ports

If it has contents, you have it. If you do not have it, download it and extract it.

1. # portsnap fetch extract
2. ... ... snip ... ... snip ... ...

Kernel Config

NFS services come in the default kernel, but if you have a custom kernel you might want to make sure you have the following options in your kernel config:

options	NFSCLIENT	# Network Filesystem Client
options	NFSSERVER	# Network Filesystem Server
options	NFS_ROOT	# NFS usable as /, requires NFSCLIENT

rc.conf

All the services we need are bootable via rc.conf at startup. We need to enable the NFS services:

1. # vi /etc/rc.conf
2. ... ... snip ... ... snip ... ...
3. rpcbind_enable="YES"
4. nfs_server_enable="YES"
5. mountd_flags="-r"
6. ... ... snip ... ... snip ... ...

/etc/exports

exports defines who may access your shares, what permission those shares are, and where the shares point to on the local system. The following is needed for our little project, but more options can be found by using the man exports command.

The IP used below is an example and is the address of the CLIENT. Change this as necessary.

1. # vi /etc/exports
2. /usr/ports -maproot=root 172.16.5.100

Start Daemons

You can take the easy way out by restarting (restart -r now) or load them manually.

1. # /etc/rc.d/rpcbind start
2. # /etc/rc.d/nfsd start
3. # /etc/rc.d/mountd start

Client

This process is even simpler than the server's config.

rc.conf

1. # vi /etc/rc.conf
2. nfs_client_enable="YES"

Kernel Config

1. ... ... snip ... ... snip ... ...
2. nfs_client_enable="YES"
3. ... ... snip ... ... snip ... ...

Start Daemons

You can take the easy way out by restarting (restart -r now) or load them manually.

1. # /etc/rc.d/nfsclient start

Test It Out

The IP below is the NFS server, so your topology could differ.

1. # mkdir /usr/ports
2. # mount_nfs 172.16.5.1:/usr/ports /usr/ports
3. # cd /usr/ports/net/isc-dhcp3-server
4. # make install clean distclean

This port should do all the fun stuff and install. If not, check back over this howto or consult the ultimate resource on this: FreeBSD Handbook - NFS

Conclusion

See, that was pretty easy, huh? Now you have have what ever package you please installed with out taking up all the space that whole ports tree would have otherwise taken up.