/boot was NOT mounting for the Original OS. Fixed

This was a problem because if there was a kernel update for both the
RAM Session and the Original OS, this is what would happen:

-RAM Session updates, and puts new kernel on real /boot
-Original OS updates, and puts new kernel on fake /boot
-Original OS automatically runs 'update-grub' after kernel
	updates, which writes the new grub.cfg to fake /boot
-After everything unmounts and you reboot, the fake grub.cfg
	that has the Original OS using the new kernel is NOT
	read, and the real boot's grub.cfg still has the
	Original OS using the old kernel