9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] VMware and 9atom
Date: Sun,  6 Oct 2013 17:02:00 -0400	[thread overview]
Message-ID: <03f9d57fe00bfad0e6eae5355b51951f@ladd.quanstro.net> (raw)
In-Reply-To: <CAH7AAvpqFUcU=MfvgBv=Ssd4Z-Z-B6dT_X7=2Kf3dkFP+6TA6w@mail.gmail.com>

> >> > Has anyone been able to install 9atom on any version of VMware
> >> > Workstation? If so, would you please share the settings you used to
> >> > get it working. I am trying to setup a go dev environment and need
> >> > 9atom for python 2.7.
> >
> > sorry about that.  the last time i messed with vmware, ended up being
> > a large waste of time because vmware networking didn't do what i needed.
>
> I understand why you'd see vmware as a waste of time. It is indeed
> problematic on a few fronts.

i don't mean to give that impression.  vmware can be a great solution.
but when i've wanted to use it, it was impossible.  the virtual networking
does not always play nicely with l2 protocols.

it's one of the thousand things i really need to get around to.  :-)

- erik



  reply	other threads:[~2013-10-06 21:02 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-06 19:33 Christopher Nielsen
2013-10-06 19:49 ` Matthew Veety
2013-10-06 19:56   ` Christopher Nielsen
2013-10-06 20:21     ` Jacob Todd
2013-10-06 20:35       ` Christopher Nielsen
2013-10-06 20:42         ` Jacob Todd
2013-10-06 20:44         ` cinap_lenrek
2013-10-06 20:32   ` erik quanstrom
2013-10-06 20:48     ` Christopher Nielsen
2013-10-06 21:02       ` erik quanstrom [this message]
2013-10-06 21:02       ` erik quanstrom
2013-10-06 21:08         ` Christopher Nielsen
2013-10-06 21:10           ` Jacob Todd
2013-10-06 21:14             ` erik quanstrom
2013-10-06 21:15             ` Christopher Nielsen
2013-10-07  4:43             ` Jens Staal
2013-10-09 19:52               ` Terry Wendt
2013-10-09 20:08                 ` Matthew Veety
2013-10-09 20:10                   ` Shane Morris
2013-10-09 20:13                   ` erik quanstrom
2013-10-09 20:25                     ` Matthew Veety
2013-10-09 20:34                     ` Terry Wendt
2013-10-09 21:02                       ` Deepak Chawla
2013-10-09 22:15                         ` Bakul Shah
2013-10-09 23:07                           ` Terry Wendt
2013-10-09 23:19                             ` Kurt H Maier
2013-10-10 15:08                             ` David du Colombier
2013-10-10 15:54                               ` Richard Miller
2013-10-10 16:03                                 ` Aram Hăvărneanu
2013-10-10 16:16                                   ` Bakul Shah
2013-10-10 20:05                                   ` Steffen Daode Nurpmeso
2013-10-09 22:19                         ` Christopher Nielsen
2013-10-09 22:51                           ` erik quanstrom
2013-10-10  0:02                       ` blstuart
2013-10-06 21:13           ` Aram Hăvărneanu
2013-10-06 21:20             ` Christopher Nielsen
2013-10-06 21:43       ` erik quanstrom

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=03f9d57fe00bfad0e6eae5355b51951f@ladd.quanstro.net \
    --to=quanstro@quanstro.net \
    --cc=9fans@9fans.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).