From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: [ANNOUNCEMENT] cygwin 3.4.0-1
Date: Sun, 04 Dec 2022 14:58:56 +0100 [thread overview]
Message-ID: <announce.20221204145856.2386232-1-corinna-cygwin@cygwin.com> (raw)
The following packages have been uploaded to the Cygwin distribution:
* cygwin-3.4.0-1
* cygwin-devel-3.4.0-1
* cygwin-doc-3.4.0-1
==========================================================================
IMPORTANT DEPRECATION NOTES
==========================================================================
- Cygwin 3.4 is the FIRST major version dropping support for
- 32 bit Windows including WOW64 on 64 bit Windows.
- Windows Vista
- Windows Server 2008
- Cygwin 3.4 is the LAST major version supporting
- Windows 7
- Windows Server 2008 R2
- Windows 8
- Windows Server 2012
- Cygwin 3.5, which will probably be release at some point in late 2023,
will run on
- Windows 8.1
- Windows 10
- Windows 11
- Windows Server 2012 R2
- Windows Server 2016
- Windows Server 2019
- Windows Server 2022
There are no plans to deprecate support for 64 bit systems starting with
Windows 8.1 / Windows Server 2012 R2 any time soon.
==========================================================================
What's new:
-----------
- Drop support for Vista and Server 2008.
- Drop support for 32 bit Windows and WOW64.
- Allow to run with full ASLR enabled and enable on Cygwin DLL by default.
- Remove any special handling for the .com filename suffix. It has to
be used always explicitely.
- Add code to handle setrlimit(RLIMIT_AS).
- Add code to handle signal masks in /proc/<PID>/status.
- Handle UDP_SEGMENT and UDP_GRO socket options.
What changed:
-------------
- The CYGWIN=pipe_byte option is now set by default, so that pipes are
opened in byte mode rather than message mode.
Addresses: https://cygwin.com/pipermail/cygwin/2021-March/247987.html
- The stdio input functions no longer try again to read after EOF.
This aligns Cygwin behavior to that of Linux.
Addresses: https://cygwin.com/pipermail/cygwin/2022-June/251672.html
- Treat an empty path (empty element in PATH or PATH is absent) as
the current directory as Linux does.
Addresses: https://cygwin.com/pipermail/cygwin/2022-June/251730.html
- The default values of FD_SETSIZE and NOFILE are now 1024 and 3200,
respectively.
Addresses: https://cygwin.com/pipermail/cygwin/2022-July/251839.html
Bug Fixes
---------
- Don't error out if getfacl(1) is called on a socket file.
Partially addresses: https://cygwin.com/pipermail/cygwin/2022-July/251768.html
- Make serial ioctl(TIOCMBIS/TIOCMBIC) work on USB CDC devices.
Addresses: https://cygwin.com/pipermail/cygwin/2022-November/252443.html
- Fix a SEGV when running a process with changed primary group.
Addresses: https://cygwin.com/pipermail/cygwin-apps/2022-September/042245.html
- Fix primary group handling when running a process tree containing
non-Cygwin processes and with changed primary group. The Cygwin child
process of a non-Cygwin process will have reverted its primary group
to the default primary group erroneously.
Addresses: https://cygwin.com/pipermail/cygwin-apps/2022-September/042245.html
- Fix parsing Windows command line when non-ASCII chars are in the input.
Addresses: https://cygwin.com/pipermail/cygwin/2022-November/252481.html
reply other threads:[~2022-12-04 14:12 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=announce.20221204145856.2386232-1-corinna-cygwin@cygwin.com \
--to=corinna-cygwin@cygwin.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).