From 08fa84c9662c3ac2b0b0bb6284efc97b87bfc815 Mon Sep 17 00:00:00 2001
From: Thomas Schwinge <thomas@codesourcery.com>
Date: Tue, 11 Mar 2014 11:10:40 +0100
Subject: Interlink file locking issues.

---
 open_issues/file_locking.mdwn | 28 ++++++++++++++++++++++++++--
 open_issues/glibc.mdwn        | 10 +---------
 open_issues/visudo.mdwn       |  4 ++--
 3 files changed, 29 insertions(+), 13 deletions(-)

(limited to 'open_issues')

diff --git a/open_issues/file_locking.mdwn b/open_issues/file_locking.mdwn
index 563307a4..7dfbdb94 100644
--- a/open_issues/file_locking.mdwn
+++ b/open_issues/file_locking.mdwn
@@ -1,4 +1,5 @@
-[[!meta copyright="Copyright © 2010, 2011 Free Software Foundation, Inc."]]
+[[!meta copyright="Copyright © 2010, 2011, 2014 Free Software Foundation,
+Inc."]]
 
 [[!meta license="""[[!toggle id="license" text="GFDL 1.2+"]][[!toggleable
 id="license" text="Permission is granted to copy, distribute and/or modify this
@@ -10,7 +11,25 @@ License|/fdl]]."]]"""]]
 
 [[!tag open_issue_hurd open_issue_glibc]]
 
-IRC, #hurd, 2010-12-31.
+[[!toc]]
+
+
+# Google Summer of Code Project Idea
+
+[[community/gsoc/project_ideas/File_Locking]].
+
+
+# visudo
+
+[[visudo]].
+
+
+# Existing Work
+
+[[!GNU_Savannah_patch 332]].
+
+
+# IRC, freenode, #hurd, 2010-12-31
 
     <pinotree> youpi: i found the issue with python-apt
     <pinotree> s/with/of/
@@ -72,3 +91,8 @@ IRC, #hurd, 2010-12-31.
     <youpi> ah, no, on Linux flock is its own system call
     <youpi> (which is independant from lockf from the locking point of view,
       iirc)
+
+
+# 2014-03-11
+
+[[!message-id "1394523876.28244.11.camel@workhorse-peter-baumgarten-com"]].
diff --git a/open_issues/glibc.mdwn b/open_issues/glibc.mdwn
index 923ca99d..33041e71 100644
--- a/open_issues/glibc.mdwn
+++ b/open_issues/glibc.mdwn
@@ -1853,15 +1853,7 @@ Last reviewed up to the [[Git mirror's 64a17f1adde4715bb6607f64decd73b2df9e6852
             <braunr> teythoon: i think it should be in glibc
             <braunr> maybe in mach/
 
-      * POSIX record locking
-
-        IRC, freenode, #hurd, 2014-02-27:
-
-            <azeem_> tschwinge: schould POSIX record locking be on
-              http://darnassus.sceen.net/~hurd-web/open_issues/glibc/#missing
-              as well. or is that strictly a Hurd thing? (I don't remember)
-            <tschwinge> azeem_: Neither do I :-), but I'll have a look later
-              on.
+      * [[POSIX file record locking|file_locking]]
 
       * <a name="execve_relative_paths">`execve` with relative paths</a>
 
diff --git a/open_issues/visudo.mdwn b/open_issues/visudo.mdwn
index e9892e33..4e87fd8d 100644
--- a/open_issues/visudo.mdwn
+++ b/open_issues/visudo.mdwn
@@ -1,4 +1,4 @@
-[[!meta copyright="Copyright © 2013 Free Software Foundation, Inc."]]
+[[!meta copyright="Copyright © 2013, 2014 Free Software Foundation, Inc."]]
 
 [[!meta license="""[[!toggle id="license" text="GFDL 1.2+"]][[!toggleable
 id="license" text="Permission is granted to copy, distribute and/or modify this
@@ -16,7 +16,7 @@ visudo does not work:
 
     /etc/sudoers is busy, try again later
 
-Apparently there is some locking that sudo does which does not
+Apparently there is some [[file_locking]] that sudo does which does not
 work. Uninvestigated for now.
 
 One can just edit the /etc/sudoers file and take care of correctness by hand.
-- 
cgit v1.2.3