From: Earnie B. <ea...@us...> - 2001-10-15 22:22:38
|
Update of /cvsroot/mingw/msys/rt/src/winsup/doc In directory usw-pr-cvs1:/tmp/cvs-serv30329/winsup/doc Modified Files: ChangeLog Makefile.in how-programming.texinfo how-resources.texinfo how-using.texinfo install.texinfo relnotes.texinfo who.texinfo Log Message: Merge in cygwin-1.3.3 Index: ChangeLog =================================================================== RCS file: /cvsroot/mingw/msys/rt/src/winsup/doc/ChangeLog,v retrieving revision 1.3 retrieving revision 1.4 diff -C2 -d -r1.3 -r1.4 *** ChangeLog 2001/10/14 14:57:52 1.3 --- ChangeLog 2001/10/15 22:22:33 1.4 *************** *** 1,2 **** --- 1,15 ---- + Fri Sep 7 12:47:47 2001 Michael Schaap <cy...@ms...> + + * how-resources.texinfo: Add some additional words about where to find + documentation. + + Wed Jun 13 13:54:35 2001 Christopher Faylor <cg...@cy...> + + * who.texinfo: Oops. Add a couple of important folk. + + Wed Jun 13 13:45:44 2001 Christopher Faylor <cg...@cy...> + + * who.texinfo: Remove email addresses. Modernize. + Tue May 29 21:30:07 2001 Christopher Faylor <cg...@cy...> Index: Makefile.in =================================================================== RCS file: /cvsroot/mingw/msys/rt/src/winsup/doc/Makefile.in,v retrieving revision 1.2 retrieving revision 1.3 diff -C2 -d -r1.2 -r1.3 *** Makefile.in 2001/09/04 22:06:25 1.2 --- Makefile.in 2001/10/15 22:22:33 1.3 *************** *** 40,43 **** --- 40,44 ---- cygwin-ug-net/cygwin-ug-net.html \ cygwin-api-int/cygwin-api-int.html \ + cygwin-api/cygwin-api.html \ $(DOC) \ $(HTMLDOC) Index: how-programming.texinfo =================================================================== RCS file: /cvsroot/mingw/msys/rt/src/winsup/doc/how-programming.texinfo,v retrieving revision 1.1.1.1 retrieving revision 1.2 diff -C2 -d -r1.1.1.1 -r1.2 *** how-programming.texinfo 2001/08/07 17:51:18 1.1.1.1 --- how-programming.texinfo 2001/10/15 22:22:33 1.2 *************** *** 236,249 **** Normally, this will also attempt to build the documentation, which ! additionally requires db2html, texi2html and possibly others. ! These tools are not included in the Cygwin distribution, but are readily ! obtainable: ! ! @table @samp ! @item db2html ! Part of docbook, from @file{http://sources.redhat.com/docbook-tools/}. ! @item texi2html ! From @file{http://www.mathematik.uni-kl.de/~obachman/Texi2html/}. ! @end table To check a cygwin1.dll, run "make check" in the winsup/cygwin directory. --- 236,242 ---- Normally, this will also attempt to build the documentation, which ! additionally requires db2html, and possibly other tools, which are not ! included in the Cygwin distribution. You can get db2html as part of ! docbook, from @file{http://sources.redhat.com/docbook-tools/}. To check a cygwin1.dll, run "make check" in the winsup/cygwin directory. Index: how-resources.texinfo =================================================================== RCS file: /cvsroot/mingw/msys/rt/src/winsup/doc/how-resources.texinfo,v retrieving revision 1.1.1.1 retrieving revision 1.2 diff -C2 -d -r1.1.1.1 -r1.2 *** how-resources.texinfo 2001/08/07 17:51:18 1.1.1.1 --- how-resources.texinfo 2001/10/15 22:22:33 1.2 *************** *** 3,6 **** --- 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}. + 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 Index: how-using.texinfo =================================================================== RCS file: /cvsroot/mingw/msys/rt/src/winsup/doc/how-using.texinfo,v retrieving revision 1.1.1.1 retrieving revision 1.2 diff -C2 -d -r1.1.1.1 -r1.2 *** how-using.texinfo 2001/08/07 17:51:18 1.1.1.1 --- how-using.texinfo 2001/10/15 22:22:33 1.2 *************** *** 111,120 **** other UNIX implementations, but is not likely to change. ! @subsection Why doesn't man work? Even after installing the @samp{man} package, you get an error like this: @example ! bash-2.03$ man man Error executing formatting or display command. System command (cd /usr/man ; (echo -e ".pl 1100i"; cat /usr/man/man1/man.1; echo ".pl \n(nlu+10") | /usr/bin/tbl | /usr/bin/groff -Tascii -mandoc | less -is) exited with status 32512. --- 111,130 ---- other UNIX implementations, but is not likely to change. ! @subsection Where is the @samp{su} command? ! ! The @samp{su} command is not ported to Cygwin, so it is no longer ! provided in the distribution. You may be able to use @samp{login} ! instead, but you should read ! @file{http://www.cygwin.com/ml/cygwin/2001-03/msg00337.html} first. ! ! If you have a copy of su, then it's from an old Cygwin distribution, and ! it probably doesn't work properly anyway. ! ! @subsection Why doesn't man (or apropos) work? Even after installing the @samp{man} package, you get an error like this: @example ! bash-2.04$ man man Error executing formatting or display command. System command (cd /usr/man ; (echo -e ".pl 1100i"; cat /usr/man/man1/man.1; echo ".pl \n(nlu+10") | /usr/bin/tbl | /usr/bin/groff -Tascii -mandoc | less -is) exited with status 32512. *************** *** 123,128 **** You also need /bin/sh, which is found in the @samp{ash} package. ! Install this too. @subsection Why doesn't chmod work? --- 133,147 ---- You also need /bin/sh, which is found in the @samp{ash} package. ! You must install this too. ! ! In addition, before you can use @samp{man -k} or @samp{apropos}, you ! must create the whatis database. Just run the command ! ! @example ! /usr/sbin/makewhatis ! @end example + (it may take a minute to complete). + @subsection Why doesn't chmod work? *************** *** 206,213 **** @subsection How do I print under Cygwin? ! In lieu of a comprehensive FAQ entry (which will come soon), there are a ! couple of messages from the mailing list archives that may be helpful. ! Start at @file{http://cygwin.com/ml/cygwin/2001-04/msg00657.html}. @subsection Why don't cursor keys work under Win95/Win98? --- 225,269 ---- @subsection How do I print under Cygwin? ! There is no working lp or lpr system as you would find on UNIX. ! ! Jason Tishler has written a couple of messages that explain how to use ! a2ps (for nicely formatted text in PostScript) and ghostscript (to print ! PostScript files on non-PostScript Windows printers). Start at ! @file{http://cygwin.com/ml/cygwin/2001-04/msg00657.html}. Note that the ! @samp{file} command is now available as part of Cygwin setup. ! ! Alternatively, on NT, you can use the Windows @samp{print} command. (It ! does not seem to be available on Win9x.) Type ! ! @example ! bash$ print /\? ! @end example ! ! for usage instructions (note the @samp{?} must be escaped from the ! shell). + Finally, you can simply @samp{cat} the file to the printer's share name: + + @example + bash$ cat myfile > //host/printer + @end example + + You may need to press the formfeed button on your printer or append the + formfeed character to your file. + + @subsection Why don't international (8-bit) characters work? + + Before you can type international characters (£åäö) in bash, you must + add the following lines to your @code{~/.inputrc} file: + + @example + set meta-flag on + set convert-meta off + set output-meta on + @end example + + These are options to the @code{readline} library, which you can read + about in the @code{bash(1)} man page. + @subsection Why don't cursor keys work under Win95/Win98? *************** *** 426,435 **** @example ! Device Directory Type Flags ! C:\cygwin\bin /usr/bin user binmode ! C:\cygwin\lib /usr/lib user binmode ! C:\cygwin / user binmode @end example Note that /bin and /usr/bin point to the same location, as do /lib and /usr/lib. This is intentional, and you should not undo these mounts --- 482,493 ---- @example ! bash$ mount ! C:\cygwin\bin on /usr/bin type system (binmode) ! C:\cygwin\lib on /usr/lib type system (binmode) ! C:\cygwin on / type system (binmode) @end example + (Exactly what you see depends on what options you gave to @code{setup.exe}.) + Note that /bin and /usr/bin point to the same location, as do /lib and /usr/lib. This is intentional, and you should not undo these mounts *************** *** 481,485 **** exploited by a hostile non-Cygwin program, so do this at your own risk. ! @subsection Why can't I run bash as a shell under NT Emacs? The Windows port of GNU Emacs (aka "NT emacs") uses the Windows command --- 539,543 ---- exploited by a hostile non-Cygwin program, so do this at your own risk. ! @subsection How do I run bash as a shell under NT Emacs? The Windows port of GNU Emacs (aka "NT emacs") uses the Windows command *************** *** 572,573 **** --- 630,640 ---- Perhaps that may be your problem? + @subsection Why doesn't Cygwin tcl/tk understand Cygwin paths? + + The versions of Tcl/Tk distributed with Cygwin (e.g. cygtclsh80.exe) are + not actually "Cygwin versions" of those tools. They are built with the + @samp{-mno-cygwin} option to @code{gcc}, which means they do not + understand Cygwin mounts or symbolic links. + + See the entry "How do I convert between Windows and UNIX paths?" + elsewhere in this FAQ. Index: install.texinfo =================================================================== RCS file: /cvsroot/mingw/msys/rt/src/winsup/doc/install.texinfo,v retrieving revision 1.1.1.1 retrieving revision 1.2 diff -C2 -d -r1.1.1.1 -r1.2 *** install.texinfo 2001/08/07 17:51:19 1.1.1.1 --- install.texinfo 2001/10/15 22:22:33 1.2 *************** *** 21,24 **** --- 21,26 ---- @end example + (This list is almost certainly out of date as new packages are added.) + Full source code is available for all packages and tools. *************** *** 174,207 **** README file for that package.) - @subsection Setup screwed up my mounts! - - Setup will remove the following mounts, should you have them: - - @example - / - /usr - /usr/bin - /usr/lib - /var - /lib - /bin - /etc - @end example - - It will then restore (or create new) mounts for /, /usr/bin and /usr/lib - as follows (assuming the default install root C:\cygwin): - - @example - Device Directory - C:\cygwin\bin /usr/bin - C:\cygwin\lib /usr/lib - C:\cygwin / - @end example - - Since setup is not a Cygwin program, it cannot know about your mounts - (or symlinks, for that matter), and so must impose and enforce this - structure. You should not try to defeat it, unless you know what you - are doing and can deal with the consequences. - @subsection How do I uninstall Cygwin? --- 176,179 ---- *************** *** 228,243 **** @subsection Can I use setup to install snapshots? ! Yes. If experimenting with developer snapshots from @file{http://cygwin.com/snapshots/}, you should generally install the full @code{cygwin-inst-YYYYMMDD.tar.bz2} update, rather than just the ! DLL, otherwise some components may be out of sync. However, Cygwin tar ! won't work because it will load the DLL that you're trying to update, ! and a non-Cygwin program like WinZip will put everything in the wrong ! place. The solution is to use @code{setup.exe}. ! Just bunzip2 the cygwin-inst tarball, rename it to cygwin-YYYYMMDD.tar, ! gzip it, put it in an empty directory, and run @code{setup.exe} there. ! You should be given the option to install it. The obvious warnings about updating the cygwin package and using developer snapshots apply: --- 200,228 ---- @subsection Can I use setup to install snapshots? ! No. It used to be possible, but not any more. ! ! If experimenting with developer snapshots from @file{http://cygwin.com/snapshots/}, you should generally install the full @code{cygwin-inst-YYYYMMDD.tar.bz2} update, rather than just the ! DLL, otherwise some components may be out of sync. Cygwin tar won't be ! able to update @code{/usr/bin/cygwin1.dll}, but it should succeed with ! everything else. The following steps should work: ! @enumerate + @item Download the snapshot, and run: + @example + cd / + tar jxvf /posix/path/to/cygwin-inst-YYYYMMDD.tar.bz2 --exclude=usr/bin/cygwin1.dll + cd /tmp + tar jxvf /posix/path/to/cygwin-inst-YYYYMMDD.tar.bz2 usr/bin/cygwin1.dll + @end example + + @item After closing all Cygwin apps (see below), use Explorer or the + Windows command shell to move @code{C:\cygwin\tmp\usr\bin\cygwin1.dll} + to @code{C:\cygwin\bin\cygwin1.dll}. + + @end enumerate + The obvious warnings about updating the cygwin package and using developer snapshots apply: *************** *** 245,257 **** @enumerate - @item Always download the latest version of setup from - @file{http://cygwin.com/setup.exe}. - @item Close all Cygwin apps, including shells and services ! (e.g. inetd), before running setup. You may have to restart Windows to ! clear the DLL from memory. @item Snapshots are risky. They have not been tested. Use them @strong{only} if ! there is a feature or bugfix that you need to try. @item If you cannot download a snapshot from the main ftp distribution --- 230,240 ---- @enumerate @item Close all Cygwin apps, including shells and services ! (e.g. inetd), before updating @code{cygwin1.dll}. You may have to ! restart Windows to clear the DLL from memory. @item Snapshots are risky. They have not been tested. Use them @strong{only} if ! there is a feature or bugfix that you need to try, and you are willing ! to deal with any problems. @item If you cannot download a snapshot from the main ftp distribution Index: relnotes.texinfo =================================================================== RCS file: /cvsroot/mingw/msys/rt/src/winsup/doc/relnotes.texinfo,v retrieving revision 1.1.1.1 retrieving revision 1.2 diff -C2 -d -r1.1.1.1 -r1.2 *** relnotes.texinfo 2001/08/07 17:51:19 1.1.1.1 --- relnotes.texinfo 2001/10/15 22:22:33 1.2 *************** *** 1,6 **** ! @chapter Known/potential Problems in the Latest Net Release @section Aware of the problem, no solution known. @subsection On Win9x, scp and cvs/ssh leave ssh processes running --- 1,13 ---- ! @chapter Known Problems in the Latest Net Release @section Aware of the problem, no solution known. + @subsection Pipe key (@samp{|}) doesn't work on non-US keyboards in Win9x/ME + + This might get fixed someday, but meanwhile, just use rxvt, which does + not have this problem. This is no real loss, because rxvt has many + other advantages. (Do not attempt to use the "broken" pipe key + (@samp{¦}) as a substitute, it is a different character.) + @subsection On Win9x, scp and cvs/ssh leave ssh processes running *************** *** 21,23 **** @section Fixed in the Next Release ! Nothing currently. --- 28,30 ---- @section Fixed in the Next Release ! (section empty) Index: who.texinfo =================================================================== RCS file: /cvsroot/mingw/msys/rt/src/winsup/doc/who.texinfo,v retrieving revision 1.1.1.1 retrieving revision 1.2 diff -C2 -d -r1.1.1.1 -r1.2 *** who.texinfo 2001/08/07 17:51:19 1.1.1.1 --- who.texinfo 2001/10/15 22:22:33 1.2 *************** *** 1,68 **** @chapter Who's behind the project? ! @strong{(Please note: This section has not yet been updated for the latest ! net release.)} ! Chris Faylor (cgf@@cygnus.com) is behind many of the recent ! changes in Cygwin. Prior to joining Cygnus, he contributed significant ! fixes to the process control and environ code, reworked the strace ! mechanism, and rewrote the signal-related code from scratch as a Net ! contributor. In addition to continuing to make technical contributions, ! Chris is also currently the group's manager. ! Geoffrey Noer (noer@@cygnus.com) took over the Cygwin project from its' ! initial author Steve Chamberlain in mid-1996. As maintainer, he ! produced Net releases beta 16 through 20; made the development ! snapshots; worked with Net contributors to fix bugs; made many various ! code improvements himself; wrote a paper on Cygwin for the ! 1998 Usenix NT Symposium; authored the project WWW pages, FAQ, README; ! etc. ! DJ Delorie (dj@@cygnus.com) has done important work in profiling Cygwin, worked on the Dejagnu automated testing framework, merged the dlltool functionality into ld, wrote a good deal of the Cygwin Users' Guide, authored the cygcheck utility, and made automated snapshots available ! from our project WWW page. ! Steve Chamberlain (sac@@transmeta.com) designed and implemented Cygwin in 1995-1996 while working for Cygnus. He worked with the Net to improve the technology, ported/integrated many of the user tools for the first time to Cygwin, and produced all of the releases up to ! beta 14. ! ! Marco Fuykschot (marco@@ddi.nl) and Peter Boncz (boncz@@ddi.nl) of ! Data Distilleries contributed nearly all of the changes required to ! make Cygwin thread-safe. They also provided the pthreads interface. ! Sergey Okhapkin (sos@@prospect.com.ru) has been an invaluable Net ! contributor. He implemented the tty/pty support, has played a ! significant role in revamping signal and exception handling, and has ! made countless contributions throughout the library. He also provided ! binaries of the development snapshots to the Net after the beta 19 ! release. ! Mumit Khan (khan@@xraylith.wisc.edu) has been most helpful on the EGCS ! end of things, providing quite a large number of stabilizing patches to ! the compiler tools for the B20 release. ! Corinna Vinschen <corinna@@vinschen.de> has contributed several ! useful fixes to the path handling code, console support, improved security ! handling, and raw device support. ! Philippe Giacinti (giac@@dalim.de) contributed the implementation of ! dlopen, dlclose, dlsym, dlfork, and dlerror in Cygwin. ! Many other people at Cygnus have made important contributions to Cygwin. ! Tobin Brockett wrote the InstallShield-based installer for the beta 19 ! and 20 releases. Ian Lance Taylor did a much-needed rework of the path ! handling code for beta 18, and has made many assorted fixes throughout ! the code. Jeremy Allison made significant contributions in the area of ! file handling and process control, and rewrote select from scratch. ! Doug Evans rewrote the path-handling code in beta 16, among other ! things. Kim Knuttila and Michael Meissner put in many long hours ! working on the now-defunct PowerPC port. Jason Molenda and Mark Eichin ! have also made important contributions. ! Please note that those of us here at Cygnus that work on Cygwin try to be as responsive as possible and deal with patches and questions as we get them, but realistically we don't have time to answer all of the --- 1,82 ---- @chapter Who's behind the project? ! @strong{(Please note that if you have cygwin-specific questions, all of these ! people will appreciate it if you use the cygwin mailing lists rather than ! sending personal email.)} ! Chris Faylor is behind many of the recent changes in Cygwin. Prior to ! joining Cygnus, he contributed significant fixes to the process control ! and environ code, reworked the strace mechanism, and rewrote the ! signal-related code from scratch as a Net contributor. In addition to ! continuing to make technical contributions, Chris is also currently the ! group's manager. ! Corinna Vinschen has contributed several useful fixes to the path ! handling code, console support, improved security handling, and raw ! device support. Corinna is currently employed by Red Hat as a ! GDB/Cygwin engineer. ! DJ Delorie has done important work in profiling Cygwin, worked on the Dejagnu automated testing framework, merged the dlltool functionality into ld, wrote a good deal of the Cygwin Users' Guide, authored the cygcheck utility, and made automated snapshots available ! from our project WWW page. DJ is currently employed by Red Hat as ! a GCC engineer. ! Egor Duda has contributed many useful fixes. He is responsible for ! Cygwin's ability to start a debugger on detection of a fatal error ! as well as produce core dumps. ! ! Robert Collins has contributed many improvements to thread handling ! as well as generic fixes to cygwin itself. ! ! Kazuhiro Fujieda has contributed many bug fixes and bug reports. ! ! Earnie Boyd has contributed many bug fixes and is the mingw and w32api ! maintainer. ! ! David Starks-Browning is our dedicated FAQ maintainer. ! ! Geoffrey Noer took over the Cygwin project from its initial author Steve ! Chamberlain in mid-1996. As maintainer, he produced Net releases beta ! 16 through 20; made the development snapshots; worked with Net ! contributors to fix bugs; made many various code improvements himself; ! wrote a paper on Cygwin for the 1998 Usenix NT Symposium; authored the ! project WWW pages, FAQ, README; etc. Geoffrey is not currently employed ! by Red Hat. ! ! Steve Chamberlain designed and implemented Cygwin in 1995-1996 while working for Cygnus. He worked with the Net to improve the technology, ported/integrated many of the user tools for the first time to Cygwin, and produced all of the releases up to ! beta 14. Steve is not currently employed by Red Hat. ! Marco Fuykschot and Peter Boncz of Data Distilleries contributed nearly ! all of the changes required to make Cygwin thread-safe. They also ! provided the pthreads interface. ! Sergey Okhapkin has been an invaluable Net contributor. He implemented ! the tty/pty support, has played a significant role in revamping signal ! and exception handling, and has made countless contributions throughout ! the library. He also provided binaries of the development snapshots to ! the Net after the beta 19 release. ! Mumit Khan has been most helpful on the EGCS end of things, providing ! quite a large number of stabilizing patches to the compiler tools for ! the B20 release. ! Philippe Giacinti contributed the implementation of dlopen, dlclose, ! dlsym, dlfork, and dlerror in Cygwin. ! Ian Lance Taylor did a much-needed rework of the path handling code for ! beta 18, and has made many assorted fixes throughout the code. Jeremy ! Allison made significant contributions in the area of file handling and ! process control, and rewrote select from scratch. Doug Evans rewrote ! the path-handling code in beta 16, among other things. Kim Knuttila and ! Michael Meissner put in many long hours working on the now-defunct ! PowerPC port. Jason Molenda and Mark Eichin have also made important ! contributions. ! Please note that all of us working on Cygwin try to be as responsive as possible and deal with patches and questions as we get them, but realistically we don't have time to answer all of the |