If you, like me, owned a Netgear WNR854T router for more than 6 months, you are probably looking at a front panel with just the green power light on, desperately trying to connect to it. As a last resort you hit the interwebs to look for a fix which is when you realize that you probably should have read the reviews on amazon.com, buy.com or any other retailer. Yes my friend, you bought a piece of junk, your router is no more! It has ceased to be! It's expired and gone to meet its maker! This, is a late router! It's a stiff! Bereft of life, it rests in peace! It's rung down the curtain and joined the choir invisible! "THIS IS AN EX ROUTER!"

Mine failed after 12 months and 20 days which is, as the friendly Netgear Customer Support Representative reminded me, exactly 20 days past the warranty period. I filed a complaint with the FTC Bureau of Consumer Protection but apparently is is perfectly legal in this fine country to sell any POS as long as it gets replaced if it fails in the warranty period, to which I replied "With the same POS?", yep, that's all perfectly fine, long live capitalism. I consulted a few lawyers (no shortage of those here) and they confirmed that this is acceptable business practice, probably not good for business in the long run, but business none the less. I followed this all up with a few F-bom riddled e-mails to Netgear but they wouldn't budge and I gave up. I was planning on taking the sledge hammer to it, Office Space style, but for some reason I never did, maybe I thought I would set a bad example for my kids or maybe I felt sorry for the router, who knows.

It has been more than a year now, my replacement router, a D-Link DIR-655 has been humming along without any hick ups whatsoever, it is much faster and more configurable, a fine piece of machinery. But I still cannot believe I have a bricked router in the house, I never got over it and haven't had the hart to toss it out. So in one last attempt before composting it, I decided to open the thing up and see if I could find what was wrong with it.

The first thing I did when I found it was to plug it in, maybe hopping that time would have healed it, but it hadn't. I found myself staring at that green light again, like I had over a year ago, first transfixed but very quickly the sledge hammer urge came over me again like a green haze at which point a recomposed myself and started focusing on the job at hand. I couldn't immediately find any screws, maybe I would have to user a hammer after all. When I turned the router upside down, a pair of stickers drew my attention and made me chuckle:

I presumed you have to rip these off, maybe there were screws under these stickers, so I did. No screws, but it became clear that the side panels on the router are held together by those plastic hooks you can see at the bottom and the sticker will get damaged if you remove the panels, hence voiding your warranty. Put your router flat on its side so that you can read the labels at the back above the ports (i.e. make sure it is not upside down), like so:

The side panel that is now on top is the panel you need to remove first (you'll see why later). Take a sharp tool (I used scissors but a small flat head screwdriver will do to) and start pushing in the (5) plastic hooks of the top side panel one by one while slowly lifting the side panel. When you push in the last one, the panel should pop right off. There are a few internal plastic hooks along the other sides, again you can use a long tool to pry those loose while you pull, I just pulled and it came off without damaging any of those other hooks. You should be looking at something like this now:

You can clearly see the wireless card with 3 cables coming out of it. Those are the antennas and you see they run to the other panel into 3 tubes. This is why you cannot remove the other side panel first, it's kinda attached to the wireless card. It seems that the wireless card is attached to a IDE port and can be removed. As I do not need wireless on this router, I decided to start with that and see what would happen if I remove it. Start by disconnecting the 3 wires from the card, just pull them off, its a snap-on connection. You can now safely pull the other side panel off.

Next you need to remove the 2 white plastic pins in the corners opposite the IDE port that pin the card to the motherboard. I found it easiest to start from the underside of the motherboard, just squeeze them and push them through the holes, the wirless card will bend but it is very flexible. Then bend the card even further and push the pins from the other side (on the wireless card) all the way through. Alternatively, you can just clip the pins, we won't need them anymore anyway.

Now for the scary bit, removing the card from the IDE port. Unfortuntately it seems that it is soldered onto the motherboard. I took my chances and just ripped it loose (finally some revenge), pulling hard away from the port. The plastic sides broke off, but no real damage was done, the card came out clean, as did the motherboard. Here is the result, router with spare parts:

I thought after this major surgery I would give my router another try and I plugged the power in (be careful not to touch any components when you do this OR better, put the panels back before you try this). It had been so long since I last used it that I did't remember the boot sequence anymore. As a result, my first reaction was disappointment, that all to familiar green light was staring back at me. But then, it suddenly started flickering and turned orange and then I remembered that this is how it boots. Hurray, it's alive, ALIVE! I plugged in my internet connection and poof, the internet light started flickering.

So there you have it, by removing your wireless card you can revive your WNR854T router from the dreaded Green Ring of Death (GROD). You will loose the wireless capabilities, but at least it's not bricked.

Mission Accomplished.

In the next article I will explain how to use this router as a second router in your LAN.

As promised, in this post I will detail how to install NX (No Machine) on your Ubuntu server and a NX client on your windows PC.

Open your favorite browser on your server, point it here and download the client, node and server. The client is needed because it ships libraries used by the node. The node is needed because it ships tools needed by the server. Make sure you install them in that order. Your web browser should automatically ask you if you want to install the files. If it doesn't, save the files, open a terminal window and issue the following commands:

$ sudo dpkg -i nxclient_3.3.0-3_i386.deb
$ sudo dpkg -i nxnode_3.3.0-3_i386.deb
$ sudo dpkg -i nxserver_3.3.0-8_i386.deb

Next you need to get the Windows Client and install it. Once installed, proceed by opening the client and it will present you with the Connection Wizard. Provide a name for your session (can be anything) and enter your server's IP address in the Host field. Leave the port set to 22. You can also select an Internet connection Type, since I am using it over my LAN I set it to LAN.

The next screen is where you set the Desktop you want to use in your Linux session that will get initiated by NX. I use the same as my server (Unix/GNOME), but you can pick anything you want, regardless of what you use normally on your server. You also set the screen size in this window, set it to available area to have your session run in a full screen window. And finally you can add a shortcut on your desktop so that you can launch this session directly just by double clicking the icon on your desktop.

If you want to send sound from your server to the NX client, you need to configure both the client and the server a bit more. Open the NX Client for Windows tool, select your just configured session and hit Configure. Go to the Services Tab and tick the box next to Multimedia Support.

On the server, you need to play sounds using the Enlightened Sound Daemon (ESD). Most Gnome applications use the gstreamer subsystem to play sounds so you will need to configure gstreamer to use esd as the output.


System -> Preferences -> More Preferences -> Multimedia System Selector
-> Audio -> Default Output Plugin -> Output = ESD


KDE Control Center -> Sound & Multimedia -> Sound System -> Hardware ->
Select the audio device = Enlightened Sound Daemon

I could not get this to work so I used VLC and the VLC ESD plugin and that works perfect.

I made a reference to No Machine in a previous post so I thought I let you know how to install it and why, starting with the latter.

I have already described one method of connecting remotely to your server (using VNC), No Machine offers an alternative. It has a few distinct advantages over VNC which is why I actually prefer it.

The most notable feature is that NX is much faster than VNC. It responds much faster to mouse movements and keyboard entries. This in itself is all the reasons I need to use NX, however there is more.

When you connect to your server using NX, you do not have to connect to an existing session. By default, it will start a completely new session and you can even choose whether you want to use GNOME or KDE for that session, regardless of what you have running on your server already. Unlike with VNC, you do not take over the session on the server and if somebody should be sitting at that server, he can continue to work independent of you, in fact he wouldn't even know you were connected. You cannot do that with VNC.

Another nice feature is that because you have a new session, you do not have to use the same screen resolution as the server. For me, this comes in very handy as I have a crappy monitor connected to my server with a very low resolution but the computer I use to remotely control my server has a very nice, large screen. When I use VNC, I get a very small window that shows me the same desktop as on the server's screen, when I connect with VNC, it will use the whole screen of my desktop giving me much more real estate to work with.

Finally, you can pipe sounds from the server to your remote machine with NX, again that doesn't work with VNC. And since I have no speakers attached to my server, but I obviously do to my desktop, this feature gives a voice to my server that I actually never had before.

It is however not Open Source although you can download a free version that allows 2 users to connect at the same time no matter what their location is, and share the desktop, which suits me just fine.

In my next post I will explain how to install NX and configure it.

Today we are going to look back at one of the commands I mentioned in an earlier post; the sudo command.

Each Linux system (including Ubuntu) comes installed with a special user, a superuser, called root. It is the equivalent of the "Administrator" account in Windows and is used for the same purpose, to administer the system. To be able to do this, the root superuser has access to everything and can do anything on your system, including destroying it. You can see that the root account should not be used by just anybody and you should keep the password of it a close secret. In fact, root can be so dangerous that in Ubuntu the account is disabled by default, in other words you cannot even use it (you could re-enable it but as you will see, there really is no reason to do this).

So how do you, the non-superuser perform administrative tasks, i.e. how do you run commands that require root level privileges? You use the sudo command. sudo stands for super user do and allows authorized users to run commands as root without using the actual root account. So even though you are not root, you can pretend to be root. You do this by simply prepending the command you need to run with sudo, e.g. as I showed in an earlier post:

$ sudo apt-get install firefox

The apt-get command requires root privileges so in order to be able to run it as me, I have to prepend it with sudo. You will notice that when you do this, you will be asked to provide a password. This is YOUR USER password, not the root account's password (remember, root is disabled), i.e. the same password you provide when you enter Ubuntu (if you didn't already enable the automatic login option as discussed in Configure Ubuntu For Remote Access, Part II: Wake On LAN (WOL)).

Anything you need to do as administrator of an Ubuntu system can be done via sudo which is why there is no reason to ever enable the root account. However, this begs the question, what is the difference between using the root account directly and using sudo. There are a few subtle but very important ones actually. Fist of all, if you log in as root and leave your terminal, anybody sitting at it after you leave could do anything they want to your machine. If you use sudo they would have to provide YOUR (obviously super secure) password before they could do anything. Also, the user would not have to remember another (the root account's) password. It also will prompt YOU every time you try to do something with root privileges making you think twice before you do something you really didn't want to do. Next, you can restrict which user can do sudo and which can not (see below). And finally, each and every command run with sudo will get logged into a file (/var/log/auth.log) which you can always read to verify who did what and maybe even reverse what they did (and shouldn't have done).

To allow a user to us the sudo command, open the Users and Groups tool from System->Administration menu.

You will notice that the forms is mostly disabled because, guess what, changing User and Groups' properties requires root privileges. Just as in a terminal window, you will need to perform the equivalent of sudo on the User Settings window. You do this by clicking on the Unlock button and provide your user password. You will now see that all settings are enabled. Select the user you want to enable sudo for from the list, then click on on properties. Choose the User Privileges tab. In the tab, find "Administer the system" and check that.

An there you have it, the magical sudo command. You better get used to it because you will need to use it all the time.


Today, Ubuntu released its latest version: Ubuntu 8.10 (Intrepid Ibex).  You can download it from the ubuntu website which also has Upgrade instructions.  I will install it myself over the w/e and report back on how it went.


Hi everybody, just wanted to make everybody aware that the 3rd season of "30 Rock" starts tonight over on NBC. Given my number of readers, I don't think that my endorsement will make the slightest of difference, but if I can convert just one of you I'm a happy camper.

"30 Rock" is quite possibly the most underrated comedy series currently showing on TV, how in the world more people watch "2 1/2 Men" than this nugget I will never understand.

Common people, if you have to watch TV tonight, watch 30 Rock, you will not be disappointed.

One of the first things you probably want to do after installing Ubuntu is adding your favorite programs, not in the least because the CD version comes with practically no extra software. Don't bother looking for "Add/Remove Programs" like I did for the first few hours because you won't find it. In Linux, software comes in packages, no really, they are called packages. These contain everything you need to install the software and in that respect don't seem to differ that much from .exe files in Windows. However there are a few crucial differences. For one, you can't just run the package to install the software, you need a Package Management System for that. Luckily Ubuntu comes pre-installed with one of those called Synaptic Package Manager. It can be accessed from the menu System -> Administration -> Synaptic Package Manager

Packages can be found in package repositories all over the internet and you can configure Synaptic Package Manager to connect to any one (or all) of them, putting at your fingertips quite possibly the largest collection of free software I have ever seen. To add a repository just select Settings -> Repositories and make sure your first Tab (Ubuntu Software) looks like this

Then on the second tab (Third-Party Software) you can add your own repositories (I have not found the need yet to do this, the default ones had all the packages that I needed so far). I'll walk you through the installation of Firefox as an example of the installation process.

On the main screen hit the search button, type in Firefox in the Search Box that pops up and press the Search button

From the list that gets returned, select Firefox (verify the version from the Latest Version column) and from the window that pops up select "Mark for Installation" (it should be the only one available). The icon in the first column should have changed to indicate that you selected this for installation. Note that at this moment nothing has been installed yet. For that you need to press the Apply button at the top of the screen

It will ask for confirmation and when you confirm your selected packages will get installed. You will notice that the icon now becomes green indicating that that package is installed on your system.

If you want to remove (uninstall) a package you just click on the green icon and select Mark for Removal

and again select the Apply button after you made your selection. You can select as many installations or removals as you want before hitting Apply, when you then finally do hit apply, all those queued installs and removals get applied all in one go.

After having had so many issues with WoL this was quite a welcome reprieve and I this system is a far better approach to managing software applications than the complete mess in Windows (if only they just called it "Add/Remove Programs")

Oh and of course, for the brave ones, there is also a command you can execute from a terminal that will install your package:

$ sudo apt-get install firefox

Have Fun.

from the Star Tribune:

In July, St. Paul software developer CodeWeavers came up with the gimmick to make its products available free for a day if any one of five positive (but seemingly unlikely at the time) things happened during Bush's last six months in office: gas drops to $2.79 a gallon, milk drops to $3.50 a gallon, U.S. jobs exceed 138 million, the Twin Cities median home price returns to $233,000 or Osama bin Laden is captured.

Bingo on No. 1.
When CodeWeavers CEO Jeremy White saw that gas was $2.79 a gallon during a recent fill-up, "I screamed, 'Woohoo!' Then I yelled, 'Oh, crap!' as I realized every American can now have my software for free -- kind of upsets my fourth-quarter revenue projections," he said.

So on Tuesday, all of CodeWeavers products, which allow Mac and Linux users to run Windows applications, can be downloaded for free -- instead of $40 each -- at the company's website.

starts TUESDAY!!!
Link to site

Before I move on posting another "instructional" entry, I thought I'd first get something off my chest, it is after all a blog, my blog even, and I can do whatever I want, nobody seems to be reading it anyway. As I mentioned in my previous post, I had some trouble getting WoL to work on my Ubuntu Server and in fact it still does not work properly. I got this working flawlessly on my Windows PC in 1 minute.

I am not a Linux/Unix expert, but I certainly am not new at it, I've been using it for years at work. In fact I would argue that I am the same kind of user on Linux that I have always been on Windows. I use it because the software I employ needs an operating system to run in, period. I don't administer users on it (I am the only user), I don't fool around in the registry (scared to death) and I haven't open a DOS window since Windows 2000. Same with Linux, the tools I use at work are just run in a Linux environment and so I use it. Yet getting this feature enabled on Windows was easy for a user like me, in Ubuntu on the other hand it was more akin to giving birth to a 10 pound baby, slow, painful and I was cursing the person who conceived it. Finding a solution was like a treasure hunt gone horribly wrong. I changed scripts, config files, startup routines and at some point I was even told I need to recompile the kernel! That is where I drew the line and kinda gave up on the feature until I noticed that WoL does work when I shutdown the machine manually (shutdown -h now). However nobody can tell me why that works whereas if I use the Standby/Hibernate it does not.

I am well aware that WoL probably isn't high on many computer users must-have-features list, but that is not the point. In my deep dive sessions in the world of WoL I noticed Linux users complaining about the power management features and how they can't find a fix for them either or that it inexplicably works in some cases but not in others, very similar as my experience with WoL and I am sure that is high on people's feature list. I never heard anybody complaining about those on Windows. The point I am making is that a user like me should get these features to work without any problems on Ubuntu. If I can't get it to work, a novice user doesn't stand a chance and there are a lot more novices out there than experts. I am sure a lot of users would have given up already after such an experience, one of the downsides I guess of free software, if you don't like it, you toss it.

There, I've said it. It is way to early for me to give up on Ubuntu, I am a tinkerer after all so this suites me just fine. I am hopeful that it will get better from here on and that I will discover things that are easier to do in Ubuntu than in Windows, but I definitly concluded that Ubuntu is not ready for the masses ... yet.

In the previous post, we discussed how to access your server remotely from another machine (using VNC). However this did not go far enough for me (yes I am that lazy). In order to conserve energy (electrical, not my own in this case) I don't want my server to run 24/7 so I shut it down whenever I am not planning to use it. That bit I obviously can do remotely through VNC. However, every time I wanted to use the server I had to go to my garage and push the power button, too much work for me. So I started to wonder if there is a way to remotely wake up the server. And what do you know, there is, it is called Wake-on-LAN or WoL for short and it allows you to wake up your powered off computer using another computer connected to the same LAN, magic (literally, as you'll see in a moment). The caveat is that your computer and network card need to support this feature. This is usually advertised on the feature list of your NIC but if you aren't sure, you can verify this in Linux by issuing the following command in a terminal window:

$ sudo ethtool eth0

Don't worry to much about what this all means just yet, we will get to that in later posts, for now, just stick with me and you should see something like this in your terminal window:

The bit we are interested is the line that says "Supports Wake-on: umbg". If you cannot see this line at all, your card does not support wake on anything. If you do see this line, but not the exact same letters as I have (umbg) don't panic, the only letter you really need is g. This indicates your card supports Wake on Magicpacket (tm) (I told you!) which is what we are going to use to wake our server over the LAN.

Now that we have established that your NIC supports Wake on LAN, we need to enable it. You can see from the output that I have already done this (Wake-on: g), you can do the same by issuing the following command:

$ sudo ethtool -s eth0 wol g

That should set the Wake-on line to g. You can verify this by rerunning the command

$ sudo ethtool eth0

That covers the server part. Now you need to get a piece of software that can generate a MagicPacket and send it to your server. I am using something called WOL Magic Packet Sender for my windows machine (I haven't moved completely to Linux :-) which is free and you can get from http://magicpacket.free.fr/ but you can use any one. On Linux you can use the wakeonlan command. Before you shut down your server you first need to write down its IP address and the MAC address of the NIC, both of these can be found on the Connection Information window which I explained how to open in the previous post. Now you are ready for some magic.

Shut down your server by issuig the following command:

$ sudo shutdown -h now

This will obviously kill your VNC session but we will bring it back up when the server starts up, more on that later. Open up your favorite MagicPacket generator and try to send one to your server (use IP address and MAC address obtained earlier). Your server should roar back to live.

This leaves us with one more issue to tackle, when you wake up your server it will halt at the login screen, waiting for someone to provide a user and password. At this point in time, the VNC server has NOT yet been started so you cannot connect remotely to the server to do this. You have to enter the required information on the server itself meaning a trip to the garage/basement, not what I wanted. Luckily in Linux there is a feature that allows you to login users automatically. Go to System -> Administration -> Login Window, go to the Security tab and check "Enable Automatic Login" and pick a user:

The next time your computer boots up it will go straight into Ubuntu desktop (as the user you selected), whether you boot manually or use WoL. So please give it another go now, shutdown the server and send a MagicPacket from another PC. After a minute or so you should be able to start VNC again and log back into your server. Now I finally have what I wanted, full remote control of my server, including power on and off, from anywhere in the house.

So much for the instructions. Now here's the bad news, I build my server from scratch, component by component and then installed Ubuntu on it in about an hour. Getting WoL to work took me more than 2 weeks, and it still does not work the way I want to. It should work for most of you with the above instructions, but if it does not, let me know and I'll get you the lowdown on what you should check and configure in Ubuntu to get it to work properly.

Before we move on, maybe this is a good time to enlighten you all exactly what I am planning to do with this Linux Box. When I embarked on this project, the plan was to build a superfast NAS from scratch and prove that you can do this cheaper than buying an off-the-shelf NAS solution (TheCus, ReadyNAS etc.). However, I completely overspec'ed the machine and therefor decided to use it as a full blown server rather than just a file server. The plan right now is to use it mainly as a Media Server (pics, music and movies) but I have other plans with it which you will learn all about in later posts.

So why am I boring you with these details? Well, I don't want this frankensteinish contraption that I constructed anywhere near my living room, yet that is where I will need to use it the most. My media center is there and that is also were I usually work from using one of my laptops. So the Linux Box is in the garage but I am in the living room, how do I do anything on my Linux machine? That is what this post is all about, remote connection to my server from my laptops.

The first step is to enable VNC on Ubuntu. You do this by selecting system -> preferences -> Remote Desktop:

On the Remote Desktop Preferences window you then tick the box next to "Allow other users to view your desktop" and "Allow other users to control your desktop" and that is it, VNC is now enabled and you can control your linux server from any computer that has a VNC client (see later). You should uncheck the box next to "Ask you for confirmation" because otherwise someone on the server needs to give permission every time somebody tries to connect to it, pretty much defeating the purpose of what I am trying to achieve here. I do recommend thought to require users (that want to connect) to enter a password. This will prompt each user that wants to connect for the password you provide here. If they do not know the password they cannot connect. This is how my preferences look:

Do not worry about the Advanced tab, just close the preferences window and you are done on the server.

Next you need to install a VNC client on each machine you want to connect to linux from. I use VNC Viewer from realvnc.com but you can use any flavor. Once installed, lookup the IP address of your Linux Server by rightclicking on the network icon and select Connection Information:

(You should setup your router so that your server has a fixed IP address or that your DHCP server always gives the same IP address to your server otherwise you IP address will keep changing and you will need to reconfigure the VNC client with the new IP address.)

Now start your VNC client and provide this IP address and you will be prompted for a password. Give the one that you filled in earlier and after a few seconds you will see your Ubuntu desktop in a window. You can now fully control your server through this window as if you were sitting at the server. I absolutely love this feature!

I am aware of the NoMachine (NX) alternative and I am actually using that at work but VNC serves my needs just fine at home and I will stick to that for now.

Next we will apply some magic and wake up our machine using a magic packet! See you then.

Well, I suppose it is appropriate to start at the beginning, installing Linux. As a novice I choose to go with Ubuntu as it is known to be a very user friendly version of Linux, leaning closely to Windows. There are actually 2 versions available, a server and a desktop version and even though I am planning to run my Linux box as a server I picked Ubuntu Desktop (8.04). There really is no difference except for the software (packages in Linux speak, more on that later) that gets installed for you when you install the OS. And the desktop version comes with a nice UI (again this is just a package), the server version doesn't. That's right, if you install Ubuntu Server, you get no UI, you have to interact with the OS through a terminal, just like you used to with DOS before windows. You can simply install a UI afterwards (and there are several you can choose from, getting confused yet?), but I thought it would be easier to start with a UI. Whatever gets installed in the server version of Ubuntu, you can install yourself manually later, and vice versa for the desktop vesion.

Your first step is to locate a CD or DVD image of Ubuntu. You can easily find one on the official ubuntu website, but you can download it much faster from bittorrent. And you always thought that bittorrent is only useful to expand your porn collection or illegal movie/music library, right? Nothing could be farther from the truth, at this very moment more than 30,000 souls are seeding the Ubuntu Ultimate DVD Image (that is a version of Ubuntu that contains all the packages officially supported by Ubuntu) which will result in blistering download speeds.

Once downloaded you need to burn the image to a CD (or DVD), pop it into your PC and reboot (make sure you have setup your Bios to boot from CD). After a few minutes you will get asked to pick your language:

and then you'll be presented with the following screen:

You just pick the second option (Install Ubuntu) which will load the necessary components into the RAM. You'll then be presented with a few simple questions, the first one of which is the option to choose your language for the OS

Then you need to pick your location

Next your Keyboard Layout

Then you will get asked how to partition your Hard Drive. I am installing a brand new system so no dual boot shenanigans for me. If you are in the same boat, just pick "Guided - use entire disk" and you are done with this step.

And finally you need to provide some information about yourself and your system:

And that is it really, you then just click "Install" and Ubuntu will do all the rest for you. In fact the installation is far less painful then with Windows. Ubuntu will not halt the process half way through to ask more questions, it will install without interruption. It is also much faster than installing Windows. In my case it went without a hitch and when I booted into Ubuntu after installation everything worked perfectly. I was on my network, could reach the internet and was ready to go.

Next time I will discuss how you can customize Ubuntu and talk a bit more about those packages that I mentioned earlier.


Posted by mvilrokx | 10:56 AM | 0 comments »


Posted by mvilrokx | 10:05 PM | , , , | 0 comments »

Well, I finally decided to put my trials and tribulations that I am experiencing with Linux (Ubuntu) out there so that other people can benefit from it. It has been a few weeks now and I have managed to setup my Linux Box pretty much the way I wanted (although there are still a few kinks I would like to iron out maybe with your help).

I have been a Unix and Linux user for many years actually, but never as an administrator. We use it at work to store our code (SCS) and so I am quite familiar with vi, ls, pwd etc. But now I wanted to setup my own server at home and that was really something else. Over the next few posts I will go over the details of what I have been going through so stay tuned.