Reorganize the Hurd FAQ in a single place

move all the hurd faq pages to the top-level faq directory;
the faq.mdwn index now uses two simples map of all the subpages
(one for the debian items, and the other for the non-debian items)

TODO: now some of the items would need better titles

26 files changed, 1154 insertions, 0 deletions

diff --git a/faq/2_gib_partition_limit.mdwn b/faq/2_gib_partition_limit.mdwn
new file mode 100644
index 00000000..195191cb
--- /dev/null
+++ b/faq/2_gib_partition_limit.mdwn
@@ -0,0 +1,13 @@
+[[!meta copyright="Copyright © 2007, 2008 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]]."]]"""]]
+
+[[!meta title="2 GiB Partition Limit"]]
+
+The 2 GiB limit has been removed in Debian GNU/Hurd.
diff --git a/faq/bad_hypermeta_data.mdwn b/faq/bad_hypermeta_data.mdwn
new file mode 100644
index 00000000..bc960e30
--- /dev/null
+++ b/faq/bad_hypermeta_data.mdwn
@@ -0,0 +1,15 @@
+[[!meta copyright="Copyright © 2007, 2008 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]]."]]"""]]
+
+If you get the error `bad hypermeta data` when trying to mount an ext3
+partition from GNU/Linux, that is usually because the file system has not been
+unmounted cleanly (maybe GNU/Linux got suspended to disk) and the Hurd cannot
+mount it as ext2 without checking.  Either boot back into GNU/Linux and unmount
+it or you can try to run `fsck.ext3` from GNU/Hurd directly.
diff --git a/faq/debian/apt_umount.mdwn b/faq/debian/apt_umount.mdwn
new file mode 100644
index 00000000..db0dbfd1
--- /dev/null
+++ b/faq/debian/apt_umount.mdwn
@@ -0,0 +1,25 @@
+[[!meta copyright="Copyright © 2007, 2008 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]]."]]"""]]
+
+[[!meta title="apt: unmount cdroms"]]
+
+You can add a shell script umount so that apt can automatically unmount cdroms.
+
+    #!/bin/sh
+    # Filename: /usr/bin/umount
+    
+    settrans -fg "$@"
+
+Give executable permission to the script.
+
+    # chmod +x /usr/bin/umount
+
+In `/etc/fstab` add a trailing `/` after cdrom like `/cdrom/` since apt uses a
+trailing `/`.
diff --git a/faq/debian/other_repositories.mdwn b/faq/debian/other_repositories.mdwn
new file mode 100644
index 00000000..88781d46
--- /dev/null
+++ b/faq/debian/other_repositories.mdwn
@@ -0,0 +1,16 @@
+[[!meta copyright="Copyright © 2007, 2008 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]]."]]"""]]
+
+If you want to use the `apt-get source` facility, make sure that
+`/etc/apt/sources.list` contains a line like
+
+    deb-src http://ftp.de.debian.org/debian unstable main
+
+... replacing _de_ with your homeland's code.
diff --git a/faq/debugging_inside_glibc.mdwn b/faq/debugging_inside_glibc.mdwn
new file mode 100644
index 00000000..91b71d64
--- /dev/null
+++ b/faq/debugging_inside_glibc.mdwn
@@ -0,0 +1,19 @@
+[[!meta copyright="Copyright © 2007, 2008, 2009 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]]."]]"""]]
+
+To get [[debugging]] information for glibc, you need to install the
+`libc0.3-dbg` package.  At the place [[debugging/GDB]] looks for debugging
+symbols by default (`/usr/lib/debug/lib/`), Debian's `libc0.3-dbg` stores only
+the frame unwind information used for backtracing.  If you want to step into
+glibc while debugging, you need to add `LD_LIBRARY_PATH=/usr/lib/debug` to
+debugged program's environment (`set env VAR value` from the GDB command line).
+If that still does not work, try `LD_PRELOAD=/usr/lib/debug/libc.so.0.3`
+instead.
diff --git a/faq/debugging_translators.mdwn b/faq/debugging_translators.mdwn
new file mode 100644
index 00000000..b55484e1
--- /dev/null
+++ b/faq/debugging_translators.mdwn
@@ -0,0 +1,15 @@
+[[!meta copyright="Copyright © 2007, 2008 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]]."]]"""]]
+
+In order to [[debug|debugging]] translators and being able to step into glibc
+during it, you need the `hurd-dbg` and `libc0.3-dbg` packages installed.  If you need to debug the initialization of the translator,
+start the translator like `settrans -P /foo /usr/bin/env
+LD\_LIBRARY\_PATH=/usr/lib/debug /hurd/foofs`. The `-P` option will make it
+pause and you will be able to attach [[debugging/GDB]] to the process.
diff --git a/faq/df.mdwn b/faq/df.mdwn
new file mode 100644
index 00000000..bbd3a7b9
--- /dev/null
+++ b/faq/df.mdwn
@@ -0,0 +1,19 @@
+[[!meta copyright="Copyright © 2007, 2008 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]]."]]"""]]
+
+There is no `/etc/mtab` (due to dynamic translator startup, its content is hard
+to define actually, see
+[[the mtab GSoC project idea|community/gsoc/project_ideas/mtab]]),
+so just running `df` will yield the following error.
+
+    df: cannot read table of mounted file systems
+
+Pass `df` a path like `df /` or `df ./` to see the disk usage of that particular
+file system.
diff --git a/faq/eata.mdwn b/faq/eata.mdwn
new file mode 100644
index 00000000..fa7dbdec
--- /dev/null
+++ b/faq/eata.mdwn
@@ -0,0 +1,13 @@
+[[!meta copyright="Copyright © 2010 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]]."]]"""]]
+
+In some virtual machines (e.g. VirtualBox), "probing eata on XXX" may be
+quite long. This is apparently due to poor efficiency of the virtualizer, not
+Mach. There is no such issue on real hardware or using qemu/kvm.
diff --git a/faq/how_about_drivers.mdwn b/faq/how_about_drivers.mdwn
new file mode 100644
index 00000000..0e1887ba
--- /dev/null
+++ b/faq/how_about_drivers.mdwn
@@ -0,0 +1,18 @@
+[[!meta copyright="Copyright © 2009, 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
+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]]."]]"""]]
+
+[[!meta title="What drivers does GNU/Hurd have?"]]
+
+Currently, for disks Mach integrates drivers from Linux 2.0 through some
+[[community/gsoc/project_ideas/driver_glue_code]].  As it's very old, that
+limits hardware support a lot, of course.  For network boards, we use the
+[[DDE]] toolkit to run linux drivers in userland processes,
+which provides both long-term support for new hardware and safety against driver
+bugs.
diff --git a/faq/how_to_switch_microkernels.mdwn b/faq/how_to_switch_microkernels.mdwn
new file mode 100644
index 00000000..21f7a371
--- /dev/null
+++ b/faq/how_to_switch_microkernels.mdwn
@@ -0,0 +1,15 @@
+[[!meta copyright="Copyright © 2009, 2010 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]]."]]"""]]
+
+[[!meta title="How difficult would it be to switch to another microkernel?"]]
+
+One would have to reimplement the `mach/` and `sysdeps/mach/` parts of
+[[glibc]] and [[libpthread]].  Quite a few other Hurd tools also assume a
+[[microkernel/Mach]] kernel and would have to be adapted or rewritten.
diff --git a/faq/hurd_console.mdwn b/faq/hurd_console.mdwn
new file mode 100644
index 00000000..5cccc83c
--- /dev/null
+++ b/faq/hurd_console.mdwn
@@ -0,0 +1,13 @@
+[[!meta copyright="Copyright © 2007, 2008, 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
+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]]."]]"""]]
+
+Edit `/etc/default/hurd-console` to configure the Hurd console.
+See [[console]] for further information about the Hurd console.
diff --git a/faq/kernel_logs.mdwn b/faq/kernel_logs.mdwn
new file mode 100644
index 00000000..d539bf1b
--- /dev/null
+++ b/faq/kernel_logs.mdwn
@@ -0,0 +1,14 @@
+[[!meta copyright="Copyright © 2007, 2008, 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
+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]]."]]"""]]
+
+[[!meta title="dmesg, kernel logs"]]
+
+There is no dmesg command: the kernel does not keep a buffer of its messages. syslog however dumps them into `/var/log/dmesg`, so you can simply cat that.
diff --git a/faq/native-install_doesnt_finish.mdwn b/faq/native-install_doesnt_finish.mdwn
new file mode 100644
index 00000000..a852e1dd
--- /dev/null
+++ b/faq/native-install_doesnt_finish.mdwn
@@ -0,0 +1,24 @@
+[[!meta copyright="Copyright © 2009 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]]."]]"""]]
+
+Copying baseGNU to the virtual disk works. Even booting got through but when I
+try to run native-install it never gets to the very end. First time it froze on
+*sed* package, the other time on *sysv-rc*.
+
+> How much memory did you configure for the [[QEMU]] system?  It may simply be
+> -- I've seen this myself -- that the system runs out of memory, as at the
+> native-install stage (I think at least) swap is not yet configured and
+> enabled.  What I've been doing is: boot (with -s), MAKEDEV hdWHATEVER in
+> /dev/ for the swap device, run /hurd/mach-defpager, followed by swapon
+> /dev/hdWHATEVER.  Does this help?
+
+>> Thank You very much, more memory solved the freezing.
+
+[[!tag open_issue_hurd]]
diff --git a/faq/off.mdwn b/faq/off.mdwn
new file mode 100644
index 00000000..8c90d53e
--- /dev/null
+++ b/faq/off.mdwn
@@ -0,0 +1,21 @@
+[[!meta copyright="Copyright © 2010, 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
+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]]."]]"""]]
+
+[[!meta title="How am I supposed to shut my Hurd system down?"]]
+
+The GNU/Hurd does not use SYSV runlevels, so commands like
+
+    $ shutdown -h now
+
+will not work. Simply use the equivalent shortcut
+
+    $ halt
+
+which is provided natively on GNU/Hurd, instead of from SYSV runlevels.
diff --git a/faq/old-stuff.mdwn b/faq/old-stuff.mdwn
new file mode 100644
index 00000000..f5be2814
--- /dev/null
+++ b/faq/old-stuff.mdwn
@@ -0,0 +1,30 @@
+In addition to the [general FAQ](http://www.gnu.org/software/hurd/docs.html#TOCfaq) there are the following typical newbie questions. (There is an [updated version](http://tuxou.ouvaton.org/hurd/) which is not official yet.)
+
+If you still have problems, do not hesitate to make use of the [[mailing lists]] or the [[IRC]].
+
+* **_You say GNU, don't you mean GNU/Hurd?_**
+  * Yes and no. GNU refers to the system as a whole, while GNU/Hurd is more specific, saying that it is the GNU system running on the Hurd -- to differentiate it from the GNU system running on Linux, GNU/Linux.
+
+* **_Why can't I get the answers I need from Hurd hackers?_**
+  * This [document](http://www.catb.org/~esr/faqs/smart-questions.html) may help you understand some developers attitudes and social norms.
+
+* **_Where are the virtual consoles I use when running Linux?_**
+  * The userland [[console]] provides it. You could still [use screen](http://www.gnu.org/software/hurd/faq.en.html#q4-6) of course.
+
+* **_What is a translator?_**
+  * The official FAQ [answers](http://www.gnu.org/software/hurd/faq.en.html#q4-2) this question by a reference to [hurd-doc-translator](http://www.debian.org/ports/hurd/hurd-doc-translator).
+
+* **_Where's the sauce?_**
+  * It's on [Savannah](http://savannah.gnu.org). See also the [GNU Development Resources](http://www.gnu.org/software/devel.html), for more information.
+
+* **_What is GNU Mach vs. oskit-mach?_**
+  * There used to be different versions of the Mach microkernel that supported the Hurd that runs on top of it. We currently only use GNU Mach. For more info, see [[Mach]]
+
+* **_What software is available for GNU?_**
+  * Most (3/4) packages from [Debian](http://www.debian.org/) [GNU/Linux](http://www.gnu.org/gnu/linux-and-gnu.html) which aren't linux-specific ([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, [GNOME](http://www.gnome.org), and [KDE](http://www.kde.org) work. See the [[porting/guidelines]] document for some common build problems and their solutions.
+  * If you can't fetch a package with "apt-get install ", try building it from source: "apt-get source  &amp;&amp; cd &lt;package\_dir&gt; &amp;&amp; debian/rules binary".
+  * As of March 2013, 78% of Debian packages have been ported on the Hurd. Of course, bug testing is welcome.
+
+* **_How do I initialize a serial console on the Hurd?_**
+  * You can try out the Serial Howto at <http://www.nongnu.org/thug/serial-howto.txt>
+  * For kernel messages, you can append `console=com0` to the kernel command line.
diff --git a/faq/old_faq.txt b/faq/old_faq.txt
new file mode 100644
index 00000000..24127462
--- /dev/null
+++ b/faq/old_faq.txt
@@ -0,0 +1,533 @@
+[[!meta copyright="Copyright © 2001, 2002, 2003, 2004, 2005, 2008 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]]."]]"""]]
+
+            Frequently Asked Questions about the GNU Hurd
+
+This document attempts to answer the questions that most often plague
+users when they are talking about, installing, using, compiling and
+developing the GNU Hurd as well as its binary distribution Debian
+GNU/Hurd.  Be sure to read this before asking for help.
+
+The GNU Hurd is under active development and a stable version has not
+yet been released.  Be aware that:  there is a lot of work yet to be
+completed; you will find bugs; your system will crash.  That said, there
+is a lot of room for contributions at all levels:  development of the
+Hurd and Mach proper, porting applications, writing documentation and,
+most importantly, user feedback.
+
+Should you have a question that is not answered by this document and you
+feel that it should be, submit it and, if possible, with an answer.
+
+Each section is copyright its respective author(s).  Permission is
+granted to copy, distribute and/or modify this document under the terms
+of the GNU Free Documentation License, Version 1.1 or any later version
+published by the Free Software Foundation; with no Invariant Sections,
+with no Front-Cover Texts and with no Back-Cover Texts.  A copy of the
+license is included in the file COPYRIGHT.
+
+                                                     Neal H Walfield
+						     neal@cs.uml.edu
+
+? Installation
+
+??	What partition type should I use for my GNU/Hurd partitions?
+
+{MB} You should use an ext2 filesystem.  Alternatively, you may use BSD
+style ufs.  The partition type number for ext2fs is 0x83 (this is the
+same as in Linux), not 0x63 (GNU HURD).  Thomas explains why 0x63 is the
+wrong choice:
+
+	One day we may have a new filesystem format, which would
+	probably be called the GNU Hurd filesystem format, and might
+	well use that partition code.
+
+Regardless, as Roland points out, it is always an error to use that code
+for an ext2fs partition, 
+
+??	How do I name partitions?
+
+{MB,NHW} I knew you would ask this.  If I had to reduce this FAQ to only
+one question, I'd choose this one.  It is pretty easy, but you have to
+know that there are actually several incompatibly naming convention.
+
+First, the Hurd:  if the disk is question is a SCSI disk, you must know
+the SCSI device number; if it is an IDE disk, you must know what
+controller the disk is on and whether it is a master or a slave.  The
+Hurd uses the BSD naming convention which, is to say, disks are ordered
+according to their physical location, numerically, starting from zero.
+This naming scheme is quite similar to that found in Linux.  There, the
+master disk on the primary controller is designated as `hda' and the
+slave as `hdb'.  On the secondary controller, the master and the slave
+are designated by `hdc' and `hdd' respectively.  Under the Hurd, `hda'
+would become `hd0', `hdb' would be referred to as `hd1', etc.
+
+In the Hurd, like in BSD, partitions are called `slices' and are
+numbered starting from one.  Thus, to name a particular partition, we
+take the disk name, append a `s' and the partition number.  Again, this
+is similar to Linux except, there is no `s'.  For instance, `hda1' would
+become `hd0s1'.
+
+GRUB, the boot loader, uses a completely different nomenclature: it
+probes the BIOS and appends each disk in turn to an array.  Disks are enumerated
+using zero based arrays. GRUB 2 enumerates partitions from one, while GRUB 1
+used to enumerate them from zero.
+The format is:
+`hd (<disk>, <partition>)'.  Thus, in GRUB 2 `hd (0, 1)' refers to the first
+partition on the first drive detected by the BIOS (or the second partition with
+GRUB 1).  As Grub now has tab
+completion, there is not a lot of guess work.
+
+??	Can I use partitions larger than 2GB?
+
+{ST} Yes. Disk drivers however currently do not support more than 2^32 sectors, i.e.
+2TiB.
+
+??	How much swap do I need?
+
+{ST} The usual rule of thumb applies: the same amount as RAM, for instance.
+
+??	Can I share swap space between GNU/Linux and GNU/Hurd?
+
+{NHW} Yes.  The default pager recognises and respects Linux swap
+partitions.  It will also swap to a raw partition, i.e. anything that it
+does not recognize as Linux swap.  Therefore: BE CAREFUL.
+
+??	Why do I get ``Operation not permitted error''?
+
+{MB} You forgot to set the file system owner of the GNU/Hurd partition to
+``hurd''.  The Hurd uses additional information in the inodes to set
+translators.  To make this work, the partition must be marked as ``owned
+by the Hurd''.  This is normally done by passing the `-o hurd' option to
+`mke2fs' when creating ext2 system from other operating systems
+(filesystems created in GNU/Hurd automatically enable this option).
+If you failed to do this, you can still use the `e2os' script.
+
+??	After `native-install' is finished, I had to write tthhiiss
+	wwaayy.  In particular, I had to type `rreebboooott' to reboot.
+
+{MB} Funny, isn't it? In addition to the rescue `term' server in
+`/tmp/console', another `term' server got started and is clobbing the
+keyboard input.  After a reboot this problem vanishes as only one `term'
+server will remain.  If `tar' would support translator, we would not
+have this problem...  Even if you don't experience this problem right
+after the installation, reboot immediately so you don't hit this bug by
+accident.
+
+? Setup
+
+??	How do I add a swap partition?
+
+{MB} A swap partition is also called a paging file.  Usually, it is
+sufficient to add the swap partition to `/etc/fstab', just as you would
+under Linux.  You can swap to a Linux swap partition and the Hurd will
+honour the Linux swap signature (both versions).  The Hurd will just as
+happily swap to any other raw disk space and overwrite anything it
+finds.  So, be careful!
+
+If you want to swap to a file or make sure that it checks the Linux swap
+signature before, you need to edit `/boot/servers.boot'.  The syntax is
+the partition device file name plus, optionally, the swap file inside an
+ext2fs partition, followed by a space and then one of:
+`$(add-raw-paging-file)', `$(add-linux-paging-file)',
+`$(add-paging-file)'.  The first works with any partition or file and
+does not honour any swap signature or other data.  The second has a
+safety check and only uses the file if a Linux swap signature is found.
+The third looks for a swap signature first and falls back to raw paging
+if it failed to find one.  This is also the default for entries in
+`/etc/fstab'.
+
+??	How do I set up a network?
+	How do I set up a loopback device?
+
+{MB} In the former case, be sure that GNU Mach detected your network
+card.  Either way, you need to setup `pfinet'.  Documentation can be
+found at:
+
+	http://www.debian.org/ports/hurd/hurd-doc-server#pfinet
+
+Don't forget to fill in `/etc/resolv.conf', `/etc/hosts', etc.
+
+Of course, you only need to do this if the installation routine didn't
+do it for you.
+
+??	Can I use the GNU/Linux version of `e2fsck' on a GNU/Hurd partition?
+
+{MB} Yes, at least since `e2fsprogs-1.05'.  Check this with `e2fsck -V'
+first.
+
+{NHW} Do not try to defrag your partition as this utility does not know
+about translators.
+
+??	Why are pipes not working?
+
+{MB} `settrans -fgc /servers/socket/1 /hurd/pflocal' should help.
+
+? Usage
+
+??	Where is the documentation?
+
+{NHW,MM} There are neither man pages nor info nodes for the Hurd
+translators and commands.  Documentation lives inside of the binaries
+and can be found by passing the `--help' option to a given command.
+For instance:
+
+	# /hurd/ext2fs --help
+
+will tell you what types of options the ext2fs translator accepts.
+
+The GNU/Hurd User's Guide and the GNU Hurd Reference Manual both
+provide some help about the usage of and concepts behind the GNU Hurd.
+You can find them, among others, at:
+
+	http://www.gnu.org/software/hurd/docs.html
+
+??	What is a translator?
+
+{MB} There is a text about translators available at:
+
+	http://www.debian.org/ports/hurd/hurd-doc-translator
+
+Read this and ask further questions on the mailing lists.
+
+??	What is the login shell?
+
+{MB} The Hurd has the concept of a not-logged in user.  This user has
+neither user ids nor groups ids.  This stems from the fact that the Hurd
+supports uid and gid sets and one possibility is, of course, the empty
+set.  Rather than deny access in this case, filesystems in the Hurd offer a
+fourth permission triplet (i.e. rwx) which is used to determine the
+privileges for users with no credentials.  This, however, needs to be
+enabled on a file by file basis.  By default, the `other' permission
+triplet is used.
+
+The Hurd login shell is a shell running with neither uids nor gids.  To
+restrict access to your files, either enable and change the fourth
+permission triplet or change the login shell of the `login' user in the
+password file to `/bin/loginpr' which implements the standard login
+prompt.
+
+??	How do I use non-US keyboard bindings?
+
+{ST} On Debian Hurd, you can configure the console layout from
+`/etc/default/hurd-console`.
+
+??	How do I enable color on the console?
+
+{NHW} If you are using the GNU Mach microkernel, you can set your
+terminal to `mach-color'.  For instance:
+
+	# export TERM=mach-color
+
+??	How can I enable virtual consoles?
+
+{ST} On Debian Hurd, it is already enabled by default, and configured from
+`/etc/default/hurd-console`.
+
+{AMS} This can be done by running the following command:
+
+	console -d vga -d pc_kbd -d generic_speaker /dev/vcs
+
+If something went wrong, or if you just wish to exit the Hurd console
+then hitting C-A-<backspace> will exit it.
+
+??	What is the status of X?
+
+{MB} It works!  The packages are available at any Debian ftp mirror.
+XFree86 4.0.2 is available, as are some of the v3 servers.  Instructions
+on how to use the packages are in the mailing list archive (link follow
+later).
+
+??	What are these strange pids `0`, `2', `3', `4`, and `5`?
+
+{MB,ST} Zero is the `proc` processus server (and thus does not really have a pid
+:) ) Two is the kernel, three is the root filesystem server, four is the `exec`
+server (which handles starting programs), five is the `auth` server (which
+handles user authentication).
+
+??	Why does `ps aux' give me strange output?
+
+{MB,MM} Try `ps Aux'.  Indeed, under GNU/Hurd, `ps aux' doesn't list
+all processes: it omits the session and group leaders, and the
+processes without parent.
+
+??	I have a hung process that I want to kill, however, `ps' is now
+	hanging too.
+
+{MB} Interrupt it and pass it the `-M' option.
+
+{NHW} By default, `ps' gathers information from both the proc server and
+the processes themselves (via their message port).  If a process it
+hung, it will not be able respond to its message port and thus, ps will
+wait forever.  The `-M' option instructs ps to not gather information
+that would require use of the message port.
+
+??	Where are ...
+
+{MB} `dmesg' is not available. You can read `/var/log/dmesg` instead.
+
+??	Why does the command `df' not work?
+
+{NHW} It does, you just have to tell it what filesystem to query.  E.g.
+
+	# df /
+
+??	Why are my translators dying?
+
+{NHW} Try passing the `-ap' flag to settrans.  By default, settrans only
+sets a passive translator, therefore, no output will show up on your
+terminal.  Using `-ap', however, sets both the active and the passive
+translator which, means that the translator starts immediately and its
+stderr is connected to you terminal.
+
+Additionally, the biggest problem is passing relative paths to passive
+translators.  You cannot predict what the current working directory of a
+translator will be when it is setup as a passive translator.
+
+??	Why can I `read' a directory?
+
+{MB} It is important to understand that there is nothing special about a
+directory under the Hurd, it is just another file.  This fits in with
+the translator concept where a translator can appear as a directory but
+provide also as a file.
+
+? Trouble shooting
+
+??	When the APM support in the BIOS spins down my disk drives, the
+	Hurd is unable to wake up.  What's wrong?
+
+{MB} APM is not supported in the current version of GNU Mach, sorry.
+Please disable APM in your BIOS setup.
+
+??	What are these messages referring to `default pager', `paging',
+	and `pager request'?
+
+{MB} The default pager handles virtual memory allocation.  If it can't
+allocate a new memory page because you are out of memory, some terrible
+things may happen.  Whenever you get errors referring to any of these,
+you either need more memory (make sure you have swap) or you have found
+a memory leak.
+
+??	What is a gratuitous error?
+
+{MB} This comes from `strerror(EGRATUITOUS)'.  If you check glibc's
+documentation, it will say that this error code has no purpose.  This,
+however, is not quite true.  You only get this when something terrible
+happens.  Thomas explains:
+
+	More precisely `EGRATUITOUS' officially means that some server
+	has responded in an impossible or protocol-violating fashion.
+	There are some cases in the Hurd where `EGRATUITOUS' is returned
+	and probably something else should be chosen instead.
+
+If you can reproduce this error message, please report it.
+
+??	What does ``computer bought the farm'' mean ?
+
+{FH} This message is the text that corresponds to the errno code
+`EIEIO'.  Roland McGrath explains:
+
+	That message is not output by any particular servers at
+	particular times; rather it is the perror text for the errno
+	code EIEIO, which is returned by various RPCs and functions
+	for a variety of "hopeless" error conditions.
+
+
+??	What does ``/dev/hd0s1: MOUNTED READ-ONLY; MUST USE `fsysopts
+	--writable''' mean?
+
+{NHW} In this case, /dev/hd0s1 was not unmounted cleanly.  The Hurd
+will, on boot up, run ``fsck -p'' on any partitions that it finds in
+/etc/fstab, so, you may want to consider adding this partition to that
+file.  If you are sure that the partition is fine, you can run:
+
+	# fsysopts /home --writable
+
+to ask the translator sitting on /home to change from read-only to
+read/write mode.  Note that the command is being sent to the filesystem
+and not the store (e.g. /dev/hd0s1).
+
+??	When GNU/Hurd crashes, GNU Mach automatically reboots.  Is
+	there anyway I can make it pause so I can write down the error?
+
+{MB} Pass the `-H' option to init (add it to the boot command line), and
+`init' will tell Mach to enter the kernel debugger instead to rebooting
+it.  At the debugger prompt (`db>'), you can type `reboot' any time to
+reboot the system.
+
+? Porting
+
+??	What programs have been ported?
+
+{NHW} A lot, take a look at the Debian archive.  Many programs, however,
+do not necessarily need to be ported; they have just never been
+compiled.
+
+??	Is porting easy?
+
+{NHW} Porting applications to GNU/Hurd is relatively easy assuming the
+application is POSIX compliant as GNU/Hurd does its best to be a
+conforming operating system.
+
+The most common error made by programmers is assuming the MAXPATHLEN and
+PATH_MAX are defined.  On most operating systems this is set to a few
+thousand, however, on GNU/Hurd, there is no maximum and thus, this is
+not set.  The correct thing to do is to submit a patch to the upstream
+author that allocates memory dynamically.
+
+??	How can I help?
+
+{ST} Please see the contributing page:
+http://www.gnu.org/software/hurd/contributing.html
+
+? Compiling
+
+??	Where can I get the source?
+
+{AMS} Instructions on how to download the CVS tree from Savanah are
+available at https://savannah.gnu.org/cvs/?group=hurd
+
+{NHW} To get the source to the latest debian package, look on any
+debian mirror.
+
+??	Can I cross compile?
+
+{ST} To REDO.
+
+{NHW} Yes.  If you are running Debian GNU/Linux on IA32, this is quite
+easy as there is a cheap cross compiler available; all that is required
+is installing the gcc-i386-gnu and mig-i386-gnu Debian packages.  When
+running configure, you will have to specify tools directly:
+
+	# MIG=/usr/bin/i386-gnu-mig CC=/usr/bin/i386-gnu-gcc \
+	  ../src/hurd/configure ...
+
+If you are running another distribution, you will have to do this the
+long way.  You can find instructions at the Cross Compiling HOW-TO
+available at:
+
+	http://hurddocs.sourceforge.net/howto/cross.html
+
+Farid Hajji <farid.hajji@ob.kamp.net> also talks about his experiences
+at:
+
+	http://lists.debian.org/debian-hurd-0012/msg00062.html
+
+??	Any general tips?
+
+{NHW} Yeah, building in the source tree is untested.  Try:
+
+	# ../src/hurd/configure ...
+
+? Development
+
+??	What is OSKit-Mach?
+
+{NHW,FH} There are two versions of GNU Mac that are in use: GNU Mach
+1.x and GNU Mach 2.x, formerly known as OSKit-Mach.  The former uses
+the drivers from Linux 2.0.x while the latter uses the University of
+Utah's OSKit library for drivers.  You can find out more about the
+OSKit library at:
+
+ 	http://www.cs.utah.edu/flux/oskit
+
+GNU Mach 2.x is usable, but some things are still missing or not
+working, like the serial port and scsi drivers.  This is why GNU Mach
+2.0 hasn't released yet and the two versions coexist.
+
+??	Where is the documentation?
+
+{NHW} There were several books written on the Mach kernel.  The
+information that they contain is still mostly pertinent and should be
+considered required reading for potential hackers.  They can be found
+at:
+
+	http://www.cs.cmu.edu/afs/cs/project/mach/public/www/doc/publications.html
+
+The documentation for the Hurd is quite inadequate.  The starting of a
+book, ``The GNU Hurd'' is in the doc directory in the Hurd source.  You
+can read this using:
+
+	# info hurd
+
+The authoritative place is, of course, the source code; that does not,
+however, mean that we would not welcome more documentation.  To get
+started, take a look at <hurd>/doc/navigating.
+
+??	How do I make sure that my code is POSIX compliant?
+
+{NHW} Unfortunately, you have to buy the POSIX standard from IEEE.  The
+Single Unix Specification version 2, a superset of POSIX, is available
+for free on the Internet.  Try:
+
+	http://www.unix-systems.org/online.html
+
+??	Who do I submit patches to?
+
+{NHW} If they are against the Hurd, Mach or MiG, send a patch to the
+bug-hurd mailing list.
+
+If they are against other packages, the Debian BTS is a good place.  In
+this case, be sure to advise the debian-hurd mailing list of the bug.
+
+??	In what format should patches for the Hurd and GNU Mach be?
+
+{MB} All patches should be sent in unified context diff format (option
+`-u' to GNU diff).  It is helpful for us if you also use the `-p'
+option which includes information about the function changed by a
+patch.  Changes that are similar can be grouped together in one file,
+but unrelated changes should be sent in seperate files.  The patches
+can be included in the message or as a MIME attachement.  They should
+not be compressed and/or archived unless they are very large, and if
+they are very large it is probably better to store them on-line at
+some place and only sent an URL.
+
+Write a ChangeLog entry for each change, following the format of the
+existing files.  Here is an example:
+
+	2000-12-02  Marcus Brinkmann  <marcus@gnu.org>
+
+		* ops.c (op_readlink): Before returning, check if the buffer
+	        pointed to by transp is ours.  If not, munmap it.
+	        (op_read): Likewise for bp.
+	        (op_readdir): Don't alloca a buffer here.  Instead initialize
+	        BUF and BUFSIZE to 0 and let the server (eh, MiG) do it.
+	        munmap BUF before returning.
+
+The file name and the name of the function changed should always be
+spelled out completely, and not abbreviated or otherwise mangled (like
+foo.{c,h}), because that would make searching for all changes to a
+file or function impossible.  Local variable names are all
+capitalized.  There are two spaces between sentences.  You can use
+``C-x 4 a'' in Emacs to add a new ChangeLog entry.  If you do that
+with the mark being in a function, Emacs will automatically fill in
+the file and function name for you.
+
+Do not send in a patch for the ChangeLog file.  Rather include the
+ChangeLog entries in the message that contains the patch.  Patches for
+ChangeLog files often conflict.
+
+If you have the original source tree in the directory `hurd-orig', and
+the modified source tree in the directory `hurd', the following
+command will produce a good patch (please make sure there are no extra
+files like backups in the modified tree, or leave away the option
+`-N').  You will need to collect the ChangeLog entries seperately.
+
+	# diff -x ChangeLog -Nurp hurd-orig hurd
+
+
+Answers were given by (in chronological order):
+* {NHW} Neal H Walfield  <neal@cs.uml.edu>
+* {MB} Marcus Brinkmann  <Marcus.Brinkmann@ruhr-uni-bochum.de>
+* {AMS} Alfred M. Szmidt <ams@gnu.org>
+* {OK} Ognyan Kulev	 <ogi@fmi.uni-sofia.bg>
+* {FH} Frédéric Henry	 <neryel@reveries.info>
+* {MM} Manuel Menal	 <mmenal@hurdfr.org>
+* {ST} Samuel Thibault	 <samuel.thibault@gnu.org>
diff --git a/faq/old_hurd_faq.txt b/faq/old_hurd_faq.txt
new file mode 100644
index 00000000..4ebe019b
--- /dev/null
+++ b/faq/old_hurd_faq.txt
@@ -0,0 +1,145 @@
+The Unofficial (and no longer maintained) GNU&nbsp;Hurd FAQ, Version 0.13
+
+Contributions by:
+
+Michael I. Bushnell <mib@gnu.org>
+Len Tower <tower@gnu.org>
+Trent Fisher <trent@gnurd.uu.pdx.edu>
+jlr@usoft.spb.su
+Remy Card <Remy.Card@masi.ibp.fr>
+Louis-Dominique Dubeau <hallu@info.polymtl.ca>
+
+Original Document by: Derek Upham <upham@cs.ubc.ca>
+
+
+==============================
+
+Contents:
+
+Q0.  Where can I get the Unofficial GNU Hurd FAQ?
+Q2.  Where can I get a copy?
+Q3.  Why bother writing a new OS when we have Linux and 386/BSD?
+Q4.  What's all this about Mach 3.0 (and Mach 4.0)?
+Q5.  Where can I find more information?
+Q7.  What sort of machines will run Hurd in the future?
+Q8.  What is the current development status?
+Q9.  What sort of system would we have if the Hurd was bootable today?
+
+==============================
+
+Q0.  Where can I get the Unofficial GNU Hurd FAQ?
+
+The Unofficial Hurd FAQ (what you are reading now) is occasionally
+posted to the USENET newsgroup, gnu.misc.discuss.  It is also
+available from
+
+   http://www.enci.ucalgary.ca/~gord/hurd/hurd-faq.txt  (Broken Link ?)
+
+If you don't have WWW access, you may send mail to me, Gordon
+Matzigkeit <gord@enci.ucalgary.ca> with a subject line that reads:
+
+   Subject: send hurd-faq
+
+You should receive a PGP-signed copy of the current version of this
+document in a matter of minutes.
+
+
+Q2.  Where can I get a copy?
+
+To put it simply, you can't.  It is still under development (by
+Michael Bushnell, Roland McGrath and Miles Bader).  It is almost, but
+not quite, at the point where you can do real work on it.  Keep your
+fingers crossed.
+
+Some people have actually bootstrapped it, but the work is not easy,
+and the current snapshot won't work until a new multiserver boot
+mechanism is made.
+
+If you *really* want to try it, beware that it is still pre-alpha
+code, and that it will likely crash on you.  See Trent Fisher's Hurd
+pages (under question 5) for the latest information.
+
+
+Q3.  Why bother writing a new OS when we have Linux and 386/BSD?
+
+For one thing, Linux and BSD don't scale well.  Hardware designers are
+shifting more and more toward multiprocessor machines for performance,
+and standard Unix kernels do not provide much multiprocessor support.
+The Hurd, on the other hand, runs on top of the Mach 3.0 micro-kernel
+[[1]] from CMU.  Mach was designed precisely for multiprocessing
+machines, so its portability should carry over nicely to the Hurd.
+
+In addition, the Hurd will be considerably more flexible and robust
+than generic Unix.  Wherever possible, Unix kernel features have been
+moved into unprivileged space.  Once there, anyone who desires can
+develop custom replacements for them.  Users will be able to write and
+use their own file systems, their own `exec' servers, or their own
+network protocols if they like, all without disturbing other users.
+
+The Linux kernel has now been modified to allow user-level file
+systems, so there is proof that people will actually use features such
+as these.  It will be much easier to do under the Hurd, however,
+because the Hurd is almost entirely run in user space and because the
+various servers are designed for this sort of modification.
+
+
+Q4.  What's all this about Mach 3.0 (and Mach 4.0)?
+
+As mentioned above, Mach is a micro-kernel, written at Carnegie Mellon
+University.  A more descriptive term might be a greatest-common-factor
+kernel, since it provides facilities common to all ``real'' operating
+systems, such as memory management, inter-process communication,
+processes, and a bunch of other stuff.  Unfortunately, the system
+calls used to access these facilities are only vaguely related to the
+familiar and cherished Unix system calls.  There are no "fork",
+"wait", or "sleep" system-calls, no SIGHUPs, nothing like that.  All
+this makes it rather difficult to, say, port GNU Emacs to a Mach box.
+
+The trick is, of course, to write an emulation library.  Unix programs
+can then use (what they think are) POSIX system calls and facilities
+while they are really using Mach system calls and facilities.
+
+The simplest way of going about this is to take an ordinary Unix
+kernel, open it up, and rip out all the machine-specific guts; any
+time the Unix kernel talks to the machine, replace the code with calls
+to the Mach micro-kernel.  Run this fake kernel on a Mach machine and
+you end up with something that looks and acts just like Unix (even to
+GNU Emacs).  Note that the Unix kernel we have implemented is just one
+Really Big Mach program (called a single-server).
+
+The Hurd, on the other hand, breaks the giant Unix kernel down into
+various Mach programs running as daemons.  Working in concert with
+facilities placed in the C library, these daemons provide all of the
+POSIX system-calls and features; from the outside they look just like
+a standard Unix kernel.  This means that, for practical purposes,
+anything that you can port to Linux will also port to the Hurd.
+
+Of course, if a user wishes to run his own daemons, he can do that as
+well....
+
+Mach 4.0 is an enhanced version of Mach 3.0, put out by the people at
+the University of Utah.  They are working on another free operating
+system, and part of it includes an enhanced, more flexible version of
+Mach.  The Hurd has moved to Mach 4.0, which is good, because it is a
+lot easier to build than 3.0 was.
+
+You can find more information on Mach by browsing the Hurd pages given
+in the next answer, or by looking at the Project Mach and Flux
+homepages at:
+
+Carnegie Mellon University (for Mach versions before 4.0):
+
+   http://www.cs.cmu.edu/afs/cs.cmu.edu/project/mach/public/www/mach.html
+
+the University of Utah (for Mach 4.0):
+
+   http://www.cs.utah.edu/projects/flux/mach4/html/
+
+
+
+==============================
+
+Footnotes:
+
+[[1]] Yes, I know that ``micro-kernel'' is about as apt a description
+as ``Reduced Instruction Set Chip'', but we're stuck with it.
diff --git a/faq/ps_hangs.mdwn b/faq/ps_hangs.mdwn
new file mode 100644
index 00000000..b58a3308
--- /dev/null
+++ b/faq/ps_hangs.mdwn
@@ -0,0 +1,13 @@
+[[!meta copyright="Copyright © 2007, 2008, 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
+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]]."]]"""]]
+
+If `ps` hangs, try `ps -M` which should still work by not getting detailed
+information from processes.
diff --git a/faq/ram_limit.mdwn b/faq/ram_limit.mdwn
new file mode 100644
index 00000000..447ff20c
--- /dev/null
+++ b/faq/ram_limit.mdwn
@@ -0,0 +1,22 @@
+[[!meta copyright="Copyright © 2007, 2008, 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
+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]]."]]"""]]
+
+[[!meta title="830 MiB RAM Limit"]]
+
+Just like any 32bit OS without bad tricks, GNU Mach does not cope well with lots
+of memory.  Latest versions of the Debian `gnumach` package will limit themselves
+to around 1.7 GiB of memory. If you want more, you can twiddle the VM_MAX_ADDRESS
+limit between kernelland and userland in i386/include/mach/i386/vm_param.h.
+
+If you have an older version, or still experience problems with `vmstat` (see
+above) reported much less memory than you have, the best is to limit the memory
+it can see via GRUB's `upppermem` feature.  Add `uppermem 786432` to GRUB's Hurd
+entry in `menu.lst`.
diff --git a/faq/release.mdwn b/faq/release.mdwn
new file mode 100644
index 00000000..d80c6825
--- /dev/null
+++ b/faq/release.mdwn
@@ -0,0 +1,15 @@
+[[!meta copyright="Copyright © 2008 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]]."]]"""]]
+
+[[!meta title="When will the Hurd be released?"]]
+
+Next year.
+
+Save that, read about the Hurd's [[status]].
diff --git a/faq/reporting_bugs.mdwn b/faq/reporting_bugs.mdwn
new file mode 100644
index 00000000..40781ab0
--- /dev/null
+++ b/faq/reporting_bugs.mdwn
@@ -0,0 +1,19 @@
+[[!meta copyright="Copyright © 2007, 2008 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]]."]]"""]]
+
+Please try to reproduce bugs which are not obviously Hurd-specific on Debian
+GNU/Linux and then file them there.
+
+If you find a genuine issue in Debian GNU/Hurd, please file it in our Alioth
+bug tracker at
+<http://alioth.debian.org/tracker/?atid=411594&group_id=30628&func=browse>
+If you find a bug in the Hurd or GNU Mach themselves, either file a bug against
+the respective Debian packages, or directly at
+<http://savannah.gnu.org/bugs/?group=hurd>
diff --git a/faq/sata_disk_drives.mdwn b/faq/sata_disk_drives.mdwn
new file mode 100644
index 00000000..dad10cb9
--- /dev/null
+++ b/faq/sata_disk_drives.mdwn
@@ -0,0 +1,11 @@
+[[!meta copyright="Copyright © 2008 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]]."]]"""]]
+
+GNU Mach does not support SATA disk drives (/dev/sda etc. in GNU/Linux) natively, so using device:sd0s1 will not work, sd* devices are for SCSI drives only.  The only way to get those drives to work is to put them into compatibility mode in the BIOS, if such an option exists.  GNU Mach will then recognize them as hda etc.
diff --git a/faq/slash_usr_symlink.mdwn b/faq/slash_usr_symlink.mdwn
new file mode 100644
index 00000000..5c47f4e1
--- /dev/null
+++ b/faq/slash_usr_symlink.mdwn
@@ -0,0 +1,20 @@
+[[!meta copyright="Copyright © 2001, 2002, 2003, 2004, 2005, 2008 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]]."]]"""]]
+
+[[!meta title="Why is `/usr' a symbolic link to `.'?"]]
+
+The distinction between `/` and `/usr` has historical reasons.  Back when [[Unix]]
+systems were booted from two tapes, a small root tape and a big user tape.
+Today, we like to use different partitions for these two spaces.  The Hurd
+throws this historical garbage away.  We think that we have found a more
+flexible solution called union filesystems, which allow to create virtual
+filesystems which are the union of several other filesystems.  However, support
+for union filesystems is still in early development.
diff --git a/faq/slash_usr_symlink/discussion.mdwn b/faq/slash_usr_symlink/discussion.mdwn
new file mode 100644
index 00000000..219e14e4
--- /dev/null
+++ b/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/faq/still_useful.mdwn b/faq/still_useful.mdwn
new file mode 100644
index 00000000..bffeaebd
--- /dev/null
+++ b/faq/still_useful.mdwn
@@ -0,0 +1,46 @@
+[[!meta copyright="Copyright © 2009 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]]."]]"""]]
+
+what are the advantages with the Hurd over Linux, in general of course, nothing
+in depth
+
+> Flexibility for the user:
+> 
+> transparent ftp
+> 
+>     $ cd /ftp://ftp.debian.org/debian
+>     $ ls
+> 
+> personnal filesystem
+> 
+>     $ dd < /dev/zero > myspace.img bs=1M count=1024
+>     $ mke2fs myspace.img
+>     $ settrans myspace /hurd/ext2fs myspace.img
+>     $ cd myspace
+
+>> Just curious, but I keep seeing these (and other similar) concepts being
+>> brought up as the amazing selling points of the Hurd, but all of this is
+>> entirely doable now in Linux with FUSE or things like it.
+
+>>> Nowadays, at LAST, yes, partly.
+
+>> I'm not sure if an ftp filesystem has been implemented for FUSE yet, but its
+>> definately doable; and loopback filesystems like in your second example have
+>> been supported for years.
+
+>>> As a normal user?  And establish a tap interface connected through ppp over
+>>> ssh or whatever you could want to imagine?
+
+>>  What, then, are the major selling points or benefits?
+
+>>> These were just examples, Linux is trying to catch up in ugly ways indeed
+>>> (yes, have a look at the details of fuse, it's deemed to be inefficient).
+>>> In the Hurd, it's that way from the _ground_ and there is no limitation
+>>> like having to be root or ask for root to add magic lines, etc.
diff --git a/faq/xserver-common.mdwn b/faq/xserver-common.mdwn
new file mode 100644
index 00000000..3420154c
--- /dev/null
+++ b/faq/xserver-common.mdwn
@@ -0,0 +1,15 @@
+[[!meta copyright="Copyright © 2007, 2008, 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
+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]]."]]"""]]
+
+[[!meta title="normal users can't start X"]]
+
+You need to run `dpkg-reconfigure x11-common` and select `Anybody` for
+starting X as there is no way to detect console users currently.