anchor.diff:  Clone the Github repository you forked as "example" to your home directory /home/student/YourID/.
   
   ....
  +YourStudentID@serverXXX:~$:~$ git clone https://github.com/YourGithubID/example
   Cloning into 'example'...
   remote: Counting objects: 6, done.
   remote: Compressing objects: 100% (3/3), done.
  
positive.code: [more]
  ....
  
  You may get the following prompt. It is a bug of some sort I have not been able to figure out. 50 points for anyone who can fix it. Type "vagrant" to move past it:
  
  ....
  Text will be echoed in the clear. Please install the HighLine or Termios libraries to suppress echoed text.
  vagrant@127.0.0.1's password:vagrant
  
  [ ... a whole lot of stuff ... ]
  stdin: is not a tty
  ==> default: Checking for guest additions in VM...
  ==> default: Mounting shared folders...
      default: /vagrant => /home/student/YourStudentID/example
  ....
  
  **Script your work**
  
  Go into your VM:
  
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.
  
  