[Hurdextras-hackers] Users guide patch

[James A Morrison]

 Hey,

  I've read through some more of the users guide.  It's looking good.  Anyway,
here is a patch that cleans up the lines lengths and such.  I will also
start a changelog (C-x 4 a, in emacs) if/when this gets commited.

  Something documentors should read while documenting GNU projects is the
GNU Coding Standards[1], they do have a documentation section.

  Please read over the Who should use the Hurd parts that I have changed.

Jim
[1] http://www.gnu.org/prep/standards.html

2002-11-09  James A. Morrison  <address@hidden>

        * using_gnuhurd.texi (An Introduction to Texinfo): Point the reader
        to info info and info texinfo.
        (Basic CVS Usage): Pass the reader to info cvs.
        (Accessing FTP): Align text to 80 characters.
        (Accessing FTP): Leave a space after each prompt.
        (More Basics): Align text to 80 characters.
        (Who Should Use the Hurd?): Reword some paragraphs to be more concise.


Index: using_gnuhurd.texi
===================================================================
RCS file: /cvsroot/hurdextras/documentation/using_gnuhurd.texi,v
retrieving revision 1.3
diff -u -p -r1.3 using_gnuhurd.texi
--- using_gnuhurd.texi  8 Nov 2002 18:40:23 -0000       1.3
+++ using_gnuhurd.texi  9 Nov 2002 22:09:32 -0000
@@ -319,7 +319,8 @@ bugs would prove extremely annoying.
 
 For such people, a more stable system is preferable.  Fortunately, the GNU 
 system currently exists in a very stable state with Linux substituted for 
-the Hurd as the kernel, so it is possible for end-users to use a powerful, 
+the Hurd at the core of the system, so it is possible for end-users to use a 
+powerful, 
 stable, and Free Unix-like operating system. Debian GNU/Linux, a very 
 high-quality GNU/Linux distribution, is available; in addition, many 
 commercial companies sell boxed GNU/Linux distributions with printed 
@@ -334,12 +335,11 @@ Hurd, but do not have experience with Un
 learn the ropes using a more stable GNU/Linux system. Those folks that
 are daring and ambitious might find using the Hurd a good starting 
 point because it can run on old hardware, is not as hyped as others, 
-and isn't quite as complex as GNU/Linux (@emph{ yet }).
+and isn't quite as complex as GNU/Linux.
 
-Unix-like systems are 
-quite different from other systems you may have used, and they take some 
-getting used to.  If you plan to use the GNU/Hurd in the future, we 
-recommend you use Debian GNU/Linux.
+If you are unfamiliar with Unix-like systems, we recommend you use
+GNU/Linux is a nice user-friendly way to start learning about Unix-like
+system.
 
 @c FIXME: the meaning here is unclear, what is the difference between
 @c what is said in the final sentence here, and what is said in the
@@ -347,28 +347,28 @@ recommend you use Debian GNU/Linux.
 
 If you consider yourself computer-literate, but are not a programmer, you can 
 still contribute to the Hurd project.  Tasks for non-programmers include 
-running GNU/Hurd systems and testing them for bugs, writing documentation, and 
+running GNU/Hurd systems, reporting bugs, writing documentation, and 
 translating existing documentation into other languages. At present, most 
 GNU/Hurd documentation is available only in English and/or French.
 
-Anyone who might be interested in the Hurd: a student studying the system, a 
-programmer helping to develop the Hurd servers, or an end-user finding bugs 
-or writing documentation, will be interested in how GNU/Hurd is similar to, 
+Anyone who might be interested in the Hurd, e.g. a student studying operating
+systems, will be interested in how GNU/Hurd is similar to, 
 and different from, Unix-like kernels.
 
-For all intents and purposes, the Hurd is a modern Unix-like kernel, like 
-Linux and the BSDs.  GNU/Hurd uses the GNU C Library, whose development 
+For all intents and purposes, the GNU Hurd is a modern replacement for the 
+Unix-like kernels, e.g. Linux.  GNU/Hurd systems use the GNU C Library, whose 
+development 
 closely tracks standards such as ANSI/ISO, BSD, POSIX, Single Unix, SVID, 
-and X/Open.  Hence, most programs available on GNU/Linux and BSD systems 
-will eventually be ported to run on GNU/Hurd systems.
+and X/Open.  Hence, most programs available on GNU/Linux and/or BSD systems 
+do run on GNU/Hurd systems.
 
 An advantage of all these systems - GNU/Hurd, GNU/Linux, and the BSDs - 
-is that, unlike many popular operating systems, is that they are Free Software.
+is that, unlike many popular operating systems, is that they are made up
+entirely of Free Software.
 Anybody can use, modify, and redistribute these systems under the terms of 
-the GNU General Public License (@pxref{GNU General Public License}) in the 
case of 
-GNU/Hurd and GNU/Linux, and the BSD license in the case of the BSDs.  In fact, 
-the entire GNU System is a complete Unix-like operating system licensed under 
-the GNU GPL.
+the GNU General Public License (@pxref{GNU General Public License}) in the 
+case of 
+GNU/Hurd and GNU/Linux, and the BSD license in the case of the BSDs.
 
 Although it is similar to other Free Unix-like kernel projects, the Hurd has 
 the potential to be much more.  Unlike these other projects, the Hurd has an 
@@ -376,12 +376,12 @@ object-oriented structure that allows it
 design. This structure will help the Hurd undergo major redesign and
 modifications without having to be entirely rewritten.  This 
 extensibility makes the Hurd an attractive platform for learning 
-how to become a kernel hacker or for implementing new ideas in 
-kernel technology, as every part of the system is designed to 
+how to become an operating systems guru or for implementing new ideas in 
+operating system technology, as every part of the system is designed to 
 be modified and extended.  For example, the MS-DOS FAT filesysetem  
 was not supported by GNU/Hurd until a developer wrote a translator that 
 allows us to access this filesystem. In a standard Unix-like enviroment, 
-such a feature would be put into the kernel.  In GNU/Hurd, this is 
+such a feature would be put into the kernel.  With the GNU Hurd, this is 
 done in a different manner and recompiling the kernel is not necessary, 
 since the filesystem is implemented as a user-space program.
 
@@ -668,7 +668,7 @@ disk, and directly start a more advanced
 
 @cindex GRUB
 @cindex GRand Unified Bootloader
-Currently, @address@hidden GRand Unified Bootloader, available
+Currently, @dfn{GRUB} @footnote{The GRand Unified Bootloader, available
 from @uref{http://www.gnu.org/software/grub/}.} is the GNU bootloader.
 GNU GRUB provides advanced functionality, and is capable of loading several
 different kernels (such as Linux, the *BSD family, and DOS).
@@ -703,7 +703,7 @@ First you will need to make a directory 
 be logged in as root).
 
 @example
-bash-2.05#mkdir /boot/grub
+bash-2.05# mkdir /boot/grub
 @end example
 
 Now you must copy the contents of the GRUB installed loader files.  These 
@@ -711,7 +711,7 @@ are usually located in /lib/grub/i386-un
 directory need to be copied to the boot directory.
 
 @example
-bash-2.05#cp /lib/grub/i386-unknown-pc/* /boot/grub/
+bash-2.05# cp /lib/grub/i386-unknown-pc/* /boot/grub/
 @end example
 
 Now, you have two more things to do.  You must construct a @file{menu.lst} 
@@ -753,7 +753,7 @@ This will put you at the GRUB command pr
 start with the @command{root} command.
 
 @example 
-:grub>root (hd0,0)
+grub> root (hd0,0)
 @end example
 
 The @command{root} command in the above example tells GRUB that my GNU/Hurd 
system 
@@ -1113,7 +1113,8 @@ for a brief introduction.
 @comment node, next, prev, up
 @section The Basics
 
address@hidden:} @emph{When showing command prompts, I use # to indicate root 
user, and $ to indicate normal user.}  
address@hidden:} @emph{When showing command prompts, I use # to indicate root 
user, 
+and $ to indicate normal user.}  
       
 If you successfully installed GNU/Hurd and you are in multi-user mode,
 you should have a login shell ready for you, which should look like this:
@@ -1130,11 +1131,11 @@ Debian GNU/Hurd comes with ABSOLUTELY NO
 permitted by applicable law.
 login>
 
-Type Login:USER or type HELP 
+Type login USER or type help 
 
 @end display
 
-You can go ahead and type @code{login address@hidden<ENTER>} to get started.  
+You can go ahead and type @code{login root} @key{<ENTER>} to get started.  
 
 What you need to know for using GNU/Hurd is your basic Unix-like commands.
 The GNU Project has written a replacement for almost every Unix command.
@@ -1150,7 +1151,7 @@ default editor first, then come back to 
 GNU/Hurd shell commands.
 
 The shell is the the program that interacts with the filesystem and the data
-on the filesystem.  This is called bash (Bourne again shell)@footnote{This is 
+on the filesystem.  This is called bash (Bourne again shell) @footnote{This is 
 a pun on the name of the original Unix shell, the Bourne shell, and the 
 Christian idea of being ``born again''.}.  Once you get 
 comfortable with the shell, you can happily sit at any Unix-like workstation 
@@ -1167,7 +1168,8 @@ your current working directory.  Your pr
 bash-2.05$
 @end example
 
-To make a directory for yourself, you would use the @command{mkdir} (make 
directory)
+To make a directory for yourself, you would use the @command{mkdir} (make 
+directory)
 command.  You can make as many as you want as long as they are in your home 
 directory.
 
@@ -1181,8 +1183,10 @@ is many command names that are confusing
 bash-2.05$ mkdir docs tmp sources <ENTER>
 @end example
 
-To change directories you would use the @command{cd} (change directory) 
command.  
-One thing to remember is that wherever you are in the filesytem, typing 
@command{cd} 
+To change directories you would use the @command{cd} (change directory) 
+command.  
+One thing to remember is that wherever you are in the filesytem, typing 
address@hidden 
 alone will put you back in your home directory.  (Note:@emph{The bash shell 
 features command line completion, by pressing the first letter of the file 
 or directory plus @key{<TAB>} will do this.})
@@ -1192,8 +1196,8 @@ bash-2.05$ cd /usr/local <ENTER> #this p
 bash-2.05$ cd <ENTER>            #this puts you back in the home directory. 
 @end example
 
-There is another short cut, @code{ cd ../} This puts you in the directory 
above the one
-you're currently in.
+There is another short cut, @code{ cd ../} This puts you in the directory above
+the one you're currently in.
  
 There are many ways to view a file, but we'll use the most common command 
 called @command{cat} @footnote{An abbreviation for @emph{concatenate}, since 
@@ -1205,12 +1209,11 @@ bash-2.05$ cat README | less <ENTER>
 
 You may wonder what @code{ | less} mean. We use the | (pipe symbol) to take 
 the output of @file{README} and feed it to the @command{less} command.  
address@hidden allows you to view 
address@hidden allows you to view
 the documents one screen at a time and it allows you to go back to the 
-beginning of the document.  You have to type @key{q} to quit @command{less}. 
-
+beginning of the document.  You have to type @key{q} to quit @command{less}.
 To copy a file from one place to another you use the @command{cp} (copy) 
-command.  The @command{cp} command has many options such as @code{cp -f -v 
-r}.  
+command.  The @command{cp} command has many options such as @code{cp -f -v -r}.
 Luckily for us, the @command{info }
 command will clarify many of the confusing commands and all three options. 
 
@@ -1228,22 +1231,27 @@ bash-2.05$ cp -rfv foo1/ file2.txt tmp/ 
 bash-2.05$ cp -rf /cdrom/* ~/ <ENTER>
 @end example
 
-The @code{-r} means ``recursive'', so @file{file2.txt}, the @file{foo1} 
directory,
+The @code{-r} means ``recursive'', so @file{file2.txt}, the @file{foo1} 
+directory,
 and all the contents of @file{foo1} are copied to the @file{tmp} directory.  
 The @code{-f} means ``force'', I have a habit of forcing things.  
-The @code{-v} means ``verbose'', It will show you on the screen what files are 
being 
-copied.  In the second example, we have this @code{~/}, which is a short cut 
representing  
-your home directory.  So that command would copy the contents of @file{/cdrom} 
to 
-your home directory.(Note:@emph{The asterik symbol '*' is called a wildcard
+The @code{-v} means ``verbose'', It will show you on the screen what files are
+being 
+copied.  In the second example, we have this @code{~/}, which is a short cut 
+representing  
+your home directory.  So that command would copy the contents of @file{/cdrom}
+to 
+your home directory.(Note: @emph{The asterik symbol '*' is called a wildcard
 character which means "anything"}.)
 
 @c FIXME: I'm for taking the -f out of the example. Passing -f to cp
 @c is a little esoteric for beginners, IMHO, and the explanation 
 @c doesn't add a lot of information.
 
-To rename or move a file or directory you would use the @command{mv} (move) 
command. 
-Be careful, because @command{mv} is a very powerful command.  You can lose 
data if 
-you're not careful about what you do.  To rename a file or directory you 
+To rename or move a file or directory you would use the @command{mv} (move) 
+command. 
+Be careful, because @command{mv} is a very powerful command.  You can lose data
+if you're not careful about what you do.  To rename a file or directory you 
 would type, for example:
 
 @example 
@@ -1253,26 +1261,30 @@ bash-2.05$ mv foo1/ foo2 <ENTER>
 Now you no longer have a @file{foo1} directory, it's called @file{foo2} now.  
 The same thing can be done with plain files, too.
 
-I'll bet you're saying, "I'm doing all this work, but how do I view my 
directories?"
-You answer would be the @command{ls} (list)command.  The @command{ls} command 
also 
+I'll bet you're saying, "I'm doing all this work, but how do I view my 
+directories?"
+You answer would be the @command{ls} (list)command.  The @command{ls} command 
+also 
 has many options.
 
 @example 
 bash-2.05$ ls -al <ENTER>
 @end example
 
-The two options I have here are used more often than any others.  The 
@code{-a} 
-will show us all hidden files in the current address@hidden files are 
+The two options I have here are used more often than any others.  The @code{-a}
+will show us all hidden files in the current directory.
address@hidden files are 
 often hidden, to prevent the user from accidentally deleting them.}  The 
 @code{-l} option tells us to display the directory in long format.  
-This means it shows us the date modified, file size, file attributes, etc. of 
all 
-files.  As I was saying in the beginning, 
+This means it shows us the date modified, file size, file attributes, etc. of 
+all files.  As I was saying in the beginning, 
 a grasp of these basics will help you on any Unix-like operating system. 
 
 Now that you have made all this mess in your home directory, I'll bet you're 
 wondering how you can get rid of things.  There are two important deleting 
 commands.  The @command{rm} (remove) command is convienent for removing files. 
address@hidden command can also remove directorys that the @command{rmdir} 
command 
address@hidden command can also remove directorys that the @command{rmdir} 
+command 
 can't. I'll show the you a basic @command{rm} example, then my favorite with 
 the extra options.  The @command{rmdir} command will only delete directories 
 that are empty.
@@ -1287,11 +1299,12 @@ Now, @command{rm} with some options:
 bash-2.05$ rm -rf foo2/ <ENTER>
 @end example
 
-The second example is very powerful.  The @code{-r} means ``recursive'' and 
the 
+The second example is very powerful.  The @code{-r} means ``recursive'' and the
 -f means ``force.''  This removes all the contents of @file{foo2}, without 
 prompting the user for confirmation.
 
-These are only the basic commands to get you address@hidden there are many, 
many
+These are only the basic commands to get you address@hidden there are many, 
+many
 two- and three-letter commands.  The more you use GNU/Hurd, the more options
 and commands you'll learn.  The more you learn, the more freedom you'll 
 have.
@@ -1308,8 +1321,8 @@ Filesystem           1k-blocks      Used
 /dev/hd0s1            1920748   1203996    619180  67% /
 @end example
 
-If you don't put a directory after the command such as @file{/} or 
@file{/home}, 
-the @command{df} (diskfree) command will spit out some errors. 
+If you don't put a directory after the command such as @file{/} or
address@hidden/home}, the @command{df} (diskfree) command will spit out some 
errors. 
 
 If your prompt is not telling you what directory you are in, you can use the 
 @command{pwd} (present working directory) command:
@@ -1318,7 +1331,8 @@ bash-2.05$ pwd <ENTER>
 /usr/src 
 @end example 
 
-As a final note, always remember: @address@hidden is your friend on GNU/Hurd.}
+As a final note, always remember: @address@hidden is your friend on 
+GNU/Hurd.}
 
 @node More Basics, , , 
 @comment node, next, prev, up
@@ -1332,18 +1346,26 @@ extensions tell us what type of archive 
 in forms of .tgz, .tar.gz, .tar.bz2, .gz, etc.
 
 @dfn{Archiving} is a method of packaging files.  It has been around 
-since the early days of computing.  The @command{tar} command that we use when 
working 
-with archives stands for ``tape archiver''. It was originally used to create 
archived 
+since the early days of computing.  The @command{tar} command that we use when
+working
+with archives stands for ``tape archiver''. It was originally used to create 
+archived 
 files for backup on large tape drives.
 
-Closely associated with archiving is the concept of @dfn{compressing}. Various 
algorithms 
-dan be used to pack data into a smaller format. Archives are often compressed 
before being 
-distributed; for example, a tarball may have the extension @file{.tar.gz}, 
which means that 
-the tarball is a @code{tar} archive that has been compressed using 
@command{gzip}. Most software 
-that you try and install from source-code will be packaged this way.  I will 
try to give you 
+Closely associated with archiving is the concept of @dfn{compressing}. Various
+algorithms 
+dan be used to pack data into a smaller format. Archives are often compressed 
+before being
+distributed; for example, a tarball may have the extension @file{.tar.gz}, 
+which means that 
+the tarball is a @code{tar} archive that has been compressed using 
address@hidden Most software
+that you try and install from source-code will be packaged this way.  I will 
+try to give you 
 some examples; if you're confused, always consult the info pages.
 
-Let's say we get a @code{tar} file that has some documents you want to read.  
Make 
+Let's say we get a @code{tar} file that has some documents you want to read.  
+Make 
 sure that you are in your home directory, then type:
 
 @example
@@ -1353,18 +1375,22 @@ bash-2.05$ tar xv docs.tar <ENTER>
 After running this command, you would see the contents of the tar file 
extracted
 to your home directory.  The @code{x} stands for ``extract'' and the @code{v} 
 means ``verbose'', which shows us the contents of the archive as it's being 
-decompressed.  Compressing a file or directory is very simliar.  You would use 
type:
+decompressed.  Compressing a file or directory is very simliar.  You would use
+type:
 
 @example
 bash-2.05$ tar -cv new.tar foo1/ foo2/ <ENTER>
 @end example
 
-The @code{-c} is to create the tar file.  We add the name of the tar file, 
then the 
-contents that we want.  In the above example, we created a file called 
@file{new.tar}
-and we added the directories @file{foo1/} and @file{foo2/} to the tar file.  
With 
-the @code{-v} option we see what is being added.  
+The @code{-c} is to create the tar file.  We add the name of the tar file, 
+then the 
+contents that we want.  In the above example, we created a file called 
address@hidden
+and we added the directories @file{foo1/} and @file{foo2/} to the tar file.  
+With the @code{-v} option we see what is being added.  
 
-The @command{gzip} compression format is commonly used in the GNU system.  
Files with 
+The @command{gzip} compression format is commonly used in the GNU system.  
+Files with 
 the extionsion @file{.gz} are associated with @command{gzip}.  The utilities 
 @command{tar} and @command{gzip} work so well together that people 
 have patched the tar command so that it can compress and decompress 
@command{gzip}ed 
@@ -1372,13 +1398,14 @@ files.  Note, however, that @command{tar
 @command{gzip}ed files that are not @command{tar} archives. 
 
 @example 
-bash-2.05$ tar -zxv file.tar.gz <ENTER> #This file was compressed once with 
tar 
-                                         then with gzip
-bash-2.05$ gzip -d file.gz <ENTER>     #notice no tar in filename means you 
use 
-                                         gzip
+bash-2.05$ tar -zxv file.tar.gz <ENTER># This file was archived with tar
+                                       # then compressed with gzip.
+bash-2.05$ gzip -d file.gz <ENTER>    # notice no tar in filename means you use
+                                      # gzip.
 @end example
 
-In the first example, the @code{z} after the @command{tar} command is the 
option 
+In the first example, the @code{z} after the @command{tar} command is the 
+option 
 that tells @command{tar} that the file has been @command{gzip}ed.  The second 
 example is the @command{gzip} command, using the @code{d} option to decompress 
 @file{file.gz}.  @command{gunzip} is a command that is equivalent to 
@@ -1418,18 +1445,21 @@ bash-2.05$ bzcat file.tar.bz2 |tar -xv <
 @end example
 
 The @command{bzcat} command is a combination of @command{bunzip2} and 
@command{cat}.  
-We @command{bzcat} the file, then pipe(|) the file to the @command{tar} 
command.  
-Once again, I use @code{-x} to extract the file, and @code{-v} to see its 
contents.  
+We @command{bzcat} the file, then pipe(|) the file to the @command{tar} 
+command.  
+Once again, I use @code{-x} to extract the file, and @code{-v} to see its 
+contents.  
 To compress a file using @command{bzip2} you would type:
 
 @example
 bash-2.05$ bzip2 -z file1.txt <ENTER>
 @end example
 
-This command compresses @file{file1.txt} to @file{file1.txt.bz2}.  You can 
also use 
-the @code{'-9'} option for best compression.
+This command compresses @file{file1.txt} to @file{file1.txt.bz2}.  You can 
+also use the @code{'-9'} option for best compression.
 
-Hopefully, this little chapter has gotten you more interested in using 
GNU/Hurd.
+Hopefully, this little chapter has gotten you more interested in using 
+GNU/Hurd.
 If you are still confused, please read the info pages for the command that's 
 giving you trouble.  The command @code{info} will give you a list of all the 
 programs on your Hurd machine that have documentation with them.  
@@ -1441,22 +1471,24 @@ This chapter is meant to give you a step
 @comment node, next, prev, up
 @section Administration
 
-After the last chapter, you're probably wondering about this ``root user'' 
that 
+After the last chapter, you're probably wondering about this ``root user'' that
 everyone is so fond of.  The Hurd is trying to get all things root out 
 of the picture and allow you the freedom of doing things only root can do
 on legacy Unix systems.  The designers and developers want you, the user, 
-to be able to do things that you cannot do on a traditional Unix-like 
operating 
+to be able to do things that you cannot do on a traditional Unix-like operating
 system.
 
 For the time being, though, you will have to deal with the root user.  
 
-One reasonable request of the Unix-type gurus is making a normal user account. 
A 
-normal user can only write to his or her home directory, and has limited 
access 
-to system configuration.  The reasoning behind this is that a normal user can 
not mess
+One reasonable request of the Unix-type gurus is making a normal user account.
+A 
+normal user can only write to his or her home directory, and has limited access
+to system configuration.  The reasoning behind this is that a normal user can 
+not mess
 up the computer.  This is a decent compromise because the more we explore and
-play, the more likely we'll lose a important file or make some other fatal 
mistake.  
-So what we'll do is set up a user account for you.  You must be root to 
-do this.
+play, the more likely we'll lose a important file or make some other fatal
+mistake.  So what we'll do is set up a user account for you.  You must be root
+to do this.
 
 @example  
 bash-2.05# adduser <ENTER>
@@ -1501,12 +1533,12 @@ file system. On GNU/Hurd, we don't @comm
 a similar mechanism for accessing devices called "setting a translator".  
 
 We use the @command{settrans} command to do this.  @command{settrans} is a 
-program that aligns a type of Hurd server called a @dfn{translator} to a 
device 
+program that aligns a type of Hurd server called a @dfn{translator} to a device
 supported by the kernel.  For instance, 
 on my GNU/Hurd system my cdrom device was detected as hd2.  To get to my data 
 on a iso9660 CD, I first had to make the device.  Then I had to run the 
address@hidden command.  This had to be done as the root user (root is the only 
-user that has these privileges).
address@hidden command.  This had to be done as the root user (root is the
+only user that has these privileges).
 
 @c FIXME: We should add more detail. If I were coming fresh from a diet of 
 @c Windows beer, this would confuse the heck out of me.
@@ -1517,7 +1549,8 @@ bash-2.05# ./MAKEDEV hd2
 bash-2.05# settrans -ac /cdrom /hurd/isofs /dev/hd2
 @end example
 
-This isn't too hard, is it?  Those options after @command{settrans} are very 
important.
+This isn't too hard, is it?  Those options after @command{settrans} are very 
+important.
 The @code{-a} makes the @command{/hurd/isofs} translator active. The @code{-c} 
 creates the translator, and is only needed the first time.
 
@@ -1529,7 +1562,8 @@ Now you can type @command{cd /cdrom} and
 
 This section will help you get some data off of your floppy disk. I note that
 the @code{vfat (fat32)} and @code{msdos (fat16)} filesystems are currently 
-not supported. The support will come eventually, but for now you can only 
access 
+not supported. The support will come eventually, but for now you can only 
+access 
 GNU/Linux floppies. You must be root to get to your floppy.
 
 @example
@@ -1543,10 +1577,10 @@ Now you can head to the @code{/floppy} d
 @comment node, next, prev, up
 @chapter Networking
 
-In this chapter, you'll learn about the Hurd's networking features.  The 
Hurd's 
-networking is a work in progress.  The services that the Hurd now has should 
be 
-sufficient for the average user.  Available now are @command{ftp}, 
@command{nfs}, 
address@hidden, and, of course, web-surfing and e-mail.
+In this chapter, you'll learn about the Hurd's networking features.  The Hurd's
+networking is a work in progress.  The services that the Hurd now has should be
+sufficient for the average user.  Available now are @command{ftp}, 
address@hidden, @command{telnet}, and, of course, web-surfing and e-mail.
 
 @menu
 Networking
@@ -1574,8 +1608,10 @@ bash-2.05# settrans -fgcap /servers/sock
 
 In this example, the @command{settrans} command uses the following options:
 @code{'f', 'g', 'c', 'a'}, and @code{'p'}.  The @code{-fg} forces anything 
-that is attached to @file{/servers/socket/2} and @file{/hurd/pfinet} to go 
away.  
-Next, the @code{-c} tells @command{settrans} to create a translator.  The 
@code{-ap} 
+that is attached to @file{/servers/socket/2} and @file{/hurd/pfinet} to go 
+away.  
+Next, the @code{-c} tells @command{settrans} to create a translator.  The 
address@hidden 
 tells the @file{/server/socket/2} and @file{/hurd/pfinet} 
 to be both active and passive. The passive option will make the
 configuration remain valid even after the reboots and shutdowns.  Here are the 
@@ -1588,10 +1624,12 @@ rest of the options:
 -g 192.168.1.5 = This is the gateway machine on the network.
 @end example
 
-Unfortunately, GNU/Hurd currently has no @dfn{DHCP} client (DHCP stands for 
Dynamic 
+Unfortunately, GNU/Hurd currently has no @dfn{DHCP} client (DHCP stands for 
+Dynamic 
 Host Configuration Protocol, its used by many computers to attach themselves 
 to a network). There is, however, a workaround if you have another operating 
-system, such as Debian GNU/Linux, installed on your GNU/Hurd machine. In 
describing 
+system, such as Debian GNU/Linux, installed on your GNU/Hurd machine. In 
+describing 
 this workaround, I'll assume that you are using a GNU/Linux system.
 
 Boot GNU/Linux and log in as root. Type the following two commands, and 
@@ -1630,28 +1668,35 @@ are 154.17.21.134, 255.255.240.0, and 
 machine addresses. Reboot into GNU/Hurd, and use these values to set your 
 network translator as described above.
 
-The next items to configure are our @file{resolv.conf} file and our 
@file{hosts} file.  
-These are located in the @file{/etc} directory.  In fact, all GNU/Hurd's 
configuration 
-files are located in the @file{/etc} directory.  The @file{resolv.conf} file 
is the first 
+The next items to configure are our @file{resolv.conf} file and our 
address@hidden file.  
+These are located in the @file{/etc} directory.  In fact, all GNU/Hurd's 
+configuration 
+files are located in the @file{/etc} directory.  The @file{resolv.conf} file 
+is the first 
 file to edit.  It only consists of 2 to 3 lines but it is one of the most 
 important networking files.  Here is an example:
 
 @example
-search mydomain            #This should be your networks domain name
-nameserver xxx.xxx.xxx.xxx #These should be the primary and secondary 
-nameserver xxx.xxx.xxx.xxx #ip addresses of your isp's nameservers(aka DNS 
servers)
+search mydomain            # This should be your networks domain name
+nameserver xxx.xxx.xxx.xxx # These should be the primary and secondary 
+nameserver xxx.xxx.xxx.xxx # ip addresses of your isp's nameservers
+                           # (aka DNS servers)
 @end example
 
 If you used the DHCP workaround described above, just copy your 
address@hidden/etc/resolv.conf} (in GNU/Linux) to @file{/etc/resolv.conf} (in 
GNU/Hurd).
address@hidden/etc/resolv.conf} (in GNU/Linux) to @file{/etc/resolv.conf} 
+(in GNU/Hurd).
 
-After this is all set up, you should be able to use the 
@address@hidden@command{ping} 
-is a small program that we use to test whether or not we can talk to another 
machine.} program
-on any host on the Internet and recieve a response. The next file to setup is 
the 
address@hidden/etc/hosts} file.  This 
+After this is all set up, you should be able to use the @command{ping}
address@hidden@command{ping} 
+is a small program that we use to test whether or not we can talk to another 
+machine.} program
+on any host on the Internet and recieve a response. The next file to setup is 
+the @file{/etc/hosts} file.  This 
 file is used for machines you access frequently.  Instead if typing ip 
-addresses for computers on your network, you edit @file{/etc/hosts} to allow 
you to 
-just type the name of the computer you want to access.
+addresses for computers on your network, you edit @file{/etc/hosts} to allow 
+you to just type the name of the computer you want to access.
 
 @c FIXME: I think this could be a little clearer, but I don't know enough about
 @c Unix networking to suggest a good solution at the moment.
@@ -1663,9 +1708,12 @@ just type the name of the computer you w
 192.168.1.6    mojo.mydomain.org mojo 
 @end example
 
-Now I can access 192.168.1.5 by simply using its name, @emph{jojo}.  The same 
is true 
-with @emph{mojo} also. For instance if I wanted to @command{telnet} into 
@emph{jojo}, 
-I would type @command{telnet address@hidden the proliferation of mischief on 
the Internet 
+Now I can access 192.168.1.5 by simply using its name, @emph{jojo}.  The same 
+is true 
+with @emph{mojo} also. For instance if I wanted to @command{telnet} into 
address@hidden, 
+I would type @command{telnet jojo}.
address@hidden the proliferation of mischief on the Internet 
 it is recommended you use the OpenSSH suite to access remote computers.} 
 
 @node Accessing FTP, , , 
@@ -1675,26 +1723,28 @@ it is recommended you use the OpenSSH su
 FTP stands for File Transfer Protocol.  This protocol has been around since 
 the beginnings of GNU and Unix.  It is a easy and fast way of sending files 
 to friends, family, and colleagues.  The Hurd has two methods of using ftp.
-One is setting a translator with the Hurds @code{ftpfs} server.  The other way 
is 
+One is setting a translator with the Hurds @code{ftpfs} server.  The other way
+is 
 the traditional client-server method in which you login and use @command{get} 
 and @command{put} commands.
 
-The @command{ftpfs} translator is quite unique.  It allows you to have a 
remote 
+The @command{ftpfs} translator is quite unique.  It allows you to have a remote
 FTP server accessible on a local directory.  You would then begin 
 copying files to and from it as if it were a directory on your machine.
 
 @example 
-$bash-2.05#settrans -ac /mnt /hurd/ftpfs / alpha.gnu.org
+bash-2.05# settrans -ac /mnt /hurd/ftpfs / alpha.gnu.org
 @end example
 
 This command will set a translator for @command{ftpfs}.  The @command{ftpfs} 
 translator places the root directory of alpha.gnu.org's anonymous ftp server 
-on the @file{/mnt} directory. Now one can access the data as if it were a 
local 
+on the @file{/mnt} directory. Now one can access the data as if it were a local
 filesystem.
 
 The FTP protocol is traditionally accessed using a client.
-Typical console-based clients are the ones that come with the 
@code{inet-utils} package
-(The Hurd's native ftp client,ncftp, and many others).  The traditional method 
+Typical console-based clients are the ones that come with the @code{inet-utils}
+package
+(The Hurd's native ftp client, ncftp, and many others).  The traditional method
 of ftp is pretty much a standard for Unix-like operating systems. If you learn 
 this method you should be able to comfortably sit at any Unix-like workstation 
 and send and retrieve files. I will give you a start but, there are many more 
@@ -1703,8 +1753,8 @@ options, so read the info pages for some
 @c FIXME: I don't understand (The Hurds... and many others).
 
 @example
-bash-2.05:$ftp <ENTER>
-ftp>open ftp.gnu.org
+bash-2.05$ ftp <ENTER>
+ftp> open ftp.gnu.org
 @end example
 
 You should then be prompted for a username and password.  You can log into
@@ -1715,19 +1765,21 @@ the password.
 
 The standard commands that are used are @code{get}, @code{put}, @code{mget},
  @code{mput}, @code{ls}, @code{pwd}, and @code{cd}.  These will work with any
-standard ftp client.  The commands themselves are fairly self-explanatory.  
The 
address@hidden and @code{mput} are for multiple files.  An example would be:
+standard ftp client.  The commands themselves are fairly self-explanatory.  
+The @code{mget} and @code{mput} are for multiple files.  An example would be:
 
 @example
 ftp> mget *.tar.gz
 @end example
 
-This would try to download any files in the current directory with a 
@file{.tar.gz}
-extension.  Don't worry if you say @code{mget} instead of @code{get} by 
accident, 
+This would try to download any files in the current directory with a 
address@hidden
+extension.  Don't worry if you say @code{mget} instead of @code{get} by 
+accident, 
 because it will prompt you at every file.  It will allow you to say 
 @code{yes, no, all, abort} and @code{quit}.  The ftp protocol and applications 
-are fairly simple to learn, you just have to practice.  Trying it a handful of 
times 
-will get you very familiar with it, very quickly.
+are fairly simple to learn, you just have to practice.  Trying it a handful of
+times will get you very familiar with it, very quickly.
 
 @node Accessing NFS, , , 
 @comment node, next, prev, up
@@ -2124,7 +2176,7 @@ Most importantly you need to make sure t
 module lines; Brackets, Spaces, Etc.  have thier meannings and cannot 
 be interchanged. If your editor is a pain you can put a forward slash
 to seperate the commands on seperate lines. This will still be seen
-as one module line to Grub.For instance:
+as one module line to Grub.  For instance:
 @display
 module /hurd/ext2fs.static @\
 address@hidden@} @\
@@ -2226,8 +2278,9 @@ testing, and may contain serious bugs.}
 @comment node, next, prev, up
 @section Basic CVS Usage
 
-basics of CVS so the user isn't confused by all the references to CVS on 
-Free Software web pages
+ Using CVS is beyond the scope of this document.  However, the CVS manual
+is quite good and can be accessed locally by typing @code{info cvs} in your
+shell.
 
 @node Using gcc
 @comment node, next, prev, up
@@ -2245,7 +2298,13 @@ make makes things easy for the user
 @comment node, next, prev, up
 @section An Introduction to Texinfo
 
-structure of Info documents, why TeX/Texinfo is good, etc.
+ Using @info{info} is beyond the scope of this document.  However, the info 
+manual is quite good and can be accessed locally by typing @code{info info} 
+in your shell.
+
+ Writing TeXinfo is also beyond the scope of this document but see 
address@hidden texinfo} for information on how to write TeXinfo documents.
+
 
 @node Reporting Bugs, , , 
 @comment node, next, prev, up