ugh... I completely spaced re /dev being the linux device directory. My intent was to define to neutral directory to nav to for various projects located under my host machine's ~/.../dev directory. I tweaked that to a better name and it works as expected. Thanks for helping!
On Tuesday, February 25, 2014 3:32:50 PM UTC-8, Damon Rolfs wrote: > > I'm using VMWare Fusion 6.0.2; Vagrant 1.4.3 > > I've been using vagrant-vmware for a dev project for weeks without issue. > A couple days ago I wanted to reset the machine via the vagrant destroy and > up. Since this refresh, while I have not been able to completely ssh into > the machine. My bash shell doesn't seem to set up correctly, so I get > something like the following: > > >> *dr@DR-MBP:~/dev/project/setup/dev$ vagrant ssh*Welcome to Ubuntu >> 12.04.1 LTS (GNU/Linux 3.2.0-29-virtual x86_64) >> * Documentation: https://help.ubuntu.com/ >> >> *bash -i*bash: no job control in this shell >> *vagrant@precise64:~$* > > > Running ssh using VAGRANT_LOG=debug doesn't show any warnings, errors. > Info and debug statements look okay, but I don't know what I don't know. > > I have other vagrant-vmware projects where I have left the existing box, > and I am able to ssh into it as expected. I originally derived the working > Vagrantfile from the problem project, and while there are minor differences > in a couple of specific settings (e.g., private_network subnet) I cannot > determine a material variation. > > Any help / ideas to troubleshoot is greatly appreciated! > > Thanks in advance, Damon > > > -- You received this message because you are subscribed to the Google Groups "Vagrant" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
