summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorSamuel Thibault <samuel.thibault@ens-lyon.org>2010-03-08 03:48:37 +0100
committerSamuel Thibault <samuel.thibault@ens-lyon.org>2010-03-08 03:48:37 +0100
commitacae65d8ec98e1bea1d8d903e8748e8c911b3baf (patch)
tree89192278c33c99a69c3d81c20f15bc04e6a09727
parentbfbae422574a8bfd9df9d0051aa55fc7c58db33a (diff)
lockf is (almost) not implement at all
-rw-r--r--community/gsoc/project_ideas/file_locking.mdwn5
1 files changed, 3 insertions, 2 deletions
diff --git a/community/gsoc/project_ideas/file_locking.mdwn b/community/gsoc/project_ideas/file_locking.mdwn
index b6b393f9..af010c98 100644
--- a/community/gsoc/project_ideas/file_locking.mdwn
+++ b/community/gsoc/project_ideas/file_locking.mdwn
@@ -8,7 +8,7 @@ Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license
is included in the section entitled
[[GNU Free Documentation License|/fdl]]."]]"""]]
-[[!meta title="Fix File Locking"]]
+[[!meta title="Fix and Complete File Locking Support"]]
Over the years, [[UNIX]] has aquired a host of different file locking mechanisms.
Some of them work on the Hurd, while others are buggy or only partially
@@ -17,7 +17,8 @@ implemented. This breaks many applications.
The goal is to make all file locking mechanisms work properly. This requires
finding all existing shortcomings (through systematic testing and/or checking
for known issues in the bug tracker and mailing list archives), and fixing
-them.
+them. The biggest missing feature is record locking, i.e. the lockf variant,
+which needs a complete implementation.
This task will require digging into parts of the code to understand how file
locking works on the Hurd. Only general programming skills are required.