[ANNOUNCEMENT] TEST RELEASE: Cygwin 2.0.0-1

[ANNOUNCEMENT] TEST RELEASE: Cygwin 2.0.0-1

[Corinna Vinschen]

Hi Cygwin friends and users,


as outlined in https://cygwin.com/ml/cygwin/2015-04/msg00171.html I've
now created a TEST release of Cygwin which can be installed via
setup-x86{_64}.exe.

The version number is 2.0.0-0.1.  Yes, we're going full Torvalds
with the release numbers and bump them to 2.0.  In future,
bugfix releases will bump the last number, new feature releases
will bump the middle number.

  Bugfix?  2.0.1, 2.0.2, ...
  New features?  2.1, 2.2, ...

The important change in this release is the POSIX permission handling
change, a rewrite of the underlying routines reading and creating
Windows ACLs following POSIX permission rules and POSIX ACL creating
rules per POSIX 1003.1e draft 17, as on Linux.

For a description of POSIX ACLs, see http://linux.die.net/man/5/acl


All changes in this release so far:
===================================

- New, unified implementation of POSIX permission and ACL handling.  The
  new ACLs now store the POSIX ACL MASK/CLASS_OBJ permission mask, and
  they allow to inherit the S_ISGID bit.  ACL inheritance now really
  works as desired, in a limited, but theoretically equivalent fashion
  even for non-Cygwin processes.

  To accommodate Windows default ACLs, the new code ignores SYSTEM and
  Administrators group permissions when computing the MASK/CLASS_OBJ
  permission mask on old ACLs, and it doesn't deny access to SYSTEM and
  Administrators group based on the value of MASK/CLASS_OBJ when
  creating the new ACLs.
  
  The new code now handles the S_ISGID bit on directories as on Linux:
  Setting S_ISGID on a directory causes new files and subdirs created
  within to inherit its group, rather than the primary group of the user
  who created the file.  This only works for files and directories
  created by Cygwin processes.
  
- 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> 

- 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

  NOTE: This change introduces a not yet addressed regression.
  Native Windows tools generating output with Unix LF instead of
  Windows CRLF line endings will not get OPOST handling.  This
  prominently affects icacls.

- 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


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

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Cygwin version numbers [Was: [ANNOUNCEMENT] TEST RELEASE: Cygwin 2.0.0-1]

[Adam Dinwoodie]

On 11/04/2015 11:35, Corinna Vinschen wrote:
> The version number is  2.0.0-0.1.  Yes, we're going full Torvalds with
 > the release numbers and bump them to 2.0.  In future, bugfix releases
 > will bump the last number, new feature releases will bump the middle
 > number.
 >
 > Bugfix?  2.0.1, 2.0.2, ...
 > New features?  2.1, 2.2, ...

Does this mean the version number distinction between the GPL and 
propriety versions of the Cygwin DLL are disappearing? IIRC it's 
currently the case that version 1.<even> indicates a closed-source 
license version, and 1.<odd> indicates a GPL-licensed version.

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Re: Cygwin version numbers [Was: [ANNOUNCEMENT] TEST RELEASE: Cygwin 2.0.0-1]

[Corinna Vinschen]

[-- Attachment #1: Type: text/plain, Size: 1359 bytes --]

On Apr 12 16:15, Adam Dinwoodie wrote:
> On 11/04/2015 11:35, Corinna Vinschen wrote:
> >The version number is  2.0.0-0.1.  Yes, we're going full Torvalds with
> > the release numbers and bump them to 2.0.  In future, bugfix releases
> > will bump the last number, new feature releases will bump the middle
> > number.
> >
> > Bugfix?  2.0.1, 2.0.2, ...
> > New features?  2.1, 2.2, ...
> 
> Does this mean the version number distinction between the GPL and propriety
> versions of the Cygwin DLL are disappearing?

There is no propriety version of the Cygwin DLL.  The distinction (the
idea being about 15 years old) was only for the sake of being able to
identify the upstream from the supported version.  The supported version
will just get an own subversion and a marker, along the lines of
"2.0.5rh".

> IIRC it's currently the case
> that version 1.<even> indicates a closed-source license version, and 1.<odd>
> indicates a GPL-licensed version.

There are no Cygwin versions for which the source code isn't available,
While, technically, a third party can purchase a GPL buyout for their
own, proprietary product, the Cygwin sources are always freely available.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]

Re: [ANNOUNCEMENT] TEST RELEASE: Cygwin 2.0.0-1

[Houder]

> It's what we haxxers call "a bug".  I made a typo in another function,
> copy-pasted the code over to the chmod function, fixed it in the
> original function and then forgot to fix it in chmod.

[snip]

> I just uploaded a new test release 2.0.0-0.2.  It's supposed to fix
> this bug.  Give it a bit of time to hit the mirrors.

... wait ... more waiting ...

Confirmed. This bug has gone. (you knew where to look for it, did you
not? :-)

Many thanks for all your hard work!

Regards,

Henri


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Re: [ANNOUNCEMENT] TEST RELEASE: Cygwin 2.0.0-1

[Achim Gratz]

Houder writes:
> :-) ... I understand ... my problem is, that I am usually NOT subscribed
> to the (any) list, and that I process all my e-mail using webmail, and as
> far as I aware of, it does not provide the "In-Reply-To" feature.

You can post via Gmane rather than the webmailer.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

Wavetables for the Waldorf Blofeld:
http://Synth.Stromeko.net/Downloads.html#BlofeldUserWavetables

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Re: [ANNOUNCEMENT] TEST RELEASE: Cygwin 2.0.0-1

[Houder]

>> Reference: https://cygwin.com/ml/cygwin/2015-04/msg00201.html
>>  - [ANNOUNCEMENT] TEST RELEASE: Cygwin 2.0.0-1
>
> I really appreciate bug reports, but, please, try to keep the threading
> intact.  Please reply to mails rather than creating new threads which
> have no connection to the original threads.  Or if so, at least set the
> "In-Reply-To:" Header field correctly.

:-) ... I understand ... my problem is, that I am usually NOT subscribed
to the (any) list, and that I process all my e-mail using webmail, and as
far as I aware of, it does not provide the "In-Reply-To" feature.

As a result of that, my "first" e-mail will be "out-of-line". Sigh.

[snip]

> Btw., the output from SetACL isn't that helpful, because it doesn't
> add information to what icacls already delivers.  What I'd be more
> interested in is the output of our own getfacl in conjunction with
> icacls.  It allows me to see the POSIX ACL the internal ACL reading
> routine created from the Windows ACL.

:-) Will do!

Regards,

Henri


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Re: [ANNOUNCEMENT] TEST RELEASE: Cygwin 2.0.0-1

[Corinna Vinschen]

[-- Attachment #1: Type: text/plain, Size: 1525 bytes --]

Hi Henri,

On Apr 11 15:25, Houder wrote:
> Hi Corinna,
> 
> Reference: https://cygwin.com/ml/cygwin/2015-04/msg00201.html
>  - [ANNOUNCEMENT] TEST RELEASE: Cygwin 2.0.0-1

I really appreciate bug reports, but, please, try to keep the threading
intact.  Please reply to mails rather than creating new threads which
have no connection to the original threads.  Or if so, at least set the
"In-Reply-To:" Header field correctly.

By additionally changing the subject you're making searching the
archives unnecessarily hard for others.  I changed the subject back.

> Sorry, Corinna, but I have to ask: will this be the correct behaviour of Cygwin
> from now on? ... because I am very much surprised ...

It's what we haxxers call "a bug".  I made a typo in another function,
copy-pasted the code over to the chmod function, fixed it in the
original function and then forgot to fix it in chmod.

Btw., the output from SetACL isn't that helpful, because it doesn't
add information to what icacls already delivers.  What I'd be more
interested in is the output of our own getfacl in conjunction with
icacls.  It allows me to see the POSIX ACL the internal ACL reading
routine created from the Windows ACL.

I just uploaded a new test release 2.0.0-0.2.  It's supposed to fix
this bug.  Give it a bit of time to hit the mirrors.


Thanks,
Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]