6 files changed, 44 insertions, 35 deletions
diff --git a/faq/issues/got_a_db_prompt.mdwn b/faq/issues/got_a_db_prompt.mdwn
index 0835520e..ce376728 100644
--- a/faq/issues/got_a_db_prompt.mdwn
+++ b/faq/issues/got_a_db_prompt.mdwn
@@ -5,24 +5,30 @@ 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]]."]]"""]]
 
-[[!meta title="I've just gotten a db> prompt"]]
+[[!meta title="Help, I've just gotten a db> prompt"]]
 
-Something bad happened in the kernel (think of it as the equivalent of the Linux
-Oops). The `db>` prompt is actually the kernel debugger. You can then type the
-`trace` command, which will bring you something like:
+If you see a `db>` prompt on the console, something unexpected and bad happened
+inside the [[GNU Mach kernel|microkernel/mach/gnumach]], which it cannot
+recover from.  (Think of it as the equivalent of a [[!wikipedia
+Linux_kernel_oops]], for example.)  The `db>` prompt is actually the GNU Mach
+kernel debugger waiting for your commands.  For example, you can then reboot
+the system by issuing the `reboot` command, or if you want to help analyze the
+problem, start by typing in the `trace` command, which will display the
+function call trace leading to the crash:
 
     0x8007cf1(8088488,5e,40000008,2aa008,0)
     0x80071bc(0,0,0,0,0)
     0x8006831(24fe00,2000,b,800,0)
 
-Which is actually the function call trace, which can be decyphered by using:
+This can be decyphered by using:
 
     $ addr2line -i -f -e /boot/gnumach 0x8007cf1 0x80071bc 0x8006831
 
-You can then send us the result of the `trace` and the `addr2line`, as well as
-the exact version of the gnumach kernel you were running, for further
-investigation. [[More information about the gnumach
+You can then [[send us|contact_us]] the results of the `trace` and the
+`addr2line` commands, as well as
+the exact version of the GNU Mach kernel you were running, for further
+investigation.  More information about the [[GNU Mach
 debugger|microkernel/mach/gnumach/debugging]] is available.
diff --git a/faq/support/0-drivers.mdwn b/faq/support/0-drivers.mdwn
index 1c6f58dc..54b2d744 100644
--- a/faq/support/0-drivers.mdwn
+++ b/faq/support/0-drivers.mdwn
@@ -15,7 +15,8 @@ Currently, for disks Mach integrates drivers from Linux 2.0 through some
 limits hardware support a lot, of course.  For network boards, we use the
 [[DDE]] toolkit to run linux 2.6.32 drivers in userland processes,
 which provides both long-term support for new hardware and safety against driver
-bugs. Xen is also supported, both blkfront and netfront.
+bugs.  [[microkernel/mach/gnumach/ports/Xen]] is also supported, both blkfront
+and netfront.
 
 Note however that we have of course not tested all drivers, we obviously don't
 even have all kinds of hardware. So we can not promise that they will all
diff --git a/faq/support/0-software.mdwn b/faq/support/0-software.mdwn
index 9c33a4db..e58e0bd8 100644
--- a/faq/support/0-software.mdwn
+++ b/faq/support/0-software.mdwn
@@ -11,16 +11,15 @@ License|/fdl]]."]]"""]]
 
 [[!meta title="What software is available for GNU?"]]
 
-As of March 2013, 78% of Debian packages have been ported on the Hurd. Of
-course, bug testing and fixing is welcome, as we have obviously not tested all
-of them.
+As of March 2013, 78% of all [Debian](http://www.debian.org/)
+[packages](http://packages.debian.org/) are available for [[Debian
+GNU/Hurd|hurd/running/debian]].  Of course, testing and bug fixing is welcome,
+as we have obviously not tested all of them.
 
-Most packages from [Debian](http://www.debian.org/)
-[GNU/Linux](http://www.gnu.org/gnu/linux-and-gnu.html)
-which aren't Linux-specific (see [Packages That Won't Be
+Generally, packages
+that aren't Linux-specific (see [Packages That Won't Be
 Ported](http://www.debian.org/ports/hurd/hurd-devel-debian))
-are expected to work on GNU/Hurd too. See the database in
-<http://packages.debian.org/>. Notably, [Xorg](http://www.x.org/),
+are expected to work on GNU/Hurd too.  Notably, [X.Org](http://www.x.org/),
 [GNOME](http://www.gnome.org/), [KDE](http://www.kde.org/),
 [Firefox](http://www.mozilla.org/firefox) work. See
 the [[hurd/porting/guidelines]] document for some common build problems and their
diff --git a/open_issues/llvm.mdwn b/open_issues/llvm.mdwn
index 22bbe947..2a4b4ed5 100644
--- a/open_issues/llvm.mdwn
+++ b/open_issues/llvm.mdwn
@@ -47,10 +47,10 @@ git log --reverse --topo-order --pretty=fuller --stat=$COLUMNS,$COLUMNS -w -p -C
 -->
 
 Last reviewed up to the [[Git mirror's sources|source_repositories/llvm]]: llvm
-760fa5dc8022dcf6982969c26ef566dfbeea979c (2013-03-10), clang
-3521c49fc4867ff9ac78d4ad6a9e3e5566ba8b83 (2013-03-10), compiler-rt
-07020829d181dcd352ff6f01eab4d353c37a19b6 (2013-03-09), test-suite
-3135166052dac85b312a98bafbc59a59511546d5 (2013-03-06).
+6f7becfe23f38e8c28e9422d883263974058aeed (2013-03-24), clang
+495cfa46300979642acde8d93a1f21c9291dac98 (2013-03-23), compiler-rt
+a06fe9183fbffb78798a444da9bc3040fdd444aa (2013-03-23), test-suite
+5a05572d268568fb15b48f374f9fc9f882adecd2 (2013-03-23).
 
   * <http://anonscm.debian.org/viewvc/pkg-llvm/llvm/trunk/debian/patches/>.
 
@@ -69,6 +69,8 @@ Last reviewed up to the [[Git mirror's sources|source_repositories/llvm]]: llvm
 
   * [low] Linuxisms
 
+      * In some CMake files (`CMakeLists.txt`, for example).
+
       * `test/`, `unittests`, `tools/clang/test/`, `tools/clang/unittests/` not
         yet examined.
 
@@ -100,10 +102,10 @@ Last reviewed up to the [[Git mirror's sources|source_repositories/llvm]]: llvm
 
 Here's a log of a LLVM build run; this is from our [[Git repository's
 sources|source_repositories/llvm]], llvm
-a276c9d4e58db920ed984a349b03cb6ef505bd00 (2013-03-10), clang
-29f4b2545b11bff73a934e9f6138476a15ec8655 (2013-03-10), compiler-rt
-07020829d181dcd352ff6f01eab4d353c37a19b6 (2013-03-09), test-suite
-c1298f8eb55a6840bd4f438f71cfa3bda1fd30d8 (2013-03-10; 2013-03-06), run on
+dc218fb6ae3241f4b66e9bf2c9d6352efecc0a14 (2013-03-24), clang
+744290b5ecd48bddb4a6cf96d68cdc4a57e24e36 (2013-03-24), compiler-rt
+a06fe9183fbffb78798a444da9bc3040fdd444aa (2013-03-23), test-suite
+1821ab0ef1c73430705356fdfde3769460092382 (2013-03-24), run on
 kepler.SCHWINGE and coulomb.SCHWINGE.
 
     $ export LC_ALL=C
@@ -126,7 +128,7 @@ for the corresponding GNU/Linux build).  Using `--enable-debug-symbols
 the corresponding GNU/Linux build).  Also there is a separate
 `--enable-debug-runtime`.
 
-This takes up around 3 GiB, and needs roughly 1.25 h on kepler.SCHWINGE and
+This takes up around 3.2 GiB, and needs roughly 1.5 h on kepler.SCHWINGE and
 5.25 h on coulomb.SCHWINGE.
 
 Configuring without `--enable-optimized` even crashes mighty darnassus,
diff --git a/open_issues/visudo.mdwn b/open_issues/visudo.mdwn
index 0332b0e3..e9892e33 100644
--- a/open_issues/visudo.mdwn
+++ b/open_issues/visudo.mdwn
@@ -1,5 +1,4 @@
-[[!meta copyright="Copyright © 2013 Free Software Foundation,
-Inc."]]
+[[!meta copyright="Copyright © 2013 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
@@ -9,6 +8,8 @@ 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]]."]]"""]]
 
+[[!meta title="visudo: /etc/sudoers is busy, try again later"]]
+
 [[!tag open_issue_hurd]]
 
 visudo does not work:
diff --git a/toolchain/logs b/toolchain/logs
-Subproject 3196edb72f833a64ad57f7d8e60392b0168e57c
+Subproject 17ecfe30c4c1cb2c5833bc58f0ec355ec38b107