anchor.diff:  vagrant@vagrant:/vagrant$ sudo chmod 755 YourStudentID-Lab02.sh
   vagrant@vagrant:/vagrant$ ls -l
   total 44
  --rw-r--r-- 1 vagrant vagrant 14183 Feb 20 15:22 example-Instructions.md
  --rw-r--r-- 1 vagrant vagrant  1084 Feb 20 15:22 LICENSE
  +
  +-rw-r--r-- 1 vagrant vagrant   152 Feb 20 15:22 2015-09.adoc
   -rw-r--r-- 1 vagrant vagrant    33 Feb 20 15:22 README.md
  -drwxr-xr-x 1 vagrant vagrant  4096 Feb 20 15:22 resources
   -rw-r--r-- 1 vagrant vagrant   152 Feb 20 15:22 starter.sh
  +-rw-r--r-- 1 vagrant vagrant   296 Feb 20 15:45 Vagrantfile
   -rwxr-xr-x 1 vagrant vagrant   152 Feb 20 15:58 YourStudentID-Lab02.sh
  --rw-r--r-- 1 vagrant vagrant    24 Feb 20 15:33 YourStudentID-testfile.adoc
  --rw-r--r-- 1 vagrant vagrant   296 Feb 20 15:45 Vagrantfile
   ....
   
   Run the script to confirm you can execute it (it's still empty, and will run fine - it just won't do anything):
  
positive.code: 
  We will work with a commercial implementation of the Git platform in this class provided by Github. You can create a free account on Github and host public code repositories, like the one we setup for this lab.
  
  NOTE: Everyone should setup an individual Github account. If you are working in teams, you have the option of either doing the next section individually, or choosing one team member to perform the git forking and cloning tasks.
  
  You will do the exercises in part 2 on the main server, not your VM (which you have now destroyed, right?).
  
  
negative.code: 
  ....
  Vagrant.configure(2) do |config|
    config.vm.box = .....
    config.vm.provision             :shell, path: "./MyStudentID-Lab02.sh"
  end
  ....
  