anchor.diff:  
   Start out by copying the starter.sh script to a new file, and then set the file permissions to allow execution.
   
  - vagrant@xenial64:/vagrant$ cp starter.sh YourStudentID-Lab02.sh
  - vagrant@xenial64:/vagrant$ sudo chmod 755 YourStudentID-Lab02.sh
  + vagrant@XXXXXX:/vagrant$ cp starter.sh YourStudentID-Lab02.sh
  + vagrant@XXXXXX:/vagrant$ sudo chmod 755 YourStudentID-Lab02.sh
   
   Yes, you can use sudo (administrative privileges) *within your VM.* If you get an error, it means you are likely not in your VM, but back out on the course server.
   
   Remember to substitute your actual ID for "YourStudentID."
   
   ....
  -vagrant@vagrant:/vagrant$ sudo chmod 755 YourStudentID-Lab02.sh
  -vagrant@vagrant:/vagrant$ ls -l
  +vagrant@XXXXXX:/vagrant$ sudo chmod 755 YourStudentID-Lab02.sh
  +vagrant@XXXXXX:/vagrant$ ls -l
   total 44
   
   -rw-r--r-- 1 vagrant vagrant   152 Feb 20 15:22 2015-09.adoc
  
positive.code: 
  Exit the Vagrant instance (now back on the class server prompt) and destroy your Vagrant virtual machine:
  
      vagrant@vagrant:/vagrant$ exit
  	logout
  	Connection to 127.0.0.1 closed.
  	YourStudentID@serverXXX:~/examples$ vagrant destroy
  
  Notice that your script is still in your ~/examples directory. Again, all files in the /vagrant directory on your virtual machine were mapped to the ~/examples directory on the host server.
  
  
negative.code: When you are satisfied, push your local repository back into your Github account (also known as the origin).
  
  ....
  vagrant@XXXXXX:/vagrant$ git push origin master
  Username for 'https://github.com': YourGithubID
  Password for 'https://YourGithubID@github.com':
  Counting objects: 8, done.
  