From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] the meaning of group
Date: Mon, 28 Jan 2008 18:35:53 -0500 [thread overview]
Message-ID: <a8975e41122eb752119c23cb0818c369@quanstro.net> (raw)
In-Reply-To: <aba77204b8663789b433fd89cd1d5f76@terzarima.net>
On Mon Jan 28 18:01:00 EST 2008, forsyth@terzarima.net wrote:
> > without any agreed-upon or secure arbiter of groups which tracks centralized
> > information, this does not seem like a good idea to me.
>
> `centralised' information?
>
> i assume you'd have to be hostowner to load it, so it's up to the host-owner process that loads it what it
> regards as `adequately reliable' data. on a cpu server, it can be consistent with the user names associated with
> processes on that system. that's not centralised though: it's a local convention.
i don't mean coordiated outside our site. perhaps i didn't make that clear.
what you're saying sounds like, say, putting some configuration in /rc/bin/cpurc.
the problem is that this information needs to be updated across all cpu servers
more often than everything is rebooted.
perhaps a file on /srv/boot could be given to the fs which could be opened to check
group permission? too cute?
- erik
next prev parent reply other threads:[~2008-01-28 23:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-28 19:57 erik quanstrom
2008-01-28 20:29 ` Charles Forsyth
2008-01-28 20:33 ` erik quanstrom
2008-01-28 22:10 ` Charles Forsyth
2008-01-28 22:49 ` erik quanstrom
2008-01-28 23:06 ` Charles Forsyth
2008-01-28 23:35 ` erik quanstrom [this message]
2008-01-29 5:28 ` Bruce Ellis
2008-01-29 15:58 ` roger peppe
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=a8975e41122eb752119c23cb0818c369@quanstro.net \
--to=quanstro@quanstro.net \
--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).