The version there is Plan9ports and should work under Plan 9 as well -- if it
doesn't, beat on Noah :)
-eric
On Apr 26, 2010, at 9:33 AM, Akshat Kumar wrote:
> 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 <eri...@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
>> <aku...@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 <st...@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
>>>>
>>>>
>>>
>>
>>
>
