9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Jim Choate <ravage@einstein.ssz.com>
To: <9fans@cse.psu.edu>
Subject: Re: [9fans] 'wall' messages
Date: Wed,  8 Oct 2003 00:48:02 -0500	[thread overview]
Message-ID: <Pine.LNX.4.33.0310080034280.4102-100000@einstein.ssz.com> (raw)
In-Reply-To: <02d201c38d1b$c20dbee0$c901a8c0@cc77109e>


On Wed, 8 Oct 2003, Bruce Ellis wrote:

>  drawterm sets up and maintains a namespace
> which is exported to the cpu server just as a p9 terminal does.

Exactly! So if a write to the structures on the cpu would work locally they
will work with drawterm, since the processes are running on the cpu server
side and that is the box that wants to send the shutdown warning. The fact
that I'm accessing those resources via drawterm is really moot.

With reference to the box the drawterm itself is running on, that's a
function of that OS and isn't an issue with drawterm or the cpu server.
When that box goes down drawterm will be killed in some manner and as a
result the connection to the cpu server is closed and those resources are
released and there isn't anything else to send a message to about the cpu
shutdown (assuming there aren't other users on of course) because that
resource pool has already been released.

And I challenge the 'just as a P9 terminal does', I am assuming by
'terminal' you mean I/O server. The difference is that the I/O server can
run processes locally whereas drawterm can't. So there is clearly a
difference in the way namespaces can interact, and the limits on which
the two approaches can interact with that data stream. One example is that
a I/O server could export its local kfs to a process on that cpu server, but
drawterm can't export its local filesystem. Near as I can tell if you want
that you need to use native tools to export that to the cpu server and
then you can import it into a namespace.

The final observation about drawterm is that it's one way, a user can use
drawterm on a box to modify the cpu server but the cpu server can't modify
the drawterm host outside of the drawterm resources. If you could run a
process on the cpu server and use that to 'tunnel' through drawterm and,
for example, reset the drawterm host that would clearly be a bug in
drawterm.


 -- --

God exists because mathematics is consistent, and the Devil exist because we
can't prove it.
                          Andre Weil, in H. Eves, Mathematical Circles Adieu

      ravage@ssz.com                            jchoate@open-forge.com
      www.ssz.com                               www.open-forge.com





  parent reply	other threads:[~2003-10-08  5:48 UTC|newest]

Thread overview: 67+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-07  0:30 mirtchov
2003-10-07  0:33 ` boyd
2003-10-07  0:35 ` jmk
2003-10-07  2:28   ` Jim Choate
2003-10-07  2:27     ` boyd
2003-10-07  2:54       ` Jim Choate
2003-10-07  2:30   ` [9fans] A final question on regex Jim Choate
2003-10-07  3:08   ` [9fans] 'wall' messages Bruce Ellis
2003-10-07  3:11     ` boyd
2003-10-07  3:31     ` Jim Choate
2003-10-07  4:04       ` andrey mirtchovski
2003-10-07  4:17         ` Jim Choate
2003-10-07  4:23           ` [9fans] A fine point on 'lazy update' Jim Choate
2003-10-07  4:25           ` [9fans] 'wall' messages andrey mirtchovski
2003-10-07 13:56             ` Jim Choate
2003-10-07 14:09               ` mirtchov
2003-10-07 14:19                 ` Dan Cross
2003-10-07 17:27                   ` Ralph Corderoy
2003-10-07  9:50       ` Bruce Ellis
2003-10-07 10:41         ` Lucio De Re
2003-10-07 11:27           ` Bruce Ellis
2003-10-07 11:52             ` Lucio De Re
2003-10-07 12:10               ` boyd
2003-10-08  1:43                 ` okamoto
2003-10-07 13:15               ` matt
2003-10-07 12:33                 ` Lucio De Re
2003-10-07 14:09                   ` Dan Cross
2003-10-07 13:40           ` Jim Choate
2003-10-08  8:39             ` Douglas A. Gwyn
2003-10-08 13:40               ` Jim Choate
2003-10-07 13:49         ` Jim Choate
2003-10-07 21:35           ` Bruce Ellis
2003-10-07 22:07             ` Joel Salomon
2003-10-08  5:34               ` Jim Choate
2003-10-08  5:48             ` Jim Choate [this message]
2003-10-08 14:21               ` rog
2003-10-08 18:14                 ` David Presotto
2003-10-08 18:52                   ` mirtchov
2003-10-09 15:07                   ` rog
2003-10-09 15:10                     ` David Presotto
2003-10-08 17:40               ` a
2003-10-07 22:38           ` boyd
2003-10-08  9:36             ` Ralph Corderoy
2003-10-08 13:57               ` Dan Cross
2003-10-07 23:19       ` a
2003-10-08  2:35         ` Jim Choate
2003-10-08  2:42           ` Bruce Ellis
2003-10-08  2:52             ` Jim Choate
2003-10-08 14:46               ` rt
2003-10-09  0:31                 ` Geoff Collyer
2003-10-09  1:29                   ` Bruce Ellis
2003-10-09 18:36                   ` rog
2003-10-09 22:32                     ` Geoff Collyer
2003-10-08  9:36           ` Ralph Corderoy
2003-10-08 13:38             ` Jim Choate
2003-10-08 17:02               ` a
2003-10-08 14:24           ` rt
2003-10-08 15:10             ` Jim Choate
2003-10-08 15:47               ` rt
2003-10-08 21:53             ` Charles Forsyth
2003-10-08 22:59               ` Jim Choate
2003-10-07  3:48     ` Dan Cross
2003-10-07  3:51       ` boyd
2003-10-07  4:09       ` Jim Choate
2003-10-07  4:15         ` boyd
2003-10-07  2:37 YAMANASHI Takeshi
2003-10-07  2:41 ` boyd

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=Pine.LNX.4.33.0310080034280.4102-100000@einstein.ssz.com \
    --to=ravage@einstein.ssz.com \
    --cc=9fans@cse.psu.edu \
    /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).