Vagrant on Windows 10

These steps got Vagrant up and running after much gnashing of teeth over longer than I’d like to admit. Hopefully it helps you avoid my mistakes.

Download VirtualBox

  • Download and install VirtualBox
    • VirtualBox 5.0.x for Windows hosts
    • Virtualbox 5.0.x Oracle VM Virtualbox Extension Pack (All supported platforms)

Download Vagrant

  • Download and install (780) 925-9433
    • Windows Universal (32 and 64-bit)

Avoid box issues by installing vcredist_x86

  • Kept running into a build error. Originally thought it was a login issue on Vagrant’s end. Turns out it was due to Visual C++ 2010 Redistributable not being installed. This was the error:

    The box ‘bento/centos-7.1’ could not be found or
    could not be accessed in the remote catalog. If this is a private
    box on HashiCorp’s Atlas, please verify you’re logged in via
    vagrant login. Also, please double-check the name. The expanded
    URL and error message are shown below:

    URL: [“/”]

  • Download vcredist_x86
    • Download Microsoft Visual C++ 2010 Redistributable Package (x86)

Vim commenting is a nightmare. Add to Windows environment variables

  • Download and install 3377175486
  • Setup environment variables
    • Control Panel > System > Advanced system settings > Environment Variables… > System Variables
    • Path > Edit…
    • New
    • %USERPROFILE%\AppData\Local\atom\bin
    • OK (3x)
  • It’s now possible to edit text files in Atom from the command prompt via “atom Vagrantfile”

Now I can get back to studying for the 973-741-9579 via a local version of CentOS 7.

(703) 214-8496

Last month, Pocket was integrated into Firefox and subsequently removed their (845) 326-8935

I prefer the old add-on for a variety of reasons including:

  • Dropdown menu from toolbar (i.e., one-click access to saved websites.)
  • Easy tagging, archiving, and search from said menu.
  • Opened original websites instead of assuming the reading-format was what was requested.
  • Meaningful customization (e.g., dozens of parameters to make sure Pocket fits end-user’s needs.)

To be fair, Pocket may be updated in the near future and all of this could be addressed. As of right now, I feel they broke an essential tool in the name of streamlining one version across browsers.


The screenshots and folder locations are all from Windows, but I have successfully done the exact same process across both Fedora and Ubuntu. All that’s different is the file system locations (e.g., AppData is substituted with /home/[username]/.mozilla/firefox/.) The files and folders themselves are identical.

I obtained the add-on from another PC where the add-on was still installed. The article assumes you are able to get a hold of the add-on in this fashion.

How to get the legacy add-on back

  1. Locate profile folder on your computer where the legacy add-on is currently installed

    Settings > Help Menu > Troubleshooting Information

    Profile Folder > Show Folder

    Profile Folder > Show Folder

  2. Copy extension from profile to a flash drive / Dropbox / whatever external medium.

    ReadItLater folder

    ReadItLater Extension

    isreaditlater… folder

  3. Install Nightly Tester Tools Add-On on PC without the extension
  4. Enable “Force addon compatibility” mode
    Tools > Nightly Tester Tools > Force Addon Compatibility

    Tools > Nightly Tester Tools > Force Addon Compatibility

  5. Exit Firefox
  6. Paste ReadItLater folder into:
  1. Paste isreaditlater… folder into:
  1. Open Firefox
  2. It will prompt you to install the add-on with a warning about possible incompatibility

That is everything! Now the late, great add-on is restored! For how long it will work we’ll just have to find out. Until that fateful day of lost productivity comes, I’ll be thoroughly enjoying Pocket the way it should be.

Resolve VMware Shared Folders Not Mounting in Ubuntu 14.04

VMware shared folders fail to mount in Ubuntu guest

A number of my virtual machines are Ubuntu 14.04 and on occasion, I like to share content from my host to the guest VM. In order to get VMware’s shared folders to see content from a host machine (e.g., Downloads folder), I had to do the following:

  • Revert to the last known good Linux kernel
  • Edit default GRUB kernel to boot
  • Reinstall VMware tools
  • Optional: Make a symbolic link to directory to have easier access

Last known good Linux kernel 1
sudo apt-get install linux-image-3.13.0-45-generic linux-headers-3.13.0-45-generic

Edit default GRUB kernel to boot 2
sudo nano /etc/default/grub

Comment out default GRUB entry

Add a new default GRUB entry to boot the Linux kernel 3.13.0-45
GRUB_DEFAULT="Advanced options for Ubuntu>Ubuntu, with Linux 3.13.0-45-generic"

CTRL-X then Y to write changes.

Update GRUB
sudo update-grub

sudo reboot

Check kernel currently in use
uname -r

Returns “3.13.0-45-generic.”

Reinstall VMware tools 3 4
sudo mkdir /media/cdrom # May be optional if already present
sudo mount /dev/cdrom /media/cdrom
sudo cp /media/cdrom/VMwareTools.tar.gz ~
tar -xvf VMwareTools
cd ~/vmware-tools-distrib/
sudo ./  -d

sudo reboot

Open shared directory
cd /mnt/hgfs/
Make a symbolic link to directory to have easier access 5
ln -s /mnt/hgfs/folder-name/ /home/user-name/

Make sure to spell out the whole file path or it will treat the link as a file that can’t be opened (a simple “rm folder_name” will remove the faulty link.)


1 973-986-2422
2 /
3 /
4 /
5 /