IRC.

8 files changed, 127 insertions, 4 deletions

diff --git a/hurd/console/discussion.mdwn b/hurd/console/discussion.mdwn
new file mode 100644
index 00000000..f887d826
--- /dev/null
+++ b/hurd/console/discussion.mdwn
@@ -0,0 +1,42 @@
+[[!meta copyright="Copyright © 2012 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]]
+
+
+# IRC, OFTC, #debian-hurd, 2012-09-24
+
+    <allesa> hello, I'm trying to get familiar with the Hurd and would like to
+      change the keyboard layout in use. It seems all the information I can
+      find (relating to console-driver-xkb) is out of date, with the latest
+      info relating to it being that this package should not be used anymore…
+    <allesa> does anyone know how changing keyboard layouts currently works?
+    <allesa> ah, never mind. I assume it doesn't currently work:
+      http://www.gnu.org/software/hurd/hurd/console.htmlq
+    <allesa> *http://www.gnu.org/software/hurd/hurd/console.html
+    <youpi> it does actually work
+    <youpi> simply dpkg-reconfigure keyboard-configuration
+    <youpi> and reboot
+    <youpi> (see http://www.debian.org/ports/hurd/hurd-install
+    <youpi> )
+    <allesa> mhm, I got that far — but selecting my layout gave me no joy, even
+      after restart. Seem to be stuck with the layout chosen during
+      installation (d-i). Just to check I'm using the right version — still on
+      the installer isos from 15 July?
+    <allesa> wait… progress is being made — slowly and subtly… 
+    <allesa> Ok, so the XKBLAYOUT is changing as you described, but XKBVARIANT
+      seems to be ignored. Could this be right?
+    <youpi> yes, the hurd console only supports keymaps
+    <youpi> (currently)
+    <allesa> Ah OK, thanks for your help on this. I imagine this is not
+      something that just requires simple repetitive work, but some actual
+      hacking?
+    <allesa> to fix that is…
+    <youpi> some hacking yes
diff --git a/hurd/libstore/nbd_store.mdwn b/hurd/libstore/nbd_store.mdwn
index 5874b162..4d4a769f 100644
--- a/hurd/libstore/nbd_store.mdwn
+++ b/hurd/libstore/nbd_store.mdwn
@@ -1,4 +1,4 @@
-[[!meta copyright="Copyright © 2007, 2008, 2009 Free Software Foundation,
+[[!meta copyright="Copyright © 2007, 2008, 2009, 2012 Free Software Foundation,
 Inc."]]
 
 [[!meta license="""[[!toggle id="license" text="GFDL 1.2+"]][[!toggleable
@@ -10,3 +10,8 @@ is included in the section entitled [[GNU Free Documentation
 License|/fdl]]."]]"""]]
 
 [[!meta title="nbd store: Linux-compatible network block device"]]
+
+
+# Open Issues
+
+  * [[!GNU_Savannah_task 5722]]
diff --git a/hurd/libthreads.mdwn b/hurd/libthreads.mdwn
index 8b1a97e6..c8d819d4 100644
--- a/hurd/libthreads.mdwn
+++ b/hurd/libthreads.mdwn
@@ -1,4 +1,4 @@
-[[!meta copyright="Copyright © 2011 Free Software Foundation, Inc."]]
+[[!meta copyright="Copyright © 2011, 2012 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
@@ -13,10 +13,14 @@ License|/fdl]]."]]"""]]
 
 # Internals
 
+## Threading Model
+
+libthreads has a 1:1 threading model.
+
 
 ## Threads' Death
 
-C threads death doesn't actually free the thread's stack (and maybe not the
+A thread's death doesn't actually free the thread's stack (and maybe not the
 associated Mach ports either).  That's because there's no way to free the stack
 after the thread dies (because the thread of control is gone); the stack needs
 to be freed by something else, and there's nothing convenient to do it.  There
@@ -26,3 +30,5 @@ However, it isn't really a leak, because the unfreed resources do get used for
 the next thread.  So the issue is that the shrinkage of resource consumption
 never happens, but it doesn't grow without bounds; it just stays at the maximum
 even if the current number of threads is lower.
+
+The same issue exists in [[libpthread]].
diff --git a/hurd/running/qemu.mdwn b/hurd/running/qemu.mdwn
index 512ea602..3648c7d6 100644
--- a/hurd/running/qemu.mdwn
+++ b/hurd/running/qemu.mdwn
@@ -105,6 +105,16 @@ If your machine supports hardware acceleration, you should really use the kvm va
 
 to the command line, see below, if you are running Linux kernels 2.6.37 or 2.6.38 else IRQs may hang sooner or later. The kvm irq problems will be solved in kernel 2.6.39. 
 
+IRC, freenode, #hurd, 2012-08-29:
+
+    <braunr> youpi: do you remember which linux versions require the
+      -no-kvm-irqchip option ?
+    <braunr> your page indicates 2.6.37-38, but i'm seeing weird things on
+      2.6.32
+    <braunr> looks like a good thing to use that option all the time actually
+    <gnu_srs> seems like kvm -h says: -no-kvm-irqchip and man kvm says:
+      -machine kernel_irqchip=off
+
 /!\ Note that there are known performance issues with KVM on Linux 2.6.39
 kernels, compared to 2.6.32: [[!debbug 634149]].  We're preparing on a change
 on our side to work around this.
diff --git a/hurd/settrans/discussion.mdwn b/hurd/settrans/discussion.mdwn
index c9ec4d34..74f1c8f5 100644
--- a/hurd/settrans/discussion.mdwn
+++ b/hurd/settrans/discussion.mdwn
@@ -1,4 +1,4 @@
-[[!meta copyright="Copyright © 2011 Free Software Foundation, Inc."]]
+[[!meta copyright="Copyright © 2011, 2012 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,3 +16,24 @@ License|/fdl]]."]]"""]]
     <antrik> ugh... I just realized why settrans -a without -f doesn't
       generally work on filesystem translators
     <antrik> obviously, it needs -R too!
+
+
+# IRC, freenode, #hurd, 2012-08-17
+
+    <antrik> youpi: no, only the -g is redundant; i.e. -ga is the same as -a
+    <antrik> (actually, not redundant, but rather simply meaningless in this
+      case)
+    <antrik> -g tells what to do with an active translator *when a passive one
+      is changed*
+    <antrik> if no passive one is changed, it does nothing
+    <antrik> (and I realized that after using the Hurd for only 6 years or so
+      ;-) )
+    <braunr> it's not obvious
+    <antrik> braunr: indeed. it's not obvious at all from the --help output :-(
+    <antrik> not sure though how to make it clearer
+    <braunr> the idea isn't obvious
+    <braunr> perhaps telling that "setting a passive translator" also applies
+      to removing it, i.e. setting it to none
+    <antrik> braunr: well, the fact that a translator is unset by setting it to
+      nothing is unclear in general, not only for passive translator. I agree
+      that pointing this out should make things much more clear in general...
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