From: Axel Belinfante <Axel.Belinfante@cs.utwente.nl>
To: 9fans@cse.psu.edu
Subject: [9fans] fs administration: how do people update multi-user fs?
Date: Fri, 14 Feb 2003 16:02:54 +0100 [thread overview]
Message-ID: <200302141502.h1EF2sr12679@zamenhof.cs.utwente.nl> (raw)
Just wondering how people who have multiple users using
their fs deal with fs permissions during update from sources.
(in case it makes a difference: non-fossil, but I assume
that the basic questions are independent of fs impl)
Planned down-time to run the update? Or update on-the-fly?
Use `allow' on boot? Use `allow' from console?
How do you avoid that those who do not run the update
profit (even just by accident) from the `allow' flag?
`Hangup' together with `noattach'?
Or is this all just a non-issue?
For updating on-the-fly, I'm wondering whether it would
help to add a version of the console `allow' command
that takes a uid, in the same way as duallow does.
Browsed the fs source; hacking it in does not seem to
be a problem, but, since it is not there yet, it seems
that people can live without it, hence I'm wondering:
what do others do?
Axel.
next reply other threads:[~2003-02-14 15:02 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-14 15:02 Axel Belinfante [this message]
2003-02-14 15:16 ` Russ Cox
2003-02-14 15:20 ` Ronald G. Minnich
2003-02-14 17:16 ` Jack Johnson
2003-02-14 17:28 ` andrey mirtchovski
2003-02-14 17:42 ` Ronald G. Minnich
2003-02-14 18:04 ` northern snowfall
2003-02-16 22:28 ` Roman V. Shaposhnick
2003-02-14 17:47 ` Ronald G. Minnich
2003-02-14 15:33 ` Lucio De Re
2003-02-14 15:37 ` Russ Cox
2003-02-14 16:08 ` [9fans] chown in fossil Fco.J.Ballesteros
2003-02-14 16:17 ` Russ Cox
2003-02-14 16:20 ` Fco.J.Ballesteros
2003-02-14 16:23 ` Russ Cox
2003-02-14 16:27 ` Fco.J.Ballesteros
2003-02-15 2:56 ` [9fans] fs administration: how do people update multi-user fs? Christopher Nielsen
2003-02-15 3:03 ` Geoff Collyer
2003-02-15 4:38 ` Christopher Nielsen
2003-02-15 3:13 ` Scott Schwartz
2003-02-15 4:39 ` Christopher Nielsen
2003-02-15 4:48 ` Andrew
2003-02-15 16:20 ` Dan Cross
2003-02-15 9:49 ` Lucio De Re
2003-02-15 14:18 ` Russ Cox
2003-02-15 15:29 ` Lucio De Re
2003-02-16 14:20 ` Russ Cox
2003-02-16 14:30 ` Lucio De Re
2003-02-16 14:36 ` Russ Cox
2003-02-15 15:53 ` Kenji Arisawa
2003-02-15 16:00 ` Lucio De Re
2003-02-15 16:22 ` Dan Cross
2003-02-15 17:58 ` Russ Cox
2003-02-14 16:16 ` Dan Cross
[not found] <cnielsen@pobox.com>
2000-11-17 23:48 ` [9fans] IL and NAT Christopher Nielsen
2000-11-17 23:56 ` Scott Schwartz
2000-11-18 14:20 ` Steve Kilbane
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=200302141502.h1EF2sr12679@zamenhof.cs.utwente.nl \
--to=axel.belinfante@cs.utwente.nl \
--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).