From: Tony Kelman <tony@kelman.net>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: RE: native Linux userland in Windows 10
Date: Wed, 13 Apr 2016 10:17:00 -0000 [thread overview]
Message-ID: <BAY169-W932587D17E1610765C9851A7960@phx.gbl> (raw)
In-Reply-To: <CA+Fg1xaJrBhiTauScQPLZbY2vM5ifPPJWKPe3mrbKV0gw9MhWA@mail.gmail.com>
> 2016-04-12 14:50 GMT+02:00 Andrew Schulman is curious:
>>
>> Has anyone had a chance to try this new feature? Does it work as well as is
>> claimed?
>>
>
> I will try ;)
>
> Here is how to:
>
> http://blog.dustinkirkland.com/2016/04/howto-ubuntu-on-windows.html
>
> Gerrit
I've been giving it a spin. Lots of things are broken or not yet
implemented, still lots of problems at this stage. Apparently they
already have fixes for some of the issues that have been reported
at https://github.com/Microsoft/BashOnWindows/issues but not rolled
out to users yet. In its current form it could only possibly be a
replacement for cygwin if you can get away with your only interoperation
between cygwin and win32 executables or libraries being the /cygdrive
mounted filesystem. Getting binaries straight from Ubuntu is a cool
trick and will be really convenient once enough of the syscalls are
working that you don't notice any gaps. I'd prefer a different distro's
userland if I had a choice, but maybe that'll be possible later.
-Tony
--
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:[~2016-04-13 10:17 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-12 12:51 Andrew Schulman
2016-04-12 12:59 ` Marco Atzeri
2016-04-12 13:41 ` Corinna Vinschen
2016-04-12 14:41 ` Philip Daniels
2016-04-12 14:54 ` wilson
2016-04-12 17:01 ` Andrew Schulman
2016-04-12 19:22 ` Eliot Moss
2016-04-12 22:08 ` Warren Young
2016-04-13 15:35 ` Andrey Repin
2016-04-13 18:21 ` John Cowan
2016-04-14 0:14 ` John Cowan
2016-04-14 1:05 ` Andrey Repin
2016-04-14 3:06 ` Eliot Moss
2016-04-14 18:35 ` Andrey Repin
2016-04-14 14:50 ` Warren Young
2016-04-14 15:08 ` Alexey Sokolov
2016-04-14 17:35 ` Eliot Moss
2016-04-14 18:35 ` Andrey Repin
2016-04-14 18:37 ` Eliot Moss
2016-04-14 18:35 ` Andrey Repin
2016-04-12 17:37 ` Achim Gratz
2016-04-13 0:12 ` Andrew Schulman
2016-04-13 5:02 ` Herbert Stocker
2016-04-12 17:42 ` Achim Gratz
2016-04-13 5:20 ` Herbert Stocker
2016-04-13 9:41 ` Gerrit Haase
2016-04-13 10:17 ` Tony Kelman [this message]
2016-04-15 11:12 ` Tobias Zawada
2016-04-15 16:48 ` John Cowan
2016-04-13 12:56 KARL BOTTS
2016-04-13 13:21 ` John Cowan
2016-04-14 15:58 ` Warren Young
2016-04-14 17:18 ` Andrew Schulman
2016-04-14 19:20 ` Andrey Repin
2016-04-14 19:26 ` Eliot Moss
2016-04-14 20:40 ` John Cowan
2016-04-14 22:50 ` Andrey Repin
2016-04-14 23:34 ` John Cowan
2016-04-15 10:05 ` Andrey Repin
2016-04-15 16:27 ` John Cowan
2016-04-17 21:35 ` Andrey Repin
2016-04-14 23:09 ` Warren Young
2016-04-14 23:53 ` John Cowan
2016-04-15 10:05 ` Andrey Repin
2016-04-20 22:23 ` Warren Young
2016-04-21 11:56 ` David Macek
2016-04-21 16:31 ` John Cowan
2016-04-22 8:04 ` David Macek
2016-04-22 8:40 ` Steven Hartland
2016-04-22 4:37 ` Andrey Repin
2016-04-14 20:49 ` John Cowan
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=BAY169-W932587D17E1610765C9851A7960@phx.gbl \
--to=tony@kelman.net \
--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).