From: Jim Choate <ravage@einstein.ssz.com>
To: <9fans@cse.psu.edu>
Subject: Re: [9fans] 'wall' messages
Date: Mon, 6 Oct 2003 22:31:45 -0500 [thread overview]
Message-ID: <Pine.LNX.4.33.0310062230000.3289-100000@einstein.ssz.com> (raw)
In-Reply-To: <027d01c38c80$456eaed0$c901a8c0@cc77109e>
On Tue, 7 Oct 2003, Bruce Ellis wrote:
> this solution works very well in practice, particularly if everyone
> runs seemail - the ominous bootes face herding everyone to
> the coffee machine.
>
> giving bootes some god-awful power to hijack other namespaces
> is not a very good solution.
Wait a minute, the users don't own those resources, they're borrowing
them. Within the context of the particular hardware it is completely
reasonable to leave bootes in control. Nobody is suggesting that bootes
necessarily be able to go out off that hardware and act as that user.
You're position basically lets the user have free reign over something
that isn't theirs. Yuck!
-- --
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
next prev parent reply other threads:[~2003-10-07 3:31 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 [this message]
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
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.0310062230000.3289-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).