|author||Joshua Branson <email@example.com>||2018-10-27 09:17:53 -0400|
|committer||Samuel Thibault <firstname.lastname@example.org>||2018-10-27 15:57:48 +0200|
* I modified tcp_ip_stack to reflect that lwip should replace pfinet.
* I modified open_issues/device_drivers_and_io_systems to include rump kernel. * I created a rump kernel wiki page, and I linked to it from the project_ideas/tcp_ip_stack webpage. * I added an obsolete logo to the DDE page, to pointe people to the Rump kernel page.
5 files changed, 54 insertions, 2 deletions
diff --git a/community/gsoc/project_ideas/driver_glue_code.mdwn b/community/gsoc/project_ideas/driver_glue_code.mdwn
index 1771756e..db1816c9 100644
@@ -27,7 +27,7 @@ This is [[!GNU_Savannah_task 5488]].
[[open issues/user-space device drivers]].
[[open issues/device drivers and io systems]].
-The most promising approach for getting newer drivers seems to be the [[Rump_Kernel]]:
+The most promising approach for getting newer drivers seems to be the [[Rump_kernel]]:
it already does the hard work of providing an environment
where the foreign drivers can run,
and offers the additional benefit of being externally maintained.
diff --git a/community/gsoc/project_ideas/tcp_ip_stack.mdwn b/community/gsoc/project_ideas/tcp_ip_stack.mdwn
index 40d1ad67..4764a6d7 100644
@@ -20,7 +20,8 @@ drivers for wireless chips, which are old drivers from an old version of linux.
lwip for a wifi connection on more modern hardware, one would also need modern
device drivers to access the internet. The promising approach to this is using
a rump kernel. This is essentially the New Driver Framework google summer of
-code project idea.
+code project idea. Hopefully, one day soon the Hurd project will completely replace pfinit
A true hurdish network stack will use a set of [[hurd/translator]] processes,
each implementing a different protocol layer. This way not only the
@@ -8,6 +8,15 @@ Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license
is included in the section entitled [[GNU Free Documentation
+[[!template id=highlight text="""/!\ Obsolete /!\
+DDE is no longer being updated or maintained. The [[Rump_kernel]] is a better alternative.
* [[community/gsoc/project ideas/driver glue code]]
* [[open issues/user-space device drivers]]
diff --git a/open_issues/device_drivers_and_io_systems.mdwn b/open_issues/device_drivers_and_io_systems.mdwn
index 085a737a..72f60e00 100644
@@ -68,6 +68,8 @@ Also see [[user-space device drivers]].
# External Projects
+ * [[Rump_kernel]]
* [Building Linux Device Drivers on
diff --git a/rump_kernel.mdwn b/rump_kernel.mdwn
new file mode 100644
@@ -0,0 +1,40 @@
+[[!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
+ The rump kernels provide existing real world drivers from netbsd. Since DDE no longer seems like a promising approach to get drivers for the Hurd, it appears that rump kernels are the best alternative. It already does the hard work of providing an environment where the foreign drivers can run, and offers the additional benefit of being externally maintained. Rump also offers the necessary facilities for running all drivers in separate userspace processes, which is more desirable than drivers running in the microkernel.
+ * [[community/gsoc/project ideas/driver glue code]]
+ * [[open issues/user-space device drivers]]
+ * [[open issues/device drivers and io systems]]
+ * <http://rumpkernel.org/>
+ * <http://www.fixup.fi/misc/usenix-login-2015/login_oct15_02_kantee.pdf>
+ This is an an opinion paper that explains why operating systems need compartmentalized kernel drivers.
+ * <https://github.com/rumpkernel/wiki/wiki/Tutorial:-Getting-started>
+ A tutorial introduction for those interested in using and deploying rump kernels.
+# Source Code
+ * <https://github.com/rumpkernel>