summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
-rw-r--r--hurd.mdwn2
-rw-r--r--hurd/libports.mdwn4
-rw-r--r--libpthread.mdwn2
-rw-r--r--microkernel/mach/thread.mdwn2
-rw-r--r--open_issues/multithreading.mdwn4
m---------toolchain/logs6
6 files changed, 4 insertions, 16 deletions
diff --git a/hurd.mdwn b/hurd.mdwn
index 625efcec..ff30f48b 100644
--- a/hurd.mdwn
+++ b/hurd.mdwn
@@ -99,8 +99,6 @@ in the *unstable* branch of the Debian archive.
* [[libps]]
* In-development Libraries
* [[libfuse]]
-* Discontinued Libraries
- * [[libthreads]]
* [[IO_Path]]
* [[Porting]]
* [[Debugging]]
diff --git a/hurd/libports.mdwn b/hurd/libports.mdwn
index b0a0f6d5..c2c39226 100644
--- a/hurd/libports.mdwn
+++ b/hurd/libports.mdwn
@@ -16,8 +16,8 @@ ports|microkernel/mach/port]]. It is documented in the [[Reference_Manual]].
Mach ports to the functionality the Hurd needs, that is, it is not meant to
provide an interface independently of the underlying [[microkernel]].
-*libports* does not itself depend on *[[libthreads]]*, but the appropriate
-threading hooks are used if present, that is if *[[libthreads]]* is used by
+*libports* does not itself depend on *[[/libpthread]]*, but the appropriate
+threading hooks are used if present, that is if *[[/libpthread]]* is used by
another component.
diff --git a/libpthread.mdwn b/libpthread.mdwn
index 0f7f28fe..424636be 100644
--- a/libpthread.mdwn
+++ b/libpthread.mdwn
@@ -58,8 +58,6 @@ 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 [[hurd/libthreads]].
-
The current implementation in libpthread is
[[buggy|open_issues/libpthread/t/fix_have_kernel_resources]].
diff --git a/microkernel/mach/thread.mdwn b/microkernel/mach/thread.mdwn
index ccce643e..911b4493 100644
--- a/microkernel/mach/thread.mdwn
+++ b/microkernel/mach/thread.mdwn
@@ -32,6 +32,6 @@ Threads have scheduling parameters and maintain various statistics about
themselves.
On GNU/Hurd, APIs for Mach threads and thereabouts are provided by the
-[[hurd/libthreads]] (cthreads), and [[libpthread]] (POSIX Threads) packages.
+[[/libpthread]] (POSIX Threads) package.
A task backing a thread is the basis for a [[UNIX process|unix/process]].
diff --git a/open_issues/multithreading.mdwn b/open_issues/multithreading.mdwn
index a66202c8..4f2db8fe 100644
--- a/open_issues/multithreading.mdwn
+++ b/open_issues/multithreading.mdwn
@@ -19,9 +19,7 @@ Hurd servers / VFS libraries are multithreaded. They can even be said to be
* well-known threading libraries
- * [[hurd/libthreads]]
-
- * [[hurd/libpthread]]
+ * [[/libpthread]]
## IRC, freenode, #hurd, 2011-04-20
diff --git a/toolchain/logs b/toolchain/logs
deleted file mode 160000
-Subproject b9d5ce62343d50df7800d02ae97790ea9e530bd