anchor.diff:  1. `vagrant up` to build the new box
   
   === RAM and CPU Settings
  -If you examine the `vagrantfile` file, you will see that the virtual machine is configured to use 6GB of RAM and
  -2 CPUs.  Feel free to change these values to match your computer's hardware.
  +If you examine the `vagrantfile` file, you will see that the virtual machine is configured to use 6GB of RAM and 2 CPUs.  Feel free to change these values to match your computer's hardware.
   
   === Low Disk Space
  -If an environment is used long enough, it is likely to run out of disk space.  The two main culprits are kernal updates
  -filling up the `/boot` partition and Docker images filling up the `/var/lib/docker` partition.  You have at least 3 options:
  +If an environment is used long enough, it is likely to run out of disk space.  The two main culprits are kernel updates filling up the `/boot` partition and Docker images filling up the `/var/lib/docker` partition.  You have at least 3 options:
   
   * throw away the environment and start fresh
   * clean up the old kernels via `sudo apt-get autoremove`
  
positive.code: 1. `ctrl-c` to exit the session
  
  === Docker-based IDEs
  We've deprecated the use of Docker-based IDEs.  We've found that projects that produce and consume Docker images can be
  challeging when running from within a container.  If Docker in Docker ever becomes mainstream, we'll look into switching back.
  
  === Applying Your Company Specific Customizations
  The system will look for an environment variable named `CORPORATE_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 CORPORATE_PLAYS=kurron/ansible-pull-transparent.git` will result in
  [this playbook](https://github.com/kurron/ansible-pull-transparent.git) getting run.  If the environment variable does
  not exist, the custom provisioning step is not run.
  
  === 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
  [this playbook](https://github.com/kurron/ansible-pull-desktop-tweaks) 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.
  
  === Customizations: Linux Example
  1. create and/or edit `~/.bash_profile`
  
negative.code: ```
  
  === I've upgrade to kurron/xenial-xubuntu:5.1.28 and things are acting weird
  As of October 1, 2017, the 5.1.28 box has not been officially announced because the switch over from JDK 8 to JDK 9 is still undergoing tests.  If you upgraded and are seeing odd behavior, there are a few simple edits to fix things.
  
  === IDE Desktop Launchers
  Right mouse click on your IDE's desktop icon and select `Properties` and then the `Launcher` tab.  You'll need to edit the `Command` to point to JDK 8. Here is an example for the PyCharm launcher `env PYCHARM_JDK=/usr/lib/jvm/jdk-8 /home/vagrant/Software/pycharm/bin/pycharm.sh`. If you are **not** doing any JVM development, then this is all you need to do.
  
  === JVM Developers
  JVM developers will need to get `JAVA_HOME` and other environment variables to point to JDK 8.  To do this, edit two files:
  
  * /etc/environment
  * /etc/profile.d/default-jdk-environment.sh
  
  Once those are changed, log out and back in again and run `echo $JAVA_HOME` and `java -version` to verify your changes.
  
  ## Where did `/vagrant` go?
  There is http://stackoverflow.com/questions/42074246/vagrant-error-unable-to-mount-virtualbox-shared-folders-guest-additions-vboxs[an issue with Windows 10 and VirtualBox 5.1.16] that prevents Vagrant from starting properly.  As a workaround, we've disabled sharing of folders.  Non-Windows users can edit the `vagrantfile` and re-enable the mount if desired.
  
  **UPDATE:** the issue has been resolved in VirtualBox 5.1.18.  The `/vagrant` folder is now mounted as usual.
  
  === Vagrant Asks Me Which Network Interface To Bind To
  By default, the box is configured to join the local network as a fully accessible machine. The `desktop.vm.network "public_network"` in the `vagrantfile` is the key to this.  If you have multiple networks available on your machine, running a VPN for example, Vagrant needs to know which network you want to put your Vagrant box onto and will wait until you give it guidance.
  
  ```
  ==> desktop: Setting the name of the VM: jvmguy.desktop
  