Quickstart for Unix


This past week I was suddenly thrown into doing some work in Solaris.  My task was to install some server software.  Solaris is a Unix based system so this meant that I had to learn Unix quickly.

I've taken courses in college related to Unix and Linux based systems but as with anything,  in a classroom you only do enough to pass the course but not as much as you would in a real world environment.

Moving around the Unix command line and inspecting and modifying files was a bit painful but after a little bit of practice I was able to get through it.

Here are some of the hurdles I ran into and some of the resources that I found to get over them.

The Unix Command Line

In Solaris the command line is anything but unavoidable. Solaris has a GUI but if you want to do anything significant the command line is the way.  The command line will help you move around the folder structure. It will help you move and manipulate files and execute shell scripts that may be part of software your need to install or run.

I found this tutorial: Unix in 10 Minutes invaluable. You can literally learn Unix in 10 minutes with this tutorial.  After those 10 minutes, you can use it as a reference or cheat sheet.


The VI Editor

You can view the contents of text files right from the command line using commands such as cat, more and less.  Those commands are good for reading but what if you need to modify a shell script or a code file?  For that you will need to use the VI editor.  My recommendation before you start modifying files in VI is this:

1. Back up the file that you will be modifying before you begin editing.  If you don't back up your file you can really screw up the file and there will be no going back.  To back up the file look up the copy command in the Unix command line tutorial. It goes something like this:

$:cp  myfile.txt myfile.backup.txt

If you find that you did screw up the file, you can always recover it since you made a back up.

2. Take this course: Using the VI Basics on youtube and practice a significant bit before you start modifying any files. This was a very painful process for me until I started getting the  basics of VI. I had to force quit out the file many times because I would screw up the file and not know what I had changed in the file.

3. Once you have taken the course you can use this Cheat Sheet to help you along once you start using the VI editor.

The resources above got me moving rather quickly.  Hopefully the will the same for you.  With these few tools you should know enough to get you moving quickly through the Unix command line.



Comments

Post a Comment

Popular posts from this blog

Putting Files on the Rackspace File Cloud

Recently, I’ve been playing around with Asp.Net MVC and I (along with some friends) am creating an Asp.Net MVC application that can access files from our website. This means that files must display on the site as well as provide a way to download/upload them. I won’t give away all the details of the project but I will say this: Sharing photos is one of the driving forces for our project.  The files are only image type files( jpg, etc) The files must be uploaded by the users and stored somewhere within our system.  We don’t necessarily know at this time how much storage space we need but we think that we will need a little at first but possibly a lot more down the road. This means that the storage of these files must be scalable. The uploading of files must be controlled by our system.  Right off the bat we started our application and were uploading files to the web server with no problem.  We only did it this way to kind of prove our system model. We were just basically writing
Read more

Setting Up XnaMobileUnit to run unit tests in Windows Phone 7 XNA Games

Image
Introducing XnaMobileUnit I decided to roll my own unit test framework for Windows Phone 7 XNA games.   I have a couple of reasons why I decided to roll my own.  Among them was the fact that you cannot reference regular .Net assemblies from Windows Mobile Framework.  That means that referencing NUnit was out of the question.  Also using some of the other libraries that can be used for Silverlight Applications didn't quite feel right for me. The framework that I have created, XnaMobileUnit, is very simple to use and provides all the necessary functionality to run unit tests.  I am still working on the framework to provide a few more capabilities and features, but for the most part it is ready to use out of the box.  XnaMobileUnit is open source licensed under the Apache 2.0 License and can be downloaded from http://code.google.com/p/xna-mobile-unit/ .  I recommend downloading the latest source and compiling it then referencing the new DLL. Otherwise you can simply download the l
Read more

Reasons to Stay Away from CSLA

We've been using CSLA - Component-based Scalable Logical Architecture in a product for approximately one year and while it solves quite a few problems it violates some major good practices. No Clear Separation of Layers While at the time that we chose CSLA we knew very little about domain driven design, it is no excuse for the framework to possess the data access layer within the business object. This makes it extremely difficult to separate the concerns. As a result, it is difficult to mock the data-access layer creating many problems when attempting to perform unit tests. This also puts the additional responsibility of data access on the business object class, violating the Single Responsibility Principle( SRP ). Data access layer should be totally separated from the business object period. Having the data access within the within the BO class is not the only additional responsibility placed on the class but is the most significant one I can think of. No Context Validation
Read more