summaryrefslogtreecommitdiff
path: root/hurd/translator
diff options
context:
space:
mode:
authorThomas Schwinge <tschwinge@gnu.org>2012-11-29 01:33:22 +0100
committerThomas Schwinge <tschwinge@gnu.org>2012-11-29 01:33:22 +0100
commit5bd36fdff16871eb7d06fc26cac07e7f2703432b (patch)
treeb430970a01dfc56b8d41979552999984be5c6dfd /hurd/translator
parent2603401fa1f899a8ff60ec6a134d5bd511073a9d (diff)
IRC.
Diffstat (limited to 'hurd/translator')
-rw-r--r--hurd/translator/ext2fs.mdwn14
-rw-r--r--hurd/translator/nfs.mdwn5
-rw-r--r--hurd/translator/procfs/jkoenig/discussion.mdwn20
3 files changed, 39 insertions, 0 deletions
diff --git a/hurd/translator/ext2fs.mdwn b/hurd/translator/ext2fs.mdwn
index 460194f9..13a1d9ec 100644
--- a/hurd/translator/ext2fs.mdwn
+++ b/hurd/translator/ext2fs.mdwn
@@ -89,6 +89,20 @@ small backend stores, like floppy devices.
<youpi> which can be quite probable
+## Sync Interval
+
+[[!tag open_issue_hurd]]
+
+
+### IRC, freenode, #hurd, 2012-10-08
+
+ <braunr> btw, how about we increase our ext2 sync interval to 30 seconds,
+ like others do ?
+ <braunr> not really because others do it that way, but because it severely
+ breaks performance on the hurd
+ <braunr> and 30 seems like a reasonable amount (better than 5 at least)
+
+
# Documentation
* <http://e2fsprogs.sourceforge.net/ext2.html>
diff --git a/hurd/translator/nfs.mdwn b/hurd/translator/nfs.mdwn
index bf24370a..81372204 100644
--- a/hurd/translator/nfs.mdwn
+++ b/hurd/translator/nfs.mdwn
@@ -10,6 +10,11 @@ License|/fdl]]."]]"""]]
Translator acting as a NFS client.
+Only NFSv2/v3 is currentl supported.
+
+[[!tag open_issue_hurd]]There are a few unmerged changes on a former GSoC
+project's topic-branch.
+
# See Also
diff --git a/hurd/translator/procfs/jkoenig/discussion.mdwn b/hurd/translator/procfs/jkoenig/discussion.mdwn
index 0ee1e238..da6f081e 100644
--- a/hurd/translator/procfs/jkoenig/discussion.mdwn
+++ b/hurd/translator/procfs/jkoenig/discussion.mdwn
@@ -329,3 +329,23 @@ Needed by glibc's `pldd` tool (commit
* pinotree has a local work to add the /proc/$pid/cwd symlink, but relying
on "internal" (but exported) glibc functions
+
+
+# "Unusual" PIDs
+
+Not actually related to procfs, but here seems to be a convenient place for
+filing these:
+
+
+## IRC, freenode, #hurd, 2012-08-10
+
+ <braunr> too bad the proc server has pid 0
+ <braunr> top & co won't show it
+
+
+## IRC, OFTC, #debian-hurd, 2012-09-18
+
+ <pinotree> youpi: did you see
+ https://enc.com.au/2012/09/careful-with-pids/'
+ <pinotree> ?
+ <youpi> nope