From mboxrd@z Thu Jan  1 00:00:00 1970
Date: Sun, 11 Apr 2010 11:47:49 -0600
To: "Devon H. O'Dell" <devon.odell@gmail.com>, <ebo@sandien.com>,
	"Fans of the OS Plan 9 from Bell Labs" <9fans@9fans.net>
From: "EBo" <ebo@sandien.com>
Message-ID: <twig.1271008069.94955@swcp.com>
In-Reply-To: <h2q9ab217671004111042sae10559bt1fc49705a8d8b7e7@mail.gmail.com>
References: <46914d2c-437d-406e-a928-123f4d09f9f7@u15g2000prd.googlegroups.com>
	<p2k4f34febc1004072053j897a36d0k569658fc8dc80917@mail.gmail.com>
	<twig.1271005595.61308@swcp.com>
	<93c7f0c907631447ddb00c5d9280f5eb@brasstown.quanstro.net>
	<twig.1271007154.39834@swcp.com>, <twig.1271007154.39834@swcp.com>
Subject: Re: [9fans] 9vx patch to read environment var PLAN9
Topicbox-Message-UUID: feef4dc2-ead5-11e9-9d60-3106f5b1d025

Got it!  Changed.  I'll also change it along the lines of Erik's suggestion.

As a note, I thought that 9vx ran on top of the p9p stuff.

  Thanks again,

  EBo --


"Devon H. O'Dell" <devon.odell@gmail.com> said:

> 2010/4/11 EBo <ebo@sandien.com>:
> > I thought p9p uses it for the root of the Plan 9 tree? �At least that is what
> > the ebuilds imply. �Maybe I am using the wrong term for what PLAN9 points to.
>
> That's true, but in the case of 9vx, the tree it points to contains
> actual plan 9 binaries, whereas p9p binaries are compiled for the host
> system. Since it is very feasible that someone may run p9p and 9vx on
> the same machine (I do, for instance), it would be a good idea to not
> overload the env var.
>
> --dho
>
> > �EBo --
> >
> >
> > erik quanstrom <quanstro@quanstro.net> said:
> >
> >> recommend using a different environment variable
> >> other than PLAN9, since that is taken by p9p to mean
> >> something else.
> >>
> >> - erik
> >>
> >
> >
> >
> > --
> >
> >
> >
> >
> >
>



--