From: Akshat Kumar <akumar@mail.nanosouffle.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Distributed Pipelines
Date: Mon, 26 Apr 2010 00:33:04 -0700 [thread overview]
Message-ID: <z2tfe41879c1004260033q204491f4zfc717d6cf80ffdd1@mail.gmail.com> (raw)
In-Reply-To: <A49BBF89-41D7-4AFE-BDCF-D0BF246879CB@gmail.com>
Hi Eric,
The only reference to PUSH I see is
at http://code.google.com/p/push
where the site reads,
"This is the new unix port of push."
Where might I find the native Plan 9
version?
Best,
ak
On 4/25/10, Eric Van Hensbergen <ericvh@gmail.com> wrote:
> Take a look at Noah's PUSH shell. It's not there yet, but maybe later
> today.
>
> Sent from my iPhone
>
> On Apr 26, 2010, at 2:50 AM, Akshat Kumar
> <akumar@mail.nanosouffle.net> wrote:
>
>> Thanks Steve,
>>
>> rx $cpu 'procdata' | process
>>
>> works well for one way.
>> However,
>>
>> procdata | rx $cpu 'process'
>>
>> is in the same way as with cpu(1).
>> Any suggestions for piping in that
>> direction?
>>
>>
>> Best,
>> ak
>>
>> On Sun, Apr 25, 2010 at 5:40 PM, Steve Simon <steve@quintile.net>
>> wrote:
>>>> cpu -c 'procdata' | process
>>>> ...
>>>> Perhaps I'm overlooking some simple solutions here.
>>>> Any suggestions?
>>>
>>> cpu(1) works by starting exportfs on the remote machine and serving
>>> the local machines filespace. The remote shell is started with its
>>> stdin/out/err attached to /mnt/term/dev/cons, thus the command you
>>> tried will not work (by design).
>>>
>>> what you want is rx(1) which does exactly what you want, somthing
>>> like rsh(1) from the Unix world, except it uses plan9' secure
>>> authentication; e.g.:
>>>
>>> rx $cpu | process
>>>
>>> -Steve
>>>
>>>
>>
>
>
next prev parent reply other threads:[~2010-04-26 7:33 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-25 23:56 Akshat Kumar
2010-04-26 0:40 ` Steve Simon
2010-04-26 0:50 ` Akshat Kumar
2010-04-26 5:45 ` Eric Van Hensbergen
2010-04-26 7:33 ` Akshat Kumar [this message]
2010-04-26 7:55 ` Eric Van Hensbergen
2010-04-26 20:00 ` Akshat Kumar
2010-04-26 21:20 ` erik quanstrom
2010-04-26 21:57 ` Akshat Kumar
2010-04-26 22:17 ` erik quanstrom
2010-04-27 8:48 ` Derek Fawcus
2010-04-27 4:29 ` Tim Newsham
2010-04-27 4:31 ` lucio
2010-04-27 12:04 ` erik quanstrom
2010-04-27 12:46 ` erik quanstrom
2010-05-01 18:51 ` Ryousei Takano
2010-05-01 19:40 ` David du Colombier
2010-05-03 3:19 ` Ryousei Takano
2010-05-03 18:10 ` David du Colombier
2010-05-03 20:22 ` Russ Cox
2010-05-04 15:46 ` Jorden M
2010-05-04 17:44 ` ron minnich
2010-05-04 18:16 ` erik quanstrom
2010-05-04 18:36 ` ron minnich
2010-05-04 18:50 ` erik quanstrom
2010-05-04 19:51 ` Russ Cox
2010-05-04 19:59 ` erik quanstrom
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=z2tfe41879c1004260033q204491f4zfc717d6cf80ffdd1@mail.gmail.com \
--to=akumar@mail.nanosouffle.net \
--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).