From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: Cygwin alongside WSL
Date: Thu, 26 Oct 2017 16:13:00 -0000 [thread overview]
Message-ID: <f0180168-fc3b-7a6a-d4b4-14e6a6da2c0d@SystematicSw.ab.ca> (raw)
In-Reply-To: <2ce18657-808a-3e1f-9c59-46f5b8e1128d@towo.net>
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
next prev parent reply other threads:[~2017-10-26 16:13 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-24 22:20 Angelo Graziosi
2017-10-25 6:30 ` Thomas Wolff
2017-10-25 12:28 ` Angelo Graziosi
2017-10-25 17:27 ` Brian Inglis
2017-10-25 17:34 ` Thomas Wolff
2017-10-25 18:30 ` Brian Inglis
2017-10-25 21:18 ` Thomas Wolff
2017-10-26 16:13 ` Brian Inglis [this message]
2017-10-26 16:57 ` Brian Inglis
2017-10-26 22:11 ` Thomas Wolff
2017-10-31 18:11 ` Thomas Wolff
2017-11-02 3:19 ` Brian Inglis
2017-11-02 22:38 ` Thomas Wolff
2017-11-03 5:15 ` Brian Inglis
-- strict thread matches above, loose matches on Subject: below --
2017-10-23 12:38 KARL BOTTS
2017-10-23 14:05 ` Andrey Repin
2017-10-23 14:57 ` arrl via cygwin
2017-10-23 16:02 ` Brian Inglis
2017-10-24 7:34 ` Frank Fesevur
2017-10-24 19:47 ` Thomas Wolff
[not found] ` <331VJXVBf1952S01.1508878951@web01.cms.usa.net>
2017-10-24 21:04 ` KARL BOTTS
2017-10-24 17:57 ` Michael Enright
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=f0180168-fc3b-7a6a-d4b4-14e6a6da2c0d@SystematicSw.ab.ca \
--to=brian.inglis@systematicsw.ab.ca \
--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).