From mboxrd@z Thu Jan  1 00:00:00 1970
MIME-Version: 1.0
In-Reply-To: <201102231835.41505.dexen.devries@gmail.com>
References: <AANLkTik7uCQ5XyUeANzs-=x4jat2VW-g1-TtwAhrC+My@mail.gmail.com>
	<AANLkTi=GAh3ZudG7yache-Xg1+=rYCDdD-_E2ZSaGuzH@mail.gmail.com>
	<AANLkTik9Mf8w9cHq136T=DN=hYFmH+zHZLuXc=drdzTr@mail.gmail.com>
	<201102231835.41505.dexen.devries@gmail.com>
Date: Fri, 25 Feb 2011 10:32:27 -0500
Message-ID: <AANLkTi=Pz5vK=NpdR+NT58DScWOGF1OD1Z2SLxXxOL7G@mail.gmail.com>
Subject: Re: [9fans] acme Local command on p9p
From: Russ Cox <rsc@swtch.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Cc: dexen deVries <dexen.devries@gmail.com>
Content-Type: text/plain; charset=UTF-8
Topicbox-Message-UUID: b4d66dbe-ead6-11e9-9d60-3106f5b1d025

> How about reading /proc/$pid/environ (where $pid is the shell spawned for
> command execution) before the $pid exits and transfering all the environment
> variables back to the Acme's own environment?

plan9port runs in more places than linux.