9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: lucio@proxima.alt.za
To: 9fans@9fans.net
Subject: Re: [9fans] New /prog idea
Date: Mon,  5 May 2014 18:38:50 +0200	[thread overview]
Message-ID: <fff7f3a87530089e6aabee829d47a321@proxima.alt.za> (raw)
In-Reply-To: <CACm3i_g4102v2TEBB8ajUCaL8ukafeZnVDXxsDQ0m-mbjgobSA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 360 bytes --]

It seems to me that this type of operation would be considerably more
successful if there was better interaction between the kernel and a
running program.  that is, if processes were engineered to accept
unsolicited signalling from the kernel and, consequently, from other
processes without being restricted to a narrow range of signals or
notes.

++L

[-- Attachment #2: Type: message/rfc822, Size: 7081 bytes --]

[-- Attachment #2.1.1: Type: text/plain, Size: 830 bytes --]

There was a proc box in the original Plan B of which there were different
version in the descendants (for files too) and
which permitted things similar to what you want. See

http://lsub.org/ls/export/man.1e.ps (page 31)
and
http://lsub.org/ls/export/ubiterm.icps05.pdf

Later, Andrey and Ron did something similar for clusters with xcpu:

http://ieeexplore.ieee.org/stamp/stamp.jsp?arnumber=04100349

G.



On Sun, May 4, 2014 at 11:59 PM, Oleksandr Iakovliev
<yshurik@lynxline.com>wrote:

>
> Just idea, but seriously, why cannot do something like this:
>
> # cat /prog/new > $id
> # cat /dis/ls.dis > /prog/$id/dis
> # echo "/" > /prog/$id/cwd
> # echo «Running» > /prog/$id/status
>
> Not to do it which echo/cat, but to have remote access to /prog/new
>



-- 
- curiosity sKilled the cat

[-- Attachment #2.1.2: Type: text/html, Size: 1678 bytes --]

      reply	other threads:[~2014-05-05 16:38 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-04 21:59 Oleksandr Iakovliev
2014-05-05  0:53 ` erik quanstrom
2014-05-05 11:03   ` tlaronde
2014-05-05 12:09     ` erik quanstrom
2014-05-05 12:33       ` Charles Forsyth
2014-05-05 13:06         ` erik quanstrom
2014-05-05 14:38           ` Oleksandr Iakovliev
2014-05-05 14:56             ` erik quanstrom
2014-05-05 15:22 ` Gorka Guardiola
2014-05-05 16:38   ` lucio [this message]

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=fff7f3a87530089e6aabee829d47a321@proxima.alt.za \
    --to=lucio@proxima.alt.za \
    --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).