anchor.diff:  
   mkdir -p main/{A/{B,C,D},E/{F,G},H/{I,J/{K,L},M}}
   touch main/{A/{aa,B/bb,C/cc,D/dd},E/{ee,F/ff,G/gg},H/{hh,I/ii,J/{jj,K/kk,L/ll},M/mm}}
  -apt-get install tree
  -apt-get install git
  +apt-get -y install tree
  +apt-get -y install git
   ....
   
   **Automate provisioning with Vagrant**
  
positive.code: Create your script.
  
      vagrant@XXXXX:~/vagrant$ nano YourStudentID-Lab02.sh
  
  Oops, something seems to be wrong when you run it:
  
  
negative.code: vagrant@precise64:~$
  ....
  
  If that worked, congratulations, you did it!
  
  But, what does this all mean?
  
  You now have your own personal Linux machine, operating within the main course server, on which you are the administrator. You have tremendous freedom to experiment with its configuration.
  
  If you damage something, you simply need to exit out to the main server command prompt and run "vagrant destroy." This will erase the machine. You can then run "vagrant up" again and the machine will be restored.
  
  IMPORTANT: If you destroy the VM you will LOSE ALL DATA you have on the machine, unless that data is stored in your ~/vagrant directory (which is mapped to your /vagrant directory in the VM).
  
  DO NOT ATTEMPT to bridge your VM to the external world. It is not hardened and possibly vulnerable. As long as you do not mess with the network configuration, you will be fine. In a future lab, you will see how to run Firefox on the course server in a X11 window over ssh on your local machine, so you can safely browse to your VM.
  
  