From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <6f9638a5b39fcfeba12510c418feed10@plan9.escet.urjc.es> To: 9fans@cse.psu.edu Subject: Re: [9fans] /sys/src/cmd/ps.c From: "Fco. J. Ballesteros" Date: Thu, 2 Sep 2004 09:45:59 +0200 In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="upas-imtynymwndtbrzefztnwkgrhgv" Topicbox-Message-UUID: db914bda-eacd-11e9-9e20-41e7f4b1d025 This is a multi-part message in MIME format. --upas-imtynymwndtbrzefztnwkgrhgv Content-Disposition: inline Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit You could have used also something like rfork n bind $1 /proc shift ps $* without having to open a new window. --upas-imtynymwndtbrzefztnwkgrhgv Content-Type: message/rfc822 Content-Disposition: inline Received: from mail.cse.psu.edu ([130.203.4.6]) by aquamar; Thu Sep 2 08:46:41 MDT 2004 Received: from psuvax1.cse.psu.edu (localhost [127.0.0.1]) by mail.cse.psu.edu (CSE Mail Server) with ESMTP id 159F018367 for ; Thu, 2 Sep 2004 02:46:35 -0400 (EDT) X-Original-To: 9fans@cse.psu.edu Delivered-To: 9fans@cse.psu.edu Received: from localhost (localhost [127.0.0.1]) by mail.cse.psu.edu (CSE Mail Server) with ESMTP id 99F31181C0 for <9fans@cse.psu.edu>; Thu, 2 Sep 2004 02:46:27 -0400 (EDT) Received: from mail.cse.psu.edu ([127.0.0.1]) by localhost (psuvax1 [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 20128-03-6 for <9fans@cse.psu.edu>; Thu, 2 Sep 2004 02:46:26 -0400 (EDT) Received: from cackle.proxima.alt.za (cackle.proxima.alt.za [196.30.44.141]) by mail.cse.psu.edu (CSE Mail Server) with ESMTP id 01D71179FA for <9fans@cse.psu.edu>; Thu, 2 Sep 2004 02:46:25 -0400 (EDT) Received: from huddle.proxima.alt.za (prawn.iba.co.za [192.168.30.22]) by cackle.proxima.alt.za (8.12.8/8.12.3) with ESMTP id i826kJMN027413 for <9fans@cse.psu.edu>; Thu, 2 Sep 2004 08:46:21 +0200 (SAST) Message-ID: To: 9fans@cse.psu.edu Organization: Proxima Research & Development X-Mailer: Plan 9 ACME/Mail Date: Thu, 2 Sep 2004 08:44:04 +0200 From: lucio@proxima.alt.za MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at cse.psu.edu Subject: [9fans] /sys/src/cmd/ps.c X-BeenThere: 9fans@cse.psu.edu X-Mailman-Version: 2.1.5 Precedence: list Reply-To: lucio@proxima.alt.za, Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu> List-Id: Fans of the OS Plan 9 from Bell Labs <9fans.cse.psu.edu> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: 9fans-bounces+nemo=lsub.org@cse.psu.edu Errors-To: 9fans-bounces+nemo=lsub.org@cse.psu.edu I've (trivially) added a "-f procdir" option to ps(1) so that I could use a different source for the /proc information. It would have been as easy to spawn a new window and import the remote /proc in it, but I'm sure I'm not the only person who feels they may want access to the local and the remote /proc simultaneously. Is it worth documenting the option and submit a patch? ++L --upas-imtynymwndtbrzefztnwkgrhgv--