From 3e7472b3d54853389cd8a17475901fbef976ef18 Mon Sep 17 00:00:00 2001
From: Thomas Schwinge <tschwinge@gnu.org>
Date: Thu, 1 Sep 2011 09:27:33 +0200
Subject: IRC.

---
 hurd/translator/discussion.mdwn                | 25 +++++++++++++++++++++++++
 hurd/translator/procfs/jkoenig/discussion.mdwn | 23 +++++++++++++++++++++++
 2 files changed, 48 insertions(+)
 create mode 100644 hurd/translator/discussion.mdwn

(limited to 'hurd/translator')

diff --git a/hurd/translator/discussion.mdwn b/hurd/translator/discussion.mdwn
new file mode 100644
index 00000000..e038ba84
--- /dev/null
+++ b/hurd/translator/discussion.mdwn
@@ -0,0 +1,25 @@
+[[!meta copyright="Copyright © 2011 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
+document under the terms of the GNU Free Documentation License, Version 1.2 or
+any later version published by the Free Software Foundation; with no Invariant
+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]]."]]"""]]
+
+[[!tag open_issue_documentation open_issue_hurd]]
+
+IRC, freenode, #hurd, 2011-08-25:
+
+    < frhodes> how can I replace an existing running server with a new one
+      without rebooting?
+    < antrik> frhodes: depends. if other critical things depend on it, you
+      can't. there is no mechanism to serialize and pass on the open sessions
+    < antrik> in some situations, you can orphan the old translator while
+      starting a new one, so the previous clients will stay with the old one
+      while new one will get the new one
+    < antrik> obviously that only works for things that aren't exclusive by
+      nature
+    < antrik> in some cases, you might even be able simply to remove the old
+      translator... but obviously only for non-critical stuff :-)
diff --git a/hurd/translator/procfs/jkoenig/discussion.mdwn b/hurd/translator/procfs/jkoenig/discussion.mdwn
index 64e3776e..01bbea42 100644
--- a/hurd/translator/procfs/jkoenig/discussion.mdwn
+++ b/hurd/translator/procfs/jkoenig/discussion.mdwn
@@ -184,3 +184,26 @@ IRC, freenode, #hurd, 2011-07-22
     <pinotree> status is 644 though
     <jkoenig> but status contains information which anyone can ask to the proc
       server anyway, I think.
+
+
+# `/proc/mounts`, `/proc/$pid/mounts`
+
+IRC, freenode, #hurd, 2011-07-25
+
+    < pinotree> jkoenig: btw, what do you think about providing empty
+      /proc/mounts and /proc/$pid/mounts files?
+    < jkoenig> pinotree, I guess one would have to evaluate the consequences
+      wrt. existing use cases (in other words, "I have absolutely no clue
+      whatsoever about whether that would be desirable" :-)
+    < jkoenig> pinotree, the thing is, an error message like "/proc/mounts: No
+      such file or directory" is rather explicit, whereas errors which would be
+      caused by missing data in /proc/mounts would maybe be harder to track
+    < braunr> this seems reasonable though
+    < braunr> there already are many servers with e.g. grsecurity or chrooted
+      environments where mounts is empty
+    < pinotree> well, currently we also have an empty mtab
+    < braunr> pinotree: but what do you need that for ?
+    < braunr> pinotree: the init system ?
+    < pinotree> and the mnt C api already returns no entries (or it bails out,
+      i don't remember)
+    < pinotree> not a strict need
-- 
cgit v1.2.3