Thinkcorps

Wow. If there’s anything more disruptive (in a good way) than open source, I haven’t seen it. I bought a Linksys Network Storage Link the other day because I was interested in setting up a home NAS, and when I heard that the Storage Link’s Linux OS had been hacked open to allow the installation of other apps, I had to have it. I specifically wanted to set up an iTunes server, to share my sizable music collection on the laptops in the house. It’s totally brilliant, BTW. All hats off to the uNSLUng folks.

I always thought Linux was great, but that it’s primary stumbling block was the user’s learning curve. I think you’re going to have that problem with any computer, BTW. There’s just a lot to learn. On an embedded device however, the limitations make it much easier to handle. The uNSLUng app that handles software installation—ipkg—is very simple to use, even on the command line. It connects to the Net, downloads and installs the SW all by itself. Very slick.

If anyone stumbles on this post while having difficulties, here’s a few suggestions:

1. Follow the instructions to the letter. Be anal, make sure everything works at every step, restart the unit when advised to.
2. Firewalls OFF! This is advice so obvious that no one mentioned it in the posts I read, and so I didn’t think of it. Your firewall is probably causing your Windows networking problems (and your inability to connect to the NSLU2). Turn it off, see if things work, then ratchet up your firewall protection until you find the maximum level that allows you access to the NSLU2. Same goes for virus protection.
3. Logging into uNSLUng as ‘root’: I had trouble logging in to my uNSLUng unit when I reconnected the hard disk. (I think there’s a password stored on the HD that was interfering?) I restarted with the HD disconnected, logged in as root, and then reconnected the hard disk. After the HD initialized, I could then run ipkg and install software.
4. Creating an mp3 folder for mt-daapd: create this folder from a remote PC, not from the command line, since you’re logged in as root there and the permissions you’re advised to set in the installation instructions won’t be sufficient.