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 08:38:07 -0500	[thread overview]
Message-ID: <Pine.LNX.4.33.0310080819520.1216-100000@einstein.ssz.com> (raw)
In-Reply-To: <dab.3f83d736.ab7a2@blake.inputplus.co.uk>


On Wed, 8 Oct 2003, Ralph Corderoy wrote:

> > The bottom line is that my view is that the complexity should be in
> > the OS hidden from the users
>
> but it could be that they feel it's better to not have the facility
> until a non-complex method can be conceived rather than add complexity
> anywhere, including the OS.

I understand that point, clearly. I want it to be as simple as possible
with a couple of provisos,

* there should be -no- additional programming or commands for a user to
  do this. The basic skeleton is already there in the namespace and that
  is where it needs to stay. Not in some command line solution. That's
  an ugly kludge at best. In other words it must be consistent with the
  current cat/cp sort of approach, if another approach is taken the this
  add another layer of commands and that complicates things. People
  expect to be able to cat/cp to anything in a namespace, and that
  includes hardare. It's all a filesystem after all, and any other
  approach will break that paradigm and add confusion.

* it needs to be available to all users, with the owner of the box where
  the hardware is resident being in control of the security.

* it needs to work across -all- hardware devices such as displays,
  keyboards, mice, soundcards, etc. It is critical that P9 make it as
  easy as possible to share these resources, as well as deny the
  sharing. Standard file permissions look like the cats meow to me.

* the owner of the box is the one who decides the range of these services
  and nobody else.

* since there are at least two filesystems that a cpu server can run
  native (ie kfs and fossil) it needs to be outside of those; otherwise
  you've got to write the code twice - yuck. That leaves only -one-
  place, the kernel. This implies two points worth delineating; 1.
  devices need to be 'logged' at boot. 2. each new user connection that
  generates a std out/std err needs to be included. 3. it can't make any
  different to the command syntax or the recipient of such messages what
  their interface is.

I see this functionality as critical to the real world success of P9. For
example with this VoIP becomes easy; I cat my microphone to your sound
card and visa versa. Musicians sharing a set of MIDI channels from several
seperate locations becomes easy. It would have a big impact in training &
education with regard to being able to grab students displays one at a
time, as well as being able to dump content to them all at once. Robotics with
respect to agent clouds becomes a lot simpler than anything that's out
there now. MMOG's would recieve a massive boost from this sort of sharing
with regard to having the actual engine running in a processor cloud. This
helps solve the 'shared world synchronicity' problem in a big way (for
examples ping times become something the game can use directly to level
the playing field). Couple this with things like global sign-on and you
really start to see the power.


 -- --

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



  reply	other threads:[~2003-10-08 13:38 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
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 [this message]
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.0310080819520.1216-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).