Completed Console Lab

README.md

@@ -3,6 +3,7 @@
 ## Objectives
 
 1. In this lab students will learn to navigate their file system using only the terminal
+
 2. Students will practice using the following commands to traverse directories and investigate their contents: `pwd`, `ls`, `cd`, `cat`, `less`, `grep`
 
 
@@ -19,22 +20,18 @@ The console (also referred to as the command line, terminal, or shell) is an ess
 - `grep` - search for the specified text or pattern
 
 ### Other commands worth knowing
-
 - `head` - display the first lines of a file
 - `tail` - display the last lines of a file
 
 
 
 ## Unit Test
-
 This lab is an instructional introduction to terminal. There are no unit tests.
 
 ## Pre-lab && Important Notes
-
 It's a good practice to have a directory called `Dev` inside your home directory for all development work. You can create one in Finder (right click -> New Folder) or in the terminal (`mkdir ~/Dev`). This directory will come in handy in case things go horribly wrong, or if you want to back up all of your work. You should always make sure you are working in Dev or a directory inside of it during this course.
 
 ## Instructions
-
 - Open up a terminal (Applications->Utilities->Terminal)
 - Find out what directory you're in using `pwd`
 - You know where you are, but not what's around you. Take a look around with `ls`
@@ -52,13 +49,11 @@ It's a good practice to have a directory called `Dev` inside your home directory
 # Part 2
 
 ## Objectives
-
 1. After this lab students will know how to create, remove, and modify files and directories using the terminal
 3. By completing this lab students will gain exposure to man pages and the use of bash commands with arguments and options.
 
 
 ## Overview
-
 In Part 1 lab you learned to navigate your file system in the terminal. In Part 2 you will learn how to actually make changes to the file system and where to find documentation to get a better grasp on commands you are already familiar with as well as those you haven't seen before. The commands you will practice in this lab are:
 
 - `touch`
@@ -74,14 +69,12 @@ In Part 1 lab you learned to navigate your file system in the terminal. In Part
 
 
 ### Creating files and directories
-
 In lab 1 you learned one way to create a file using the `echo` command and output redirection. That can be useful but there are other methods that make more sense sometimes. Here we'll focus on two other methods:
 
 - the `touch` command.
 - file editors.
 
 #### Creating files with touch
-
 To create a file using touch, simply type the command followed by the name of the file you want to create, like this: `touch filename`. Touch is actually meant to update the timestamp on files, but as a side effect it creates files that are named but don't already exist. It's time to practice `touch`ing files
 
 - Use `touch` to create two files, called myfile1 and myfile2
@@ -91,10 +84,9 @@ To create a file using touch, simply type the command followed by the name of th
 -
 
 #### Editors
-
 There are many text editors out there. We will be using an editor called VIM (short for VI iMproved -- it is a clone of the editor VI with some improvements). Other options that you can explore on your own include emacs and nano (a clone of a program called pico). Here are the VIM commands we'll use along with a few other useful basics (there are many, many, many many more):
 
-- `:w` - Write; writes the current contents of the buffer (editor) to a file. 
+- `:w` - Write; writes the current contents of the buffer (editor) to a file.
 - `:q` - Quit; Quits VIM. Complains if you have unsaved changes (use `:w` first, or `:q!` to force quit and abandon your changes)
 - `:set number`/`:set nonumber` - Enables/disables line numbers.
 - `a` - Switch to insert mode after the current character. `A` goes to the end of the line instead.
@@ -118,8 +110,6 @@ There are many text editors out there. We will be using an editor called VIM (sh
 - Ten copies of the same message might be a bit too much. Move the cursor to line 2 and type `9dd`. You should now see only one line of your message.
 
 #### Creating directories
-
-
 - Use `mkdir` to make a directory with your name
 - make two more directories inside of that one called "dir1" and "dir2"
 - You can make directories in other places than your current directory, without `cd`ing into it, make a directory inside dir1. When you give the location of a file or directory relative to your current position that's called a relative path
@@ -133,7 +123,6 @@ There are many text editors out there. We will be using an editor called VIM (sh
 - The `man` command lets you view the man(ual) pages for any command that is documented. Try viewing the man pages for ls, cp, and mv. Once you've looked at each of these and have a feel for how they are laid out, take another look at the ls man page and see if you can figure out how to view hidden files (remember, hidden files begin with a dot '.' ) <sub>**hint**: viewing man pages is like using less; you can move up and down in the file with the keyboard and when you want to exit you can press the 'q' key*</sub>
 
 ### Destroying files and directories
-
 - Make three files and two directories any way you like; create a file inside one of those directories.
 - The `rm` command deletes files, try using that on one of the files you created.
 - Another way to delete a file is the `unlink` command. Use this to delete the second file.
@@ -145,7 +134,6 @@ There are many text editors out there. We will be using an editor called VIM (sh
 
 
 ### The Art of Redirection
-
 Remember in the previous lab when you typed the command `echo "Hello Terminal" >myfile.txt`? That 'greater than' sign is actually a special character in bash used for redirecting output to a file. There are several of these operators for redirecting output and input. The main redirection operators to be aware of are as follows:
 
 - `<` - Redirects input to come from the specified file. By default input comes from a stream called STDIN (STandarD INput)
@@ -153,9 +141,6 @@ Remember in the previous lab when you typed the command `echo "Hello Terminal" >
 - `>>` - Appends output to the specified file instead of overwriting it
 - `|` - redirects the output from the previous command to be the input of the next command.
 
--
-
-
 - Use the `find` command to search for all files on your machine with "core' in the name. You can do that with `find / -name core`.
 - That's a lot of "Permission denied" errors, and they make it hard to see the useful output from that command. Fortunately that's where output redirection becomes helpful: Those errors all go to STDERR, while the output we want is going to STDOUT. Use the commands above to redirect STDERR to `/dev/null`, effectively throwing away the output from STDERR.
 - That's a little better. We want to search for specific core files in this output, so let's redirect STDOUT to a file called `corefiles.log`.
@@ -163,7 +148,6 @@ Remember in the previous lab when you typed the command `echo "Hello Terminal" >
 - Great, but there's a quicker way to do this without creating a file and running two separate commands. Try using the `|` (pipe) character to redirect the output from `find` to the input for `grep`. Don't forget to throw out the STDERR output; we don't need grep to search through that since we already know it won't contain the files we're looking for.
 
 #### Backgrounding
-
 Did you notice how you had to wait a few seconds every time you ran that find command? Sometimes you may need to use a long-running command and don't want it to lock up your terminal the whole time it's running. That's when you would want to run it in the background (by default, any command you run on a terminal runs in the foreground. Let's play with backgrounding and foregrounding a bit.
 
 - Run that same `find | grep` command that you used in the last step, but add the background operator, `&`, to the end of it. Notice that you immediately get a prompt, but after a few seconds the result of the grep prints to the command line.
@@ -178,7 +162,6 @@ Now let's practice one more backgrounding technique with a different command.
  
 
 ## Other Resources
-
 - For more practice with the basics of the terminal, try the [Command Line Crash Course](http://learnpythonthehardway.org/book/appendixa.html).
 
 - `vimtutor` -- type this command on your command line for a built-in lesson in VIM basics.
@@ -192,4 +175,3 @@ The next lab is [here](https://github.com/Zipcoder/ZCW-Microlabs-Git).
 2. "more or less" http://unix.stackexchange.com/questions/81129/what-are-the-differences-between-most-more-and-less
 3. "Command Line Crash Course" http://learnpythonthehardway.org/book/appendixa.html
 4. "VIM 101" https://www.linux.com/learn/vim-101-beginners-guide-vim
-