Like every other website on the planet, SmallNetBuilder uses cookies. Our cookies track login status, but we only allow admins to log in anyway, so those don't apply to you. Any other cookies you pick up during your visit come from advertisers, which we don't control.
If you continue to use the site, you agree to tolerate our use of cookies. Thank you!

Router Charts

Click for Router Charts

Router Ranker

Click for Router Ranker

NAS Charts

Click for NAS Charts

NAS Ranker

Click for NAS Ranker

More Tools

Click for More Tools

NAS How To

Checking it Out

Now we need to set everything up cleanly. The NFS server expects to find the exports file in the top level /etc directory, so create a symbolic link to our new exports file in the /share/hdd/conf/etc directory :

# ln -s /share/hdd/conf/etc/exports /etc/exports

Next, we need nice startup scripts for all of our new daemons. On the NSLU2, copy the rc.samba script from the /etc/rc.d directory to the new rc.d directory and modify it twice: once to create an rc.portmap script and once to create an rc.nfsd script. The rc.nfsd script should start the rpc.mountd and the rpc.nfsd.

Finally, build one script to do it all. Create the symbolic link, execute the portmap script and execute the nfsd script in that order. This script will need to be run each time the box is booted. As of yet, I have no way to automatically run startup scripts when the box boots.

Now, run the do-it-all script and try it out. A ps -ax from the NSLU2 should show three new processes running - portmap, rpc.mountd, and rpc.nfsd. Error and status messages will show up in the file /var/log/messages.

From a client machine try to mount the NSLU2. On my Mandrake system I executed the following as root:

# mkdir /mnt/nslu2 # mount /mnt/nslu2/

On my Mac OS X box, I use the "Connect to Server" option of the Finder with a server format of:


If you have any issues starting the daemons, or in mounting, check the /var/log/messages file on the NSLU2. Note that having NFS on the box does not affect SMB, they can coexist peacefully.

Now that we've shown we can build a fairly complex service for the box, the sky's the limit. A FTP server might be a good next step. Or maybe an embedded SSH server such as dropbear would be useful. Let me know how it goes!

NOTE: As I wrote this article, I started from scratch and re-executed all of my original steps in order to make sure I hadn't forgotten anything. As usual, my development box was short on disk space, so naturally I NFS mounted the disk from the NSLU2. I did all of my untarring, compilations, editing, etc. on my NFS mounted drive. It performed flawlessly!

Tip! Tip: If you want to skip all this stuff and just want a binary that you can load onto your NSLU2 (you'll still need to edit the etc/exports file), you can download the ~57 kB file from

In Part 3, I'll show you how the NSLU2 can keep you entertained as well as serve your files. In the meantime, you can follow my adventures on my Linux on the NSLU2 page.

More NAS

Wi-Fi System Tools
Check out our Wi-Fi System Charts, Ranker and Finder!

Support Us!

If you like what we do and want to thank us, just buy something on Amazon. We'll get a small commission on anything you buy. Thanks!

Over In The Forums

I was doing some research and was seeing a lot about issues with the 2.4ghz band not working after a while or having very short range (or poor perform...
YazFi v4.1.3 Updated 2020-07-11 Feature expansion of guest WiFi networks on AsusWRT-Merlin, including, but not limited to:* Dedicated VPN WiFi netw...
Aquantia has a new firmware update out for the AQC100, AQC108, AQC107 and AQN100, AQN108, AQN107 f...
I have an AC68u and I put two fans behind it to cool it off. I used a double-sided tape to attach the fan but it fell off after three days.I saw some ...

Don't Miss These

  • 1
  • 2
  • 3