From mboxrd@z Thu Jan 1 00:00:00 1970 Message-Id: <200302141502.h1EF2sr12679@zamenhof.cs.utwente.nl> To: 9fans@cse.psu.edu From: Axel Belinfante Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: [9fans] fs administration: how do people update multi-user fs? Date: Fri, 14 Feb 2003 16:02:54 +0100 Topicbox-Message-UUID: 5ee9ebf2-eacb-11e9-9e20-41e7f4b1d025 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.