[ANNOUNCEMENT] Updated: w32api-{headers,runtime}-5.0.4-1 (x86/x86_64)

[JonY]

Now released for both 32bit and 64bit Cygwin:

w32api-headers-5.0.4-1
w32api-runtime-5.0.4-1

Based on mingw-w64-v5.0.4.

  *** CYGWIN-ANNOUNCE UNSUBSCRIBE INFO ***

If you want to unsubscribe from the cygwin-announce mailing list,
look at the "List-Unsubscribe: " tag in the email header of this
message. Send email to the address specified there. It will be in the
format:

cygwin-announce-unsubscribe-you=yourdomain@cygwin.com

If you need more information on unsubscribing, start reading here:

http://sourceware.org/lists.html#unsubscribe-simple

Please read *all* of the information on unsubscribing that
is available starting at this URL.



signature.asc
Description: OpenPGP digital signature

Updated: w32api-{headers,runtime}-5.0.4-1 (x86/x86_64)

[JonY]

Now released for both 32bit and 64bit Cygwin:

w32api-headers-5.0.4-1
w32api-runtime-5.0.4-1

Based on mingw-w64-v5.0.4.

  *** CYGWIN-ANNOUNCE UNSUBSCRIBE INFO ***

If you want to unsubscribe from the cygwin-announce mailing list,
look at the "List-Unsubscribe: " tag in the email header of this
message. Send email to the address specified there. It will be in the
format:

cygwin-announce-unsubscribe-you=yourdomain@cygwin.com

If you need more information on unsubscribing, start reading here:

http://sourceware.org/lists.html#unsubscribe-simple

Please read *all* of the information on unsubscribing that
is available starting at this URL.



signature.asc
Description: OpenPGP digital signature

Re: Windows upgrade

[Andrey Repin]

Greetings, Achim Gratz!

>> I have a 32 bit cygwin installation of 8 years of age in an amd64 PC
>> with 2 GB of RAM with Windows 10. So far it's been so good. I never
>> had the need to use a 64 bit Windows, but recently 64 bit has become
>> mainstream and I also started having low memory issues, so I upgraded
>> to 4 GB of RAM. The thing is 32 bit Windows has issues with the whole
>> 4 GB of RAM therefore I have quite less available, so I decided I will
>> be switching to 64 bit Windows 10 via a clean install (yuk!) when I am
>> able.

> Well, for an installation that old it would probably be quite helpful if
> you did a clean fresh install.  A 32bit Windows can deal just fine with
> 4GB of memory (not so much with larger memory), you can make about 3GB
> of that available to user processes with a boot option (at the expense
> of memory reserved for the kernel space).

3.65GB in my experience is the best you can manage with 32-bit Windows.


-- 
With best regards,
Andrey Repin
Friday, June 15, 2018 4:46:46

Sorry for my terrible english...


--
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

License compliance when shipping cygwin binaries

[Stefan Baur]

Hi List,

I would like to bundle and ship an executable found in Cygwin and the
DLLs it requires. The files in question are:

chgrp.exe
cyggcc_s-1.dll
cygiconv-2.dll
cygintl-8.dll
cygwin1.dll

For which of these files do I have to ship the source code to comply
with the license, and what's the easiest way to get hold of it myself?
(i.e. do I have to do a full cygwin install and select "source" on
$PACKAGE, then pick the source files from there, or is there a git repo
or similar that I could clone?)

The way I understand , I don't need
the source for cygwin1.dll (please correct me if I'm wrong).  But what
about the other DLLs, and what about chgrp.exe itself?
I believe chgrp is under GPL, but I'm at loss whether there is a special
"cygwin chgrp" repo, or whether the regular chgrp source
(, I assume?) is
used, and how to fetch the source for exactly the binary I intend to ship.

Could anyone please enlighten me?

Kind Regards,
Stefan Baur

-- 
BAUR-ITCS UG (haftungsbeschränkt)
Geschäftsführer: Stefan Baur
Eichenäckerweg 10, 89081 Ulm | Registergericht Ulm, HRB 724364
Fon/Fax 0731 40 34 66-36/-35 | USt-IdNr.: DE268653243

--
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: Problematic interpretion of paths starting with double slashes

[Brian Inglis]

On 2018-06-13 02:34, Sven Eden wrote:
> However, from my two questions, one was answered, and I can
> figure out the other just fine by myself.
> Q: Can the handling of // be extended to check for / if the
> first fails?
> A: Yes
> Unanswered: Is the relevant stuff to be found in winsup/cygwin?

Look at:
https://cygwin.com/git/gitweb.cgi?p=newlib-cygwin.git;a=blob_plain;f=winsup/cygwin/fhandler_netdrive.cc;hb=HEAD

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

--
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

[ANNOUNCEMENT] Updated: csih-0.9.10-1

[Corinna Vinschen]

I just updated the csih service installation helper package to 0.9.10-1.

Fixes:

Achim Gratz (1):
  Fix creation of privileged user in /etc/passwd

J.H. van de Water (2):
  Amend prologue of csih_use_file_etc
  Move call of mkpasswd UPwards in csih_create_privileged_user

Shaddy Baddah (1):
  ssh-host-config: patch fix debug option + broken for me on Vista (non-doma
in)

Takashi Yano (1):
  Setting privileged rights to cyg_server fails on Windows 7.


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

Updated: csih-0.9.10-1

[Corinna Vinschen]

I just updated the csih service installation helper package to 0.9.10-1.

Fixes:

Achim Gratz (1):
  Fix creation of privileged user in /etc/passwd

J.H. van de Water (2):
  Amend prologue of csih_use_file_etc
  Move call of mkpasswd UPwards in csih_create_privileged_user

Shaddy Baddah (1):
  ssh-host-config: patch fix debug option + broken for me on Vista (non-doma
in)

Takashi Yano (1):
  Setting privileged rights to cyg_server fails on Windows 7.


Have fun,
Corinna

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

Re: Multiple attempts at opening same pipe for writing fail

[João Eiras]

On 13 June 2018 at 17:44, Takashi Yano  wrote:
> Hi João,
>
> Is this related to https://cygwin.com/ml/cygwin/2017-03/msg00188.html ?
>

Hi.

That seems quite likely.

In my test case, I do open+close+open and the second open fails with
errno.ENXIO.

If I skip the close and do open+open I get the same error.

Next on my TODO list I'll make another testcase just using the Win32
API and see if that is a Windows issue.

--
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: [bug: csih] Setting privileged rights to cyg_server fails on Windows 7.

[Corinna Vinschen]

On Jun 14 19:29, Takashi Yano wrote:
> Hi Corinna,
> 
> On Thu, 14 Jun 2018 11:16:42 +0200
> Corinna Vinschen wrote:
> > Thank you, too.  I pushed the patch and will release a new csih package
> > soon.
> 
> I read the discussion in the past pointed by Shaddy.
> 
> On Thu, 14 Jun 2018 11:29:40 +1000
> Shaddy Baddah wrote:
> > https://cygwin.com/ml/cygwin/2017-01/msg00233.html
> > https://cygwin.com/ml/cygwin/2017-01/msg00283.html
> 
> My understanding is that if "Run as administrator" is used,
> LOGONSERVER is not set even if the machine is on a domain.
> 
> Therefore it is hard to judge if the machine is on a domain
> or not when LOGONSERVER is not set.

Actually, I just tested this on a domain member machine.

1) I'm logged in with an administrative domain account.  If I open
   a shell with "run as administrator", LOGONSERVER is set correctly.

2) I'm logged in with a non-admin domain account.  If I open a
   shell with "run as administrator", enter credentials for the
   above domain admin account, LOGONSERVER is set correctly.

3) I'm logged in with a non-admin domain account.  If I open a
   shell with "run as administrator", enter credentials for the
   domain's "Administrator" account, LOGONSERVER is *not* set.

4) I'm logged in with a non-admin domain account.  If I open a
   shell with "run as administrator", enter credentials for the
   local machine's "Administrator" account, LOGONSERVER is *not*
   set.

I think this is a bug, but looks like we have to live with that.
Alternatively we could check for $USERDOMAIN, perhaps.  This seems
to be set correctly in all scenarios.


Corinna

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


signature.asc
Description: PGP signature

Re: [bug: csih] Setting privileged rights to cyg_server fails on Windows 7.

[Takashi Yano]

Hi Corinna,

On Thu, 14 Jun 2018 11:16:42 +0200
Corinna Vinschen wrote:
> Thank you, too.  I pushed the patch and will release a new csih package
> soon.

I read the discussion in the past pointed by Shaddy.

On Thu, 14 Jun 2018 11:29:40 +1000
Shaddy Baddah wrote:
> https://cygwin.com/ml/cygwin/2017-01/msg00233.html
> https://cygwin.com/ml/cygwin/2017-01/msg00283.html

My understanding is that if "Run as administrator" is used,
LOGONSERVER is not set even if the machine is on a domain.

Therefore it is hard to judge if the machine is on a domain
or not when LOGONSERVER is not set.

Is this right?

Do you have any good idea against this difficulty?

-- 
Takashi Yano 

--
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: [bug: csih] Setting privileged rights to cyg_server fails on Windows 7.

[Corinna Vinschen]

On Jun 14 06:22, Takashi Yano wrote:
> Hi Corinna,
> 
> On Wed, 13 Jun 2018 20:14:07 +0200
> Corinna Vinschen wrote:
> > There's something fishy in your environment.  The variable LOGONSERVER
> > is always set in Windows NT, at least since NT4.  For standalone
> > machines LOGONSERVER is set to "\\".  You should really
> > try to find out why LOGONSERVER isn't set for you.
> 
> With your advice, I have found the cause. I usually logon as a user
> who does not have administrator rights for security reason. This user
> belong to only "Users" group. When I need administrator rights,
> I use "Run as administrator" menu to switch to another user who
> has administrator rights. In this case, LOGONSERVER is not set.
> 
> If I logoff from the first user account and logon as the second user,
> LOGONSERVER is set.
> 
> Moreover, the behaviour above seems to be true not only on Windows 7,
> but also on Windows 10.
> 
> I have confirmed that iu-config successfully finishes without the
> patch I proposed, if I logon as an administrative user instead of
> using "Run as administrator".
> 
> Thank you very much.

Thank you, too.  I pushed the patch and will release a new csih package
soon.


Corinna

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


signature.asc
Description: PGP signature