From mboxrd@z Thu Jan 1 00:00:00 1970 From: dexen deVries To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Date: Wed, 23 Feb 2011 18:35:41 +0100 User-Agent: KMail/1.13.5 (Linux/2.6.38-rc5-19+; KDE/4.5.5; x86_64; ; ) References: In-Reply-To: MIME-Version: 1.0 Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Message-Id: <201102231835.41505.dexen.devries@gmail.com> Subject: Re: [9fans] acme Local command on p9p Topicbox-Message-UUID: b3b66d76-ead6-11e9-9d60-3106f5b1d025 On Wednesday 23 of February 2011 18:09:42 Russ Cox wrote: > > I'm unsure if this conversation is about Plan 9 or plan9port, but in > > any case I've used Local for lots of other things on Plan 9, > > particularly name space manipulations. There, I don't understand why > > it needs restrictions. > >=20 > > Or are you just saying that on plan9port you need to do magic so you > > might as well catalog the tricks? In that case, I understand. >=20 > Yes, the idea is that on plan9port you might change > the implementation of Local to pick off var=3Dvalue > and cd path and run those internally. It could still > shell out for other commands like Local echo $foo. How about reading /proc/$pid/environ (where $pid is the shell spawned for=20 command execution) before the $pid exits and transfering all the environmen= t=20 variables back to the Acme's own environment? I'm not sure, but I think that /proc/$pid/environ should be accessible for= =20 Acme after exit() by the $pid, but before Acme's waitpid($pid, ...) complet= es. =2D-=20 dexen deVries [[[=E2=86=93][=E2=86=92]]] > how does a C compiler get to be that big? what is all that code doing? iterators, string objects, and a full set of C macros that ensure boundary conditions and improve interfaces. ron minnich, in response to Charles Forsyth http://9fans.net/archive/2011/02/90