* how-resources.texinfo: Update documentation to /usr/share/doc.

* how-using.texinfo: Add paragraph about find -noleaf.

4 files changed, 28 insertions, 14 deletions

diff --git a/winsup/doc/ChangeLog b/winsup/doc/ChangeLog
index 4f2b897fc..7e729d6b2 100644
--- a/winsup/doc/ChangeLog
+++ b/winsup/doc/ChangeLog
@@ -1,8 +1,13 @@
-2003-06-14  Joshua Daniel Franklin  <joshuadfranklin@yahoo.com>
+2004-07-16  Joshua Daniel Franklin  <joshuadfranklin@yahoo.com>
+
+	* how-resources.texinfo: Update documentation to /usr/share/doc.
+	* how-using.texinfo: Add paragraph about find -noleaf. 
+	
+2004-06-14  Joshua Daniel Franklin  <joshuadfranklin@yahoo.com>
 
 	* how-programming.texinfo: Add section about Visual Studio linking.
 	
-2003-06-13  Joshua Daniel Franklin  <joshuadfranklin@yahoo.com>
+2004-06-13  Joshua Daniel Franklin  <joshuadfranklin@yahoo.com>
 
 	* faq.texinfo: Move outdated calls.texinfo to readme.texinfo.
 	* how-api.texinfo: Fix typos.
diff --git a/winsup/doc/how-resources.texinfo b/winsup/doc/how-resources.texinfo
index 392e0d9d3..2c86fdab8 100644
--- a/winsup/doc/how-resources.texinfo
+++ b/winsup/doc/how-resources.texinfo
@@ -3,10 +3,12 @@
 @subsection Where's the documentation?
 
 If you have installed Cygwin, you can find lots of documentation in
-@samp{/usr/doc/}.  Many packages ship with standard documentation, you
-can find this in a directory @samp{/usr/doc/@emph{package_name}}.  In
-addition, some packages have Cygwin specific instructions in a file
-@samp{/usr/doc/Cygwin/@emph{package_name}.README}.
+@samp{/usr/share/doc/}.  Many packages ship with standard documentation,
+you can find this in a directory @samp{/usr/share/doc/@emph{package_name}}.  
+In addition, some packages have Cygwin specific instructions in a file
+@samp{/usr/share/doc/Cygwin/@emph{package_name}.README}.  Some older
+packages still keep their documentation in @samp{/usr/doc/} instead of
+@samp{/usr/share/doc/}.
 
 There are links to quite a lot of it on the main Cygwin project web
 page: @file{http://cygwin.com/}.  Be sure to at least
diff --git a/winsup/doc/how-using.texinfo b/winsup/doc/how-using.texinfo
index aa4325a56..63853fb6b 100644
--- a/winsup/doc/how-using.texinfo
+++ b/winsup/doc/how-using.texinfo
@@ -165,6 +165,12 @@ itself a symbolic link, then find will not traverse it unless you
 specify the @samp{-follow} option.  This behavior is different than most
 other UNIX implementations, but is not likely to change.
 
+If find does not seem to be producing enough results, or seems to be
+missing out some directories, you may be experiencing a problem with one
+of find's optimisations.  The absence of @samp{.} and @samp{..}
+directories on some filesystems, such as DVD-R UDF, can confuse find.
+See the documentation for the option @samp{-noleaf} in the man page.
+
 @subsection Why doesn't @samp{su} work?
 
 The @samp{su} command has been in and out of Cygwin distributions, but
@@ -678,16 +684,17 @@ middle mouse buttons, respectively.  It will honor settings in your
 
 Don't invoke as simply ``rxvt'' because that will run /bin/sh (really
 ash) which is not a good interactive shell.  For details see
-@code{/usr/doc/Cygwin/rxvt-<ver>.README}.
+@code{/usr/share/doc/Cygwin/rxvt-<ver>.README}.
 
 @subsection info error "dir: No such file or directory"
 
-Cygwin packages install their info documentation in the /usr/info
-directory.  But you need to create a @code{dir} file there before the
-standalone info program (probably @code{/usr/bin/info}) can be used to
-read those info files.  This is how you do it:
+Cygwin packages install their info documentation in the
+@code{/usr/share/info} directory.  But you need to create a @code{dir}
+file there before the standalone info program (probably
+@code{/usr/bin/info}) can be used to read those info files.  This is how
+you do it:
 @example
-	bash$ cd /usr/info
+	bash$ cd /usr/share/info
 	bash$ for f in *.info ; do install-info $f dir ; done
 @end example
 This may generate warnings:
@@ -696,7 +703,7 @@ This may generate warnings:
 	install-info: warning: no info dir entry in `time.info'
 @end example
 The @code{install-info} command cannot parse these files, so you will
-have to add their entries to @code{/usr/info/dir} by hand.
+have to add their entries to @code{/usr/share/info/dir} by hand.
 
 Even if the dir file already exists, you may have to update it when
 you install new Cygwin packages.  Some packages update the dir file
diff --git a/winsup/doc/setup-net.sgml b/winsup/doc/setup-net.sgml
index f00756068..2b787b6ef 100644
--- a/winsup/doc/setup-net.sgml
+++ b/winsup/doc/setup-net.sgml
@@ -233,7 +233,7 @@ When the last post-install script is completed, <command>setup.exe</command>
 will display a box announcing the completion. A few packages, such as
 the OpenSSH server, require some manual site-specific configuration. 
 Relevant documentation can be found in the <literal>/usr/doc/Cygwin/</literal> 
-directory.
+or <literal>/usr/share/doc/Cygwin/</literal> directory.
 </para>
 </sect2>