On Jul 8, 2011, at 3:00 PM, Phil Hagelberg wrote:
>
> Maybe a "troubleshooting" section at the bottom of the readme? Sounds
> good to me; feel free to issue a pull request.
I don't have the expertise to write such a thing.
In other news, I've now done "vagrant up" in the directory containing the
readme, and a long installation ensued ending with:
[default] Copying client components to /root/.config/jark
[default] Copying server components to /root/.cljr
[default] Installed successfully.
but I'm not sure if it's really done or not because it didn't return to the
shell (I get no new prompt).
In any event I opened another Terminal window to try to proceed with the next
steps and got:
lee-spectors-macbook-pro:~ leespector$ vagrant ssh
No Vagrant environment detected. Run `vagrant init` to set one up.
So I did:
lee-spectors-macbook-pro:~ leespector$ vagrant init
create Vagrantfile
And then:
lee-spectors-macbook-pro:~ leespector$ vagrant ssh
The local file Vagrant uses to store data ".vagrant" already exists
and is a directory! If you are in your home directory, then please run
this command in another directory. If you aren't in a home directory,
then please rename ".vagrant" to something else, or configure Vagrant
to use another filename by modifying `config.vagrant.dotfile_name`.
So I did:
lee-spectors-macbook-pro:~ leespector$ mkdir vagrant-foo
lee-spectors-macbook-pro:~ leespector$ cd vagrant-foo/
But still:
lee-spectors-macbook-pro:vagrant-foo leespector$ vagrant ssh
The local file Vagrant uses to store data ".vagrant" already exists
and is a directory! If you are in your home directory, then please run
this command in another directory. If you aren't in a home directory,
then please rename ".vagrant" to something else, or configure Vagrant
to use another filename by modifying `config.vagrant.dotfile_name`.
Not sure what to do next.
BTW early in the long output from "vagrant up" I saw:
[default] The guest additions on this VM do not match the install version of
VirtualBox! This may cause things such as forwarded ports, shared
folders, and more to not work properly. If any of those things fail on
this machine, please update the guest additions and repackage the
box.
I don't know if this may be responsible for my current impasse and/or if how it
will effect the process of working with this setup if I ever get it working; I
don't have experience with VirtualBox and I don't have a sense of how files can
be moved/shared between OSes.
-Lee
--
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clojure@googlegroups.com
Note that posts from new members are moderated - please be patient with your
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
