Mashed Articles

The network-attached storage (NAS) business is booming. Everyone needs a convenient storage pod for the gigabytes of data they accumulate, and they want to be able to access it from anywhere on the local network and the wider internet. As a result, the hardware is getting increasingly powerful. High-end NAS boxes for small businesses and large homes are moving from Arm processors to Intel’s Atom platform, and turning simple file servers into far more capable mini-machines in the process. One of these expanded NAS boxes could operate as a web server, a media transcoder, a UPnP streaming hub for your PS3 and Xbox, and even a virtual desktop. The only problem is that these boxes are expensive – and that’s before buying the hard drives.

OK, it won’t look exactly like this. And it’s unlikely to have the capacity of an actual NAS. But we reckon there’s no better use for that old netbook.

Fortunately, there’s a cheaper way. These NAS boxes aren’t the only hardware to use Intel’s Atom: it’s also used in many netbooks. These machines are often cheap, accessible and easily configurable, and they’re all well suited to the task regardless of their age. They’re energy efficient, unburdened by extra hardware, feature both wireless and wired interfaces, and are small, quiet and cool. Attach a hard drive or two to a USB port, configure the operating system and you’re ready to go. We’re going to turn one of these netbooks into a super-powered NAS using some external USB storage, a LAN connection and some install media.

Install UNR

Not all Linux-based operating systems for netbooks are equal. Linpus, as bundled with the original EeePC, is particularly ill-equipped for updates and customisation, so don’t mess around with your default install if you ever want to use your machine as a netbook again. For these reasons, and to keep your current netbook data safe, we’re going to create a NAS configuration that will sit on a USB flash drive rather than your netbook’s internal storage. This will enable you to return your netbook to normal laptop duties whenever the need arises by simply removing the USB stick. However, you could omit the USB flash drive requirement and just install a new operating system over the old one if you prefer.

Start by installing an appropriate distro. UNR is hard to beat in this context, although you might choose a non-graphical version for your NAS.

There are two popular netbook distributions that we could easily shoehorn into NAS operating systems. The first is Intel’s Moblin, a finely tuned version of Linux that makes good use of a netbook’s limited capabilities. The only problem is that it’s not that easy to modify with simple packages. That leaves us with Canonical’s Ubuntu Netbook Remix (UNR), a special version of its Ubuntu operating system tailored for netbook hardware and screen sizes. The great advantage that UNR has over Moblin is that it has access to the massive library of packages that are available to any Ubuntu user, so installing and configuring these packages is an identical process on both systems.

To install UNR on your netbook, you need to get hold of an ISO of the latest release (see www.ubuntu.com/getubuntu/download-netbook). You then have two options. If you’ve got a Windows machine handy, burn the ISO to a disc and run the usb-creator.exe application from it. This will automatically install the distribution onto a USB stick without any further hassle. The second option requires a machine running Ubuntu. Use the Synaptic package manager to download and install a package called usb-creator. After this is done, run USB Startup Disk Creator from the Launch menu. In the top panel of the window that appears, click on the ‘Other’ button and point the file requester in the direction of your UNR ISO. In the lower panel, make sure you select your inserted USB device and click on ‘Format’. Get the wrong device and you’ll lose any data it contains, so be careful.

The end result of both methods is that you’ll have UNR installed on a USB stick. You can now boot into this operating system by simply inserting the USB stick into a spare port on your netbook and rebooting. When the UNR desktop appears, you’re ready to reconfigure.

Add connections

Your netbook is going to need to be connected to your LAN, either through a wireless router or a wired one. The connection is configured through the Connection icon in the top-right border of the main UNR screen. Wireless connections are easier to achieve. Your netbook hardware will be detected and your computer will join the network automatically after you’ve entered any required passwords. However, the wired connection is better for both power use and performance. If you’ve got a spare Ethernet port on your wireless router, for example, you can use this to bridge the wireless connection from your network to the wired connection on your netbook.

Plug in an external drive and Ubuntu should display its contents.

The wired connection will stop your wireless bandwidth becoming saturated if your NAS box is uploading or downloading from the internet, and will provide other wired devices with a faster route to your data. UNR is designed to be easy to use on smaller devices. Instead of the old desktop metaphor used by standard Ubuntu, you’ll find a large array of icons arranged to mimic Ubuntu’s standard Launch menu. Click on a category in the left panel, for instance, and your screen will fill with the icons for the applications contained within the menu. And when you launch an application, UNR cleverly merges the titlebar into your screen’s top bar, saving space on small screens. But these are only cosmetic changes, and you’ll find the same old Ubuntu beneath the surface. Now we need to configure it to automatically mount your remote storage.

When you connect your external USB storage device, UNR will automatically mount the device and launch the file manager to display its contents. Your device’s actual location on the filesystem will depend on its type and name, but you can find any automatically mounted devices listed under the ‘/media’ branch from the File System icon in the manager. When you’ve identified your drive, make sure you remember its location; you’ll need this to enable either the mount point (or, more sensibly, a folder within the mount point) to be shared across your LAN.

Install Samba

Before augmenting your NAS with any other features, it’s important to get the basic functionality right. To share files on your netbook USB drive with all the other machines in your network, you need to install a server called Samba. This is the open-source implementation of Microsoft’s network protocol, which means that it will work with all of the Windows, OS X and Linux machines on your LAN. It’s the most common fileserver system and it’s used by many NAS devices. UNR doesn’t waste netbook space installing Samba by default, so you need to install it manually.

It’s fairly easy to get file sharing working under the auspices of Samba.

As with the desktop version of Ubuntu, this is best done through the Synaptic package manager, which can be found in the Administration section of the System group of applications. Just search for samba and install the resulting package. After the package has installed, switch back to the file manager view for your USB storage device. Create the directory you want to be shared across your network and right-click on the folder. You should now see ‘Sharing Options’ listed in the menu that appears. When you select this, a window will open. From that window, enable the ‘Share this folder’ and ‘Guest Access’ options. The latter could be a security risk, as it means anyone with access to your LAN will be able to read the files on your NAS. This is fine if you trust your network, but unacceptable if your network is shared. In those cases, leave ‘Guest access’ disabled and make sure that each machine you want to share the folder with has a user account and password that has an identical name and password to an existing account on your netbook.

You might also want to tick the ‘Allow others to create and delete files in this folder’ box, unless you want your file sharing to be read-only. When you’ve finished with the options, click on ‘Create share’ and ‘Add the permissions automatically’ in the window that pops up. You should see that the folder icon for your share now has two arrows across it to indicate that the folder is being shared across your LAN.

Access your files

You can now access your files from other computers on your LAN, and your NAS box should appear within their network folders.

Just type the relevant location into the address bar to access your new share.

If you need to specify an address, such as from OS X’s ‘Go | Connect to a Server’ menu or Gnome’s equivalent ‘Go | Location’ menu option, then type smb://ubuntu into the location field. This is the default hostname for our new installation, and ‘smb’ is requesting access through the Samba protocol. After a few seconds, you’ll see the folder you just created appear, and you’ll be able to access files and folders within that directory as if they were local. Congratulations, your netbook is now a NAS device!

Add online backup

To bring your NAS in line with more functional boxes, it’s time to add some packages. Backup is at the top of our list, and UNR has a feature called Ubuntu One that’s perfect for this job. This service automatically copies your local files to a remote server. You can then download them from the server to any Ubuntu machine with an Ubuntu One account. Configuration is easy: just look for the Ubuntu One logo in the Internet category, click on it and either enter your account information or create a new account. You’ll then be asked to verify your computer’s name and say that you’d like the data to be synced. A free account can store up to 2GB of data, but you can subscribe to the commercial service if you want to store more.

Ubuntu One is a decent choice of online backup tool, although you may quickly run out of space if you’re installing a NAS-load of drives.

Switch to the file manager and you should see a new Ubuntu One folder. Anything you place here will be synchronised with the Ubuntu One server. Right-click on it to enable it as a shared folder.

Security and remote access

There are many security issues surrounding opening your NAS box up to the internet, but UNR should be up to the task as long as you keep your system up to date and install any patches. You should receive automatic update alerts, but this can be a problem when using your netbook as a NAS if you end up not looking at the screen very often. The easiest solution is to enable a mode where updates are applied automatically. Find and click on the Software Sources icon and in the window that appears switch to the Updates tab. This page manages the background update tasks, and you need to tick the ‘Install security updates without confirmation’ box and change the update frequency to one your connection can handle. ‘Daily’ is fine for most installations.

If you want internet access to your box, the safest way is to use SSH (the secure shell). This provides command-line access to your NAS box using a tool such as Putty on Windows machines, or the ‘ssh’ command in Linux. You’ll need to install the openssh-server package on your box. To connect, forward TCP port 22 to your NAS box through your router and log in with your standard account details. If you prefer a graphical desktop, install the tightvncserver package on your NAS and type tightvncserver :1 into the command line to create a new session. Any VNC client on your LAN can now access a desktop on the NAS using the address ‘ubuntu:1’. To access your desktop from the internet, use SSH to pipe the VNC port through the SSH connection with ssh -L 5901:localhost:5901 ubuntu.address and use a local VNC client to access ‘localhost:5901’.

Add more functionality

The best reason for using UNR on a netbook to create a NAS is that you can augment your installation with all kinds of functionality, from web servers to media players. One of the most popular is MediaTomb, a UPnP-compatible media streamer and transcoding tool that’s easy to install and configure. Install it by opening the Synaptic package manager on your netbook and searching for mediatomb. There will be several dependencies. After installation has completed, switch to the Sound and Video application launcher window and you’ll find a new MediaTomb icon. Double-click this and Firefox will launch, loading the MediaTomb web-configuration panel.

From MediaTomb’s web page, you can navigate to your media files on your storage device. Click on the ‘+’ symbol on the right to add them to the MediaTomb library. MediaTomb supports all the most common media formats. After a few moments, you’ll be able to view or listen to your content on any UPnP-compatible client such as Windows Media Player, RhythmBox, a PlayStation 3 or an Xbox 360. To run a web server from your NAS box, install the apache2 package, then type http://localhost into Firefox to see a web page that declares ‘It works!’.

Writen by Adam Knife

So, you’ve got an old computer, and you don’t know what to do with it. Sure, it can’t play new video games, maybe can’t run the latest and greatest software, don’t fret, it’s not totally worthless. Converting your old computer in to a home data server opens a range of possibilities, and a range of new things you can do with your computer(s) and the network.

So, how do you do it? Well, if it’s already set up for Windows Networking, you’ve got the basics set up for a Windows file server, and can simply use your local area network for transfering/working with files, however, this article is going to show you the more effective, and more powerful way: setting up a Linux file server.

The first step is to pick a Linux distro, DistroWatch.com lists the most popular distributions, and reviews a range of distributions, we’re going to use the Ubuntu [5.10] operating system, with a server installation, simply because it’s the operating system this author uses for his desktop, and is quickly becoming the most popular distribution around.

Your old computer likely has enough memory, and a powerful enough CPU to run Ubuntu, however, if you intend to use this server as a major central file server, it will likely need a new hard-drive. You can deal with that on your own.

When you insert the Ubuntu CD, and boot to it, instead of just pressing [enter] at the boot screen, type ‘server’ then press enter – this will prevent it from installing any of the *-desktop packages, and not setting up any unneeded applications.

After following the steps of installation, you will be prompted with a logon screen – enter the username and password you provided during installation, and you are in your brand new Linux system. From here, you can do everything from browse the web, to set up the computer for various networking tasks, to play a range of Linux-based games.

Package management is a critical part of running a Linux system, luckily Ubuntu comes with two distinct and useful tools to aid in your package managing. Aptitude [which, is actually just a UI for apt-get] and apt-get.

A package called “samba” will allow you to set up proper networking between Linux and Windows computers (at least, we hope you’ve got your networking issues sorted out). Running “sudo apt-get install samba” in your new command line will tell the apt-get application to install the samba package, and set it up with default settings.

Once samba is installed, you’ll want to set it up to share certain files/directories, and set them up on your network – samba networking is a massive topic of it’s own, and way beyond the scope of this article, however, running “man samba” will give you the samba manual file, which lists off a series of other manuals to look at. Google’s always helpful too.

Now, once you have networking and samba set up, you should be able to transfer files between Windows and Linux through Network Neighborhood/smbclient – you’ve now got a basic data server set up. That was easy, wasn’t it?

For those who want to go further, Pure-FTPd will allow you to set up a fully featured FTP (file transfer protocol) server on this box, which you could use to access your files remotely from any computer set up with an FTP client (Windows Explorer has one built in!), setting up an Apache based web-server is fairly simple with Ubuntu’s apt-get packages, and OpenSSH allows the user to remotely log in to the Linux shell from any computer equipped with an SSH client.

A slight advancement to this system could allow you to set up Bash scripts combined with cron would allow you to set up scripts which immediately backup files every X days, or scripts to do certain processing to files at certain times – the possibilities are effectively endless.

Adan X. Knife is a computer scientist, entrepreneur and web developer. He currently runs a network of websites including one about High Definition Technology and a Free Games Library. He also runs a range of communication related sites including his cellular phone reviews site.

I’ve recently been mulling over the nature of the relationship between where we store the information we create (the repository) and the rules governing its management – not least because it seems to represent one of the fundamental divides between the approach to records management which I am advocating (RM2.0 for shorthand) and the majority of ECM products on the market.

In the pre-Web 2.0 world there was a division between the applications we used to create information (e.g. MS Word) and the repository we used to store our outputs. We didn’t store our documents in Word, we stored them on our C://, on a separate file server, or even a removable storage device (though the MOD are beginning to wish they hadn’t!). All of which created a separate shared repository available for the storage of unstructured information created by a range of applications. This, in turn, influenced the nature of first EDRMS and latterly ECM technologies, the majority of which included their own separate repository for storage and intrinsically linked it to their management/rules layer.

As noted in Managing the Crowd: “The crucial difference with Web 2.0 services such as You Tube, Flickr, Facebook and the like is that they are content storage repositories as well. They no longer just represent the tools, but also the filing cabinet” which changes things considerably – especially when you consider that the majority of these services may be hosted outside the organisation. In this model there is no shared underpinning repository, nor is it possible to create and rely upon an intrinsic link between the management/rules layer and the repository of content we wish it to control. To my mind, this places those systems which are built upon the assumption of a combined repository and rules layer at a severe disadvantage by closing off the ability to manage information which it does not itself ‘physically’ hold.

One of the reasons for musing over this now was in the wake of an interesting chat I had the other day with some folks from Computer Associates marking the release of their new CA Records Manager product. In contrast to most other ECM products it apparently does not include its own integral repository – it’s a management layer only, managing content in its original native location. Though there are still currently limitations in terms of how widely this management layer can be applied (not yet extending to encompass the externally hosted Web2.0 services mentioned earlier) it seems to me to at least represent a more open-ended solution which at least offers the promise of achieving some of these wider, more demanding goals, further down the line.