summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
-rw-r--r--contributing.mdwn2
-rw-r--r--microkernel/mach/gnumach/ports.mdwn2
-rw-r--r--open_issues/gcc.mdwn2
-rw-r--r--open_issues/open_symlink.mdwn2
-rw-r--r--shortcuts.mdwn2
5 files changed, 5 insertions, 5 deletions
diff --git a/contributing.mdwn b/contributing.mdwn
index 68dcca0c..4e9512e9 100644
--- a/contributing.mdwn
+++ b/contributing.mdwn
@@ -103,7 +103,7 @@ access to it from userland. exec would probably call it from `hurd/exec/exec.c`,
which exposes the partitions of the disk image, using parted, and
the parted-based storeio (`settrans -c foos1 /hurd/storeio -T typed
part:1:file:/home/samy/tmp/foo`). This would be libnetfs-based.
-* Write [[virtio drivers for KVM|virtio#KVM]].
+* Write [[virtio drivers for KVM|open_issues/virtio#KVM]].
* Port valgrind. There is a whole
[[GSoC proposal|community/gsoc/project_ideas/valgrind ]] about this, but the
basic port could be small.
diff --git a/microkernel/mach/gnumach/ports.mdwn b/microkernel/mach/gnumach/ports.mdwn
index 2d9bc311..c81cdd2a 100644
--- a/microkernel/mach/gnumach/ports.mdwn
+++ b/microkernel/mach/gnumach/ports.mdwn
@@ -29,6 +29,6 @@ License|/fdl]]."]]"""]]
* [[open_issues/Mach_on_Top_of_POSIX]]. Status unknown.
When starting a port for a new architecture, it might make sense to first
-target a [[!wikipedie desc=paravirtualized Paravirtualization]] environment,
+target a [[!wikipedia desc=paravirtualized Paravirtualization]] environment,
that already abstracts away some of the different hardware implementations'
quirks.
diff --git a/open_issues/gcc.mdwn b/open_issues/gcc.mdwn
index d8a8cd5f..2b772cfc 100644
--- a/open_issues/gcc.mdwn
+++ b/open_issues/gcc.mdwn
@@ -314,7 +314,7 @@ Last reviewed up to the [[Git mirror's 3a930d3fc68785662f5f3f4af02474cb21a62056
* `gcc/config/gnu-user.h` defines `*SPLIT_STACK*` macros -- which aren't
valid for us (yet), I think.
- * Also see [[sourceware_PR 10686]], glibc commit
+ * Also see [[!sourceware_PR 10686]], glibc commit
ecbf434213c0333d81706074e4d107ac45011635 `Reserve new TLS field for x86
and x86_64` (`__private_ss`).
diff --git a/open_issues/open_symlink.mdwn b/open_issues/open_symlink.mdwn
index f71109a9..663bfcbd 100644
--- a/open_issues/open_symlink.mdwn
+++ b/open_issues/open_symlink.mdwn
@@ -21,7 +21,7 @@ License|/fdl]]."]]"""]]
## IRC, OFTC, #debian-hurd, 2013-05-08
- <pinotree> the hurd issue is that Q_NOFOLLOW seems broken on symlinks, and
+ <pinotree> the hurd issue is that O_NOFOLLOW seems broken on symlinks, and
thus open(symlink, O_NOFOLLOW) doesn't fail with ELOOP
<youpi> I don't really see why it should fail
<youpi> since NOFOLLOW says not to follow the symlink
diff --git a/shortcuts.mdwn b/shortcuts.mdwn
index c59c8895..ded77ca6 100644
--- a/shortcuts.mdwn
+++ b/shortcuts.mdwn
@@ -103,7 +103,7 @@ ikiwiki will include your shortcut in the standard underlay.
* [[!shortcut name=GCC_PR
url="http://gcc.gnu.org/PR%s"
- desc=GCC [BZ #%s]"]]
+ desc="GCC [BZ #%s]"]]
* [[!shortcut name=sourceware_PR
url="http://sourceware.org/PR%s"