This commit was manufactured by cvs2svn to create tag 'cygwin-pre-user-db'.cygwin-pre-user-db

Sprout from cygwin-1_7_29-release-branchpoint 2014-02-18 19:58:40 UTC cvs2svn 'This commit was manufactured by cvs2svn to create branch 'cygwin-1_7_29'
Cherrypick from master 2014-02-08 22:25:11 UTC Corinna Vinschen <corinna@vinschen.de> 'Fix ChangeLog':
    winsup/cygwin/ChangeLog
    winsup/cygwin/miscfuncs.cc
    winsup/cygwin/miscfuncs.h
    winsup/cygwin/mount.cc
Delete:
    winsup/COPYING
    winsup/CYGWIN_LICENSE
    winsup/ChangeLog
    winsup/Makefile.common
    winsup/Makefile.in
    winsup/README
    winsup/acinclude.m4
    winsup/aclocal.m4
    winsup/autogen.sh
    winsup/c++wrap
    winsup/ccwrap
    winsup/config.guess
    winsup/config.sub
    winsup/configure
    winsup/configure.ac
    winsup/configure.cygwin
    winsup/cygserver/ChangeLog
    winsup/cygserver/ChangeLog.64bit
    winsup/cygserver/Makefile.in
    winsup/cygserver/README
    winsup/cygserver/aclocal.m4
    winsup/cygserver/autogen.sh
    winsup/cygserver/bsd_helper.cc
    winsup/cygserver/bsd_helper.h
    winsup/cygserver/bsd_log.cc
    winsup/cygserver/bsd_log.h
    winsup/cygserver/bsd_mutex.cc
    winsup/cygserver/bsd_mutex.h
    winsup/cygserver/client.cc
    winsup/cygserver/configure
    winsup/cygserver/configure.ac
    winsup/cygserver/cygserver-config
    winsup/cygserver/cygserver.cc
    winsup/cygserver/cygserver.conf
    winsup/cygserver/msg.cc
    winsup/cygserver/process.cc
    winsup/cygserver/process.h
    winsup/cygserver/sem.cc
    winsup/cygserver/setpwd.cc
    winsup/cygserver/shm.cc
    winsup/cygserver/sysv_msg.cc
    winsup/cygserver/sysv_sem.cc
    winsup/cygserver/sysv_shm.cc
    winsup/cygserver/threaded_queue.cc
    winsup/cygserver/threaded_queue.h
    winsup/cygserver/transport.cc
    winsup/cygserver/transport.h
    winsup/cygserver/transport_pipes.cc
    winsup/cygserver/transport_pipes.h
    winsup/cygserver/woutsup.h
    winsup/cygwin/release/1.7.29
    winsup/doc/.cvsignore
    winsup/doc/ChangeLog
    winsup/doc/Makefile.in
    winsup/doc/README
    winsup/doc/Wishlist
    winsup/doc/aclocal.m4
    winsup/doc/bodysnatcher.pl
    winsup/doc/configure
    winsup/doc/configure.ac
    winsup/doc/cygserver.xml
    winsup/doc/cygwin-api.in.xml
    winsup/doc/cygwin-ug-net.xml
    winsup/doc/cygwin.xsl
    winsup/doc/cygwinenv.xml
    winsup/doc/dll.xml
    winsup/doc/doctool.c
    winsup/doc/doctool.txt
    winsup/doc/effectively.xml
    winsup/doc/faq-api.xml
    winsup/doc/faq-copyright.xml
    winsup/doc/faq-programming.xml
    winsup/doc/faq-resources.xml
    winsup/doc/faq-setup.xml
    winsup/doc/faq-using.xml
    winsup/doc/faq-what.xml
    winsup/doc/faq.xml
    winsup/doc/fhandler-tut.txt
    winsup/doc/filemodes.xml
    winsup/doc/fo.xsl
    winsup/doc/gcc.xml
    winsup/doc/gdb.xml
    winsup/doc/highlights.xml
    winsup/doc/legal.xml
    winsup/doc/new-features.xml
    winsup/doc/ntsec.xml
    winsup/doc/ov-ex-unix.xml
    winsup/doc/ov-ex-win.xml
    winsup/doc/overview.xml
    winsup/doc/pathnames.xml
    winsup/doc/programming.xml
    winsup/doc/setup-env.xml
    winsup/doc/setup-files.xml
    winsup/doc/setup-locale.xml
    winsup/doc/setup-maxmem.xml
    winsup/doc/setup-net.xml
    winsup/doc/specialnames.xml
    winsup/doc/textbinary.xml
    winsup/doc/ug-info.xml
    winsup/doc/using.xml
    winsup/doc/windres.xml
    winsup/doc/xidepend
    winsup/install-sh
    winsup/lsaauth/ChangeLog
    winsup/lsaauth/ChangeLog.64bit
    winsup/lsaauth/Makefile.in
    winsup/lsaauth/aclocal.m4
    winsup/lsaauth/configure
    winsup/lsaauth/configure.ac
    winsup/lsaauth/cyglsa-config
    winsup/lsaauth/cyglsa.c
    winsup/lsaauth/cyglsa.din
    winsup/lsaauth/cyglsa64.def
    winsup/testsuite/ChangeLog
    winsup/testsuite/Makefile.in
    winsup/testsuite/README
    winsup/testsuite/aclocal.m4
    winsup/testsuite/config/default.exp
    winsup/testsuite/configure
    winsup/testsuite/configure.ac
    winsup/testsuite/cygrun.c
    winsup/testsuite/libltp/include/dataascii.h
    winsup/testsuite/libltp/include/databin.h
    winsup/testsuite/libltp/include/file_lock.h
    winsup/testsuite/libltp/include/forker.h
    winsup/testsuite/libltp/include/open_flags.h
    winsup/testsuite/libltp/include/pattern.h
    winsup/testsuite/libltp/include/random_range.h
    winsup/testsuite/libltp/include/rmobj.h
    winsup/testsuite/libltp/include/search_path.h
    winsup/testsuite/libltp/include/str_to_bytes.h
    winsup/testsuite/libltp/include/string_to_tokens.h
    winsup/testsuite/libltp/include/test.h
    winsup/testsuite/libltp/include/tlibio.h
    winsup/testsuite/libltp/include/usctest.h
    winsup/testsuite/libltp/include/write_log.h
    winsup/testsuite/libltp/lib/dataascii.c
    winsup/testsuite/libltp/lib/databin.c
    winsup/testsuite/libltp/lib/datapid.c
    winsup/testsuite/libltp/lib/forker.c
    winsup/testsuite/libltp/lib/get_high_address.c
    winsup/testsuite/libltp/lib/libtestsuite.c
    winsup/testsuite/libltp/lib/open_flags.c
    winsup/testsuite/libltp/lib/parse_opts.c
    winsup/testsuite/libltp/lib/pattern.c
    winsup/testsuite/libltp/lib/rmobj.c
    winsup/testsuite/libltp/lib/search_path.c
    winsup/testsuite/libltp/lib/str_to_bytes.c
    winsup/testsuite/libltp/lib/string_to_tokens.c
    winsup/testsuite/libltp/lib/tst_res.c
    winsup/testsuite/libltp/lib/tst_sig.c
    winsup/testsuite/libltp/lib/tst_tmpdir.c
    winsup/testsuite/libltp/lib/write_log.c
    winsup/testsuite/winsup.api/checksignal.c
    winsup/testsuite/winsup.api/crlf.c
    winsup/testsuite/winsup.api/cygload.cc
    winsup/testsuite/winsup.api/cygload.exp
    winsup/testsuite/winsup.api/cygload.h
    winsup/testsuite/winsup.api/devdsp.c
    winsup/testsuite/winsup.api/devdsp_okay.h
    winsup/testsuite/winsup.api/devzero.c
    winsup/testsuite/winsup.api/iospeed.c
    winsup/testsuite/winsup.api/known_bugs.tcl
    winsup/testsuite/winsup.api/ltp/access01.c
    winsup/testsuite/winsup.api/ltp/access03.c
    winsup/testsuite/winsup.api/ltp/access04.c
    winsup/testsuite/winsup.api/ltp/access05.c
    winsup/testsuite/winsup.api/ltp/alarm01.c
    winsup/testsuite/winsup.api/ltp/alarm02.c
    winsup/testsuite/winsup.api/ltp/alarm03.c
    winsup/testsuite/winsup.api/ltp/alarm07.c
    winsup/testsuite/winsup.api/ltp/asyncio02.c
    winsup/testsuite/winsup.api/ltp/chdir02.c
    winsup/testsuite/winsup.api/ltp/chdir04.c
    winsup/testsuite/winsup.api/ltp/chmod01.c
    winsup/testsuite/winsup.api/ltp/chmod02.c
    winsup/testsuite/winsup.api/ltp/chown01.c
    winsup/testsuite/winsup.api/ltp/close01.c
    winsup/testsuite/winsup.api/ltp/close02.c
    winsup/testsuite/winsup.api/ltp/close08.c
    winsup/testsuite/winsup.api/ltp/creat01.c
    winsup/testsuite/winsup.api/ltp/creat03.c
    winsup/testsuite/winsup.api/ltp/creat09.c
    winsup/testsuite/winsup.api/ltp/dup01.c
    winsup/testsuite/winsup.api/ltp/dup02.c
    winsup/testsuite/winsup.api/ltp/dup03.c
    winsup/testsuite/winsup.api/ltp/dup04.c
    winsup/testsuite/winsup.api/ltp/dup05.c
    winsup/testsuite/winsup.api/ltp/execl01.c
    winsup/testsuite/winsup.api/ltp/execle01.c
    winsup/testsuite/winsup.api/ltp/execlp01.c
    winsup/testsuite/winsup.api/ltp/execv01.c
    winsup/testsuite/winsup.api/ltp/execve01.c
    winsup/testsuite/winsup.api/ltp/execvp01.c
    winsup/testsuite/winsup.api/ltp/exit01.c
    winsup/testsuite/winsup.api/ltp/exit02.c
    winsup/testsuite/winsup.api/ltp/fchdir01.c
    winsup/testsuite/winsup.api/ltp/fchdir02.c
    winsup/testsuite/winsup.api/ltp/fchmod01.c
    winsup/testsuite/winsup.api/ltp/fchown01.c
    winsup/testsuite/winsup.api/ltp/fcntl02.c
    winsup/testsuite/winsup.api/ltp/fcntl03.c
    winsup/testsuite/winsup.api/ltp/fcntl04.c
    winsup/testsuite/winsup.api/ltp/fcntl05.c
    winsup/testsuite/winsup.api/ltp/fcntl07.c
    winsup/testsuite/winsup.api/ltp/fcntl07B.c
    winsup/testsuite/winsup.api/ltp/fcntl08.c
    winsup/testsuite/winsup.api/ltp/fcntl09.c
    winsup/testsuite/winsup.api/ltp/fcntl10.c
    winsup/testsuite/winsup.api/ltp/fork01.c
    winsup/testsuite/winsup.api/ltp/fork02.c
    winsup/testsuite/winsup.api/ltp/fork03.c
    winsup/testsuite/winsup.api/ltp/fork04.c
    winsup/testsuite/winsup.api/ltp/fork06.c
    winsup/testsuite/winsup.api/ltp/fork07.c
    winsup/testsuite/winsup.api/ltp/fork09.c
    winsup/testsuite/winsup.api/ltp/fork10.c
    winsup/testsuite/winsup.api/ltp/fork11.c
    winsup/testsuite/winsup.api/ltp/fpathconf01.c
    winsup/testsuite/winsup.api/ltp/fstat01.c
    winsup/testsuite/winsup.api/ltp/fstat02.c
    winsup/testsuite/winsup.api/ltp/fstat03.c
    winsup/testsuite/winsup.api/ltp/fstat04.c
    winsup/testsuite/winsup.api/ltp/fsync01.c
    winsup/testsuite/winsup.api/ltp/ftruncate01.c
    winsup/testsuite/winsup.api/ltp/ftruncate02.c
    winsup/testsuite/winsup.api/ltp/ftruncate03.c
    winsup/testsuite/winsup.api/ltp/getegid01.c
    winsup/testsuite/winsup.api/ltp/geteuid01.c
    winsup/testsuite/winsup.api/ltp/getgid01.c
    winsup/testsuite/winsup.api/ltp/getgid02.c
    winsup/testsuite/winsup.api/ltp/getgid03.c
    winsup/testsuite/winsup.api/ltp/getgroups01.c
    winsup/testsuite/winsup.api/ltp/getgroups02.c
    winsup/testsuite/winsup.api/ltp/gethostid01.c
    winsup/testsuite/winsup.api/ltp/gethostname01.c
    winsup/testsuite/winsup.api/ltp/getpgid01.c
    winsup/testsuite/winsup.api/ltp/getpgid02.c
    winsup/testsuite/winsup.api/ltp/getpgrp01.c
    winsup/testsuite/winsup.api/ltp/getpid01.c
    winsup/testsuite/winsup.api/ltp/getpid02.c
    winsup/testsuite/winsup.api/ltp/getppid01.c
    winsup/testsuite/winsup.api/ltp/getppid02.c
    winsup/testsuite/winsup.api/ltp/getuid01.c
    winsup/testsuite/winsup.api/ltp/getuid02.c
    winsup/testsuite/winsup.api/ltp/getuid03.c
    winsup/testsuite/winsup.api/ltp/kill01.c
    winsup/testsuite/winsup.api/ltp/kill02.c
    winsup/testsuite/winsup.api/ltp/kill03.c
    winsup/testsuite/winsup.api/ltp/kill04.c
    winsup/testsuite/winsup.api/ltp/kill09.c
    winsup/testsuite/winsup.api/ltp/link02.c
    winsup/testsuite/winsup.api/ltp/link03.c
    winsup/testsuite/winsup.api/ltp/link04.c
    winsup/testsuite/winsup.api/ltp/link05.c
    winsup/testsuite/winsup.api/ltp/lseek01.c
    winsup/testsuite/winsup.api/ltp/lseek02.c
    winsup/testsuite/winsup.api/ltp/lseek03.c
    winsup/testsuite/winsup.api/ltp/lseek04.c
    winsup/testsuite/winsup.api/ltp/lseek05.c
    winsup/testsuite/winsup.api/ltp/lseek06.c
    winsup/testsuite/winsup.api/ltp/lseek07.c
    winsup/testsuite/winsup.api/ltp/lseek08.c
    winsup/testsuite/winsup.api/ltp/lseek09.c
    winsup/testsuite/winsup.api/ltp/lseek10.c
    winsup/testsuite/winsup.api/ltp/lstat02.c
    winsup/testsuite/winsup.api/ltp/mkdir01.c
    winsup/testsuite/winsup.api/ltp/mkdir08.c
    winsup/testsuite/winsup.api/ltp/mknod01.c
    winsup/testsuite/winsup.api/ltp/mmap001.c
    winsup/testsuite/winsup.api/ltp/mmap02.c
    winsup/testsuite/winsup.api/ltp/mmap03.c
    winsup/testsuite/winsup.api/ltp/mmap04.c
    winsup/testsuite/winsup.api/ltp/mmap05.c
    winsup/testsuite/winsup.api/ltp/mmap06.c
    winsup/testsuite/winsup.api/ltp/mmap07.c
    winsup/testsuite/winsup.api/ltp/mmap08.c
    winsup/testsuite/winsup.api/ltp/munmap01.c
    winsup/testsuite/winsup.api/ltp/munmap02.c
    winsup/testsuite/winsup.api/ltp/nice05.c
    winsup/testsuite/winsup.api/ltp/open02.c
    winsup/testsuite/winsup.api/ltp/open03.c
    winsup/testsuite/winsup.api/ltp/pathconf01.c
    winsup/testsuite/winsup.api/ltp/pause01.c
    winsup/testsuite/winsup.api/ltp/pipe01.c
    winsup/testsuite/winsup.api/ltp/pipe08.c
    winsup/testsuite/winsup.api/ltp/pipe09.c
    winsup/testsuite/winsup.api/ltp/pipe10.c
    winsup/testsuite/winsup.api/ltp/pipe11.c
    winsup/testsuite/winsup.api/ltp/poll01.c
    winsup/testsuite/winsup.api/ltp/read01.c
    winsup/testsuite/winsup.api/ltp/read04.c
    winsup/testsuite/winsup.api/ltp/readdir01.c
    winsup/testsuite/winsup.api/ltp/readlink01.c
    winsup/testsuite/winsup.api/ltp/readlink02.c
    winsup/testsuite/winsup.api/ltp/readlink03.c
    winsup/testsuite/winsup.api/ltp/rename01.c
    winsup/testsuite/winsup.api/ltp/rename02.c
    winsup/testsuite/winsup.api/ltp/rename08.c
    winsup/testsuite/winsup.api/ltp/rename10.c
    winsup/testsuite/winsup.api/ltp/rmdir01.c
    winsup/testsuite/winsup.api/ltp/rmdir04.c
    winsup/testsuite/winsup.api/ltp/rmdir05.c
    winsup/testsuite/winsup.api/ltp/sbrk01.c
    winsup/testsuite/winsup.api/ltp/select01.c
    winsup/testsuite/winsup.api/ltp/select02.c
    winsup/testsuite/winsup.api/ltp/select03.c
    winsup/testsuite/winsup.api/ltp/setgid01.c
    winsup/testsuite/winsup.api/ltp/setgroups01.c
    winsup/testsuite/winsup.api/ltp/setpgid01.c
    winsup/testsuite/winsup.api/ltp/setregid01.c
    winsup/testsuite/winsup.api/ltp/setreuid01.c
    winsup/testsuite/winsup.api/ltp/setuid01.c
    winsup/testsuite/winsup.api/ltp/setuid02.c
    winsup/testsuite/winsup.api/ltp/signal03.c
    winsup/testsuite/winsup.api/ltp/stat01.c
    winsup/testsuite/winsup.api/ltp/stat02.c
    winsup/testsuite/winsup.api/ltp/stat03.c
    winsup/testsuite/winsup.api/ltp/stat05.c
    winsup/testsuite/winsup.api/ltp/stat06.c
    winsup/testsuite/winsup.api/ltp/symlink01.c
    winsup/testsuite/winsup.api/ltp/symlink02.c
    winsup/testsuite/winsup.api/ltp/symlink03.c
    winsup/testsuite/winsup.api/ltp/symlink04.c
    winsup/testsuite/winsup.api/ltp/symlink05.c
    winsup/testsuite/winsup.api/ltp/sync01.c
    winsup/testsuite/winsup.api/ltp/sync02.c
    winsup/testsuite/winsup.api/ltp/time01.c
    winsup/testsuite/winsup.api/ltp/time02.c
    winsup/testsuite/winsup.api/ltp/times01.c
    winsup/testsuite/winsup.api/ltp/times02.c
    winsup/testsuite/winsup.api/ltp/times03.c
    winsup/testsuite/winsup.api/ltp/truncate01.c
    winsup/testsuite/winsup.api/ltp/truncate02.c
    winsup/testsuite/winsup.api/ltp/ulimit01.c
    winsup/testsuite/winsup.api/ltp/umask01.c
    winsup/testsuite/winsup.api/ltp/umask02.c
    winsup/testsuite/winsup.api/ltp/umask03.c
    winsup/testsuite/winsup.api/ltp/uname01.c
    winsup/testsuite/winsup.api/ltp/unlink05.c
    winsup/testsuite/winsup.api/ltp/unlink06.c
    winsup/testsuite/winsup.api/ltp/unlink07.c
    winsup/testsuite/winsup.api/ltp/unlink08.c
    winsup/testsuite/winsup.api/ltp/vfork01.c
    winsup/testsuite/winsup.api/ltp/wait02.c
    winsup/testsuite/winsup.api/ltp/wait401.c
    winsup/testsuite/winsup.api/ltp/wait402.c
    winsup/testsuite/winsup.api/ltp/write01.c
    winsup/testsuite/winsup.api/ltp/write02.c
    winsup/testsuite/winsup.api/ltp/write03.c
    winsup/testsuite/winsup.api/mmaptest01.c
    winsup/testsuite/winsup.api/mmaptest02.c
    winsup/testsuite/winsup.api/mmaptest03.c
    winsup/testsuite/winsup.api/mmaptest04.c
    winsup/testsuite/winsup.api/msgtest.c
    winsup/testsuite/winsup.api/nullgetcwd.c
    winsup/testsuite/winsup.api/pthread/cancel1.c
    winsup/testsuite/winsup.api/pthread/cancel10.c
    winsup/testsuite/winsup.api/pthread/cancel11.c
    winsup/testsuite/winsup.api/pthread/cancel12.c
    winsup/testsuite/winsup.api/pthread/cancel2.c
    winsup/testsuite/winsup.api/pthread/cancel3.c
    winsup/testsuite/winsup.api/pthread/cancel4.c
    winsup/testsuite/winsup.api/pthread/cancel5.c
    winsup/testsuite/winsup.api/pthread/cancel6.c
    winsup/testsuite/winsup.api/pthread/cancel7.c
    winsup/testsuite/winsup.api/pthread/cancel8.c
    winsup/testsuite/winsup.api/pthread/cancel9.c
    winsup/testsuite/winsup.api/pthread/cleanup2.c
    winsup/testsuite/winsup.api/pthread/cleanup3.c
    winsup/testsuite/winsup.api/pthread/condvar1.c
    winsup/testsuite/winsup.api/pthread/condvar2.c
    winsup/testsuite/winsup.api/pthread/condvar2_1.c
    winsup/testsuite/winsup.api/pthread/condvar3.c
    winsup/testsuite/winsup.api/pthread/condvar3_1.c
    winsup/testsuite/winsup.api/pthread/condvar3_2.c
    winsup/testsuite/winsup.api/pthread/condvar3_3.c
    winsup/testsuite/winsup.api/pthread/condvar4.c
    winsup/testsuite/winsup.api/pthread/condvar5.c
    winsup/testsuite/winsup.api/pthread/condvar6.c
    winsup/testsuite/winsup.api/pthread/condvar7.c
    winsup/testsuite/winsup.api/pthread/condvar8.c
    winsup/testsuite/winsup.api/pthread/condvar9.c
    winsup/testsuite/winsup.api/pthread/count1.c
    winsup/testsuite/winsup.api/pthread/create1.c
    winsup/testsuite/winsup.api/pthread/create2.c
    winsup/testsuite/winsup.api/pthread/equal1.c
    winsup/testsuite/winsup.api/pthread/exit1.c
    winsup/testsuite/winsup.api/pthread/exit2.c
    winsup/testsuite/winsup.api/pthread/exit3.c
    winsup/testsuite/winsup.api/pthread/inherit1.c
    winsup/testsuite/winsup.api/pthread/join0.c
    winsup/testsuite/winsup.api/pthread/join1.c
    winsup/testsuite/winsup.api/pthread/join2.c
    winsup/testsuite/winsup.api/pthread/mainthreadexits.c
    winsup/testsuite/winsup.api/pthread/mutex1.c
    winsup/testsuite/winsup.api/pthread/mutex1d.c
    winsup/testsuite/winsup.api/pthread/mutex1e.c
    winsup/testsuite/winsup.api/pthread/mutex1n.c
    winsup/testsuite/winsup.api/pthread/mutex1r.c
    winsup/testsuite/winsup.api/pthread/mutex2.c
    winsup/testsuite/winsup.api/pthread/mutex3.c
    winsup/testsuite/winsup.api/pthread/mutex4.c
    winsup/testsuite/winsup.api/pthread/mutex5.c
    winsup/testsuite/winsup.api/pthread/mutex6d.c
    winsup/testsuite/winsup.api/pthread/mutex6e.c
    winsup/testsuite/winsup.api/pthread/mutex6n.c
    winsup/testsuite/winsup.api/pthread/mutex6r.c
    winsup/testsuite/winsup.api/pthread/mutex7.c
    winsup/testsuite/winsup.api/pthread/mutex7d.c
    winsup/testsuite/winsup.api/pthread/mutex7e.c
    winsup/testsuite/winsup.api/pthread/mutex7n.c
    winsup/testsuite/winsup.api/pthread/mutex7r.c
    winsup/testsuite/winsup.api/pthread/mutex8e.c
    winsup/testsuite/winsup.api/pthread/mutex8n.c
    winsup/testsuite/winsup.api/pthread/mutex8r.c
    winsup/testsuite/winsup.api/pthread/once1.c
    winsup/testsuite/winsup.api/pthread/priority1.c
    winsup/testsuite/winsup.api/pthread/priority2.c
    winsup/testsuite/winsup.api/pthread/rwlock1.c
    winsup/testsuite/winsup.api/pthread/rwlock2.c
    winsup/testsuite/winsup.api/pthread/rwlock3.c
    winsup/testsuite/winsup.api/pthread/rwlock4.c
    winsup/testsuite/winsup.api/pthread/rwlock5.c
    winsup/testsuite/winsup.api/pthread/rwlock6.c
    winsup/testsuite/winsup.api/pthread/rwlock7.c
    winsup/testsuite/winsup.api/pthread/self1.c
    winsup/testsuite/winsup.api/pthread/self2.c
    winsup/testsuite/winsup.api/pthread/test.h
    winsup/testsuite/winsup.api/pthread/threadidafterfork.c
    winsup/testsuite/winsup.api/pthread/tsd1.c
    winsup/testsuite/winsup.api/resethand.c
    winsup/testsuite/winsup.api/samples/sample-fail.c
    winsup/testsuite/winsup.api/samples/sample-miscompile.c
    winsup/testsuite/winsup.api/samples/sample-pass.c
    winsup/testsuite/winsup.api/semtest.c
    winsup/testsuite/winsup.api/shmtest.c
    winsup/testsuite/winsup.api/sigchld.c
    winsup/testsuite/winsup.api/signal-into-win32-api.c
    winsup/testsuite/winsup.api/systemcall.c
    winsup/testsuite/winsup.api/user_malloc.c
    winsup/testsuite/winsup.api/waitpid.c
    winsup/testsuite/winsup.api/winsup.exp
    winsup/utils/COPYING.dumper
    winsup/utils/ChangeLog
    winsup/utils/ChangeLog-2000
    winsup/utils/ChangeLog.64bit
    winsup/utils/Makefile.in
    winsup/utils/aclocal.m4
    winsup/utils/autogen.sh
    winsup/utils/bloda.cc
    winsup/utils/configure
    winsup/utils/configure.ac
    winsup/utils/cygcheck.cc
    winsup/utils/cygpath.cc
    winsup/utils/cygwin-console-helper.cc
    winsup/utils/dump_setup.cc
    winsup/utils/dumper.cc
    winsup/utils/dumper.h
    winsup/utils/getconf.c
    winsup/utils/getfacl.c
    winsup/utils/kill.cc
    winsup/utils/ldd.cc
    winsup/utils/ldh.cc
    winsup/utils/loadlib.h
    winsup/utils/locale.cc
    winsup/utils/minidumper.cc
    winsup/utils/mkgroup.c
    winsup/utils/mkpasswd.c
    winsup/utils/module_info.cc
    winsup/utils/mount.cc
    winsup/utils/parse_pe.cc
    winsup/utils/passwd.c
    winsup/utils/path.cc
    winsup/utils/path.h
    winsup/utils/pldd.c
    winsup/utils/ps.cc
    winsup/utils/regtool.cc
    winsup/utils/setfacl.c
    winsup/utils/setmetamode.c
    winsup/utils/ssp.c
    winsup/utils/ssp.txt
    winsup/utils/strace.cc
    winsup/utils/testsuite.cc
    winsup/utils/testsuite.h
    winsup/utils/tzset.c
    winsup/utils/umount.cc
    winsup/utils/utils.xml
    winsup/utils/wide_path.h

1 files changed, 0 insertions, 621 deletions

diff --git a/winsup/doc/faq-setup.xml b/winsup/doc/faq-setup.xml
deleted file mode 100644
index d2a0f1cc0..000000000
--- a/winsup/doc/faq-setup.xml
+++ /dev/null
@@ -1,621 +0,0 @@
-<?xml version="1.0" encoding='UTF-8'?>
-<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook V4.5//EN"
-		"http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd">
-
-<qandadiv id="faq.setup">
-<title>Setting up Cygwin</title>
-
-<!-- faq-setup.xml -->
-<qandaentry id="faq.setup.setup">
-<question><para>What is the recommended installation procedure?</para></question>
-<answer>
-
-<para>There is only one recommended way to install Cygwin, which is to use the GUI
-installer <command>setup-*.exe</command>.  It is flexible and easy to use.  
-You can pick and choose the packages you wish to install, and update
-them individually.  Full source code is available for all packages and
-tools.  More information on using Cygwin Setup may be found at
-<ulink url="http://cygwin.com/cygwin-ug-net/setup-net.html" />.
-</para>
-<para>If you do it any other way, you're on your own!
-If something doesn't work right for you, and
-it's not covered here or in the latest development snapshot at
-<ulink url="http://cygwin.com/snapshots/">http://cygwin.com/snapshots/</ulink>, then by all means report it to the
-mailing list.
-</para>
-<para>For a searchable list of packages that can be installed with Cygwin,
-see <ulink url="http://cygwin.com/packages/">http://cygwin.com/packages/</ulink>.
-</para>
-</answer></qandaentry>
-
-<qandaentry id="faq.setup.automated">
-<question><para>What about an automated Cygwin installation?</para></question>
-<answer>
-
-<para>The Cygwin Setup program is designed to be interactive, but there are
-a few different ways to automate it. If you are deploying to multiple systems,
-the best way is to run through a full installation once, saving the entire 
-downloaded package tree. Then, on target systems, run Cygwin Setup as a
-"Local Install" pointed at your downloaded package tree. You could do this 
-non-interactively with the command line options
-<literal>-q -L -l x:\cygwin-local\</literal>, where your downloaded 
-package tree is in <literal>x:\cygwin-local\</literal> (see the next FAQ for
-an explanation of those options.)
-</para>
-<para>
-For other options, search the mailing lists with terms such as 
-<ulink url="http://www.google.com/search?q=cygwin+automated+setup">cygwin automated setup</ulink> or
-<ulink url="http://www.google.com/search?q=automated+cygwin+install">automated cygwin install</ulink>.
-</para>
-</answer></qandaentry>
-
-<qandaentry id="faq.setup.cli">
-<question><para>Does Setup accept command-line arguments?</para></question>
-<answer>
-
-<para>Yes, the full listing is written to the <literal>setup.log</literal> file 
-when you run <literal>setup-x86.exe --help</literal> or
-<literal>setup-x86_64.exe --help</literal>. The current options are:
-<screen>
-Command Line Options:
- -D --download                     Download from internet
- -L --local-install                Install from local directory
- -s --site                         Download site
- -O --only-site                    Ignore all sites except for -s
- -R --root                         Root installation directory
- -x --remove-packages              Specify packages to uninstall
- -c --remove-categories            Specify categories to uninstall
- -P --packages                     Specify packages to install
- -C --categories                   Specify entire categories to install
- -p --proxy                        HTTP/FTP proxy (host:port)
- -a --arch                         architecture to install (x86_64 or x86)
- -q --quiet-mode                   Unattended setup mode
- -M --package-manager              Semi-attended chooser-only mode
- -B --no-admin                     Do not check for and enforce running as
-                                   Administrator
- -h --help                         print help
- -l --local-package-dir            Local package directory
- -r --no-replaceonreboot           Disable replacing in-use files on next
-                                   reboot.
- -X --no-verify                    Don't verify setup.ini signatures
- -n --no-shortcuts                 Disable creation of desktop and start menu
-                                   shortcuts
- -N --no-startmenu                 Disable creation of start menu shortcut
- -d --no-desktop                   Disable creation of desktop shortcut
- -K --pubkey                       URL of extra public key file (gpg format)
- -S --sexpr-pubkey                 Extra public key in s-expr format
- -u --untrusted-keys               Use untrusted keys from last-extrakeys
- -U --keep-untrusted-keys          Use untrusted keys and retain all
- -g --upgrade-also                 also upgrade installed packages
- -o --delete-orphans               remove orphaned packages
- -A --disable-buggy-antivirus      Disable known or suspected buggy anti virus
-                                   software packages during execution.
-</screen>
-</para>
-</answer></qandaentry>
-
-<qandaentry id="faq.setup.noroot">
-<question><para>Can I install Cygwin without administrator rights?</para></question>
-<answer>
-
-<para>Yes.  The default installation requests administrator rights because
-this allows to set up the Cygwin environment so that all users can start
-a Cygwin shell out of the box.  However, if you don't have administrator
-rights for your machine, and the admins don't want to install it for you,
-you can install Cygwin just for yourself by downloading
-<command>setup-x86.exe</command> (for a 32 bit install) or
-<command>setup-x86_64.exe</command> (for a 64 bit install) and then start
-it from the command line or via the "Run..." dialog from the start menu
-using the <literal>--no-admin</literal> option, for instance:</para>
-
-<para>
-<screen>
-  setup-x86.exe --no-admin
-</screen>
-</para>
-</answer></qandaentry>
-
-<qandaentry id="faq.setup.c">
-<question><para>Why not install in C:\?</para></question>
-<answer>
-
-<para>The Cygwin Setup program will prompt you for a "root" directory.
-The default is <literal>C:\cygwin</literal>, but you can change it.  You are urged not to
-choose something like <literal>C:\</literal> (the root directory on the system drive) for
-your Cygwin root.  If you do, then critical Cygwin system directories
-like <literal>etc</literal>, <literal>lib</literal> and <literal>bin</literal> could easily be corrupted by
-other (non-Cygwin) applications or packages that use <literal>\etc</literal>,
-<literal>\lib</literal> or <literal>\bin</literal>.  Perhaps there is no conflict now, but who
-knows what you might install in the future?  It's also just good common
-sense to segregate your Cygwin "filesystems" from the rest of your
-Windows system disk.
-</para>
-<para>(In the past, there had been genuine bugs that would cause problems
-for people who installed in <literal>C:\</literal>, but we believe those are gone
-now.)
-</para>
-</answer></qandaentry>
-
-<qandaentry id="faq.setup.old-versions">
-<question><para>Can I use Cygwin Setup to get old versions of packages (like gcc-2.95)?</para></question>
-<answer>
-
-<para>Cygwin Setup can be used to install any packages that are on a
-Cygwin mirror, which usually includes one version previous to the
-current one. The complete list may be searched at 
-<ulink url="http://cygwin.com/packages/">http://cygwin.com/packages/</ulink>.  There is no complete archive of
-older packages. If you have a problem with the current version of
-a Cygwin package, please report it to the mailing list using the 
-guidelines at <ulink url="http://cygwin.com/problems.html">http://cygwin.com/problems.html</ulink>.
-</para>
-<para>That said, if you really need an older package, you may be able to find
-an outdated or archival mirror by searching the web for an old package
-version (for example, <literal>gcc2-2.95.3-10-src.tar.bz2</literal>), but keep in
-mind that this older version will not be supported by the mailing list
-and that installing the older version will not help improve Cygwin.
-</para>
-</answer></qandaentry>
-
-<qandaentry id="faq.setup.upgrade-mountpoints">
-<question><para>After upgrading from Cygwin 1.5 to Cygwin 1.7 my user mount points disappeared!  How can I get them back?</para></question>
-<answer>
-
-<para>
-When you upgrade an existing older Cygwin installation to Cygwin 1.7, your old
-system mount points (stored in the HKEY_LOCAL_MACHINE branch of your registry)
-are read by a script and the /etc/fstab file is generated from these entries. 
-No such automatism exists for the user mount points formerly stored in the
-HKEY_CURRENT_USER branch of the registry.  There's a bash script for your
-convenience, which creates a user-specific /etc/fstab/${USER} file for you,
-called /bin/copy-user-registry-fstab.  For more information on the new fstab
-files see the User's Guide at
-<ulink url="http://cygwin.com/cygwin-ug-net/using.html#mount-table">http://cygwin.com/cygwin-ug-net/using.html#mount-table</ulink>
-</para>
-</answer></qandaentry>
-
-<qandaentry id="faq.setup.virus">
-<question><para>Is Cygwin Setup, or one of the packages, infected with a virus?</para></question>
-<answer>
-
-<para>Unlikely.  Unless you can confirm it, please don't report it to the
-mailing list.  Anti-virus products have been known to detect false
-positives when extracting compressed tar archives.  If this causes
-problems for you, consider disabling your anti-virus software when
-running <literal>setup</literal>.  Read the next entry for a fairly safe way to do
-this.
-</para>
-</answer></qandaentry>
-
-<qandaentry id="faq.setup.hang">
-<question><para>My computer hangs when I run Cygwin Setup!</para></question>
-<answer>
-
-<para>Both Network Associates (formerly McAfee) and Norton anti-virus
-products have been reported to "hang" when extracting Cygwin tar
-archives.  If this happens to you, consider disabling your anti-virus
-software when running Cygwin Setup.  The following procedure should be
-a fairly safe way to do that:
-</para>
-<orderedlist><listitem><para>Download <literal>setup-x86.exe</literal> or
-<literal>setup-x86_64.exe</literal> and scan it explicitly.
-</para>
-</listitem>
-<listitem><para>Turn off the anti-virus software.
-</para>
-</listitem>
-<listitem><para>Run setup to download and extract all the tar files.
-</para>
-</listitem>
-<listitem><para>Re-activate your anti-virus software and scan everything
-in C:\cygwin (or wherever you chose to install), or your entire hard
-disk if you are paranoid.
-</para>
-</listitem>
-</orderedlist>
-
-<para>This should be safe, but only if Cygwin Setup is not substituted by
-something malicious, and no mirror has been compromised.
-</para>
-<para>See also <ulink url="http://cygwin.com/faq/faq.html#faq.using.bloda" />
-for a list of applications that have been known, at one time or another, to
-interfere with the normal functioning of Cygwin.
-</para>
-</answer></qandaentry>
-
-<qandaentry id="faq.setup.what-packages">
-<question><para>What packages should I download? Where are 'make', 'gcc', 'vi', etc?  </para></question>
-<answer>
-<para>When using Cygwin Setup for the first time, the default is to install
-a minimal subset of all available packages.  If you want anything beyond that,
-you will have to select it explicitly.  See 
-<ulink url="http://cygwin.com/packages/" /> for a searchable list of available
-packages, or use <literal>cygcheck -p </literal> as described in the Cygwin
-User's Guide at
-<ulink url="http://cygwin.com/cygwin-ug-net/using-utils.html#cygcheck" />.
-</para>
-<para>If you want to build programs, of course you'll need <literal>gcc</literal>,
-<literal>binutils</literal>, <literal>make</literal> and probably other packages from the
-``Devel'' category. Text editors can be found under ``Editors''.
-</para>
-</answer></qandaentry>
-
-<qandaentry id="faq.setup.everything">
-<question><para>How do I just get everything?</para></question>
-<answer>
-
-<para>Long ago, the default was to install everything, much to the
-irritation of most users.  Now the default is to install only a basic
-core of packages.  Cygwin Setup is designed to make it easy to browse
-categories and select what you want to install or omit from those
-categories.  It's also easy to install everything:
-</para>
-<orderedlist>
-<listitem><para>At the ``Select Packages'' screen, in ``Categories'' view, at the line 
-marked ``All'', click on the word ``default'' so that it changes to
-``install''.  (Be patient, there is some computing to do at this step.
-It may take a second or two to register the change.)  This tells Setup
-to install <emphasis>everything</emphasis>, not just what it thinks you should have
-by default.
-</para>
-</listitem>
-<listitem><para>Now click on the ``View'' button (twice) until you get to the
-``Pending'' view.  This shows exactly which packages are about to be
-downloaded and installed.
-</para>
-</listitem>
-</orderedlist>
-
-<para>This procedure only works for packages that are currently available.
-There is no way to tell Cygwin Setup to install all packages by
-default from now on.  As new packages become available that would not
-be installed by default, you have to repeat the above procedure to get
-them.
-</para>
-<para>In general, a better method (in my opinion), is to:
-</para>
-<orderedlist>
-<listitem><para>First download &amp; install all packages that would normally be
-installed by default.  This includes fundamental packages and any
-updates to what you have already installed.  Then...
-</para>
-</listitem>
-<listitem><para>Run Cygwin Setup again, and apply the above technique to get all
-new packages that would not be installed by default.  You can check
-the list in the ``Pending'' view before proceeding, in case there's
-something you really <emphasis>don't</emphasis> want.
-</para>
-</listitem>
-<listitem><para>In the latest version of Cygwin Setup, if you click the ``View''
-button (twice) more, it shows packages not currently installed.  You
-ought to check whether you <emphasis>really</emphasis> want to install everything!
-</para>
-</listitem>
-</orderedlist>
-
-</answer></qandaentry>
-
-<qandaentry id="faq.setup.disk-space">
-<question><para>How much disk space does Cygwin require?</para></question>
-<answer>
-
-<para>That depends, obviously, on what you've chosen to download and
-install.  A full installation today is probably larger than 1 GB
-installed, not including the package archives themselves nor the source
-code.
-</para>
-<para>After installation, the package archives remain in your ``Local
-Package Directory''.  By default the location of
-<literal>setup-x86{_64}.exe</literal>.  You may conserve disk space by
-deleting the subdirectories there.  These directories will have very weird
-looking names, being encoded with their URLs
-(named <literal>ftp%3a%2f...</literal>).
-</para>
-<para>Of course, you can keep them around in case you want to reinstall a
-package. If you want to clean out only the outdated packages, Michael Chase
-has written a script called <literal>clean_setup.pl</literal>, available
-at <ulink url="ftp://cygwin.com/pub/cygwin/unsupported/clean_setup.pl" />.
-</para>
-</answer></qandaentry>
-
-<qandaentry id="faq.setup.what-upgraded">
-<question><para>How do I know which version I upgraded from?</para></question>
-<answer>
-
-<para>Detailed logs of the most recent Cygwin Setup session can be found in
-<literal>/var/log/setup.log.full</literal> and less verbose information about
-prior actions is in <literal>/var/log/setup.log</literal>.
-</para>
-
-</answer></qandaentry>
-
-<qandaentry id="faq.setup.setup-fails">
-<question><para>What if setup fails?</para></question>
-<answer>
-
-<para>First, make sure that you are using the latest version of Cygwin Setup.
-The latest version is always available from the Cygwin Home Page at <ulink
-url="http://cygwin.com/">http://cygwin.com/</ulink>.  </para>
-<para>If you are downloading from the Internet, setup will fail if it cannot
-download the list of mirrors at <ulink
-url="http://cygwin.com/mirrors.html">http://cygwin.com/mirrors.html</ulink>.
-It could be that the network is too busy.  Something similar could be the
-cause of a download site not working.  Try another mirror, or try again
-later.
-</para>
-<para>If setup refuses to download a package that you know needs to be
-upgraded, try deleting that package's entry from /etc/setup.  If you are
-reacting quickly to an announcement on the mailing list, it could be
-that the mirror you are using doesn't have the latest copy yet.  Try
-another mirror, or try again tomorrow.
-</para>
-<para>If setup has otherwise behaved strangely, check the files
-<literal>setup.log</literal> and <literal>setup.log.full</literal> in
-<literal>/var/log</literal> (<literal>C:\cygwin\var\log</literal> by
-default).  It may provide some clues as to what went wrong and why.
-</para>
-<para>If you're still baffled, search the Cygwin mailing list for clues.
-Others may have the same problem, and a solution may be posted there.
-If that search proves fruitless, send a query to the Cygwin mailing
-list.  You must provide complete details in your query: version of
-setup, options you selected, contents of setup.log and setup.log.full,
-what happened that wasn't supposed to happen, etc.
-</para>
-</answer></qandaentry>
-
-<qandaentry id="faq.setup.name-with-space">
-<question><para>My Windows logon name has a space in it, will this cause problems?</para></question>
-<answer>
-
-<para>Most definitely yes!  UNIX shells (and thus Cygwin) use the space
-character as a word delimiter.  Under certain circumstances, it is
-possible to get around this with various shell quoting mechanisms, but
-you are much better off if you can avoid the problem entirely.
-</para>
-<para>You have two choices:
-</para><orderedlist>
-<listitem><para>You can rename the user in the Windows User Manager GUI and then
-run mkpasswd.
-</para>
-</listitem>
-<listitem><para>You can simply edit the /etc/passwd file and change the Cygwin user name 
-(first field). It's also a good idea to avoid spaces in the home directory.
-</para>
-</listitem>
-</orderedlist>
-
-</answer></qandaentry>
-
-<qandaentry id="faq.setup.home">
-<question><para>My <literal>HOME</literal> environment variable is not what I want.</para></question>
-<answer>
-
-<para>When starting Cygwin from Windows, <literal>HOME</literal> is determined as follows
-in order of decreasing priority:
-</para>
-<orderedlist>
-<listitem><para><literal>HOME</literal> from the Windows environment, translated to POSIX form.
-</para>
-</listitem>
-<listitem><para>The entry in /etc/passwd
-</para>
-</listitem>
-<listitem><para>/home/USERNAME
-</para>
-</listitem>
-</orderedlist>
-
-<para>When using Cygwin from the network (telnet, ssh,...), <literal>HOME</literal> is set 
-from /etc/passwd.
-</para>
-<para>If your <literal>HOME</literal> is set to a value such as /cygdrive/c, it is likely 
-that it was set in Windows. Start a DOS Command Window and type 
-"set HOME" to verify if this is the case.
-</para>
-<para>Access to shared drives is often restricted when starting from the network,
-thus Domain users may wish to have a different <literal>HOME</literal> in the 
-Windows environment (on shared drive) than in /etc/passwd (on local drive).
-Note that ssh only considers /etc/passwd, disregarding <literal>HOME</literal>. 
-</para>
-</answer></qandaentry>
-
-<qandaentry id="faq.setup.uninstall-packages">
-<question><para>How do I uninstall individual packages?</para></question>
-<answer>
-
-<para>Run Cygwin Setup as you would to install packages.  In the list of
-packages to install, browse the relevant category or click on the
-``View'' button to get a full listing.  Click on the cycle glyph until
-the action reads ``Uninstall''.  Proceed by clicking ``Next''.
-</para>
-</answer></qandaentry>
-
-<qandaentry id="faq.setup.uninstall-service">
-<question><para>How do I uninstall a Cygwin service?</para></question>
-<answer>
-<orderedlist>
-<listitem><para>List all services you have installed with 
-<literal>cygrunsrv -L</literal>. If you do not have 
-<literal>cygrunsrv</literal> installed, skip this FAQ.
-</para></listitem>
-<listitem><para>Before removing the service, you should stop it with 
-<literal>cygrunsrv --stop <replaceable>service_name</replaceable></literal>. 
-If you have <literal>inetd</literal> configured to run as a standalone
-service, it will not show up in the list, but 
-<literal>cygrunsrv --stop inetd</literal> will work to stop it as 
-well.
-</para></listitem> 
-<listitem><para>Lastly, remove the service with
-<literal>cygrunsrv --remove <replaceable>service_name</replaceable></literal>.
-</para></listitem>
-</orderedlist>
-</answer></qandaentry>
-
-<qandaentry id="faq.setup.uninstall-all">
-<question><para>How do I uninstall <emphasis role='bold'>all</emphasis> of Cygwin?</para></question>
-<answer>
-<para>Setup has no automatic uninstall facility.  The recommended method to remove all 
-of Cygwin is as follows:
-</para>
-<orderedlist>
-<listitem><para>If you have any Cygwin services running, remove by repeating 
-the instructions in <ulink
-url="http://cygwin.com/faq/faq.html#faq.setup.uninstall-service" /> for
-all services that you installed.  Common services that might have been
-installed are <literal>sshd</literal>, <literal>cron</literal>, 
-<literal>cygserver</literal>, <literal>inetd</literal>, <literal>apache</literal>, 
-<literal>postgresql</literal>, and so on.
-</para>
-</listitem>
-<listitem><para>Stop the X11 server if it is running, and terminate any Cygwin programs 
-that might be running in the background.  Exit the command prompt and ensure
-that no Cygwin processes remain.  Note: If you want to save your mount points for a later 
-reinstall, first save the output of <literal>mount -m</literal> as described at 
-<ulink url="http://cygwin.com/cygwin-ug-net/using-utils.html#mount" />.
-</para>
-</listitem>
-<listitem><para>If you installed <literal>cyglsa.dll</literal> by running the
-shell script <literal>/usr/bin/cyglsa-config</literal> as described in
-<ulink url="http://cygwin.com/cygwin-ug-net/ntsec.html" />, then you need to
-configure Windows to stop using the LSA authentication package.  You do so by
-editing the registry and restoring
-<literal>/HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Control/Lsa/Authentication Packages</literal>
-back to it's original value of <literal>msv1_0</literal>, and then rebooting.
-</para>
-</listitem>
-<listitem><para>Delete the Cygwin root folder and all subfolders.  If you get an error 
-that an object is in use, then ensure that you've stopped all services and 
-closed all Cygwin programs.  If you get a 'Permission Denied' error then you 
-will need to modify the permissions and/or ownership of the files or folders 
-that are causing the error.  For example, sometimes files used by system 
-services end up owned by the SYSTEM account and not writable by regular users.  
-</para>
-<para>The quickest way to delete the entire tree if you run into this problem is to 
-change the ownership of all files and folders to your account.  To do this in 
-Windows Explorer, right click on the root Cygwin folder, choose Properties, then 
-the Security tab.  If you are using Windows XP Home or Simple File Sharing,
-you will need to boot into Safe Mode to access the Security tab.  Select 
-Advanced, then go to the Owner tab and make sure your account is listed as 
-the owner.  Select the 'Replace owner on subcontainers and objects' checkbox 
-and press Ok.  After Explorer applies the changes you should be able to 
-delete the entire tree in one operation.  Note that you can also achieve 
-this in Cygwin by typing <literal>chown -R user /</literal> or by using other 
-tools such as <literal>CACLS.EXE</literal>. 
-</para>
-</listitem>
-<listitem><para>Delete the Cygwin shortcuts on the Desktop and Start Menu, and
-anything left by setup-x86{_64}.exe in the download directory.  However, if you
-plan to reinstall Cygwin it's a good idea to keep your setup-x86{_64}.exe
-download directory since you can reinstall the packages left in its cache
-without redownloading them.
-</para>
-</listitem>
-<listitem><para>If you added Cygwin to your system path, you should remove it unless you 
-plan to reinstall Cygwin to the same location.  Similarly, if you set your 
-CYGWIN environment variable system-wide and don't plan to reinstall, you should 
-remove it.
-</para>
-</listitem>
-<listitem><para>Finally, if you want to be thorough you can delete the registry tree 
-<literal>Software\Cygwin</literal> under <literal>HKEY_LOCAL_MACHINE</literal> and/or 
-<literal>HKEY_CURRENT_USER</literal>.  However, if you followed the directions above you 
-will have already removed everything important.  Typically only the installation
-directory has been stored in the registry at all.
-</para>
-</listitem>
-</orderedlist>
-
-</answer></qandaentry>
-
-<qandaentry id="faq.setup.snapshots">
-<question><para>How do I install snapshots?</para></question>
-<answer>
-
-<para>First, are you sure you want to do this?  Snapshots are risky.  They
-have not been tested.  Use them <emphasis role='bold'>only</emphasis> if there is a feature or
-bugfix that you need to try, and you are willing to deal with any
-problems, or at the request of a Cygwin developer.
-</para>
-<para>You cannot use Cygwin Setup to install a snapshot.
-</para>
-<para>First, you will need to download the snapshot from the snapshots
-page at <ulink url="http://cygwin.com/snapshots/">http://cygwin.com/snapshots/</ulink>.  Note the directory where
-you saved the snapshot tarball.
-</para>
-<para>Before installing a snapshot, you must first Close <emphasis role='bold'>all</emphasis> Cygwin
-applications, including shells and services (e.g., <literal>inetd</literal>, <literal>sshd</literal>).
-You will not be able to replace <literal>cygwin1.dll</literal> if any Cygwin process is
-running.  You may have to restart Windows to clear the DLL from memory
-(beware of automatic service startup).
-</para>
-<para>Most of the downloaded snapshot can be installed using <literal>tar</literal>.  Cygwin
-<literal>tar</literal> won't be able to update <literal>/usr/bin/cygwin1.dll</literal> (because it's
-used by <literal>tar</literal> itself), but it should succeed with everything else.  If
-you are only installing the DLL snapshot, skip the first tar command.  Open
-a <literal>bash</literal> shell (it should be the only running Cygwin process) and issue
-the following commands:
-<screen>
-	/bin/tar -C / -xvf /posix/path/to/cygwin-inst-YYYYMMDD.tar.* --exclude=usr/bin/cygwin1.dll
-	/bin/tar -C /tmp -xvf /posix/path/to/cygwin-inst-YYYYMMDD.tar.* usr/bin/cygwin1.dll
-</screen>
-</para>
-<para>Exit the bash shell, and use Explorer or the Windows command shell to
-first rename <literal>C:\cygwin\bin\cygwin1.dll</literal> to
-<literal>C:\cygwin\bin\cygwin1-prev.dll</literal> and then move
-<literal>C:\cygwin\tmp\usr\bin\cygwin1.dll</literal>
-to <literal>C:\cygwin\bin\cygwin1.dll</literal> (assuming you installed Cygwin in
-<literal>C:\cygwin</literal>).
-</para>
-<para>The operative word in trying the snapshots is "<emphasis>trying</emphasis>".  If you
-notice a problem with the snapshot that was not present in the release
-DLL (what we call a "regression"), please report it to the Cygwin
-mailing list (see <ulink url="http://cygwin.com/problems.html">http://cygwin.com/problems.html</ulink> for problem
-reporting guidelines).  If you wish to go back to the older version of the
-DLL, again, close all Cygwin processes, delete
-<literal>C:\cygwin\bin\cygwin1.dll</literal>, and
-rename <literal>C:\cygwin\bin\cygwin1-prev.dll</literal> back to
-<literal>C:\cygwin\bin\cygwin1.dll</literal> (again assuming that your "<literal>/</literal>" is
-<literal>C:\cygwin</literal>).  To restore the rest of the snapshot
-files, reinstall the "<literal>cygwin</literal>" package using Setup.
-</para>
-
-</answer></qandaentry>
-
-<qandaentry id="faq.setup.mirror">
-<question><para>Can Cygwin Setup maintain a ``mirror''?</para></question>
-<answer>
-
-<para>NO.  Cygwin Setup cannot do this for you.  Use a tool designed for
-this purpose.  See <ulink url="http://rsync.samba.org/">http://rsync.samba.org/</ulink>,
-<ulink url="http://www.gnu.org/software/wget/">http://www.gnu.org/software/wget/</ulink> for utilities that can do this for you.
-For more information on setting up a custom Cygwin package server, see
-the Cygwin Setup homepage at
-<ulink url="http://sourceware.org/cygwin-apps/setup.html">http://sourceware.org/cygwin-apps/setup.html</ulink>.
-</para>
-</answer></qandaentry>
-
-<qandaentry id="faq.setup.cd">
-<question><para>How can I make my own portable Cygwin on CD?</para></question>
-<answer>
-
-<para>While some users have successfully done this, for example Indiana
-University's XLiveCD <ulink url="http://xlivecd.indiana.edu/">http://xlivecd.indiana.edu/</ulink>, there is no
-easy way to do it. Full instructions for constructing a portable Cygwin
-on CD by hand can be found on the mailing list at
-<ulink url="http://www.cygwin.com/ml/cygwin/2003-07/msg01117.html">http://www.cygwin.com/ml/cygwin/2003-07/msg01117.html</ulink>
-(Thanks to fergus at bonhard dot uklinux dot net for these instructions.)
-Please note that these instructions are rather old and are referring to the
-somewhat different setup of a Cygwin 1.5.x release.  As soon as somebody set
-this up for Cygwin 1.7, we might add this information here.
-</para>
-</answer></qandaentry>
-
-<qandaentry id="faq.setup.registry">
-<question><para>How do I save, restore, delete, or modify the Cygwin information stored in the registry?</para></question>
-<answer>
-
-<para>Since Cygwin 1.7, there's nothing important in the registry anymore,
-except for the installation directory information stored there for the sake
-of setup-x86{_64}.exe.  There's nothing left to manipulate anymore.
-</para></answer></qandaentry>
-</qandadiv>
-