JehanneOS
/
newlib
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

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

* how-using.texinfo: Add paragraph about find -noleaf.
This commit is contained in:
Joshua Daniel Franklin 2004-07-16 14:17:15 +00:00
parent 75ccca2f65
commit 99d86313f4
4 changed files with 28 additions and 14 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
winsup/doc/ChangeLog
View File

@ -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. * 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. * faq.texinfo: Move outdated calls.texinfo to readme.texinfo.
* how-api.texinfo: Fix typos. * how-api.texinfo: Fix typos.

10
winsup/doc/how-resources.texinfo
View File

@ -3,10 +3,12 @@
@subsection Where's the documentation? @subsection Where's the documentation?
If you have installed Cygwin, you can find lots of documentation in If you have installed Cygwin, you can find lots of documentation in
@samp{/usr/doc/}. Many packages ship with standard documentation, you @samp{/usr/share/doc/}. Many packages ship with standard documentation,
can find this in a directory @samp{/usr/doc/@emph{package_name}}. In you can find this in a directory @samp{/usr/share/doc/@emph{package_name}}.
addition, some packages have Cygwin specific instructions in a file In addition, some packages have Cygwin specific instructions in a file
@samp{/usr/doc/Cygwin/@emph{package_name}.README}. @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 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 page: @file{http://cygwin.com/}. Be sure to at least

21
winsup/doc/how-using.texinfo
View File

@ -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 specify the @samp{-follow} option. This behavior is different than most
other UNIX implementations, but is not likely to change. 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? @subsection Why doesn't @samp{su} work?
The @samp{su} command has been in and out of Cygwin distributions, but 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 Don't invoke as simply ``rxvt'' because that will run /bin/sh (really
ash) which is not a good interactive shell. For details see 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" @subsection info error "dir: No such file or directory"
Cygwin packages install their info documentation in the /usr/info Cygwin packages install their info documentation in the
directory. But you need to create a @code{dir} file there before the @code{/usr/share/info} directory. But you need to create a @code{dir}
standalone info program (probably @code{/usr/bin/info}) can be used to file there before the standalone info program (probably
read those info files. This is how you do it: @code{/usr/bin/info}) can be used to read those info files. This is how
you do it:
@example @example
bash$ cd /usr/info bash$ cd /usr/share/info
bash$ for f in *.info ; do install-info $f dir ; done bash$ for f in *.info ; do install-info $f dir ; done
@end example @end example
This may generate warnings: This may generate warnings:
@ -696,7 +703,7 @@ This may generate warnings:
install-info: warning: no info dir entry in `time.info' install-info: warning: no info dir entry in `time.info'
@end example @end example
The @code{install-info} command cannot parse these files, so you will 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 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 you install new Cygwin packages. Some packages update the dir file

2
winsup/doc/setup-net.sgml
View File

@ -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 will display a box announcing the completion. A few packages, such as
the OpenSSH server, require some manual site-specific configuration. the OpenSSH server, require some manual site-specific configuration.
Relevant documentation can be found in the <literal>/usr/doc/Cygwin/</literal> Relevant documentation can be found in the <literal>/usr/doc/Cygwin/</literal>
directory. or <literal>/usr/share/doc/Cygwin/</literal> directory.
</para> </para>
</sect2> </sect2>