9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Brian L. Stuart" <blstuart@bellsouth.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Questions on notes
Date: Mon,  3 Nov 2008 17:05:58 +0000	[thread overview]
Message-ID: <110320081705.27472.490F2F76000AE8A400006B5022230703729B0A02D2089B9A019C04040A0DBF9B9D0E9A9B9C040D@att.net> (raw)
In-Reply-To: <1225730768.4781.14.camel@goose.sun.com>

> Frankly, I was trying to see whether an external process reading
> on somebody else's /proc/n/note would make any sense. One thing
> that I wanted to implement was a "note thief" process that would
> constantly read on a target's /proc/n/note and handle the notes
> externally using a different kind of IPC to communicate with
> the target. Am I dreaming? Would this be completely impossible
> to implement using /proc/n/note ?

If proc n needs to know about this design, then could
you just always direct the notes to the "thief?"  Or
if the thief were a little file server, could you bind
the file he listens to on top of /proc/n/note?

BLS




  reply	other threads:[~2008-11-03 17:05 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-03  5:48 Roman Shaposhnik
2008-11-03 13:03 ` erik quanstrom
2008-11-03 16:46   ` Roman V. Shaposhnik
2008-11-03 17:05     ` Brian L. Stuart [this message]
2008-11-03 17:41     ` dave.l
2008-11-05  5:05       ` Roman Shaposhnik
2008-11-05  5:16         ` ron minnich
2008-11-06  5:09           ` Roman Shaposhnik
2008-11-03 18:26 erik quanstrom
     [not found] <42d8f7e804069264141e6e4f33b8baf9@quanstro.net>
2008-11-03 18:48 ` Brian L. Stuart
2008-11-05  2:02   ` Roman V. Shaposhnik

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=110320081705.27472.490F2F76000AE8A400006B5022230703729B0A02D2089B9A019C04040A0DBF9B9D0E9A9B9C040D@att.net \
    --to=blstuart@bellsouth.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).