sourceware.org URLs are concerned.
* Throughout, simplify ulink expressions if the visible text is the
URL anyway.
* faq-programming.xml (faq.programming.dll-relocatable): Remove.
* faq-setup.xml (faq.setup.name-with-space): Change for 1.7.34.
(faq.setup.home): Ditto.
* faq-using.xml (faq.using.printing): Clarify old links and availability
of a2ps and file.
(faq.using.xemacs): Drop outdated version info and pointers to native
XEmacs.
(faq.using.ntemacs): Remove.
* faq-what.xml (faq.what.what): Rephrase to reflect reality.
(faq.what.supported): Ditto.
(faq.what.who): Rephrase slightly.
* legal.xml: Bump copyright.
* setup-net.xml (internet-setup): Fix references to setup executables.
+2015-02-03 Corinna Vinschen <corinna@vinschen.de>
+
+ * Throughout, replace http with https as far as cygwin.com and
+ sourceware.org URLs are concerned.
+ * Throughout, simplify ulink expressions if the visible text is the
+ URL anyway.
+ * faq-programming.xml (faq.programming.dll-relocatable): Remove.
+ * faq-setup.xml (faq.setup.name-with-space): Change for 1.7.34.
+ (faq.setup.home): Ditto.
+ * faq-using.xml (faq.using.printing): Clarify old links and availability
+ of a2ps and file.
+ (faq.using.xemacs): Drop outdated version info and pointers to native
+ XEmacs.
+ (faq.using.ntemacs): Remove.
+ * faq-what.xml (faq.what.what): Rephrase to reflect reality.
+ (faq.what.supported): Ditto.
+ (faq.what.who): Rephrase slightly.
+ * legal.xml: Bump copyright.
+ * setup-net.xml (internet-setup): Fix references to setup executables.
+
2015-01-23 Pierre A. Humblet <phumblet@phumblet.no-ip.org>
Corinna Vinschen <corinna@vinschen.de>
The cygwin-doc source files are kept in CVS. Please see
-http://cygwin.com/cvs.html for more information.
+https://cygwin.com/cvs.html for more information.
BUILD REQUIREMENTS:
foreign applications which try to inject threads into a Cygwin process,
or which redirect system sockets by providing an enforced so-called
<literal>Layered Service Provider</literal>. This may or may not help to
-detect <ulink url="http://cygwin.com/faq/faq.html#faq.using.bloda">
+detect <ulink url="https://cygwin.com/faq/faq.html#faq.using.bloda">
BLODAs</ulink>. Don't use this option for day-to-day usage, it will slow
down every thread and socket creation!</para>
</listitem>
contribute code to the project. If you aren't going to be happy
debugging problems in a buggy snapshot, avoid these and wait for a real
release. The snapshots are available from
-<ulink url="http://cygwin.com/snapshots/">http://cygwin.com/snapshots/</ulink>.
+<ulink url="https://cygwin.com/snapshots/"/>.
</para>
</answer></qandaentry>
<question><para>What are the copyrights?</para></question>
<answer>
- <para>Please see <ulink url="http://cygwin.com/licensing.html"/>
+ <para>Please see <ulink url="https://cygwin.com/licensing.html"/>
for more information about Cygwin copyright and licensing.</para>
</answer>
</qandaentry>
Cygwin Team is Cygwin itself.
</para>
<para>The Cygwin Package Contributor's Guide at
-<ulink url="http://cygwin.com/setup.html">http://cygwin.com/setup.html</ulink> details everything you need to know
+<ulink url="https://cygwin.com/setup.html"/> details everything you need to know
about being a package maintainer. The quickest way to get started is to
read the <emphasis>Initial packaging procedure, script-based</emphasis> section on
that page. The <literal>generic-build-script</literal> found there works well for
most packages.
</para>
<para>For questions about package maintenance, use the cygwin-apps mailing
-list (start at <ulink url="http://cygwin.com/lists.html">http://cygwin.com/lists.html</ulink>) <emphasis>after</emphasis>
+list (start at <ulink url="https://cygwin.com/lists.html"/>) <emphasis>after</emphasis>
searching and browsing the cygwin-apps list archives, of course. Be
sure to look at the <emphasis>Submitting a package</emphasis> checklist at
-<ulink url="http://cygwin.com/setup.html">http://cygwin.com/setup.html</ulink> before sending an ITP (Intent To
+<ulink url="https://cygwin.com/setup.html"/> before sending an ITP (Intent To
Package) email to cygwin-apps.
</para>
<para>You should also announce your intentions to the general cygwin list, in
<answer>
<para>If you want to contribute to Cygwin itself, see
-<ulink url="http://cygwin.com/contrib.html">http://cygwin.com/contrib.html</ulink>.
+<ulink url="https://cygwin.com/contrib.html"/>.
</para>
</answer></qandaentry>
<answer>
<para>Beware of using non-portable shell features in your Makefiles (see tips
-at <ulink url="http://cygwin.com/faq/faq.html#faq.using.shell-scripts" />).
+at <ulink url="https://cygwin.com/faq/faq.html#faq.using.shell-scripts"/>).
</para>
<para>Errors of <literal>make: execvp: /bin/sh: Illegal Argument</literal> or
<literal>make: execvp: /bin/sh: Argument list too long</literal> are often
</screen>
<para>
-See <ulink url="http://cygwin.com/cygwin-ug-net/using.html#mount-table" />
+See <ulink url="https://cygwin.com/cygwin-ug-net/using.html#mount-table"/>
for more information on using mount.
</para>
<para>
Try running cygserver. Read
-<ulink url="http://cygwin.com/cygwin-ug-net/using-cygserver.html" />. If you're
+<ulink url="https://cygwin.com/cygwin-ug-net/using-cygserver.html"/>. If you're
trying to use PostgreSQL, also read
<literal>/usr/share/doc/Cygwin/postgresql-*.README</literal>.
</para>
<note><para>There are a few restrictions for calls to the Win32 API.
For details, see the User's Guide section
-<ulink url="http://cygwin.com/cygwin-ug-net/setup-env.html#setup-env-win32">Restricted Win32 environment</ulink>,
+<ulink url="https://cygwin.com/cygwin-ug-net/setup-env.html#setup-env-win32">Restricted Win32 environment</ulink>,
as well as the User's Guide section
-<ulink url="http://cygwin.com/cygwin-ug-net/using.html#pathnames-win32-api">Using the Win32 file API in Cygwin applications</ulink>.</para></note>
+<ulink url="https://cygwin.com/cygwin-ug-net/using.html#pathnames-win32-api">Using the Win32 file API in Cygwin applications</ulink>.</para></note>
</answer></qandaentry>
<qandaentry id="faq.programming.win32-no-cygwin">
</para>
<para>This is not to be confused with 'MinGW' (Minimalist GNU for Windows),
which is a completely separate effort. That project's home page is
-<ulink url="http://www.mingw.org/index.shtml">http://www.mingw.org/index.shtml</ulink>.
+<ulink url="http://www.mingw.org/index.shtml"/>.
</para>
</answer></qandaentry>
</para>
<para>If this is an issue because you intend to distribute your Cygwin
application, then you had better read and understand
-<ulink url="http://cygwin.com/licensing.html">http://cygwin.com/licensing.html</ulink>, which explains the licensing
+<ulink url="https://cygwin.com/licensing.html"/>, which explains the licensing
options. Unless you purchase a special commercial license from Red
Hat, then your Cygwin application must be Open Source.
</para>
functions from Cygwin, it must, as a matter of fact, be linked against
it), you must apply the GPL to your source as well. Of course, this
only matters if you plan to distribute your program in binary form. For
-more information, see <ulink url="http://gnu.org/licenses/gpl-faq.html">http://gnu.org/licenses/gpl-faq.html</ulink>. If
+more information, see <ulink url="http://gnu.org/licenses/gpl-faq.html"/>. If
that is not a problem, read on.
</para>
<para>If you want to load the DLL dynamically, read
</para>
<para>Next, get the Cygwin source. Ideally, you should check out
-what you need from CVS (<ulink url="http://cygwin.com/cvs.html" />). This is the
+what you need from CVS (<ulink url="https://cygwin.com/cvs.html"/>). This is the
<emphasis>preferred method</emphasis> for acquiring the sources. Otherwise, if
you are trying to duplicate a cygwin release then you should
download the corresponding source package
symbols that you see in gdb are basically meaningless. It is also a good
idea to use the latest code in case the bug has been fixed, so we
recommend trying the latest snapshot from
-<ulink url="http://cygwin.com/snapshots/" /> or building the DLL from CVS.
+<ulink url="https://cygwin.com/snapshots/"/> or building the DLL from CVS.
</para>
<para>To build a debugging version of the Cygwin DLL, you will need to follow
-the instructions at <ulink url="http://cygwin.com/faq/faq.html#faq.programming.building-cygwin" />.
+the instructions at <ulink url="https://cygwin.com/faq/faq.html#faq.programming.building-cygwin"/>.
You can also contact the mailing list for pointers (a simple test case that
demonstrates the bug is always welcome).
</para>
<answer>
<para>If you need to change the maximum amount of memory available to Cygwin, see
-<ulink url="http://cygwin.com/cygwin-ug-net/setup-maxmem.html">http://cygwin.com/cygwin-ug-net/setup-maxmem.html</ulink>. Otherwise,
+<ulink url="https://cygwin.com/cygwin-ug-net/setup-maxmem.html"/>. Otherwise,
just pass heap/stack linker arguments to gcc. To create foo.exe with
a heap size of 200MB and a stack size of 8MB, you would invoke
gcc as:
<answer>
<para>There's documentation that explains the process in the Cygwin User's
-Guide here: <ulink url="http://cygwin.com/cygwin-ug-net/dll.html">http://cygwin.com/cygwin-ug-net/dll.html</ulink>
+Guide here: <ulink url="https://cygwin.com/cygwin-ug-net/dll.html"/>.
</para>
</answer></qandaentry>
</para>
</answer></qandaentry>
-<qandaentry id="faq.programming.dll-relocatable">
-<question><para>How can I build a relocatable dll?</para></question>
-<answer>
-
-<para><emphasis role='bold'>(Please note: This section has not yet been updated for the latest net release. However, there was a discussion on the cygwin mailing list once that addresses this issue. Read <ulink url="http://cygwin.com/ml/cygwin/2000-06/msg00688.html">http://cygwin.com/ml/cygwin/2000-06/msg00688.html</ulink> and related messages.)</emphasis>
-</para>
-<para>You must execute the following sequence of five commands, in this
-order:
-</para>
-<screen>
-$(LD) -s --base-file BASEFILE --dll -o DLLNAME OBJS LIBS -e ENTRY
-
-$(DLLTOOL) --as=$(AS) --dllname DLLNAME --def DEFFILE \
- --base-file BASEFILE --output-exp EXPFILE
-
-$(LD) -s --base-file BASEFILE EXPFILE -dll -o DLLNAME OBJS LIBS -e ENTRY
-
-$(DLLTOOL) --as=$(AS) --dllname DLLNAME --def DEFFILE \
- --base-file BASEFILE --output-exp EXPFILE
-
-$(LD) EXPFILE --dll -o DLLNAME OBJS LIBS -e ENTRY
-</screen>
-
-<para>In this example, $(LD) is the linker, ld.
-</para>
-<para>$(DLLTOOL) is dlltool.
-</para>
-<para>$(AS) is the assembler, as.
-</para>
-<para>DLLNAME is the name of the DLL you want to create, e.g., tcl80.dll.
-</para>
-<para>OBJS is the list of object files you want to put into the DLL.
-</para>
-<para>LIBS is the list of libraries you want to link the DLL against. For
-example, you may or may not want -lcygwin. You may want -lkernel32.
-</para>
-<para>DEFFILE is the name of your definitions file. A simple DEFFILE would
-consist of ``EXPORTS'' followed by a list of all symbols which should
-be exported from the DLL. Each symbol should be on a line by itself.
-Other programs will only be able to access the listed symbols.
-</para>
-<para>BASEFILE is a temporary file that is used during this five stage
-process, e.g., tcl.base.
-</para>
-<para>EXPFILE is another temporary file, e.g., tcl.exp.
-</para>
-<para>ENTRY is the name of the function which you want to use as the entry
-point. This function should be defined using the WINAPI attribute,
-and should take three arguments:
- int WINAPI startup (HINSTANCE, DWORD, LPVOID)
-</para>
-<para>This means that the actual symbol name will have an appended @12, so if
-your entry point really is named <literal>startup</literal>, the string you should
-use for ENTRY in the above examples would be <literal>startup@12</literal>.
-</para>
-<para>If your DLL calls any Cygwin API functions, the entry function will need
-to initialize the Cygwin impure pointer. You can do that by declaring
-a global variable <literal>_impure_ptr</literal>, and then initializing it in the
-entry function. Be careful not to export the global variable
-<literal>_impure_ptr</literal> from your DLL; that is, do not put it in DEFFILE.
-</para>
-<screen>
-/* This is a global variable. */
-struct _reent *_impure_ptr;
-extern struct _reent *__imp_reent_data;
-
-int entry (HINSTANT hinst, DWORD reason, LPVOID reserved)
-{
- _impure_ptr = __imp_reent_data;
- /* Whatever else you want to do. */
-}
-</screen>
-
-<para>You may put an optional `--subsystem windows' on the $(LD) lines.
-Note that if you specify a --subsytem <x> flag to ld,
-the -e entry must come after the subsystem flag, since the subsystem flag
-sets a different default entry point.
-</para>
-<para>You may put an optional `--image-base BASEADDR' on the $(LD) lines.
-This will set the default image base. Programs using this DLL will
-start up a bit faster if each DLL occupies a different portion of the
-address space. Each DLL starts at the image base, and continues for
-whatever size it occupies.
-</para>
-<para>Now that you've built your DLL, you may want to build a library so
-that other programs can link against it. This is not required: you
-could always use the DLL via LoadLibrary. However, if you want to be
-able to link directly against the DLL, you need to create a library.
-Do that like this:
-</para>
-<para>$(DLLTOOL) --as=$(AS) --dllname DLLNAME --def DEFFILE --output-lib LIBFILE
-</para>
-<para>$(DLLTOOL), $(AS), DLLNAME, and DEFFILE are the same as above. Make
-sure you use the same DLLNAME and DEFFILE, or things won't work right.
-</para>
-<para>LIBFILE is the name of the library you want to create, e.g.,
-libtcl80.a. You can then link against that library using something
-like -ltcl80 in your linker command.
-</para>
-</answer></qandaentry>
-
<qandaentry id="faq.programming.debug">
<question><para>How can I debug what's going on?</para></question>
<answer>
instead of <literal>/usr/share/doc/</literal>.
</para>
<para>There are links to quite a lot of documentation on the main Cygwin
-project web page, <ulink url="http://cygwin.com/">http://cygwin.com/</ulink>,
-including this FAQ. Be sure to at least read any 'Release Notes' or 'Readme'
-or 'read this' links on the main web page, if there are any.
+project web page, <ulink url="https://cygwin.com/"/>, including this FAQ.
+Be sure to at least read any 'Release Notes' or 'Readme' or 'read this'
+links on the main web page, if there are any.
</para>
-<para>There is a comprehensive Cygwin User's Guide at <ulink
-url="http://cygwin.com/cygwin-ug-net/cygwin-ug-net.html">http://cygwin.com/cygwin-ug-net/cygwin-ug-net.html</ulink>
-and an API Reference at <ulink
-url="http://cygwin.com/cygwin-api/cygwin-api.html">http://cygwin.com/cygwin-api/cygwin-api.html</ulink>.
+<para>There is a comprehensive Cygwin User's Guide at
+<ulink url="https://cygwin.com/cygwin-ug-net/cygwin-ug-net.html"/>
+and an API Reference at
+<ulink url="https://cygwin.com/cygwin-api/cygwin-api.html"/>.
</para>
-<para>You can find documentation for the individual GNU tools at <ulink
-url="http://www.fsf.org/manual/">http://www.fsf.org/manual/</ulink>. (You
-should read GNU manuals from a local mirror, check <ulink
-url="http://www.fsf.org/server/list-mirrors.html">http://www.fsf.org/server/list-mirrors.html</ulink>
-for a list of them.)
+<para>You can find documentation for the individual GNU tools at
+<ulink url="http://www.fsf.org/manual/"/>. (You should read GNU manuals from
+a local mirror, check
+<ulink url="http://www.fsf.org/server/list-mirrors.html"/> for a list of them.)
</para>
</answer></qandaentry>
<question><para>What Cygwin mailing lists can I join?</para></question>
<answer>
<para>Comprehensive information about the Cygwin mailing lists can be found at
-<ulink url="http://cygwin.com/lists.html" />.
+<ulink url="https://cygwin.com/lists.html"/>.
</para>
</answer></qandaentry>
<qandaentry id="faq.resources.problems">
<question><para>What if I have a problem? (Or: Why won't you/the mailing list answer my questions?)</para></question>
<answer>
-<para>Comprehensive information about reporting problems with Cygwin can be found at <ulink url="http://cygwin.com/problems.html" />.
+<para>Comprehensive information about reporting problems with Cygwin can be found at <ulink url="https://cygwin.com/problems.html"/>.
</para>
</answer></qandaentry>
</qandadiv>
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" />.
+<ulink url="https://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
+<ulink url="https://cygwin.com/snapshots/"/>, 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>.
+see <ulink url="https://cygwin.com/packages/"/>.
</para>
</answer></qandaentry>
<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
+<ulink url="https://cygwin.com/packages/"/>. 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>.
+guidelines at <ulink url="https://cygwin.com/problems.html"/>.
</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
<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" />
+<para>See also <ulink url="https://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>
<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
+<ulink url="https://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" />.
+<ulink url="https://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
<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>
+The latest version is always available from the Cygwin Home Page at
+<ulink url="https://cygwin.com/"/>.
+</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>.
+download the list of mirrors at <ulink url="https://cygwin.com/mirrors.html"/>.
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>You have two choices:
</para><orderedlist>
-<listitem><para>You can rename the user in the Windows User Manager GUI and then
-run mkpasswd.
+<listitem><para>You can rename the user in the Windows User Manager GUI.
</para>
</listitem>
-<listitem><para>If you already have an /etc/passwd file, you can simply edit
-your Cygwin user name (first field). It's also a good idea to avoid spaces in
-the home directory.
+<listitem><para>If that's not possible, you can create an /etc/passwd file
+using the <command>mkpasswd</command> command. Then you can simply edit your
+Cygwin user name (first field). It's also a good idea to avoid spaces in the
+home directory.
</para>
</listitem>
</orderedlist>
<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>When starting Cygwin from Windows, <literal>HOME</literal> is determined
+as follows:
</para>
<orderedlist>
-<listitem><para><literal>HOME</literal> from the Windows environment, translated to POSIX form.
-</para>
-</listitem>
-<listitem><para>The pw_home field from the passwd entry as returned by <command>getent passwd</command>.
+<listitem><para>If <literal>HOME</literal> is set in the Windows environment,
+translated to POSIX form.
</para>
</listitem>
-<listitem><para>/home/USERNAME
+<listitem><para>Otherwise, use the pw_home field from the passwd entry as
+returned by <command>getent passwd</command>. If you want to learn how this
+field is set by Cygwin and how you can change it, this is explained in great
+detail in the Cygwin User's Guide at
+<ulink url="https://cygwin.com/cygwin-ug-net/ntsec.html"/>.
</para>
</listitem>
</orderedlist>
-<para>When using Cygwin from the network (telnet, ssh,...), <literal>HOME</literal> is taken from the passwd entry.
+<para>When using Cygwin from a network login (via ssh for instance),
+<literal>HOME</literal> is always taken from the passwd entry.
</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
+<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 Cygwin (on local drive).
+<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 Cygwin (on local drive).
Note that ssh only considers the account information as retrieved by
getpwnam(3), disregarding <literal>HOME</literal>.
</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
+url="https://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>,
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" />.
+<ulink url="https://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
+<ulink url="https://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>
<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
+page at <ulink url="https://cygwin.com/snapshots/"/>. 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
<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
+mailing list (see <ulink url="https://cygwin.com/problems.html"/> 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
<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.
+this purpose. See <ulink url="http://rsync.samba.org/"/>,
+<ulink url="http://www.gnu.org/software/wget/"/> 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>.
+<ulink url="https://sourceware.org/cygwin-apps/setup.html"/>.
</para>
</answer></qandaentry>
<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
+University's XLiveCD <ulink url="http://xlivecd.indiana.edu/"/>, 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>
+<ulink url="https://www.cygwin.com/ml/cygwin/2003-07/msg01117.html"/>
(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
</para>
<para>For a detailed explanation of the general problem, and how to extend
it to other missing DLLs and identify their containing packages, see
-<ulink url="http://cygwin.com/ml/cygwin/2002-01/msg01619.html">http://cygwin.com/ml/cygwin/2002-01/msg01619.html</ulink>.
+<ulink url="https://cygwin.com/ml/cygwin/2002-01/msg01619.html"/>.
</para>
</answer></qandaentry>
(sshd, inetd, etc), then it depends on the method used to switch to
another user. This problem as well as its solution is described in
detail in the Cygwin User's Guide, see
-<ulink url="http://cygwin.com/cygwin-ug-net/ntsec.html" />.
+<ulink url="https://cygwin.com/cygwin-ug-net/ntsec.html"/>.
</para>
<para>Workarounds include using public network share that does not require
authentication (for non-critical files), providing your password to a
<literal>ssh username@localhost</literal> as a <literal>su</literal>
replacement.
</para>
-<para>For some technical background into why <literal>su</literal> doesn't work, read
-<ulink url="http://www.cygwin.com/ml/cygwin/2003-06/msg00897.html">http://www.cygwin.com/ml/cygwin/2003-06/msg00897.html</ulink> and
+<para>For some technical background into why <literal>su</literal> doesn't
+work, read
+<ulink url="https://www.cygwin.com/ml/cygwin/2003-06/msg00897.html"/> and
related messages.
</para>
</answer></qandaentry>
<para>For other cases, understand that Cygwin attempts to show UNIX
permissions based on the security features of Windows, so the Windows
ACLs are likely the source of your problem. See the Cygwin User's
-Guide at <ulink url="http://cygwin.com/cygwin-ug-net/ntsec.html" />
+Guide at <ulink url="https://cygwin.com/cygwin-ug-net/ntsec.html"/>
for more information on how Cygwin maps Windows permissions.
</para>
</answer></qandaentry>
<question><para>How do I print under Cygwin?</para></question>
<answer>
-<para>lpr is available in the cygutils package. Some <ulink url="http://cygwin.com/ml/cygwin/2008-05/msg00123.html">usage hints</ulink> are available courtesy of Rodrigo Medina.
+<para>lpr is available in the cygutils package. Some <ulink url="https://cygwin.com/ml/cygwin/2008-05/msg00123.html">usage hints</ulink> are available courtesy of Rodrigo Medina.
</para>
<para>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
-<ulink url="http://cygwin.com/ml/cygwin/2001-04/msg00657.html">http://cygwin.com/ml/cygwin/2001-04/msg00657.html</ulink>. Note that the
-<literal>file</literal> command is now available as part of Cygwin setup.
+<ulink url="https://cygwin.com/ml/cygwin/2001-04/msg00657.html"/>. Note that
+these are old mails and <command>a2ps</command> as well as
+<command>file</command> are long available as part of the Cygwin distribution.
</para>
-<para>Alternatively, you can use the Windows <literal>print</literal>
-command. (It does not seem to be available on Win9x.) Type
+<para>Alternatively, you can use the Windows <command>print</command>
+command. Type
</para>
<screen>
bash$ print /\?
</screen>
-<para>for usage instructions (note the <literal>?</literal> must be escaped from the
-shell).
+<para>for usage instructions (note the <literal>?</literal> must be escaped
+from the shell).
</para>
-<para>Finally, you can simply <literal>cat</literal> the file to the printer's share name:
+<para>Finally, you can simply <command>cat</command> the file to the printer's share name:
</para>
<screen>
bash$ cat myfile > //host/printer
<para>Internationalization is a complex issue. The short answer is that
Cygwin relies on the setting of the setting of LANG/LC_xxx environment
variables. The long answer can be found in the User's Guide in the
-section <ulink url="http://cygwin.com/cygwin-ug-net/setup-locale.html">Internationalization</ulink>
+section <ulink url="https://cygwin.com/cygwin-ug-net/setup-locale.html">Internationalization</ulink>
</para>
<para> Cygwin uses UTF-8 by default. To use a different character set, you
Cygwin package without exiting <emphasis>all</emphasis> Cygwin apps (including
services like sshd) beforehand.</para>
<para>The only DLL that is sanctioned by the Cygwin project is the one that
-you get by running <ulink url="http://cygwin.com/install.html">setup.exe</ulink>,
+you get by running <ulink url="https://cygwin.com/install.html">setup-x86.exe or setup-x86_64.exe</ulink>,
installed in a directory controlled by this program. If you have other
versions on your system and desire help from the cygwin project, you should
delete or rename all DLLs that are not installed by
</para></question>
<answer><para>
Only if you comply with Cygwin's <ulink
-url="http://cygwin.com/licensing.html">license</ulink> very carefully. If you
+url="https://cygwin.com/licensing.html">license</ulink> very carefully. If you
choose to distribute cygwin1.dll, you must be willing to distribute the
exact source code used to build that copy of cygwin1.dll as per the
terms of the GPL. If you ship applications that link with cygwin1.dll,
<para>Probably because there is nobody willing or able to maintain it. It
takes time, and the priority for the Cygwin Team is the Cygwin package.
The rest is a volunteer effort. Want to contribute? See
-<ulink url="http://cygwin.com/setup.html">http://cygwin.com/setup.html</ulink>.
+<ulink url="https://cygwin.com/setup.html"/>.
</para>
</answer></qandaentry>
</para>
<para>You can change the default <literal>cygdrive</literal> prefix and whether it is binmode or textmode using the <filename>/etc/fstab</filename> file
as well. See the Cygwin 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>
+<ulink url="https://cygwin.com/cygwin-ug-net/using.html#mount-table"/>
for more details.
</para>
</answer></qandaentry>
Note that with many of these products, simply disabling the firewall
does not remove these changes; it must be completely uninstalled.
</para>
-<para>See also <ulink url="http://cygwin.com/faq/faq.html#faq.using.bloda" />
+<para>See also <ulink url="https://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>
<para>To help with this problem, Cygwin supports case sensitivity
starting with Cygwin 1.7.0. For a detailed description how to use that
feature see the Cygwin User's Guilde at
-<ulink url="http://cygwin.com/cygwin-ug-net/using-specialnames.html">http://cygwin.com/cygwin-ug-net/using-specialnames.html</ulink>.
+<ulink url="https://cygwin.com/cygwin-ug-net/using-specialnames.html"/>.
</para>
</answer></qandaentry>
<para>At least that's what happens when using native Windows tools. Cygwin
1.7.0 and later can deal with these filenames just fine. Again, see the
User's Guide at
-<ulink url="http://cygwin.com/cygwin-ug-net/using-specialnames.html">http://cygwin.com/cygwin-ug-net/using-specialnames.html</ulink>
+<ulink url="https://cygwin.com/cygwin-ug-net/using-specialnames.html"/>
for a detailed description of what's possible with filenames and what is not.
</para>
</answer></qandaentry>
would be <literal>C:\cygwin\bin</literal>. Obviously, this could be
exploited by a hostile non-Cygwin program, so do this at your own risk.
</para>
-<para>See also <ulink url="http://cygwin.com/faq/faq.html#faq.using.bloda" />
+<para>See also <ulink url="https://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>
<para>Yes. Install the emacs package. This provides everything you
need in order to run GNU emacs in a terminal window. If you also want
to be able to use the X11
-(<ulink url="http://x.cygwin.com/">http://x.cygwin.com/</ulink>)
+(<ulink url="https://x.cygwin.com/"/>)
GUI, install the emacs-X11 package. In either case, you run emacs by
typing 'emacs' or '/usr/bin/emacs'.
</para>
<para>Yes. It can be used in three different modes:</para>
<para><itemizedlist>
-<listitem><para>X11 (<ulink url="http://x.cygwin.com/">http://x.cygwin.com/</ulink>) GUI</para></listitem>
+<listitem><para>X11 (<ulink url="https://x.cygwin.com/"/>) GUI</para></listitem>
</itemizedlist></para>
<para>You have to <emphasis>set</emphasis> the DISPLAY environment variable
before starting xemacs.</para>
<screen>
bash$ xemacs -nw
</screen>
-<para>The current stable Cygwin version of XEmacs is 21.4.x. But there is also a
-Cygwin test release version (21.5.x) available for download via setup.exe.
-</para>
<para>To use all the standard packages with XEmacs you should download the following
two packages:</para>
<para><itemizedlist>
<listitem><para>xemacs-sumo - XEmacs standard packages</para></listitem>
<listitem><para>xemacs-mule-sumo - XEmacs MULE (MUlti Lingual Emacs) packages</para></listitem>
</itemizedlist></para>
-<para>An alternative <emphasis>native</emphasis> distribution of XEmacs for
-Windows based systems can be downloaded from
-<ulink url="http://xemacs.org/Download/win32/index.html">http://xemacs.org/Download/win32/index.html</ulink>.
-It uses an <emphasis>InnoSetup Kit</emphasis> based installer.</para>
-</answer></qandaentry>
-
-<qandaentry id="faq.using.ntemacs">
-<question><para>What about NT Emacs?</para></question>
-<answer>
-
-<para>If you want GNU Emacs with a native Microsoft GUI interface,
-then you can either use XEmacs (see above), or native
-NT Emacs: see section
-<ulink url="http://www.gnu.org/software/emacs/windows/Getting-Emacs.html#Getting-Emacs">Where can I get pre-compiled versions?</ulink> in NT Emacs FAQ.
-
-</para>
-<para>NT Emacs uses the Windows command shell by default. Since it is not a
-Cygwin application, it has no knowledge of Cygwin mounts. With those
-points in mind, you need to add the following code to your ~/.emacs
-(or ~/_emacs) file in order to use Cygwin bash. This is particularly useful
-for the JDEE package (<ulink url="http://jdee.sunsite.dk/">http://jdee.sunsite.dk/</ulink>). The following
-settings are for Emacs 21.1:
-</para>
-<screen>
-
- ;; ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
- ;; Initial setup
- ;; ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
-
- ;; This assumes that Cygwin is installed in C:\cygwin (the
- ;; default) and that C:\cygwin\bin is not already in your
- ;; Windows Path (it generally should not be).
-
- (setq exec-path (cons "C:/cygwin/bin" exec-path))
- (setenv "PATH" (concat "C:\\cygwin\\bin;" (getenv "PATH")))
-
- ;; LOGNAME and USER are expected in many Emacs packages
- ;; Check these environment variables.
-
- (if (and (null (getenv "USER"))
- ;; Windows includes variable USERNAME, which is copied to
- ;; LOGNAME and USER respectively.
- (getenv "USERNAME"))
- (setenv "USER" (getenv "USERNAME")))
-
- (if (and (getenv "LOGNAME")
- ;; Bash shell defines only LOGNAME
- (null (getenv "USER")))
- (setenv "USER" (getenv "LOGNAME")))
-
- (if (and (getenv "USER")
- (null (getenv "LOGNAME")))
- (setenv "LOGNAME" (getenv "USER")))
-
- ;; ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
- ;; (A) M-x shell: This change M-x shell permanently
- ;; ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
-
- ;; Would call Windows command interpreter. Change it.
-
- (setq shell-file-name "bash")
- (setenv "SHELL" shell-file-name)
- (setq explicit-shell-file-name shell-file-name)
-
- ;; Remove C-m (^M) characters that appear in output
-
- (add-hook 'comint-output-filter-functions
- 'comint-strip-ctrl-m)
-
- ;; ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
- ;; (B) *OR* call following function with M-x my-bash
- ;; The M-x shell would continue to run standard Windows shell
- ;; ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
-
- (defun my-bash (&optional buffer)
- "Run Cygwin Bash shell in optional BUFFER; default *shell-bash*."
- (autoload 'comint-check-proc "comint")
- (interactive
- (let ((name "*shell-bash*"))
- (if current-prefix-arg
- (setq name (read-string
- (format "Cygwin shell buffer (default %s): " name)
- (not 'initial-input)
- (not 'history)
- name)))
- (list name)))
- (or buffer
- (setq buffer "*shell-bash*"))
- (if (comint-check-proc buffer)
- (pop-to-buffer buffer)
- (let* ((shell-file-name "bash")
- (explicit-shell-file-name shell-file-name)
- (explicit-sh-args '("--login" "-i"))
- (explicit-bash-args explicit-sh-args)
- (w32-quote-process-args ?\"));; Use Cygwin quoting rules.
- (shell buffer)
- ;; By default Emacs sends "\r\n", but bash wants plain "\n"
- (set-buffer-process-coding-system 'undecided-dos 'undecided-unix)
- ;; With TAB completion, add slash path separator, none to filenames
- (make-local-variable 'comint-completion-addsuffix)
- (setq comint-completion-addsuffix '("/" . ""))
- ;; This variable is local to buffer
- (setq comint-prompt-regexp "^[ \n\t]*[$] ?"))))
-
-</screen>
-
-<para>If you want NT Emacs to understand Cygwin paths, get
-cygwin-mount.el from <ulink url="http://www.emacswiki.org/elisp/index.html">http://www.emacswiki.org/elisp/index.html</ulink>.
-</para>
-<para>Note that all of this ``just works'' if you use the Cygwin port of
-Emacs or XEmacs from Cygwin Setup.
-</para>
</answer></qandaentry>
<qandaentry id="faq.using.symlinkstoppedworking">
</para>
<para>Alternatively, use Windows shortcuts as symlinks. See the CYGWIN
environment variable option "winsymlinks"
-<ulink url="http://cygwin.com/cygwin-ug-net/using-cygwinenv.html">http://cygwin.com/cygwin-ug-net/using-cygwinenv.html</ulink>
+<ulink url="https://cygwin.com/cygwin-ug-net/using-cygwinenv.html"/>
</para>
</answer></qandaentry>
<para>Then you need to start an X server, or if one is already running, set the
<literal>DISPLAY</literal> variable to the proper value. The Cygwin distribution
-includes an X server; please see the <ulink url="http://x.cygwin.com/docs/ug/cygwin-x-ug.html">Cygwin/X User Guide</ulink>
+includes an X server; please see the <ulink url="https://x.cygwin.com/docs/ug/cygwin-x-ug.html">Cygwin/X User Guide</ulink>
for installation and startup instructions.
</para></answer></qandaentry>
ones undoes the effects of rebaseall and often causes fork() failures
to reappear. If so, just run rebaseall again.
</para>
- <para>See the <ulink url="http://cygwin.com/cygwin-ug-net/highlights.html#ov-hi-process">
+ <para>See the <ulink url="https://cygwin.com/cygwin-ug-net/highlights.html#ov-hi-process">
process creation</ulink> section of the User's Guide for the technical reasons it is so
difficult to make <literal>fork()</literal> work reliably.</para>
</answer>
<question><para>What is it?</para></question>
<answer>
-<para>The Cygwin tools are ports of the popular GNU development tools for
-Microsoft Windows. They run thanks to the Cygwin library which
+<para>Cygwin is a distribution of popular GNU and other Open Source tools
+running on Microsoft Windows. The core part is the Cygwin library which
provides the POSIX system calls and environment these programs expect.
</para>
-<para>With these tools installed, it is possible to write Windows console
-or GUI applications that make use of significant parts of the POSIX API.
-As a result, it is possible to easily port many Unix programs without the need
-for extensive changes to the source code. This includes configuring
-and building most of the available GNU software (including the packages
-included with the Cygwin development tools themselves) as well as lots
-of BSD tools and packages (including OpenSSH). Even if
-the development tools are of little to no use to you, you may have
-interest in the many standard POSIX utilities provided with the package.
-They can be used from one of the provided Unix shells like bash, tcsh or zsh,
-as well as from the standard Windows command shell if you have to for some
-sad reason.
+<para>The Cygwin distribution contains thousands of packages from the Open
+Source world including most GNU tools, many BSD tools, an X server and a full
+set of X applications. If you're a developer you will find tools, headers
+and libraries allowing to write Windows console or GUI applications that make
+use of significant parts of the POSIX API. Cygwin allows easy porting of many
+Unix programs without the need for extensive changes to the source code. This
+includes configuring and building most of the available GNU or BSD software,
+including the packages included with the Cygwin distribution themselves.
+They can be used from one of the provided Unix shells like bash, tcsh or zsh.
</para>
</answer></qandaentry>
<question><para>What versions of Windows are supported?</para></question>
<answer>
-<para>Cygwin can be expected to run on all modern versions of Windows.
-This includes, as of the time of writing this, Windows XP SP3, Windows
-Server 2003, Windows Vista, Windows Server 2008, Windows 7, Windows
-Server 2012, Windows 8. The 32 bit version also runs in the WOW64 32 bit
-environment on released 64 bit versions of Windows
-(XP/2003/Vista/2008/7/2008 R2/8/2012).
-Since Cygwin is a community-supported free software project, patches to
-provide support for other versions would be thoughtfully considered.
-Paid support contracts or enhancements are available through Red Hat. For
-information about getting a Red Hat support contract, see
-<ulink url="http://cygwin.com/licensing.html" />.
+<para>Cygwin can be expected to run on all modern, released versions of Windows.
+State January 2015 this includes Windows XP SP3, Windows Server 2003/2003R2
+and all later versions of Windows up to Windows 8.1 and Windows Server 2012R2.
+The 32 bit version of Cygwin also runs in the WOW64 32 bit environment on
+released 64 bit versions of Windows (XP SP3 up to 8.1/2012R2), the 64 bit
+version of course only on 64 bit Windows.
</para>
<para>Keep in mind that Cygwin can only do as much as the underlying OS
supports. Because of this, Cygwin will behave differently, and
<question><para>Where can I get it?</para></question>
<answer>
-<para>The home page for the Cygwin project is <ulink url="http://cygwin.com/">http://cygwin.com/</ulink>.
+<para>The home page for the Cygwin project is
+<ulink url="https://cygwin.com/"/>.
There you should find everything you need for Cygwin, including links
for download and setup, a current list of mirror sites, a User's
-Guide, an API Reference, mailing lists and archives, and additional
-ported software.
+Guide, an API Reference, mailing lists and archives.
</para>
<para>You can find documentation for the individual GNU tools typically
as man pages or info pages as part of the Cygwin net distribution.
Additionally you can get the latest docs at
-<ulink url="http://www.gnu.org/manual/" />. (You should read GNU manuals from a
-local mirror. Check <ulink url="http://www.gnu.org/server/list-mirrors.html" />
+<ulink url="http://www.gnu.org/manual/"/>. (You should read GNU manuals from a
+local mirror. Check <ulink url="http://www.gnu.org/server/list-mirrors.html"/>
for a list of them.)
</para>
</answer></qandaentry>
<para>In particular, if you intend to port a proprietary (non-GPL'd)
application using Cygwin, you will need the proprietary-use license
for the Cygwin library. This is available for purchase from Red Hat;
-please visit <ulink url="http://cygwin.com/licensing.html" /> for more
+please visit <ulink url="https://cygwin.com/licensing.html"/> for more
information. All other questions should be sent to the public project
mailing list cygwin@cygwin.com.
</para>
<para>To find the version of the Cygwin DLL installed, you can use
<filename>uname</filename> as on Linux or <filename>cygcheck</filename>. Refer to each command's
-<literal>--help</literal> output and the <ulink url='http://cygwin.com/cygwin-ug-net/'>Cygwin User's Guide</ulink> for more information.
+<literal>--help</literal> output and the
+<ulink url='https://cygwin.com/cygwin-ug-net/'>Cygwin User's Guide</ulink>
+for more information.
</para>
<para>If you are looking for the version number for the whole Cygwin
release, there is none. Each package in the Cygwin release has its own
</para>
<para>So, how do you get the most up-to-date version of Cygwin? Easy. Just
download the Cygwin Setup program by following the instructions
-<ulink url='http://cygwin.com/install.html'>here</ulink>. The setup program will handle the task
-of updating the packages on your system to the latest version. For
-more information about using Cygwin's <filename>setup.exe</filename>, see
-<ulink url='http://cygwin.com/cygwin-ug-net/setup-net.html'>Setting Up Cygwin</ulink>
+<ulink url='https://cygwin.com/install.html'>here</ulink>.
+The setup program will handle the task of updating the packages on your system
+to the latest version. For more information about using Cygwin's
+<filename>setup.exe</filename>, see
+<ulink url='https://cygwin.com/cygwin-ug-net/setup-net.html'>Setting Up Cygwin</ulink>
in the Cygwin User's Guide.
</para></answer></qandaentry>
mailing lists rather than sending personal email.)</emphasis>
</para>
<para>
-Corinna Vinschen (corinna) is the current project lead. Corinna is a
-senior Red Hat engineer. Corinna is responsible for such important
-subsystems as security and networking and has recently added support to
-Cygwin for wide characters, increased path length, IPv6, advisory
-file locking and more.
+Corinna Vinschen is the current project lead. Corinna is a senior Red Hat
+engineer. Corinna is responsible for the Cygwin library and maintains a couple
+of packages, for instance OpenSSH, OpenSSL, and a lot more.
</para>
<para>
-Yaakov Selkowitz is the Cygwin/X coordinator. Jon Turney serves on the
-Cygwin/X team as a developer.
+Yaakov Selkowitz is another Red Hat engineer working on the Cygwin project.
+He's the guy behind the current build and packaging system and maintains by
+far the most packages in the Cygwin distribution.
+</para>
+<para>
+Jon Turney is developer and maintainer of the Cygwin X server and a couple
+of related packages.
</para>
<para>
The packages in the Net release are maintained by a large group of people;
-a complete list can be found <ulink url='http://cygwin.com/cygwin-pkg-maint'>here</ulink>.
-</para>
-<para>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
-email that is sent to the main mailing list. Making Net releases of the
-Win32 tools and helping people on the Net out is not our primary job
-function, so some email will have to go unanswered.
+a complete list can be found
+<ulink url='https://cygwin.com/cygwin-pkg-maint'>here</ulink>.
+</para>
+<para>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 email that is sent to the main mailing
+list. Making Net releases of the Win32 tools and helping people on the Net out
+is not our primary job function, so some email will have to go unanswered.
</para>
<para>Many thanks to everyone using the tools for their many contributions in
the form of advice, bug reports, and code fixes. Keep them coming!
Because many programs expect to be able to find the
<filename>/etc/passwd</filename> and
<filename>/etc/group</filename> files, we provide <ulink
-url="http://cygwin.com/cygwin-ug-net/using-utils.html">utilities</ulink>
+url="https://cygwin.com/cygwin-ug-net/using-utils.html">utilities</ulink>
that can be used to construct them from the user and group information
provided by the operating system.</para>
retry a few times automatically).</para></listitem>
<listitem><para>DLL injection by
-<ulink url="http://cygwin.com/faq/faq.html#faq.using.bloda">
+<ulink url="https://cygwin.com/faq/faq.html#faq.using.bloda">
BLODA</ulink>. Badly-behaved applications which
inject dlls into other processes often manage to clobber important
sections of the child's address space, leading to base address
<legalnotice id="legal">
-<para>Copyright © 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010, 2011, 2012, 2013, 2014 Red Hat, Inc.</para>
+<para>Copyright © 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010, 2011, 2012, 2013, 2014, 2015 Red Hat, Inc.</para>
<!--
Cygwin now comes with a real LSA authentication package. This must be
manually installed by a privileged user using the /bin/cyglsa-config
script. The advantages and disadvantages are noted in
-http://cygwin.com/ml/cygwin-developers/2006-11/msg00000.html
+https://cygwin.com/ml/cygwin-developers/2006-11/msg00000.html
</para></listitem>
<listitem><para>
packages. Add any other packages by clicking on the <literal>+</literal>
next to the Category name and selecting the package from the displayed
list. You may search for specfic tools by using the
-<ulink url="http://cygwin.com/packages/">Setup Package Search</ulink>
+<ulink url="https://cygwin.com/packages/">Setup Package Search</ulink>
at the Cygwin web site.
</para>
<para>
tools. If you intend to port a proprietary application using the Cygwin
library, you may want the Cygwin proprietary-use license.
For more information about the proprietary-use license, please go to
-<ulink url="http://www.redhat.com/services/custom/cygwin/">http://www.redhat.com/services/custom/cygwin/</ulink>.
+<ulink url="http://www.redhat.com/services/custom/cygwin/"/>.
Customers of the native Win32 GNUPro should feel free to submit bug
reports and ask questions through Red Hat channels. All other
questions should be sent to the project mailing list
<para>
The entire Cygwin toolset was available as a monolithic install. In
April 2000, the project announced a
-<ulink url="http://www.cygwin.com/ml/cygwin/2000-04/msg00269.html">
+<ulink url="https://www.cygwin.com/ml/cygwin/2000-04/msg00269.html">
New Cygwin Net Release</ulink> which provided the native non-Cygwin Win32 program
<command>setup.exe</command> to install and upgrade each package
separately. Since then, the Cygwin DLL and <command>setup.exe</command>
<sect1 id="internet-setup">
<title>Internet Setup</title>
<para>To install the Cygwin net release, go to <ulink
-url="http://cygwin.com/">http://cygwin.com/</ulink> and run either
-<ulink url="http://cygwin.com/setup-x86.exe">setup-x86.exe</ulink>
+url="https://cygwin.com/"/> and run either
+<ulink url="https://cygwin.com/setup-x86.exe">setup-x86.exe</ulink>
to install the 32 bit version of Cygwin, or
-<ulink url="http://cygwin.com/setup-x86_64.exe">setup-x86_64.exe</ulink>
+<ulink url="https://cygwin.com/setup-x86_64.exe">setup-x86_64.exe</ulink>
to install the 64 bit version of Cygwin. This will download a GUI
installer which can be run to download a complete cygwin installation
via the internet. Follow the instructions on each screen to install Cygwin.
For easier reading the installer is called <command>setup.exe</command>
throughout the following sections. This refers likewise to both
installer applications,
-<ulink url="http://cygwin.com/setup-x86.exe">setup-x86.exe</ulink>
+<ulink url="https://cygwin.com/setup-x86.exe">setup-x86.exe</ulink>
for 32 bit, as well as
-<ulink url="http://cygwin.com/setup-x86_64.exe">setup-x86_64.exe</ulink>
+<ulink url="https://cygwin.com/setup-x86_64.exe">setup-x86_64.exe</ulink>
for 64 bit. Apart from the target architecture they are the same thing.
</note>
</para>
for new users to understand while remaining flexible for the
experienced. The volunteer development team is constantly working
on <command>setup.exe</command>; before requesting a new feature,
-check the wishlist in the <ulink url="http://sourceware.org/cgi-bin/cvsweb.cgi/setup/README?cvsroot=cygwin-apps&rev=2">CVS <literal>README</literal>
+check the wishlist in the <ulink url="https://sourceware.org/cgi-bin/cvsweb.cgi/setup/README?cvsroot=cygwin-apps&rev=2">CVS <literal>README</literal>
</ulink>. It may already be present in the CVS version!
</para>
installed by simply clicking the <literal>Next</literal> button
at each page. The only exception to this is choosing a Cygwin mirror,
which you can choose by experimenting with those listed at
-<ulink url="http://cygwin.com/mirrors.html">
-http://cygwin.com/mirrors.html
-</ulink>. For more details about each of page of the
+<ulink url="https://cygwin.com/mirrors.html"/>. For more details about each of page of the
<command>setup.exe</command> installation, read on below.
Please note that this guide assumes that you have a basic understanding
of Unix (or a Unix-like OS). If you are new to Unix, you will also want
<para>
Since there is no way of knowing from where you will be downloading
Cygwin, you need to choose at least one mirror site. Cygwin mirrors
-are geographically distributed around the world; check the list at <ulink
-url="http://cygwin.com/mirrors.html">http://cygwin.com/mirrors.html</ulink>
+are geographically distributed around the world; check the list at
+<ulink url="https://cygwin.com/mirrors.html"/>
to find one near you. You can select multiple mirrors by holding down
<literal>CTRL</literal> and clicking on each one. If you have the URL of
an unlisted mirror (for example, if your organization has an internal Cygwin
small text file called <literal>setup.bz2</literal> that contains a list
of packages available from that site along with some basic information about
each package which <command>setup.exe</command> parses and uses to create the
-chooser window. For details about the format of this file, see
-the <ulink url="http://sourceware.org/cygwin-apps/setup.html">
-setup.exe homepage</ulink>.
+chooser window. For details about the format of this file, see the
+<ulink url="https://sourceware.org/cygwin-apps/setup.html">setup.exe homepage</ulink>.
</para>
<para>
The chooser is the most complex part of <command>setup.exe</command>.
script is run separately, several windows may pop up. If you are
interested in what is being done, see the Cygwin Package Contributor's
Guide at <ulink
-url="http://cygwin.com/setup.html">http://cygwin.com/setup.html</ulink>
+url="https://cygwin.com/setup.html"/>
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.
running setup, you can check the <command>setup.exe</command> log file
at <literal>/var/log/setup.log.full</literal>. Make a backup of this
file before running <command>setup.exe</command> again, and follow the
-steps for <ulink url="http://cygwin.com/problems.html">Reporting
+steps for <ulink url="https://cygwin.com/problems.html">Reporting
Problems with Cygwin</ulink>.
</para>
</sect2>
of packages. This feature requires an active internet connection, since
it must query the <literal>cygwin.com</literal> web site. In fact, it is
equivalent to the search that is available on the <ulink
- url="http://cygwin.com/packages/">Cygwin package listing</ulink>
+ url="https://cygwin.com/packages/">Cygwin package listing</ulink>
page.</para>
<para>For example, perhaps you are getting an error because you are missing
git://sourceware.org / newlib-cygwin.git / commitdiff