Re: [9fans] Porting to plan9 / PF_UNIX

["Lluís Batlle" <viriketo@gmail.com>]

2007/4/14, W B Hacker <wbh@conducive.org>:
> LLuis,
>
> Read the description.  Am confused.
>
> You connect to s server with a 'terminal' (the client?)
No. The client is also 'ts', as the server. Two processes from the
same program, doing different tasks. The server maintains a batch
queue of the commands queued by 'ts' clients.
>
> The 'client' awaits permission from the server to run the task.
The server maintains the queue of the tasks to be run (in a simple list).
>
> - But the task actually runs on the *client*?
The task (the queued command) will be forked and execed from the
client, once it received the server message allowing the task to be
run (so, all previous tasks in the queue were accomplished)
>
> Shall we presume it is the equivalent of a Plan9 'CPU' then? Or?
I don't think it's any similar at all.
>
> (i.e. plenty of RAM and CPU-cycles, but short on storage space.)
>
> - using the server for scheduling control & spooling the output?
The server knows to what file the output is stored. And it 'spools'
the tasks. I wouldn't use the verb 'schedule' for spooling.
>
> AFAIK Plan9 can do many "similar" things already.
>
> But I am missing an example or three of what you would actually use this for..
> 370-155's aside, there may be sound reason why there is nothing similar...
What are 370 and 155?

Maybe you could look at the manpage of 'ts' for more information.

Regards,
Lluís.