Welcome to mirror list, hosted at ThFree Co, Russian Federation.

cygwin.com/git/newlib-cygwin.git - Unnamed repository; edit this file 'description' to name the repository.
summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJoshua Daniel Franklin <joshuadfranklin@yahoo.com>2004-07-16 18:17:15 +0400
committerJoshua Daniel Franklin <joshuadfranklin@yahoo.com>2004-07-16 18:17:15 +0400
commit99d86313f4b339be9abf747439356d717730ff61 (patch)
tree971e75baaebbbbb1e4995b861249b5805b2dd8ce /winsup/doc/how-using.texinfo
parent75ccca2f65e3e1d5038233abbd36f993f190f785 (diff)
* how-resources.texinfo: Update documentation to /usr/share/doc.
* how-using.texinfo: Add paragraph about find -noleaf.
Diffstat (limited to 'winsup/doc/how-using.texinfo')
-rw-r--r--winsup/doc/how-using.texinfo21
1 files changed, 14 insertions, 7 deletions
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