From: andrey mirtchovski <mirtchov@cpsc.ucalgary.ca>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] execute bits
Date: Mon, 23 Jun 2003 16:22:53 -0600 [thread overview]
Message-ID: <Pine.LNX.4.44.0306231620170.16694-100000@fbsd.cpsc.ucalgary.ca> (raw)
In-Reply-To: <20030623221808.28717.qmail@g.bio.cse.psu.edu>
i've solved this by adding the user that does updates (i.e. me) to a special
group of users which have write permission over /src and /386...
it's a bit more complicated than that and is definitely not easier than
doing a disk/kfscmd allow, but ti avoids having the system in an unprotected
state.
the idea i got from /adm/users on sources.cs.bell-labs...
andrey
On Mon, 23 Jun 2003, Scott Schwartz wrote:
> | one should avoid having the system in an 'allowed' state as much as
> | possible.
>
> Yes, but when a really big update is being pull-ed, it might
> be in that state for a while.
>
next prev parent reply other threads:[~2003-06-23 22:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-23 18:42 Scott Schwartz
2003-06-23 19:44 ` Joel Salomon
2003-06-23 21:34 ` Kenji Arisawa
2003-06-23 21:41 ` andrey mirtchovski
2003-06-23 21:53 ` Kenji Arisawa
2003-06-23 22:18 ` Scott Schwartz
2003-06-23 22:22 ` andrey mirtchovski [this message]
2003-06-24 0:17 ` Kenji Arisawa
2003-06-24 7:25 ` Fco.J.Ballesteros, nemo
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.44.0306231620170.16694-100000@fbsd.cpsc.ucalgary.ca \
--to=mirtchov@cpsc.ucalgary.ca \
--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).