Re: [ANNOUNCEMENT] Cygwin 3.0.0-1

On Feb 17 20:07, Andrey Repin wrote: > Greetings, Corinna Vinschen! > > > On Feb 17 18:28, Andrey Repin wrote: > >> Greetings, Corinna Vinschen! > >> > >> > I uploaded a new Cygwin release 3.0.0-1. > >> > >> The redirection issue I mentioned for 3.0-0.9 is still happens. > >> And I see the STC d

Re: [ANNOUNCEMENT] TEST: Cygwin 3.0.0-0.2

On Feb 17 10:48, Brian Inglis wrote: > On 2019-01-30 13:29, Corinna Vinschen wrote: > > We also have to make sure we're not breaking scripts, especially > > autoconf etc., so on forth thought, I'll rather stick to the current > > format. > > I have zero problems with your previous considerations a

Re: Windows to Cygwin username mapping: Domain before local account when duplicate name?

On Feb 16 18:40, Corinna Vinschen wrote: > On Feb 16 09:15, Brian Inglis wrote: > > On 2019-02-16 08:33, Corinna Vinschen wrote: > > > On Feb 16 08:09, Brian Inglis wrote: > > >> On 2019-02-16 02:45, Corinna Vinschen wrote: > > >>> On Feb 15 14:51, Bill Stewart wrote: > > On Fri, Feb 15, 2019

Re: antrun versus wsl versus cygwin

Am 17.02.2019 um 15:14 schrieb LRN: > On 17.02.2019 14:11, Franz Fehringer wrote: >> Hi all (half off topic), >> >> I have installed (on a Windows 10 1809 system) both Cygwin and WSL (only >> the Windows component, no real Linux distribution yet). >> This scenario gives me a strange problem with an

Re: antrun versus wsl versus cygwin

Am 18.02.2019 um 00:00 schrieb Andrey Repin: > Greetings, Franz Fehringer! > >> Am 17.02.2019 um 20:09 schrieb Csaba Ráduly: >>> On 17/02/2019 12:11, Franz Fehringer wrote: Hi all (half off topic), I have installed (on a Windows 10 1809 system) both Cygwin and WSL (only the Win

Re: textmode for stdout, what is "correct" now?

On 2/16/19 6:43 PM, Corinna Vinschen wrote: > On Feb 16 18:13, Michael Haubenwallner wrote: >> On 2/16/19 10:38 AM, Corinna Vinschen wrote: >>> setmode(fd, O_BINARY) works on Cygwin. >> >> Well... true. >> >> What I'm trying to say is that restoring the *default* mode is currently >> broken, becau

Re: portable use of dos2unix WAS: Re: textmode for stdout, what is "correct" now?

On 2/15/19 10:00 PM, Corinna Vinschen wrote: > On Feb 15 20:33, Michael Haubenwallner wrote: >> On 2/15/19 7:35 PM, Andrey Repin wrote: >>> I have a different question though. The commands you presented in the OP >>> look like you aren't using Cygwin-suppied OpenSSL binary. >> >> This is true: The

Re: [ANNOUNCEMENT] Cygwin 3.0.0-1

On Feb 18 09:28, Corinna Vinschen wrote: > On Feb 17 20:07, Andrey Repin wrote: > > Greetings, Corinna Vinschen! > > > > > On Feb 17 18:28, Andrey Repin wrote: > > >> Greetings, Corinna Vinschen! > > >> > > >> > I uploaded a new Cygwin release 3.0.0-1. > > >> > > >> The redirection issue I menti

Re: fixup_mmaps_after_fork failure with cygwin-3.0.0

On Feb 17 17:39, Corinna Vinschen wrote: > On Feb 17 16:34, Ken Brown wrote: > > On 2/17/2019 10:07 AM, Corinna Vinschen wrote: > > > On Feb 17 14:56, Ken Brown wrote: > > >> On 2/17/2019 4:13 AM, Corinna Vinschen wrote: > > If I may place a bet, please try to replace > > PROCESS_QUERY_LI

Re: portable use of dos2unix WAS: Re: textmode for stdout, what is "correct" now?

On Feb 18 11:01, Michael Haubenwallner wrote: > On 2/15/19 10:00 PM, Corinna Vinschen wrote: > > On Feb 15 20:33, Michael Haubenwallner wrote: > >> On 2/15/19 7:35 PM, Andrey Repin wrote: > >>> I have a different question though. The commands you presented in the OP > >>> look like you aren't using

Re: textmode for stdout, what is "correct" now?

On Feb 18 10:40, Michael Haubenwallner wrote: > On 2/16/19 6:43 PM, Corinna Vinschen wrote: > > I really miss the problem you're trying to solve here. Why should an > > application setting O_BINARY explicitely revert this decision on the > > same file descriptor? That doesn't make sense. > > Wel

Re: antrun versus wsl versus cygwin

On Mon, 18 Feb 2019 10:25:42, Franz Fehringer wrote: in the antrun block gives C:\Projekte\dev\bin\gmake41;\ C:\Tools\VisualStudio\2017\VC\Tools\MSVC\14.16.27023\bin\HostX64\x64;\ C:\Tools\VisualStudio\2017\VC\VCPackages;\ C:\Tools\VisualStudio\2017\MSBuild\15.0\bin\Roslyn;\ C:\Tools\VisualStud

Problem with sshd on W7 with 32bit cygwin 3.0

After upgrading to cygwin 3.0.0 (32bit version) on W7 64bit, it is not possible to connect using ssh. The returned error is something like "Connection closed by x.x.x.x port 22". I also tried the 2019-02-18 snapshot without success. However, simply downgrading to 2.11.2 fixes the issue. This issu

Re: [ANNOUNCEMENT] Cygwin 3.0.0-1

Greetings, Corinna Vinschen! >> > >> TYPE "%SystemRoot%\win.ini" | diff -u "%SystemRoot%\win.ini" - >> > >> > > I'm baffled. diff calls fstat on descriptor 0. fstat returns >> > > with st_mode set to S_IFIFO | S_IRUSR, so it *knows* descriptor >> > > 0 is a pipe and thus not seekable. Neverthe

Re: [ANNOUNCEMENT] Cygwin 3.0.0-1

On Mon, 18 Feb 2019 14:01:40, Andrey Repin wrote: [snip] > The snapshot only contains a lonely cygwin1.dll. You have to download the tar(.xz) file ... See faq for further details. Henri -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Do

Re: textmode for stdout, what is "correct" now?

On 2/18/19 11:26 AM, Corinna Vinschen wrote: > On Feb 18 10:40, Michael Haubenwallner wrote: >> On 2/16/19 6:43 PM, Corinna Vinschen wrote: >>> I really miss the problem you're trying to solve here. Why should an >>> application setting O_BINARY explicitely revert this decision on the >>> same fil

Re: antrun versus wsl versus cygwin

Am 18.02.2019 um 11:42 schrieb Houder: > On Mon, 18 Feb 2019 10:25:42, Franz Fehringer wrote: > > in the antrun block gives > > C:\Projekte\dev\bin\gmake41;\ > C:\Tools\VisualStudio\2017\VC\Tools\MSVC\14.16.27023\bin\HostX64\x64;\ > C:\Tools\VisualStudio\2017\VC\VCPackages;\ > C:\Tools\VisualSt

Re: portable use of dos2unix WAS: Re: textmode for stdout, what is "correct" now?

On Mon, Feb 18, 2019 at 5:01 AM Michael Haubenwallner wrote: > > On 2/15/19 10:00 PM, Corinna Vinschen wrote: > > On Feb 15 20:33, Michael Haubenwallner wrote: > >> On 2/15/19 7:35 PM, Andrey Repin wrote: > >>> I have a different question though. The commands you presented in the OP > >>> look lik

Re: antrun versus wsl versus cygwin

On Mon, 18 Feb 2019 13:15:02, Franz Fehringer wrote: > Am 18.02.2019 um 11:42 schrieb Houder: [snip] > > Now show us the output of an antrun script, where the executable > > is C:\Tools\Cygwin\bin\which and its argument: bash > > > > Henri > > > > > > > > > > > > > gives > > [exec

Re: textmode for stdout, what is "correct" now?

On Feb 18 12:47, Michael Haubenwallner wrote: > On 2/18/19 11:26 AM, Corinna Vinschen wrote: > > On Feb 18 10:40, Michael Haubenwallner wrote: > >> On 2/16/19 6:43 PM, Corinna Vinschen wrote: > >>> I really miss the problem you're trying to solve here. Why should an > >>> application setting O_BIN

Re: antrun versus wsl versus cygwin

Am 18.02.2019 um 14:07 schrieb Houder: > On Mon, 18 Feb 2019 13:15:02, Franz Fehringer wrote: >> Am 18.02.2019 um 11:42 schrieb Houder: > [snip] > >>> Now show us the output of an antrun script, where the executable >>> is C:\Tools\Cygwin\bin\which and its argument: bash >>> >>> Henri >>> >>> >>

Re: Problem with sshd on W7 with 32bit cygwin 3.0

On Feb 18 11:58, Enrico Forestieri wrote: > After upgrading to cygwin 3.0.0 (32bit version) on W7 64bit, it is > not possible to connect using ssh. The returned error is something > like "Connection closed by x.x.x.x port 22". > > I also tried the 2019-02-18 snapshot without success. > However, si

Re: fixup_mmaps_after_fork failure with cygwin-3.0.0

On 2/18/2019 5:10 AM, Corinna Vinschen wrote: > On Feb 17 17:39, Corinna Vinschen wrote: >> On Feb 17 16:34, Ken Brown wrote: >>> On 2/17/2019 10:07 AM, Corinna Vinschen wrote: On Feb 17 14:56, Ken Brown wrote: > On 2/17/2019 4:13 AM, Corinna Vinschen wrote: >>> If I may place a bet, p

Re: fixup_mmaps_after_fork failure with cygwin-3.0.0

On Feb 18 14:28, Ken Brown wrote: > On 2/18/2019 5:10 AM, Corinna Vinschen wrote: > PROCESS_VM_OPERATION has to be specified additionally, not replacing > PROCESS_QUERY_{LIMITED_}INFORMATION. Sorry if that wasn't clear. > >>> > >>> Success: Simply adding PROCESS_VM_OPERATION to the exist

Re: [ANNOUNCEMENT] Cygwin 3.0.0-1

On Feb 18 14:01, Andrey Repin wrote: > Greetings, Corinna Vinschen! > > >> > >> TYPE "%SystemRoot%\win.ini" | diff -u "%SystemRoot%\win.ini" - > >> > > >> > > I'm baffled. diff calls fstat on descriptor 0. fstat returns > >> > > with st_mode set to S_IFIFO | S_IRUSR, so it *knows* descriptor >

Re: textmode for stdout, what is "correct" now?

On 2/18/19 2:15 PM, Corinna Vinschen wrote: > On Feb 18 12:47, Michael Haubenwallner wrote: >> On 2/18/19 11:26 AM, Corinna Vinschen wrote: >>> On Feb 18 10:40, Michael Haubenwallner wrote: On 2/16/19 6:43 PM, Corinna Vinschen wrote: > I really miss the problem you're trying to solve here.

Re: textmode for stdout, what is "correct" now?

On Feb 18 15:45, Michael Haubenwallner wrote: > On 2/18/19 2:15 PM, Corinna Vinschen wrote: > > You have two modes for input and three for output: > > > > - input O_BINARY -> only \n > > - input O_TEXT-> \n and \r\n > > > > - output 0-> generates \n or \r\n depending on mount mode >

Re: Problem with sshd on W7 with 32bit cygwin 3.0

On Mon, Feb 18, 2019 at 03:11:11PM +0100, Corinna Vinschen wrote: > > Two workarounds for now: > > - Start sshd as 64 bit Cygwin process. > - Utilize https://cygwin.com/cygwin-ug-net/ntsec.html#ntsec-nopasswd3 Thank you. The second method above worked. This is a private network, so that is Ok.

Re: antrun versus wsl versus cygwin

On Mon, 18 Feb 2019 14:39:11, Franz Fehringer wrote: > Am 18.02.2019 um 14:07 schrieb Houder: > > On Mon, 18 Feb 2019 13:15:02, Franz Fehringer wrote: [snip] > >> > >> > >> > >> > >> > >> > >> > >> gives > >> > >> [exec] /usr/bin/bash > >> [exec] W i n d o w s S u b s y s t e m f o

Re: antrun versus wsl versus cygwin

Am 18.02.2019 um 17:20 schrieb Houder: > On Mon, 18 Feb 2019 14:39:11, Franz Fehringer wrote: >> Am 18.02.2019 um 14:07 schrieb Houder: >>> On Mon, 18 Feb 2019 13:15:02, Franz Fehringer wrote: > [snip] > gives [exec] /usr/bin/bash

Re: antrun versus wsl versus cygwin

Am 18.02.2019 um 17:20 schrieb Houder: > On Mon, 18 Feb 2019 14:39:11, Franz Fehringer wrote: >> Am 18.02.2019 um 14:07 schrieb Houder: >>> On Mon, 18 Feb 2019 13:15:02, Franz Fehringer wrote: > [snip] > gives [exec] /usr/bin/bash

Re: antrun versus wsl versus cygwin

Am 17.02.2019 um 14:39 schrieb Franz Fehringer: Am 17.02.2019 um 13:53 schrieb Thomas Wolff: Am 17.02.2019 um 12:11 schrieb Franz Fehringer: Hi all (half off topic), I have installed (on a Windows 10 1809 system) both Cygwin and WSL (only the Windows component, no real Linux distribution yet).

Re: Problem with sshd on W7 with 32bit cygwin 3.0

On Feb 18 17:04, Enrico Forestieri wrote: > On Mon, Feb 18, 2019 at 03:11:11PM +0100, Corinna Vinschen wrote: > > > > Two workarounds for now: > > > > - Start sshd as 64 bit Cygwin process. > > - Utilize https://cygwin.com/cygwin-ug-net/ntsec.html#ntsec-nopasswd3 > > Thank you. The second method

Re: antrun versus wsl versus cygwin

On Mon, 18 Feb 2019 13:15:02, Franz Fehringer wrote: > Am 18.02.2019 um 11:42 schrieb Houder: [snip] > > Now show us the output of an antrun script, where the executable > > is C:\Tools\Cygwin\bin\which and its argument: bash > > > > > > > > > gives > > [exec] /usr/bin/bash > [exec]