anchor.diff:  === Applying Your Personal Customizations
   The system will look for an environment variable named `USER_PLAYS`.  If the shell running Vagrant specifies the variable such that it points to an Ansible project on GitHub, the plays will be run and the changes applied.  For example `export USER_PLAYS=kurron/ansible-pull-desktop-tweaks.git` will result in https://github.com/kurron/ansible-pull-desktop-tweaks[this playbook] getting run.  If the environment variable does not exist, the custom provisioning step is not run.
   
  -IMPORTANT: use a **copy** of the project if you decide to apply customizations. If you reference this project, you will get somebody else's customizations, including Git configuration, which most certainly you do not want.
  +IMPORTANT: use a **copy** of the project if you decide to apply customizations. If you use the project referenced in the example, you will get somebody else's customizations, including Git configuration, which most certainly you do not want.
   
   === Customizations: Linux Example
   1. create and/or edit `~/.bash_profile`
  
positive.code: * https://www.vagrantup.com/[Vagrant] installed and working
  * https://www.virtualbox.org/[VirtualBox] installed and working
  * https://www.virtualbox.org/wiki/Downloads[VirtualBox Extension Pack] installed into VirtualBox
  * **https://en.wikipedia.org/wiki/X86_virtualization[Virtualization support] enabled in your BIOS**
  * a working internet connection
  * Your corporate VPN running (if you want to apply some work-specific plays)
  
  IMPORTANT: if you don't enable virtualization support in your BIOS, VirtualBox will not run correctly.
  
  == Building
  All the components of the environment live in repositories on the internet so there is nothing to build. **UPDATE:** some people have experienced issues when rebuilding a box due to flaky networks, online assets moving to different locations or installation processes changing.  When you need your box, you need your box and you don't have the time to troubleshoot an installation issue.  To combat this problem, we've decided to change the build model and bake in much of the software into the base image.  The trade-off we've made to ensure quick and stable rebuilds is a larger initial download.  All boxes are currently housed in https://app.vagrantup.com/kurron[HashiCorp's Vagrant Cloud] repository.
  
  == Installation
  Use Git to clone this project, go into the project folder and type `vagrant up` and go get a cup of coffee.  The construction time of the box greatly depends on your internet speeds.
  
negative.code: Sometimes networks fail or mirror sites go down. If you experience a failure, you can attempt to resume the construction by issuing `vagrant provision` at the command line.  Vagrant will attempt to start over, but will skip any provisions that have already taken place.
  
  === Cannot Acquire Repository Lock
  TIP: we've altered some of the installation logic to perform the retry logic described below automatically so you probably don't have to worry about this scenario any longer.
  
  One of the first steps is to update the APT repositories via `apt-get update` which every once in a while can fail. What appears to happen in those cases is that the Ubuntu GUI has already acquired the lock and is running the update on its own.  The solution is to wait a bit and then reset the environment so that provisioning can continue.  This issue will manifest in "Ansible is not installed" errors.
  
  