From: Tim Prince <n8tm@aol.com>
To: cygwin@cygwin.com
Subject: Re: Windows Subsystem For Linux
Date: Mon, 29 Aug 2016 13:17:00 -0000 [thread overview]
Message-ID: <9a99e8fc-9f68-d967-6011-71d922bd13e6@aol.com> (raw)
In-Reply-To: <CAOYw7dtGs1s4WS8tEg9hdGbqzMg9W762Koyzwh-oOT858V=G3Q@mail.gmail.com>
On 8/29/2016 7:15 AM, Ray Donnelly wrote:
> On Mon, Aug 29, 2016 at 12:00 PM, Schwarz, Konrad
> <konrad.schwarz@siemens.com> wrote:
>> So I was wondering if the Windows Subsystem For Linux, apparently part of Windows 10 Anniversary Update, obsoletes Cygwin.
>>
> That seems a *little* inflammatory to me. Since Windows Subsystem for
> Linux can't inter-operate with Windows very well, no it doesn't.
Although the Ubuntu subsystem doesn't provide a current gcc, it's
possible to build one now in the Anniversary version. Attempting to run
the g++ testsuite hangs the subsystem, requiring a reboot. It is
possible to run other individual test suites in parallel in separate
bash sessions, unlike under cygwin.
I've been wondering whether any conclusions might be drawn from the
relative performance of cygwin and linux subsystem. Disk and internet
access appear slow in the subsystem, but math functions and OpenMP seem
to perform better under linux.
As Win10 works on only one of my 3 Windows installations (the oldest
box), it doesn't look to be a replacement any time soon. For just one
example, the Ubuntu vim isn't nearly as convenient as I've become used to.
> 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
next prev parent reply other threads:[~2016-08-29 12:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-29 12:42 Schwarz, Konrad
2016-08-29 12:54 ` Ray Donnelly
2016-08-29 13:17 ` Tim Prince [this message]
2016-08-29 14:22 ` Keith Christian
2016-08-29 17:43 ` Andrey Repin
2016-08-29 18:30 ` Andrew Schulman
[not found] <1454779106.2980080.1472543049625.ref@mail.yahoo.com>
2016-08-30 13:06 ` lloyd.wood
2016-08-30 17:45 ` Marco Atzeri
2016-08-30 21:27 ` Andrey Repin
2016-08-31 10:51 ` Erik Soderquist
2016-09-04 7:35 ` Herbert Stocker
2016-08-30 13:40 Schwarz, Konrad
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=9a99e8fc-9f68-d967-6011-71d922bd13e6@aol.com \
--to=n8tm@aol.com \
--cc=cygwin@cygwin.com \
--cc=tprince@computer.org \
/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).