Merge remote-tracking branch 'fp/master'

Conflicts:
	open_issues/glibc_madvise_vs_static_linking.mdwn

4 files changed, 163 insertions, 5 deletions

diff --git a/hurd/faq/slash_usr_symlink/discussion.mdwn b/hurd/faq/slash_usr_symlink/discussion.mdwn
new file mode 100644
index 00000000..219e14e4
--- /dev/null
+++ b/hurd/faq/slash_usr_symlink/discussion.mdwn
@@ -0,0 +1,45 @@
+[[!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, freenode, #hurd, 2012-02-01
+
+    <marcusb> I remember the time when we had a /usr symlink.  Now fedora 17
+      will move / to /usr and have /foo symlinks.  :)
+    <marcusb> braunr:
+      http://www.freedesktop.org/wiki/Software/systemd/TheCaseForTheUsrMerge
+    <marcusb> braunr: fedora and others are merging /bin, /sbin and some other
+      into /usr
+    <marcusb> braunr: back in 1998 we tried for two years or so to have /usr ->
+      ..  in Debian GNU/Hurd, but eventually we gave up on it, because it broke
+      some stuff
+    <gnu_srs> marcusb: Hi, which one is better (in your opinion): / or /usr?
+    <marcusb> gnu_srs: fedora says that using /usr allows better separation of
+      distribution files and machine-local files
+    <braunr> marcusb: won't it break remote /usr ?
+    <marcusb> so you can atomically mount the OS files to /usr
+    <marcusb> gnu_srs: but in the end, it's a wash
+    <marcusb> personally, I think every package should get its own directory
+    <braunr> marcusb: what PATH then ?
+    <marcusb> braunr: well, I guess you'd want to assemble a union filesystem
+      for a POSIX shell 
+    <braunr> marcusb: i don't see what you mean :/
+    <braunr> ah this comes from Lennart Poettering
+    <marcusb> braunr: check out for example how http://nixos.org/ does it
+    <manuel> braunr: something like, union /package1/bin /package2/bin
+      /package3/bin for /bin, /package1/lib /package2/lib /package3/lib for
+      /lib, etc. I guess
+    <braunr> manuel: would that scale well ?
+    <marcusb> the idea that there is only one correct binary for each program
+      with the name foo is noble, but a complete illusion that hides the
+      complexity of the actual configuration management task
+    <braunr> marcusb: right
diff --git a/hurd/translator.mdwn b/hurd/translator.mdwn
index 3527267f..619c0db5 100644
--- a/hurd/translator.mdwn
+++ b/hurd/translator.mdwn
@@ -1,4 +1,4 @@
-[[!meta copyright="Copyright © 2007, 2008, 2009, 2010, 2011 Free Software
+[[!meta copyright="Copyright © 2007, 2008, 2009, 2010, 2011, 2012 Free Software
 Foundation, Inc."]]
 
 [[!meta license="""[[!toggle id="license" text="GFDL 1.2+"]][[!toggleable
@@ -75,7 +75,8 @@ available.
 Read about translator [[short-circuiting]].
 
 The [[concept|concepts]] of translators creates its own problems, too:
-[[open_issues/translators_set_up_by_untrusted_users]].
+[[open_issues/translators_set_up_by_untrusted_users]], and
+[[trust_the_behavior_of_translators]].
 
 
 # Existing Translators
diff --git a/hurd/translator/devfs.mdwn b/hurd/translator/devfs.mdwn
index 27df23aa..8784e998 100644
--- a/hurd/translator/devfs.mdwn
+++ b/hurd/translator/devfs.mdwn
@@ -1,12 +1,12 @@
-[[!meta copyright="Copyright © 2009 Free Software Foundation, Inc."]]
+[[!meta copyright="Copyright © 2009, 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]]."]]"""]]
+is included in the section entitled [[GNU Free Documentation
+License|/fdl]]."]]"""]]
 
 `devfs` is a translator sitting on `/dev` and providing what is to be provided
 in there in a dynamic fashion -- as compared to static passive translator
@@ -18,3 +18,22 @@ settings as they're used now.
 
 If applicable, it has to be taken care that all code concerning the page-in
 path is resident at all times.
+
+---
+
+# IRC, freenode, #hurd, 2012-01-29
+
+    <pinotree> what would be an hurdish way to achieve something like the
+      various system (udev, devfs, devd, etc) for populating devices files
+      automatically according to the found system devices?
+    <pinotree> (not that i plan anything about that, just curious)
+    <youpi> it's not really a stupid question at all :)
+    <youpi> I guess translators in /dev
+    <youpi> such as a blockfs on /dev/block
+    <antrik> pinotree: in an ideal world (userspace drivers and all), the
+      device nodes will be exported by the drivers themselfs; and the drivers
+      will be launched by the bus respective bus driver
+    <antrik> an interesting aspect is what to do if we want a traditional flat
+      /dev directory with unique device names... probably need some
+      unionfs-like translator that collects the individual driver nodes in an
+      intelligent manner
diff --git a/hurd/translator/tmpfs/discussion.mdwn b/hurd/translator/tmpfs/discussion.mdwn
index 0409f046..1d441c7d 100644
--- a/hurd/translator/tmpfs/discussion.mdwn
+++ b/hurd/translator/tmpfs/discussion.mdwn
@@ -283,3 +283,96 @@ License|/fdl]]."]]"""]]
     <mcsim> what kind of log do you mean?
     <antrik> vmstat 1 I mean
     <mcsim> ah...
+
+
+## IRC, freenode, #hurd, 2012-02-01
+
+    <mcsim> I run fsx with this command:  fsx -N3000 foo/bar -S4
+      -l$((1024*1024*8)). And after 70 commands it breaks.
+    <mcsim> The strangeness is at address 0xc000 there is text, which was
+      printed in fsx with vfprintf
+    <mcsim> I've lost log. Wait a bit, while I generate new
+    <jkoenig_> mcsim, what's fsx / where can I find it ?
+    <mcsim> fsx is filesystem exersiser
+    <mcsim> http://codemonkey.org.uk/projects/fsx/
+    <jkoenig_> ok thanks
+    <mcsim> i use it to test tmpfs
+    <mcsim> here is fsx that compiles on linux: http://paste.debian.net/154390/
+      and Makefile for it: http://paste.debian.net/154392/ 
+    <jkoenig_> mcsim, hmm, I get a failure with ext2fs too, is it expected?
+    <mcsim> yes
+    <mcsim> i'll show you logs with tmpfs. They slightly differ
+    <mcsim> here: http://paste.debian.net/154399/
+    <mcsim> pre last operation is truncate
+    <mcsim> and last is read
+    <mcsim> during pre-last (or last) starting from address 0xa000, every
+      0x1000 bytes appears text
+    <mcsim> skipping zero size read
+    <mcsim> skipping zero size read
+    <mcsim> truncating to largest ever: 0x705f4b
+    <mcsim> signal 2
+    <mcsim> testcalls = 38
+    <mcsim> this text is printed by fsx, by function prt
+    <mcsim> I've mistaken: this text appears even from every beginning 
+    <mcsim> I know that this text appears exactly at this moment, because I
+      added check of the whole file after every step. And this error appeared
+      only after last truncation.
+    <mcsim> I think that the problem is in defpager (I'm fixing it), but I
+      don't understand where defpager could get this text
+    <jkoenig_> wow I get java code and debconf templates
+    <mcsim> So, my question is: is it possible for defpager to get somehow this
+      text?
+    <jkoenig_> possibly recycled, non-zeroed pages?
+    <mcsim> hmmm... probably you're right
+    <jkoenig_> 0x1000 bytes is consistent with the page size
+    <mcsim> Should I clean these pages in tmpfs?
+    <mcsim> or in defpager?
+    <mcsim> What is proper way?
+    <jkoenig_> mcsim, I'd say defpager should do it, to avoid leaking
+      information, I'm not sure though.
+    <jkoenig_> maybe tmpfs should also not assume the pages have been blanked
+      out.
+    <mcsim> if i do it in both, it could have big influence on performance.
+    <mcsim> i'll do it only in defpager so far.
+    <mcsim> jkoenig_: Thank you a lot
+    <jkoenig_> mcsim, no problem.
+
+
+## IRC, freenode, #hurd, 2012-02-08
+
+    <tschwinge> mcsim: You pushed another branch with cleaned-up patches?
+    <mcsim> yes.
+    <tschwinge> mcsim: Anyway, any data from your report that we could be
+      interested in?  (Though it's not in English.)
+    <mcsim> It's completely in ukrainian an and mostly describes some aspects
+      of hurd's work.
+    <tschwinge> mcsim: OK.  So you ran out of time to do the benchmarking,
+      etc.?
+    <tschwinge> Comparing tmpfs to ext2fs with RAM backend, etc., I mean.
+    <mcsim> tschwinge: I made benchmarking and it turned out that tmpfs up to 6
+      times faster than ext2fs
+    <mcsim> tschwinge: is it possible to have a review of work, I've already
+      done, even if parallel writing doesn't work?
+    <tschwinge> mcsim: Do you need this for university or just a general review
+      for inclusion in the Git master branch?
+    <mcsim> general review
+    <tschwinge> Will need to find someone who feels competent to do that...
+    <mcsim> the branch that should be checked is tmpfs-final
+    <pinotree> cool, i guess you tested also special types of files like
+      sockets and pipes? (they are used in eg /run, /var/run or similar)
+    <mcsim> Oh. I accidentally created this branch. It is my private
+      branch. I'll delete it now and merge everything to mplaneta/tmpfs/master
+    <mcsim> pinotree: Completely forgot about them :( I'll do it by all means
+    <pinotree> mcsim: no worries :)
+    <mcsim> tschwinge: Ready. The right branch is mplaneta/tmpfs/master
+
+
+## IRC, freenode, #hurd, 2012-03-07
+
+    <pinotree> did you test it with sockets and pipes?
+    <mcsim> pinotree: pipes work and sockets seems to work too (I've created
+      new pfinet device for them and pinged it).
+    <pinotree> try with simple C apps
+    <mcsim> Anyway all these are just translators, so there shouldn't be any
+      problems.
+    <mcsim> pinotree: works