| 1 |
On Fri, Jan 02, 2009 at 01:40:09PM -0800, Alec Warner wrote: |
| 2 |
> How hard would it be to change permissions on the ,v file for this and |
| 3 |
> just run the use.local.desc updater as a user with different |
| 4 |
> privileges? |
| 5 |
It does have different permissions. It's the directory permissions that |
| 6 |
matter however. I already tried the file permissions. If we want to |
| 7 |
truly block it while not affecting commits to the rest of the directory, |
| 8 |
we need to add CVS ACLS, which I've been meaning to do, but just never |
| 9 |
got around to. |
| 10 |
|
| 11 |
CVS does (the short version): |
| 12 |
1. Take a file-based lock (#A) for the target ,v file. |
| 13 |
No writes permitted, reads are permitted. |
| 14 |
2. Build the new version of the ,v in the temp space. |
| 15 |
3. Copy the new version to a different name in the target directory. |
| 16 |
4. Upgrade lock #A, no reads permitted now. |
| 17 |
5. unlink the old ,v file |
| 18 |
(the kernel checks the directory permissions, not the file perms). |
| 19 |
6. rename the new file into place. |
| 20 |
7. Release lock #A. |
| 21 |
|
| 22 |
-- |
| 23 |
Robin Hugh Johnson |
| 24 |
Gentoo Linux Developer & Infra Guy |
| 25 |
E-Mail : robbat2@g.o |
| 26 |
GnuPG FP : 11AC BA4F 4778 E3F6 E4ED F38E B27B 944E 3488 4E85 |
Archives