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>
Cc: <hangar18-general@open-forge.org>
Subject: Re: [9fans] 'wall' messages
Date: Tue,  7 Oct 2003 21:35:08 -0500	[thread overview]
Message-ID: <Pine.LNX.4.33.0310072120310.4102-100000@einstein.ssz.com> (raw)
In-Reply-To: <c71850fa6c9cfd3a6a614ab29bb10446@9srv.net>


On Tue, 7 Oct 2003 a@9srv.net wrote:

> another problem with the 'echo 'rebooting now' > /dev/screen/*' or
> whatever is the fact that it requires more specific resources to
> exist. my primary interaction with plan 9 these days is (sadly) via
> ssh (ether on Virtual PC, anyone?), so most of the common /dev
> entries present on a terminal, via drawterm, or via vnc won't show
> up for me.

I don't see that as a serious problem. After all rio runs from a rc
prompt. Looks to me like all connections start with a rc shell that then
invokes other programs in some manner. So track the initial connection and
then as other things get cranked up (eg rio) you simply follow the chain.
The OS has to have a means (probably vector tables of one sort or another)
to keep track of it.

And as to there not being a /dev, that's a simple issue of creating a
logical alias on that initial rc connection into /dev/display/*. As that
gets updated (ie I execute the 'rio' command) another logical device could
be added or even replace the rc connection. In the case of a serial device
the logical link would work the same way once the handshaking was
completed.

It's not like there is any magic there, it's bits, it -all- breaks down
to read/write/and/or/not/shift/jump on bits in ram or a register in the
final analysis. The bottom line is that my view is that the complexity
should be in the OS hidden from the users (including bootes/eve) and the
users shouldn't have to jump through hoops to do things as simple as
sending a note to all logged in users. The exact scope of that permission
(ie should it be bootes/eve or all users or just particular groups)
should be left up to the system operators and a config script of some
sort.

The ability to share resources -is just as important- as being able to
prevent access. Perhaps more so if you're speaking of individuals working
on groups.

 -- --

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  2:35 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 [this message]
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.0310072120310.4102-100000@einstein.ssz.com \
    --to=ravage@einstein.ssz.com \
    --cc=9fans@cse.psu.edu \
    --cc=hangar18-general@open-forge.org \
    /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).