From: Andrew Schulman <schulman.andrew@epa.gov>
To: cygwin@cygwin.com
Subject: native Linux userland in Windows 10
Date: Tue, 12 Apr 2016 12:51:00 -0000 [thread overview]
Message-ID: <70rpgbh81o3fkrdgh8ldh2hmon25ihnr1s@4ax.com> (raw)
By now I guess most of us have seen the reports of bash, and in fact a full
Linux userland, running natively in Windows 10:
http://www.osnews.com/story/29149/Microsoft_and_Canonical_partner_to_bring_Ubuntu_to_Windows_10
http://www.hanselman.com/blog/DevelopersCanRunBashShellAndUsermodeUbuntuLinuxBinariesOnWindows10.aspx
http://blog.dustinkirkland.com/2016/03/ubuntu-on-windows.html
It's in beta release and doesn't seem to have been widely tested yet. Apparently
Microsoft has developed an API translation layer, simliar to the Cygwin DLL, to
make this work. But unlike with Cygwin, Linux apps don't have to be rebuilt -
they can run natively as-is in Windows 10. So you can get, allegedly, the full
Linux userland out-of-the-box.
The first link cited above suggests that if this is all it claims to be, it
would remove the need for Cygwin. I can see the point.
Has anyone had a chance to try this new feature? Does it work as well as is
claimed?
I realize this may be strictly off-topic here, but it seems to me to be
potentially so important to the future of Cygwin that it's worth discussing here
insted of on cygwin-talk.
Andrew
--
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 reply other threads:[~2016-04-12 12:51 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-12 12:51 Andrew Schulman [this message]
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
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=70rpgbh81o3fkrdgh8ldh2hmon25ihnr1s@4ax.com \
--to=schulman.andrew@epa.gov \
--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).