Re: Cygwin alongside WSL

Re: Cygwin alongside WSL

[Angelo Graziosi]

Thomas Wolff wrote:
>
> Mintty 2.8.0 simplifies WSL integration a lot.
> In Cygwin, you can simply start e.g. mintty --WSL=Ubuntu (add -~ to start in the WSL home).
>

Does it mean that 2.8.0 does not need wslbridge [*] any more?

Ciao,
 Angelo.

----
[*] https://github.com/rprichard/wslbridge

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

[Thomas Wolff]

Am 25.10.2017 um 00:19 schrieb Angelo Graziosi:
> Thomas Wolff wrote:
>> Mintty 2.8.0 simplifies WSL integration a lot.
>> In Cygwin, you can simply start e.g. mintty --WSL=Ubuntu (add -~ to start in the WSL home).
> Does it mean that 2.8.0 does not need wslbridge [*] any more?
No, sorry, I forgot to mention that wslbridge would have to be installed
in /bin to make this work.
Thomas

---
Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprüft.
https://www.avast.com/antivirus


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

[Angelo Graziosi]

> Il 25 ottobre 2017 alle 8.29 Thomas Wolff <towo@towo.net> ha scritto:
> 
> 
> >> Mintty 2.8.0 simplifies WSL integration a lot.
> >> In Cygwin, you can simply start e.g. mintty --WSL=Ubuntu (add -~ to start in the WSL home).
> > Does it mean that 2.8.0 does not need wslbridge [*] any more?
> No, sorry, I forgot to mention that wslbridge would have to be installed
> in /bin to make this work.

If I understand, 2.8.0 is a big step forward because instead to have this (as target link)

C:\msys64\usr\bin\mintty.exe /bin/wslbridge.exe --distro-guid {AAAAA-CCCC-BBBB-DDD-123123} -C~ -t /bin/bash -l

we just need this

C:\msys64\usr\bin\mintty.exe --WSL=Ubuntu -~

Right?

Thanks,
 Angelo.

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

[Brian Inglis]

On 2017-10-25 00:29, Thomas Wolff wrote:
> Am 25.10.2017 um 00:19 schrieb Angelo Graziosi:
>> Thomas Wolff wrote:
>>> Mintty 2.8.0 simplifies WSL integration a lot.
>>> In Cygwin, you can simply start e.g. mintty --WSL=Ubuntu (add -~ to start in
>>> the WSL home).
>> Does it mean that 2.8.0 does not need wslbridge [*] any more?
> No, sorry, I forgot to mention that wslbridge would have to be installed
> in /bin to make this work.

As it is not a Cygwin package, I have installed wslbridge in /usr/local/bin/,
which is in the system Path in Windows format, so also in the Cygwin path in
Unix format - will this work?

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

Re: Cygwin alongside WSL

[Thomas Wolff]

Am 25.10.2017 um 19:27 schrieb Brian Inglis:
> On 2017-10-25 00:29, Thomas Wolff wrote:
>> Am 25.10.2017 um 00:19 schrieb Angelo Graziosi:
>>> Thomas Wolff wrote:
>>>> Mintty 2.8.0 simplifies WSL integration a lot.
>>>> In Cygwin, you can simply start e.g. mintty --WSL=Ubuntu (add -~ to start in the WSL home).
>>> Does it mean that 2.8.0 does not need wslbridge [*] any more?
>> No, sorry, I forgot to mention that wslbridge would have to be installed in /bin to make this work.
> As it is not a Cygwin package, I have installed wslbridge in /usr/local/bin/,
> which is in the system Path in Windows format, so also in the Cygwin path in
> Unix format - will this work?
No, sorry again. Mintty assumes /bin/wslbridge as a fixed location. A 
cygwin package for wslbridge would be good, on this occasion. Or simply 
copy it there.
Thomas

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

[Brian Inglis]

On 2017-10-25 11:27, Brian Inglis wrote:
> On 2017-10-25 00:29, Thomas Wolff wrote:
>> Am 25.10.2017 um 00:19 schrieb Angelo Graziosi:
>>> Thomas Wolff wrote:
>>>> Mintty 2.8.0 simplifies WSL integration a lot.
>>>> In Cygwin, you can simply start e.g. mintty --WSL=Ubuntu (add -~ to start in
>>>> the WSL home).
>>> Does it mean that 2.8.0 does not need wslbridge [*] any more?
>> No, sorry, I forgot to mention that wslbridge would have to be installed
>> in /bin to make this work.
> 
> As it is not a Cygwin package, I have installed wslbridge in /usr/local/bin/,
> which is in the system Path in Windows format, so also in the Cygwin path in
> Unix format - will this work?

Would a symlink, winsymlink, or .lnk as /bin/wslbridge to /usr/local/bin/?

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

Re: Cygwin alongside WSL

[Thomas Wolff]

Am 25.10.2017 um 20:30 schrieb Brian Inglis:
> On 2017-10-25 11:27, Brian Inglis wrote:
>> On 2017-10-25 00:29, Thomas Wolff wrote:
>>> Am 25.10.2017 um 00:19 schrieb Angelo Graziosi:
>>>> Thomas Wolff wrote:
>>>>> Mintty 2.8.0 simplifies WSL integration a lot.
>>>>> In Cygwin, you can simply start e.g. mintty --WSL=Ubuntu (add -~ to start in
>>>>> the WSL home).
>>>> Does it mean that 2.8.0 does not need wslbridge [*] any more?
>>> No, sorry, I forgot to mention that wslbridge would have to be installed
>>> in /bin to make this work.
>> As it is not a Cygwin package, I have installed wslbridge in /usr/local/bin/,
>> which is in the system Path in Windows format, so also in the Cygwin path in
>> Unix format - will this work?
> Would a symlink, winsymlink, or .lnk as /bin/wslbridge to /usr/local/bin/?
Why don't you just try it? Both wslbridge and wslbridge-backend must 
reside in /bin, hard links will work of course.

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

[Brian Inglis]

On 2017-10-25 15:18, Thomas Wolff wrote:
> Am 25.10.2017 um 20:30 schrieb Brian Inglis:
>> On 2017-10-25 11:27, Brian Inglis wrote:
>>> On 2017-10-25 00:29, Thomas Wolff wrote:
>>>> Am 25.10.2017 um 00:19 schrieb Angelo Graziosi:
>>>>> Thomas Wolff wrote:
>>>>>> Mintty 2.8.0 simplifies WSL integration a lot.
>>>>>> In Cygwin, you can simply start e.g. mintty --WSL=Ubuntu (add -~ to start in
>>>>>> the WSL home).
>>>>> Does it mean that 2.8.0 does not need wslbridge [*] any more?
>>>> No, sorry, I forgot to mention that wslbridge would have to be installed
>>>> in /bin to make this work.
>>> As it is not a Cygwin package, I have installed wslbridge in /usr/local/bin/,
>>> which is in the system Path in Windows format, so also in the Cygwin path in
>>> Unix format - will this work?
>> Would a symlink, winsymlink, or .lnk as /bin/wslbridge to /usr/local/bin/?
> Why don't you just try it? Both wslbridge and wslbridge-backend must reside in
> /bin, hard links will work of course.

It looks like without the Fall Update --WSL= does not work with either
no/default distribution found, and the same result with a variety of obvious names:

	$ mintty --WSL
	Option '--WSL' requires an argument
	$ mintty --WSL=
	WSL distribution '' not found
	Try '--help' for more information
	$ mintty --version
	mintty 2.8.0 (x86_64-pc-cygwin)
	© 2013/2017 Andy Koppe / Thomas Wolff
	License GPLv3+: GNU GPL version 3 or later
	There is no warranty, to the extent permitted by law.
	$ uname -srvmo
	CYGWIN_NT-10.0 2.9.0(0.318/5/3) 2017-09-12 10:18 x86_64 Cygwin

but --help does not even mention --WSL=, and the man page mentions wslconfig
which is not installed on the system.

On a legacy install, the only reg values available are:

$ ls -FR
/proc/registry/HKEY_CURRENT_USER/SOFTWARE/Microsoft/Windows/CurrentVersion/Lxss/
/proc/registry/HKEY_CURRENT_USER/SOFTWARE/Microsoft/Windows/CurrentVersion/Lxss/:
DefaultGid  DefaultUid  DefaultUsername  State

$ regtool -lpv list \\HKCU\\SOFTWARE\\Microsoft\\Windows\\CurrentVersion\\Lxss
DefaultUsername (REG_SZ) = "..."
DefaultUid (REG_DWORD) = 0x000003e8 (1000)
DefaultGid (REG_DWORD) = 0x000003e8 (1000)
State (REG_DWORD) = 0x00000001 (1)

It would be nice if --WSL did the right thing for legacy installs also.

The problem seems to be in winmain.c on a legacy install, there is no guid, and
no BasePath, so you return false.

If the distro name wslname is null or empty, or no DefaultDistribution,
distribution subkeys, guid, BasePath, or PackageFamilyName, you should take the
else legacy path, and fake the guid, fake the BasePath variable bp to
W("%LOCALAPPDATA%\\lxss") and PackageFamilyName variable pn to Bash, and maybe
also the distro and wslname to Bash.

Also for longopts --WSL should allow an optional_argument, as there should be no
distinction between --WSL and --WSL=, they should be parsed as if they were
--WSL[[ =][distro]], and optional arguments omitted either way, with following
options also terminating the argument scan.

I can raise these as issues on github if you prefer to track there?

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

Re: Cygwin alongside WSL

[Brian Inglis]

On 2017-10-26 10:13, Brian Inglis wrote:
> On 2017-10-25 15:18, Thomas Wolff wrote:
>> Am 25.10.2017 um 20:30 schrieb Brian Inglis:
>>> On 2017-10-25 11:27, Brian Inglis wrote:
>>>> On 2017-10-25 00:29, Thomas Wolff wrote:
>>>>> Am 25.10.2017 um 00:19 schrieb Angelo Graziosi:
>>>>>> Thomas Wolff wrote:
>>>>>>> Mintty 2.8.0 simplifies WSL integration a lot.
>>>>>>> In Cygwin, you can simply start e.g. mintty --WSL=Ubuntu (add -~ to start in
>>>>>>> the WSL home).
>>>>>> Does it mean that 2.8.0 does not need wslbridge [*] any more?
>>>>> No, sorry, I forgot to mention that wslbridge would have to be installed
>>>>> in /bin to make this work.
>>>> As it is not a Cygwin package, I have installed wslbridge in /usr/local/bin/,
>>>> which is in the system Path in Windows format, so also in the Cygwin path in
>>>> Unix format - will this work?
>>> Would a symlink, winsymlink, or .lnk as /bin/wslbridge to /usr/local/bin/?
>> Why don't you just try it? Both wslbridge and wslbridge-backend must reside in
>> /bin, hard links will work of course.
> 
> It looks like without the Fall Update --WSL= does not work with either
> no/default distribution found, and the same result with a variety of obvious names:
> 
> 	$ mintty --WSL
> 	Option '--WSL' requires an argument
> 	$ mintty --WSL=
> 	WSL distribution '' not found
> 	Try '--help' for more information
> 	$ mintty --version
> 	mintty 2.8.0 (x86_64-pc-cygwin)
> 	© 2013/2017 Andy Koppe / Thomas Wolff
> 	License GPLv3+: GNU GPL version 3 or later
> 	There is no warranty, to the extent permitted by law.
> 	$ uname -srvmo
> 	CYGWIN_NT-10.0 2.9.0(0.318/5/3) 2017-09-12 10:18 x86_64 Cygwin
> 
> but --help does not even mention --WSL=, and the man page mentions wslconfig
> which is not installed on the system.
> 
> On a legacy install, the only reg values available are:
> 
> $ ls -FR
> /proc/registry/HKEY_CURRENT_USER/SOFTWARE/Microsoft/Windows/CurrentVersion/Lxss/
> /proc/registry/HKEY_CURRENT_USER/SOFTWARE/Microsoft/Windows/CurrentVersion/Lxss/:
> DefaultGid  DefaultUid  DefaultUsername  State
> 
> $ regtool -lpv list \\HKCU\\SOFTWARE\\Microsoft\\Windows\\CurrentVersion\\Lxss
> DefaultUsername (REG_SZ) = "..."
> DefaultUid (REG_DWORD) = 0x000003e8 (1000)
> DefaultGid (REG_DWORD) = 0x000003e8 (1000)
> State (REG_DWORD) = 0x00000001 (1)
> 
> It would be nice if --WSL did the right thing for legacy installs also.
> 
> The problem seems to be in winmain.c on a legacy install, there is no guid, and
> no BasePath, so you return false.

(in getlxssinfo and getlxssdistinfo)

> If the distro name wslname is null or empty, or no DefaultDistribution,
> distribution subkeys, guid, BasePath, or PackageFamilyName, you should take the
> else legacy path, and fake the guid, fake the BasePath variable bp to
> W("%LOCALAPPDATA%\\lxss") and PackageFamilyName variable pn to Bash, and maybe
> also the distro and wslname to Bash.
> 
> Also for longopts --WSL should allow an optional_argument, as there should be no
> distinction between --WSL and --WSL=, they should be parsed as if they were
> --WSL[[ =][distro]], and optional arguments omitted either way, with following
> options also terminating the argument scan.
> 
> I can raise these as issues on github if you prefer to track there?

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

Re: Cygwin alongside WSL

[Thomas Wolff]

Am 26.10.2017 um 18:13 schrieb Brian Inglis:
> On 2017-10-25 15:18, Thomas Wolff wrote:
>> Am 25.10.2017 um 20:30 schrieb Brian Inglis:
>>> On 2017-10-25 11:27, Brian Inglis wrote:
>>>> On 2017-10-25 00:29, Thomas Wolff wrote:
>>>>> Am 25.10.2017 um 00:19 schrieb Angelo Graziosi:
>>>>>> Thomas Wolff wrote:
>>>>>>> Mintty 2.8.0 simplifies WSL integration a lot.
>>>>>>> In Cygwin, you can simply start e.g. mintty --WSL=Ubuntu (add -~ to start in
>>>>>>> the WSL home).
>>>>>> Does it mean that 2.8.0 does not need wslbridge [*] any more?
>>>>> No, sorry, I forgot to mention that wslbridge would have to be installed
>>>>> in /bin to make this work.
>>>> As it is not a Cygwin package, I have installed wslbridge in /usr/local/bin/,
>>>> which is in the system Path in Windows format, so also in the Cygwin path in
>>>> Unix format - will this work?
>>> Would a symlink, winsymlink, or .lnk as /bin/wslbridge to /usr/local/bin/?
>> Why don't you just try it? Both wslbridge and wslbridge-backend must reside in
>> /bin, hard links will work of course.
> It looks like without the Fall Update --WSL= does not work with either
> no/default distribution found, and the same result with a variety of obvious names:
>
> ...
>
> It would be nice if --WSL did the right thing for legacy installs also.
Yes, I am aware of this gap, see https://github.com/mintty/wsltty/issues/64
> ...
> Also for longopts --WSL should allow an optional_argument, ...
I was not aware of this feature of getopt, thanks.
Thomas

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

[Thomas Wolff]

Am 27.10.2017 um 00:10 schrieb Thomas Wolff:
> Am 26.10.2017 um 18:13 schrieb Brian Inglis:
>> On 2017-10-25 15:18, Thomas Wolff wrote:
>>> Am 25.10.2017 um 20:30 schrieb Brian Inglis:
>>>> On 2017-10-25 11:27, Brian Inglis wrote:
>>>>> On 2017-10-25 00:29, Thomas Wolff wrote:
>>>>>> Am 25.10.2017 um 00:19 schrieb Angelo Graziosi:
>>>>>>> Thomas Wolff wrote:
>>>>>>>> Mintty 2.8.0 simplifies WSL integration a lot.
>>>>>>>> In Cygwin, you can simply start e.g. mintty --WSL=Ubuntu (add
>>>>>>>> -~ to start in
>>>>>>>> the WSL home).
>>>>>>> Does it mean that 2.8.0 does not need wslbridge [*] any more?
>>>>>> No, sorry, I forgot to mention that wslbridge would have to be
>>>>>> installed
>>>>>> in /bin to make this work.
>>>>> As it is not a Cygwin package, I have installed wslbridge in
>>>>> /usr/local/bin/,
>>>>> which is in the system Path in Windows format, so also in the
>>>>> Cygwin path in
>>>>> Unix format - will this work?
>>>> Would a symlink, winsymlink, or .lnk as /bin/wslbridge to
>>>> /usr/local/bin/?
>>> Why don't you just try it? Both wslbridge and wslbridge-backend must
>>> reside in
>>> /bin, hard links will work of course.
>> It looks like without the Fall Update --WSL= does not work with either
>> no/default distribution found, and the same result with a variety of
>> obvious names:
>>
>> ...
>>
>> It would be nice if --WSL did the right thing for legacy installs also.
> Yes, I am aware of this gap, see
> https://github.com/mintty/wsltty/issues/64
This should be working now with mintty 2.8.1. Please try.

---
Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprüft.
https://www.avast.com/antivirus


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

[Brian Inglis]

On 2017-10-31 12:11, Thomas Wolff wrote:
> Am 27.10.2017 um 00:10 schrieb Thomas Wolff:
>> Am 26.10.2017 um 18:13 schrieb Brian Inglis:
>>> On 2017-10-25 15:18, Thomas Wolff wrote:
>>>> Am 25.10.2017 um 20:30 schrieb Brian Inglis:
>>>>> On 2017-10-25 11:27, Brian Inglis wrote:
>>>>>> On 2017-10-25 00:29, Thomas Wolff wrote:
>>>>>>> Am 25.10.2017 um 00:19 schrieb Angelo Graziosi:
>>>>>>>> Thomas Wolff wrote:
>>>>>>>>> Mintty 2.8.0 simplifies WSL integration a lot.
>>>>>>>>> In Cygwin, you can simply start e.g. mintty --WSL=Ubuntu (add
>>>>>>>>> -~ to start in
>>>>>>>>> the WSL home).
>>>>>>>> Does it mean that 2.8.0 does not need wslbridge [*] any more?
>>>>>>> No, sorry, I forgot to mention that wslbridge would have to be
>>>>>>> installed
>>>>>>> in /bin to make this work.
>>>>>> As it is not a Cygwin package, I have installed wslbridge in
>>>>>> /usr/local/bin/,
>>>>>> which is in the system Path in Windows format, so also in the
>>>>>> Cygwin path in
>>>>>> Unix format - will this work?
>>>>> Would a symlink, winsymlink, or .lnk as /bin/wslbridge to
>>>>> /usr/local/bin/?
>>>> Why don't you just try it? Both wslbridge and wslbridge-backend must
>>>> reside in
>>>> /bin, hard links will work of course.
>>> It looks like without the Fall Update --WSL= does not work with either
>>> no/default distribution found, and the same result with a variety of
>>> obvious names:
>>>
>>> ...
>>>
>>> It would be nice if --WSL did the right thing for legacy installs also.
>> Yes, I am aware of this gap, see
>> https://github.com/mintty/wsltty/issues/64
> This should be working now with mintty 2.8.1. Please try.

This is now working nicely with --WSL and symlinks from
/usr/local/bin/wslbridge* to /usr/bin/.
Using mintty makes cross-checking Cygwin vs Linux operation very pleasant.

[Nitpick: with --WSL, argument "-" does not find DefaultUserName in
BasePath/rootfs/etc/passwd and launch the default shell as the login shell:
/bin/wslbridge: Exit 1.
error: could not exec '-': No such file or directory]

Thanks for all your efforts since you adopted this package, in updating it to
modern standards, all the Unicode, vtterm, and xterm support you have added, all
the new features and improvements in every release, adaptation for WSL, all the
fixes you constantly make, and your frequent releases.

I am sorry for those who can only use Xwindow terminal emulators! ;^>

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

Re: Cygwin alongside WSL

[Thomas Wolff]

Am 02.11.2017 um 04:19 schrieb Brian Inglis:
> On 2017-10-31 12:11, Thomas Wolff wrote:
>> Am 27.10.2017 um 00:10 schrieb Thomas Wolff:
>>> Am 26.10.2017 um 18:13 schrieb Brian Inglis:
>>>> On 2017-10-25 15:18, Thomas Wolff wrote:
>>>>> Am 25.10.2017 um 20:30 schrieb Brian Inglis:
>>>>>> On 2017-10-25 11:27, Brian Inglis wrote:
>>>>>>> On 2017-10-25 00:29, Thomas Wolff wrote:
>>>>>>>> Am 25.10.2017 um 00:19 schrieb Angelo Graziosi:
>>>>>>>>> Thomas Wolff wrote:
>>>>>>>>>> Mintty 2.8.0 simplifies WSL integration a lot.
>>>>>>>>>> In Cygwin, you can simply start e.g. mintty --WSL=Ubuntu (add
>>>>>>>>>> -~ to start in
>>>>>>>>>> the WSL home).
>>>>>>>>> Does it mean that 2.8.0 does not need wslbridge [*] any more?
>>>>>>>> No, sorry, I forgot to mention that wslbridge would have to be
>>>>>>>> installed
>>>>>>>> in /bin to make this work.
>>>>>>> As it is not a Cygwin package, I have installed wslbridge in
>>>>>>> /usr/local/bin/,
>>>>>>> which is in the system Path in Windows format, so also in the
>>>>>>> Cygwin path in
>>>>>>> Unix format - will this work?
>>>>>> Would a symlink, winsymlink, or .lnk as /bin/wslbridge to
>>>>>> /usr/local/bin/?
>>>>> Why don't you just try it? Both wslbridge and wslbridge-backend must
>>>>> reside in
>>>>> /bin, hard links will work of course.
>>>> It looks like without the Fall Update --WSL= does not work with either
>>>> no/default distribution found, and the same result with a variety of
>>>> obvious names:
>>>>
>>>> ...
>>>>
>>>> It would be nice if --WSL did the right thing for legacy installs also.
>>> Yes, I am aware of this gap, see
>>> https://github.com/mintty/wsltty/issues/64
>> This should be working now with mintty 2.8.1. Please try.
> This is now working nicely with --WSL and symlinks from
> /usr/local/bin/wslbridge* to /usr/bin/.
> Using mintty makes cross-checking Cygwin vs Linux operation very pleasant.
>
> [Nitpick: with --WSL, argument "-" does not find DefaultUserName in
> BasePath/rootfs/etc/passwd and launch the default shell as the login shell:
> /bin/wslbridge: Exit 1.
> error: could not exec '-': No such file or directory]
Both features, finding the default user and starting a login shell, 
would depend on improved wslbridge support.
About "-", I've submitted an issue: 
https://github.com/rprichard/wslbridge/issues/18

> Thanks for all your efforts since you adopted this package, in updating it to
> modern standards, all the Unicode, vtterm, and xterm support you have added, all
> the new features and improvements in every release, adaptation for WSL, all the
> fixes you constantly make, and your frequent releases.
Thanks for flattering me :) Sounds good after all the people asking for 
ever more features, silly ones as well as good ones.
Actually, after the WSL and Virtual Tabs endeavours, release frequency 
should become lower now.
I'd still like to bundle the package with a number of themes and perhaps 
bell sounds, to populate the config directory not only with localization 
files. I've so far hesitated because I don't want to get involved in 
copyright discussions. Any idea or opinion?
Thomas

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

[Brian Inglis]

On 2017-11-02 16:38, Thomas Wolff wrote:
> Am 02.11.2017 um 04:19 schrieb Brian Inglis:
>> On 2017-10-31 12:11, Thomas Wolff wrote:
>>> Am 27.10.2017 um 00:10 schrieb Thomas Wolff:
>>>> Am 26.10.2017 um 18:13 schrieb Brian Inglis:
>>>>> On 2017-10-25 15:18, Thomas Wolff wrote:
>>>>>> Am 25.10.2017 um 20:30 schrieb Brian Inglis:
>>>>>>> On 2017-10-25 11:27, Brian Inglis wrote:
>>>>>>>> On 2017-10-25 00:29, Thomas Wolff wrote:
>>>>>>>>> Am 25.10.2017 um 00:19 schrieb Angelo Graziosi:
>>>>>>>>>> Thomas Wolff wrote:
>>>>>>>>>>> Mintty 2.8.0 simplifies WSL integration a lot.
>>>>>>>>>>> In Cygwin, you can simply start e.g. mintty --WSL=Ubuntu (add
>>>>>>>>>>> -~ to start in
>>>>>>>>>>> the WSL home).
>>>>>>>>>> Does it mean that 2.8.0 does not need wslbridge [*] any more?
>>>>>>>>> No, sorry, I forgot to mention that wslbridge would have to be
>>>>>>>>> installed
>>>>>>>>> in /bin to make this work.
>>>>>>>> As it is not a Cygwin package, I have installed wslbridge in
>>>>>>>> /usr/local/bin/,
>>>>>>>> which is in the system Path in Windows format, so also in the
>>>>>>>> Cygwin path in
>>>>>>>> Unix format - will this work?
>>>>>>> Would a symlink, winsymlink, or .lnk as /bin/wslbridge to
>>>>>>> /usr/local/bin/?
>>>>>> Why don't you just try it? Both wslbridge and wslbridge-backend must
>>>>>> reside in
>>>>>> /bin, hard links will work of course.
>>>>> It looks like without the Fall Update --WSL= does not work with either
>>>>> no/default distribution found, and the same result with a variety of
>>>>> obvious names:
>>>>>
>>>>> ...
>>>>>
>>>>> It would be nice if --WSL did the right thing for legacy installs also.
>>>> Yes, I am aware of this gap, see
>>>> https://github.com/mintty/wsltty/issues/64
>>> This should be working now with mintty 2.8.1. Please try.
>> This is now working nicely with --WSL and symlinks from
>> /usr/local/bin/wslbridge* to /usr/bin/.
>> Using mintty makes cross-checking Cygwin vs Linux operation very pleasant.
>>
>> [Nitpick: with --WSL, argument "-" does not find DefaultUserName in
>> BasePath/rootfs/etc/passwd and launch the default shell as the login shell:
>> /bin/wslbridge: Exit 1.
>> error: could not exec '-': No such file or directory]
> Both features, finding the default user and starting a login shell, would depend
> on improved wslbridge support.
> About "-", I've submitted an issue:
> https://github.com/rprichard/wslbridge/issues/18
> 
>> Thanks for all your efforts since you adopted this package, in updating it to
>> modern standards, all the Unicode, vtterm, and xterm support you have added, all
>> the new features and improvements in every release, adaptation for WSL, all the
>> fixes you constantly make, and your frequent releases.
> Thanks for flattering me :) Sounds good after all the people asking for ever
> more features, silly ones as well as good ones.

You and Ryan have done a stellar job of making Windows, Cygwin, and WSL more
useful for everyone who has come across your projects.

> Actually, after the WSL and Virtual Tabs endeavours, release frequency should
> become lower now.
> I'd still like to bundle the package with a number of themes and perhaps bell
> sounds, to populate the config directory not only with localization files. I've
> so far hesitated because I don't want to get involved in copyright discussions.
> Any idea or opinion?

Leverage the Unix GUI desktop projects with Cygwin compatible licenses.
There are a lot of themes, icon sets, sounds, and other resources available
which are not available in Cygwin, but are in other distros.

That's why I like WSL being easier to use with Cygwin: I can apt install or
apt-get build-dep and apt-get source --compile packages unavailable on Cygwin,
and use the resources or source, sharing directly between Cygwin, Ubuntu, and
Windows.

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

Re: Cygwin alongside WSL

[KARL BOTTS]

I (karl Botts) wrote:
> Does anybody have any concrete experience using Windows Subsystem for
Linux...

Thank you, arri, Brian Inglis, Frank Fesevur, Michael Enright, Thomas Wolf,
and anybody else I missed.  Your overviews are exactly what I was hoping for.

Not to go into details now, but I have tried it, and immediately had trouble.
Now, based on your feedback, I am sure it is my fault: I suspect I have some
symlinks
or the like in my Cygwin world that is leading to conflict.  Now that I know
it
should work, I am pretty sure I can get it to work.  I will report here on
the ultimate result.  Thanks again.


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

[Thomas Wolff]

Am 24.10.2017 um 09:33 schrieb Frank Fesevur:
> 2017-10-23 14:38 GMT+02:00 KARL BOTTS:
>> Does anybody have any concrete experience using Windows Subsystem for Linux
>> (hence WSL) on the same machine, alongside Cygwin?
> ... I am also looking into combining mintty and wsl, which takes some effort.
Mintty 2.8.0 simplifies WSL integration a lot.
In Cygwin, you can simply start e.g. mintty --WSL=Ubuntu (add -~ to 
start in the WSL home).
Also you can configure WSL invocation into the new session launcher.
So Cygwin users don't even need the WSLtty package (except you favour 
other invocation methods,
like desktop/startmenu shortcuts, .bat scripts, and Explorer context 
menu entries).
Thomas

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

[Michael Enright]

On Mon, Oct 23, 2017 at 5:38 AM, KARL BOTTS <kdbotts@usa.net> wrote:
>
> Does anybody have any concrete experience using Windows Subsystem for Linux
> (hence WSL) on the same machine, alongside Cygwin?
>

Yes. I have. I assume you are soliciting some descriptions of people's
experience.

I have various projects which come from various git repos. I use
Eclipse CDT to edit these most of the time. This makes it a little
tricky to use WSL.

I use Cygwin, 64-bit version, when I have to do checkouts or pushes,
and I do this from a Cygwin mintty bash session. This puts my files in
a subdirectory of $HOME in Cygwin.

I use WSL to build and execute my programs. I generally would be using
a straight g++ command to build, or CMake. Eclipse, which we may think
of as an "ordinary Windows program" for this discussion, cannot access
files in the WSL filesystem without using unsupported tricks, so
that's why I don't keep my files under WSL's filesystem. On the other
hand, using WSL I have less differences with Debian. Since the
projects are not meant to support "all POSIX systems" or "Cygwin and
Linux", these things give me what I need.

Most of the time I don't run into differences between Cygwin and WSL,
because I don't go into the areas where they do differ. I have done a
few graphical projects but they output to raster files instead of the
screen.

The biggest problem in this is Eclipse, and indeed the complete lack
of a decent graphical IDE for WSL. This means that the most useable
configuration for Eclipse is to define the project as a Cygwin
project, which will have minor differences with Ubuntu. The two have
different schedules for updating the C++ compiler, CMake, and so on.
Also most IDEs default to cr-lf line separators when they run on
Windows. But at least Eclipse can be configured to newline separators.
Some IDE's do not allow themselves to be configured 'non-native'.

The Windows boxes in question are allowed to update themselves
overnight and I run the usual update commands on WSL itself. I haven't
found this update policy to interfere with my work so far.

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

[Frank Fesevur]

2017-10-23 14:38 GMT+02:00 KARL BOTTS:
> Does anybody have any concrete experience using Windows Subsystem for Linux
> (hence WSL) on the same machine, alongside Cygwin?

I'm using them both without much problems (on Creator Update, not on
Fall Creator Update yet). I use them only for the command line. As
mentioned the CMD is not the best, but it gets the job done. I am also
looking into combining mintty and wsl, which takes some effort.

Since the architecture is much different, wsl is much faster and has
all the good stuff from the official Ubuntu repositories. But Cygwin
is available on Win7 and on servers, and Cygwin has cygrunsrv, which
wsl both lacks.

And I use 'noacl' on my /cygdrive mounts. WSL lack something like that
as well. That is really a big thing to me. I don't want a bash-script
to mess up my file permissions, especially not on network drives where
permissions can be crucial. WSL cannot mount network drives, at least
in the version I'm using.

I don't see myself choosing sides any time soon. Cygwin is still my
favorite and most used.

Regards,
Frank

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

[Brian Inglis]

On 2017-10-23 06:38, KARL BOTTS wrote:
> 
> Does anybody have any concrete experience using Windows Subsystem for Linux
> (hence WSL) on the same machine, alongside Cygwin?

Yes, I have used Bash on Ubuntu on Windows/WSL/lxss and found cmd console
useless, so I installed wsltty from github, and I just finished replacing my
wsltty install, using standard Cygwin 64 mintty, with wslbridge installed into
/usr/local/bin/, and adjustments to the WSL shortcuts to use those paths, with
the  Ubuntu Circle of Friends bash.ico, in a Ubuntu Start Menu folder, manually.
I'm looking to convert the wsltty install scripts with Cygwin scripts.
I use a lot of native Windows GUIs instead of Cygwin/X apps for responsiveness,
as my system is from 2010.

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

Re: Cygwin alongside WSL

[arrl via cygwin]

On 10/23/2017 10:02 AM, Andrey Repin wrote:
> Greetings, KARL BOTTS!
>
>> Does anybody have any concrete experience using Windows Subsystem for Linux
>> (hence WSL) on the same machine, alongside Cygwin?
> If you have any specific question - ask it.
> Asking a yes-or-no question doesn't add to the knowledge, and essentially
> boils down to "may I ask a question?"
> Yes, you may ask a question.
>
If you've watched gcc test results, you will have noticed that I have
been posting results for both cygwin and WSL since WSL first became
capable (occasionally) of running those tests.  My WSL results are
generally on an older box which is better able to run WSL than the newer
one, however it requires running external memory recovery more
frequently than cygwin does, and lately has been dying frequently anyway
in gfortran testsuite.    I haven't seen a feasible way to install WSL
other than with the Ubuntu.
Gcc attempts (unsuccessfully) to build and test cilkplus on WSL.  On
cygwin, there are major unsupported facilities (e.g. gstabs) which
produce hundreds of failures.  Although those 2 examples might
eventually be removed as being unworthy of support, it may be considered
that neither target is sufficiently popular with developers to see
support on the level of linux.

-- 
Tim Prince


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

[Andrey Repin]

Greetings, KARL BOTTS!

> Does anybody have any concrete experience using Windows Subsystem for Linux
> (hence WSL) on the same machine, alongside Cygwin?

If you have any specific question - ask it.
Asking a yes-or-no question doesn't add to the knowledge, and essentially
boils down to "may I ask a question?"
Yes, you may ask a question.


-- 
With best regards,
Andrey Repin
Monday, October 23, 2017 16:58:44

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

Cygwin alongside WSL

[KARL BOTTS]

Does anybody have any concrete experience using Windows Subsystem for Linux
(hence WSL) on the same machine, alongside Cygwin?


---
Karl Botts, kdbotts@usa.net


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