shell

[Hershel Fisch]

On 1/18/10 3:13 PM, "stephen barncard" <stephenREVOLUTION2 at barncard.com>
wrote:

> Alex Tweedly has a sample UDP (datagram) stack at Rev Online
Could you be a bit more precise please? Didn't find it.
Hershel
> -------------------------
> Stephen Barncard
> San Francisco
> http://houseofcubes.com/disco.irev
> 
> 
> 2010/1/18 Hershel Fisch <hershrev at syp2u4c.com>
> 
>> Hi, after knocking my head against the wall I decided to try to go via
>> sockets, but I have some misunderstandings for unpredicted behavior, now my
>> questions if somebody could give a full statement example?
>> Thanks, Hershel
>> 
>> 
>> On 1/7/10 5:12 AM, "Bernard Devlin" <bdrunrev at gmail.com> wrote:
>> 
>>> Hi Herschel,
>>> 
>>> I am unfamiliar with Hylafax.  I don't think "shell" is going to cut
>>> it for your needs.  What you may need is "open process", "write to
>>> process" and "read from process".  Open process is kind of like
>>> opening a non-visible terminal, where the state of the program opened
>>> as a process persists throughout your read/write interactions with it.
>>> 
>>> If you have a CLI client for hylafax for OS X & Windows, then you can
>>> use that as the process to open.  If the only CLI client you have for
>>> hylafax is on the server, then you will need to run remote sessions to
>>> the server.  On OS X you could try 'talking' to the remote hylafax
>>> client via ssh opened via "open process".  If that works, you've got a
>>> start.  On Windows you would then have to use something like plink
>>> (part of the Putty suite of ssh programs for windows).
>>> 
>>> A final option might be to use the Expect program locally to talk to
>>> the remote hylafax client.  I have never used Expect, but I imagine it
>>> would be more complex to use than "open process" + ssh.
>>> 
>>> It's going to be convoluted, but it might work.
>>> 
>>> Bernard
>>> 
>>> On Wed, Jan 6, 2010 at 6:36 PM, Hershel Fisch <hershrev at syp2u4c.com>
>> wrote:
>>>> My server is FreeBSD or OSX, Client is OSX and Win.
>>>> 
>>>>> What is the problem with writing multiple arguments?  Do you mean
>>>>> multiple successive shell commands, or multiple arguments to one
>>>>> program?
>>>> 
>>>> I want to write a GUI to connect to the server. Now I see in Rev, when a
>>>> shell command is issued its sent and returns the prompt, if I need to
>>>> respond to that prompt then it issues a different shell session and not
>> a
>>>> continuation of the previous one, e.g. I want to connect to a server or
>>>> change user, put shell("su - userABC") it returns "password" that means
>> that
>>>> it wants a password to continue now where and who can I provide a
>> password
>>>> it should continue the current session? In terminal I just type it in
>> and
>>>> its done.
>>> _______________________________________________
>>> use-revolution mailing list
>>> use-revolution at lists.runrev.com
>>> Please visit this url to subscribe, unsubscribe and manage your
>> subscription
>>> preferences:
>>> http://lists.runrev.com/mailman/listinfo/use-revolution
>> 
>> 
>> _______________________________________________
>> use-revolution mailing list
>> use-revolution at lists.runrev.com
>> Please visit this url to subscribe, unsubscribe and manage your
>> subscription preferences:
>> http://lists.runrev.com/mailman/listinfo/use-revolution
>> 
> _______________________________________________
> use-revolution mailing list
> use-revolution at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription
> preferences:
> http://lists.runrev.com/mailman/listinfo/use-revolution