Hello,
My name is Joshua Branson, and I've recently made some small
changes to the hurd reference manual in hurd/doc/hurd.texi. My changes
in patch.diff are as follows:
1) I made a tiny grammatical fix.
2) I changed the "don't get any funny ideas" to be more specific to
the reader.
3) I improved the section on shutdown to use the commands reboot or
halt. I found this information in the hurd-users-guide.
4) I removed the line explaining that the hurd uses Cthreads, and
instead said that the hurd uses pthreads.
This might be a significant enough change to require me assigning
copyright to the FSF. I was not paid by my employer to make these
changes, and
I might continue to make some tiny changes to the hurd
documentation in the future, time permitting.
The FSF does not have my signed copyright on file. I found this
link explaining how to assign copyright to the FSF:
https://www.gnu.org/licenses/why-assign.html It says that I
should ask one of the maintainers of the software to assist me in
assigning copyright.
Would someone assist me in assigning copyright to the FSF? Should I
send one of the files found here?
http://git.savannah.gnu.org/cgit/gnulib.git/tree/doc/Copyright
Thanks for the help!
Joshua
diff --git a/.gitignore b/.gitignore
deleted file mode 100644
index 1719508..0000000
--- a/.gitignore
+++ /dev/null
@@ -1,15 +0,0 @@
-*~
-
-*.d
-*.o
-*.a
-*.so
-*.so.*
-TAGS
-
-autom4te.cache/
-/config.log
-/config.make
-/config.status
-/configure
-/version.h
diff --git a/doc/hurd.texi b/doc/hurd.texi
index 2f36bdc..65abf50 100644
--- a/doc/hurd.texi
+++ b/doc/hurd.texi
@@ -386,7 +386,7 @@ libraries they use. At that point, you should be able to study the
source code of existing Hurd servers and understand how they use the
Hurd libraries.
-The final level of mastery is learning the about the RPC interfaces
+The final level of mastery is learning about the RPC interfaces
which the Hurd libraries implement. The last section of each chapter
describes any Hurd interfaces used in that subsystem. Those sections
assume that you are perusing the referenced interface definitions as you
@@ -670,18 +670,14 @@ $ @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, so don't get any funny ideas. 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.
-
-@c FIXME: the `don't get any funny ideas' comment is confusing. Am
-@c I genuinely in some sort of danger if I contemplate sharing
-@c microkernel devices between two running Hurds?
-@c tb: not if you know what you are doing. But there is no clever
-@c device mediation going on. Two hurds, with two filesystems writing
-@c the same partition, will wreak havoc. Two hurds reading from the
-@c same terminal device will not share nicely.
+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.
+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'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
@@ -770,8 +766,14 @@ If neither @option{--interleave} or @option{--layer} is specified, multiple
@scindex halt
@scindex reboot
-FIXME: finish
+You can shut down your GNU/Hurd machine by typing
+
+$ @kbd{reboot}
+If this fails, one can shutdown via
+
+$ @kbd{su}
+# @kbd{halt}
@node Foundations
@chapter Foundations
@@ -820,11 +822,8 @@ the microkernel and the underlying hardware. The Hurd threads library,
@code{libthreads}, contains the default Hurd thread implementation, which
is declared in @code{<cthreads.h>}.
-Currently (April 1998), the Hurd uses cthreads, which have already been
-documented thoroughly by CMU. Eventually, it will be migrated to use
-POSIX pthreads, which are documented in a lot of places.
+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
