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

> Sorry about the confusion. I was looking for any current information
> on how to successfully install 9atom on vmware. What I've found via
> google is very sparse and not recent. From what I am able to gather,
> it sounds like the vmware ATA hardware emulation is severely lacking
> and doesn't agree with what's in 9atom's sdata.c. It's a starting
> point, though. Does that help?

http://9atom.org has some information.

9atom is the system we use every day.  it should be the same as sources,
except when that's not possible.  obviously there is a little skew, too.
this is generally because we need more hardware support, or additional
programs.  but it also leads 9atom to have full support for amd64.
(it's the default platform here.)  and lead 9atom to have full 21-bit rune
support in 2010.

the reason 9atom is out there is to help people use plan 9.  more hardware
support is better, so patches are welcome.  new ideas are good, too.  but
since 9atom is the basis for production systems, care is necessary.

all changes (except binaries) are submitted through patches.  if you're
curious, add this to 9fs.  (9fs -a forces authentication; useful for sources.
nflag is its converse, which is the default.)


	nflag=-n
	if(~ $1 -a){
		shift
		nflag=()
	}
	if(~ $1 -m)
		shift
	switch($1){
[...]
	case atom
		# import -E ssl atom.9atom.org /n/atom /n/atom
		srv $nflag -q tcp!atom.9atom.org atom &&
			mount $nflag /srv/atom /n/atom atom
	case atomdump
		# mount $nflag
		9fs atom && mount /srv/atom /n/atomdump atomdump
[...]

the atom patch programs are then in /n/atom/plan9/rc/bin/apatch.
the interface is very similar to sources patches.  so patch(1) will be
a good overview.

- erik



      parent reply	other threads:[~2013-10-06 21:43 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
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 [this message]

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=3fd76956a855cd5a7a3c247091ddd62a@coraid.com \
    --to=quanstro@labs.coraid.com \
    --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).