From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] Adding a new user on 9-Front
Date: Mon, 23 Dec 2013 08:55:11 -0500 [thread overview]
Message-ID: <b6dffdc5bfabeb43dd6ac0952e90ab24@brasstown.quanstro.net> (raw)
In-Reply-To: <1711f5ea085fc6f4270380a7e33e439b@hamnavoe.com>
On Mon Dec 23 08:47:19 EST 2013, 9fans@hamnavoe.com wrote:
> > ah, but being hostowner gives you no special status on the file
> > server.
>
> Which file server are you referring to? In the case of Plan 9 and fossil,
> hostowner can talk to /srv/fscons which is effectively root power.
i considered that, but felt it was still worth pointing out because
a) on unix, root can remove nearly everything with rm; being the hostowner
itself gives you no such priviliges. the fact that there is often a fscons
to override this is not quite the same thing. at a minimum, it provides
fat-finger protection. and but for the fact there is no other way to
safely shutdown fossil, it could be omitted.
b) if you do add terminals or other cpu servers, #s/fscons will not be
accessable if a different hostowner is used.
perhaps i've missed the point, but they don't quite look the same to me.
- erik
next prev parent reply other threads:[~2013-12-23 13:55 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-23 2:37 Blake McBride
2013-12-23 5:19 ` Sergey Zhilkin
2013-12-23 6:15 ` Matthew Veety
2013-12-23 13:34 ` erik quanstrom
2013-12-23 13:46 ` Richard Miller
2013-12-23 13:55 ` erik quanstrom [this message]
2013-12-23 14:36 ` Blake McBride
2013-12-23 15:10 ` Blake McBride
2013-12-23 15:32 ` Bence Fábián
2013-12-23 17:13 ` sl
2013-12-23 18:00 ` Blake McBride
2013-12-23 18:03 ` Blake McBride
2013-12-23 18:28 ` Kurt H Maier
2013-12-23 20:03 ` Blake McBride
2013-12-23 20:18 ` erik quanstrom
2013-12-23 20:23 ` Rubén Berenguel
2013-12-23 20:48 ` Blake McBride
2013-12-23 21:20 ` Steve Simon
2013-12-23 20:51 ` Kurt H Maier
2013-12-23 21:45 ` Blake McBride
2013-12-23 22:00 ` Matthew Veety
2013-12-23 22:07 ` sl
2013-12-23 22:45 ` erik quanstrom
2013-12-23 23:47 ` sl
2013-12-23 23:54 ` Kurt H Maier
2013-12-24 12:06 ` Steffen Daode Nurpmeso
2013-12-24 12:24 ` lucio
2013-12-24 17:47 ` Steffen Daode Nurpmeso
2013-12-25 5:30 ` lucio
2013-12-25 5:58 ` Federico G. Benavento
2013-12-24 0:16 ` Kurt H Maier
2013-12-24 0:57 ` andrey mirtchovski
2013-12-24 2:49 ` Skip Tavakkolian
2013-12-24 3:03 ` Bruce Ellis
2013-12-23 19:18 ` Richard Miller
2013-12-23 19:30 ` cinap_lenrek
2013-12-23 19:37 ` erik quanstrom
2013-12-23 20:29 ` cinap_lenrek
2013-12-23 15:42 ` cinap_lenrek
2013-12-23 9:38 ` Richard Miller
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=b6dffdc5bfabeb43dd6ac0952e90ab24@brasstown.quanstro.net \
--to=quanstro@quanstro.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).