Haz's Blog

So I’ve been getting into some really cool stuff recently – or at least I think so at least. I’ve been learning more about my favourite Operating System; Linux. More specifically, the Debian-based distro Ubuntu. To be exact, how to use and maintain Ubuntu Server.

Before I go on, I would like to take this opportunity to thank the #ubuntu-uk community (mainly through IRC) for all their help and support. Without them I don’t think I would have learned as much as I did. They helped me get started, and for that I’m really grateful. Some of the people who have helped a considerable amount are: brobostigon; shauno; AlenBell; MartijnVdS; popey; MooDoo; ali1234; and a few others. Thank you all :). If I’ve missed anyone out, please let me know.

I’ve been wanting to get into the server side of things for a long time, and like most who have come from using a Windows environment, doing so can seem like quite a challenge. Mainly because you get so wrapped up in everything being placed in a graphical interface, that you sometimes forget that there is more to the machine than what you actually see.

Let’s take me for example, the most I’ve ever done was tweaked the registry; changed a few configuration files here and there; removed/replaced files and libraries so that things worked better; heck I’ve even did some minor tweaks like placing library files in the same folder as an application to avoid installing a full framework. Thing is, all that wouldn’t have been possible if I couldn’t see anything… or so I thought…

Everything I knew, or have used in the past, was basically using an file management program of some sort, browsing files and directories to find that key file that might do something I may want it to actually do. Once I’ve found it, do a few short-cut commands type in the editor of choice and then see if I can mess with it enough to do what I wanted it to do – and I’m talking about basic config files here. Browsing the directories with a mouse/keyboard makes life so much easier – I can move a folder to one side and have something going on in the other… using my monitor screen space to the fullest. All was great!

However, one has to remember – to obtain a Licence for a Microsoft server O/S isn’t cheap. Heck, it might not even be fully secure! All it takes is for someone to find a vulnerability in any of the applications running to tamper with it, and lets face it. There’s more going on when you have a full graphical suite open at all times (even if you don’t have a monitor attached to it), which means your leaving more holes open in your system. Here is what lead me to my adventure.

I thought, lets try and build a home server using a Linux distro. I mean all that’s running is the main kernels that drives it, a terminal, and possibly a few daemons to keep it all in check. Nothing graphical other than a blinking cursor waiting for your command. Its bound to be more secure! Besides, its Open-Sourced… anything that does go wrong will have a fix eventually before you’ve even realised there was a problem. But hold on, lets rewind a second… “did you just say only a blinking cursor?”, I hear you say. Yes that is correct, I must admit I was a little shocked at first, I mean I’ve known it for a long time that server based distros are only command line based, but to actually be greeted with it was a culture shock for me.

I’ve been so use to using graphical tools for so long, to actually be greeted with a screen that shows “haz@host:~$” and nothing else was strange. Don’t get me wrong, I’ve used the terminal inside ubuntu for years! Mainly for installing/removing/clearing applications (using aptitude) and possibly copying a few tweaks I’ve read online to help fix problems. I’ve never had to navigate and control a system with only CLI tools before though. I mean think about it, if we got rid of every graphical tool we use today and throw ourselves into a pure terminal – most of us would be lost. We all take for granted what our graphical tools actually do behind the scenes that we never think; what is another way to do this, that the system is probably doing for us.

So that’s how it all began… and you know what, for the first time I feel like I am fully in control of what my system is actually doing. I can’t wait until I feel very comfortable using the terminal to finally migrate my existing server over to Linux. That will be the best day once I finally do it.

Currently I just have Ubuntu Server running in a virtual machine inside my existing server, and to access and control it I’m using a tool called ssh inside of a terminal (or on the rare occasion that I’m in Windows, using PuTTY to access it via ssh).

Anyways, I feel I’ve wrote too much on this post… so I might have to put everything I’ve been using into a separate post. I hope you enjoyed reading this, and I hope you all follow me while I take the plunge and finally start learning some new tools and ways to configure and manage my server. I will migrate my server over to Linux soon, and I can’t wait! I’ve been wanting to do this for a long time but I have been too scared to because of the thought of using only a command line interface. For those of you who are also scared, but would like to setup their own server… best way is to do like what I did, install it in a virtual machine and test all you want. Don’t be afraid to break it, I mean after all its a virtual machine – if things go really wrong, format and try again :).