From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin-announce@cygwin.com
Subject: TEST RELEASE: Cygwin 2.0.0-0.8
Date: Fri, 24 Apr 2015 10:25:00 -0000 [thread overview]
Message-ID: <20150424081109.GA7768@calimero.vinschen.de> (raw)
Hi Cygwin friends and users,
New 2.0.0-0.8 test release. This release got ripped out all the new
POSIX ACL handling code due to a design flaw which needs much more work.
========================================================================
Note
Those of you testing the previous versions should make sure to duplicate
files they created with those test versions and remove the old files.
I can't guarantee that the ACLs created by these test versions won't
collide with ACLs created by future versions of Cygwin. Sorry!
========================================================================
Therefore, the upcoming Cygwin 2.0.0 release will be basically a bug fix
release only. I'm planning to release it next week.
What's new:
-----------
- basename(3) now comes in two flavors, POSIX and GNU. The POSIX version is
the default. You get the GNU version after
#define _GNU_SOURCE
#include <string.h>
What changed:
-------------
- The maximum number of PTYs has been raised from 64 to 128.
Bug Fixes
---------
- Fix potential hang in pseudo ttys when generating ECHO output while the slave
is flooding the pty with output.
Addresses: https://cygwin.com/ml/cygwin/2015-03/msg00019.html
- Fix potential premature SIGHUP in pty code.
Addresses: https://cygwin.com/ml/cygwin/2015-03/msg00070.html
- Fix a name change from symlink to target name in calls to execvp, system, etc.
Addresses: https://cygwin.com/ml/cygwin/2015-03/msg00270.html
- Fix internal error in pty -ONLCR handling. Fix timing bug in pty OPOST
handling.
Addresses: https://cygwin.com/ml/cygwin/2015-02/msg00929.html
- Avoid creating passwd and group records from fully qualified Windows
account names (domain\name, name@domain).
Addresses: https://cygwin.com/ml/cygwin/2015-03/msg00528.html
- Avoid potential crash at startup or in getgroups(2).
Addresses: https://cygwin.com/ml/cygwin/2015-04/msg00010.html
- Fix UTF-16 surrogate handling in wctomb and friends.
Addresses: https://cygwin.com/ml/cygwin/2015-03/msg00452.html
- Fix shmget usage of size parameter for already existing segments.
Addresses: https://cygwin.com/ml/cygwin/2015-04/msg00105.html
- Fix how in-use files on virtual drives created via subst are moved to
the recycler in unlink(2).
Addresses: https://cygwin.com/ml/cygwin/2015-04/msg00527.html
- Fix how in-use files on Samba drives are renamed in unlink(2).
To install 32-bit Cygwin use https://cygwin.com/setup-x86.exe
To install 64 bit Cygwin use https://cygwin.com/setup-x86_64.exe
If you're already running a 32 bit version of Cygwin on 64 bit Windows
machines, you can continue to do so. If you're planning a new install
of Cygwin on a 64 bit Windows machine, consider to use the new 64 bit
Cygwin version, unless you need certain packages not yet available in
the 64 bit release.
Have fun,
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Red Hat
reply other threads:[~2015-04-24 10:25 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=20150424081109.GA7768@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--cc=cygwin-announce@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).