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

Simple Example of Using Pipes with C#

Image
So I decided to dig into understanding how Asp.net works under the hood, out of curiosity.  In the articles that I found the authors described the architecture in lower level details.  One of the things that caught my eyes was the use of named Pipes as a means of inter-process communications by the architecture.   So I decided to dig into that portion a little bit deeper.  I discovered that the .Net framework has a namespace for named pipes and it's quite easy to use. I intend to demonstrate a small example that I cooked up rather quickly by setting up a named pipe server and then connecting a pipe client to it.  Before I do that, I want to say as a disclaimer that I don't know that this example demonstrates the best way to use pipes.  What it does do is show the most straightforward way to use them.  Also, before you use pipes you should consider using something else like WCF instead if you need well defined interfaces, as using pipes is pretty raw.   Being the type of perso
Read more

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

Why I Hate Regular Expressions

I have a love-hate relationship with regular expressions.  I admire their power yet I hate the pain and agony they have caused on more than one occasion. Just recently one of my colleagues used a regular expression for validating passwords. It seems pretty fair to use regular expressions for validating character sequence patterns. After all it seems they were created exactly for that.  However when regular expressions fail they fail hard.  What I mean by that is that they usually fail in the production environment. In case you are wondering what a regular expression is take a look at the wikipedia explanation of regular expressions . So we go live and all of a sudden new users can't be created because the regular expression says that the password is not valid due to one of the complexity rules.  But how?  The regular expression passed all the unit tests.  In fact the application works fine in our development and test deployment.  So what happened? The validation works fine unti
Read more