Hello Olaf,
I've modified my patch.diff to fix the problems you had with the first
draft. Namely I,
1) Added my .gitignore back to the diff. BUT that means that I've added
some lines to the .gitignore, because I ran texi2pdf inside the hurd/doc
directory. If it is not advisable to add more lines to the .gitignore,
then I can fix that as well.
2) I fixed the section on sharing microkernel devices between two
running hurds. I pretty much copied verbatim what you said in the last
email. I hope you don't mind.
3) I removed the "when you're finished here..." paragraph. That was an
error on my part.
4) And I removed the reboot line from the shutdown section, because the
"running the hurd" in the qemu section on the wiki says to NOT reboot
the hurd to avoid file-system corruption.
On 09/26/2015 09:24 AM, Olaf Buddenhagen wrote:
Hi,
On Fri, Sep 25, 2015 at 01:52:25PM -0400, Joshua Branson wrote:
diff --git a/.gitignore b/.gitignore
deleted file mode 100644
Not sure what happened to your .gitignore -- but you definitely don't
want this in the patch :-)
+Note that it is impossible to share microkernel devices between
+two running Hurds. If you do not know what you are doing, this could
+cause serious harm. For example, two hurds with two filesystems
+writing to the same partition will wreak havoc. In the same way, two
+hurds reading from the same terminal device will not share nicely.
It probably should be mentioned though that sharing *is* possible for
network devices. The different pfinet instances will just pick the
packets applying to them, based on IP.
There is also a "proper" user-space multiplexer for network devices now,
called eth-multiplexer. This is only needed though if you also want to
allow network traffic between the Hurd instances uning the device in
question, rather than just each of them communicating with other
machines.
+When you're finished testing your new Hurd, then you can run the
+@command{halt} or @command{reboot} programs to return control to the
+parent Hurd.
I don't think this really belongs here?...
-antrik-
diff --git a/.gitignore b/.gitignore
index 1719508..12c2bb9 100644
--- a/.gitignore
+++ b/.gitignore
@@ -13,3 +13,17 @@ autom4te.cache/
/config.status
/configure
/version.h
+/doc/hurd.aux
+/doc/hurd.cp
+/doc/hurd.cps
+/doc/hurd.fn
+/doc/hurd.ky
+/doc/hurd.log
+/doc/hurd.pdf
+/doc/hurd.pg
+/doc/hurd.sc
+/doc/hurd.toc
+/doc/hurd.tp
+/doc/hurd.vr
+/patch.diff
+/doc/patch.diff
diff --git a/doc/hurd.texi b/doc/hurd.texi
index f7340a6..8c03be0 100644
--- a/doc/hurd.texi
+++ b/doc/hurd.texi
@@ -670,14 +670,19 @@ $ @kbd{boot -d -D /mnt -I /mnt/boot/servers.boot /dev/hd2s1}
See @pxref{Invoking boot} for help with boot.
@end enumerate
-Note that it is impossible to share microkernel devices between the
-two running Hurds. If you do not know what you are doing, this could
-cause serious harm. For example, two hurds with two filesystems
-writing to the same partition will wreak havoc. In the same way, two
-hurds reading from the same terminal device will not share nicely.
-When you're finished testing your new Hurd, then you can run the
-@command{halt} or @command{reboot} programs to return control to the
-parent Hurd.
+If you do not know what you are doing, sharing microkernel devices
+between two running hurds could cause serious harm. For example, two
+hurds with two filesystems writing to the same partition will wreak
+havoc. In the same way, two hurds reading from the same terminal
+device will not share nicely.
+
+However, sharing is possible for network devices. The different pfinet
+instances will just pick the packets applying to them, based on
+IP. There is also a proper user-space multiplexer for network devices
+now, called eth-multiplexer. This is only needed though if you also
+want to allow network traffic between the Hurd instances uning the
+device in question, rather than just each of them communicating with
+other machines.
If you're satisfied with your new Hurd, you can arrange for your
bootloader to start it, and reboot your machine. Then, you'll be in a
@@ -766,9 +771,9 @@ If neither @option{--interleave} or @option{--layer} is specified, multiple
@scindex halt
@scindex reboot
-You can shut down your GNU/Hurd machine by typing these
-commands:
+You can shutdown your GNU/Hurd machine by typing
+$ @kbd{su}
# @kbd{halt}
@node Foundations
@@ -820,7 +825,6 @@ is declared in @code{<cthreads.h>}.
The Hurd uses POSIX pthreads, which are documented in a lot of places.
@c Thomas, 26-03-1998
-
@c FIXME: it would be nice if we referred specifically to some of
@c the places in which POSIX pthreads are documented.
@c tb: yes, but alas we are only allowed to refer to free
