public inbox for cygwin-talk@cygwin.com
 help / color / mirror / Atom feed
From: Warren Young <warren@etr-usa.com>
To: cygwin-talk@cygwin.com
Subject: Re: MS recommends Cygwin
Date: Fri, 16 Mar 2012 15:04:00 -0000	[thread overview]
Message-ID: <4F635682.6050500@etr-usa.com> (raw)
In-Reply-To: <20120315184401.GA30751@ednor.casa.cgf.cx>

On 3/15/2012 12:44 PM, Christopher Faylor wrote:
> On Thu, Mar 15, 2012 at 06:47:40AM -0600, Warren Young wrote:
>> On 3/15/2012 5:42 AM, Andy Koppe wrote:
>>> http://technet.microsoft.com/en-us/library/hh831568.aspx
>>>
>>> "Features Removed or Deprecated in Windows Server "8" Beta
>>> ...
>>> The Subsystem for UNIX-based Applications (SUA) is deprecated. If you
>>> use the SUA POSIX subsystem with this release, use Hyper-V to
>>> virtualize the server. If you use the tools provided by SUA, switch to
>>> Cygwin or Mingw."
>>
>> Ding dong, the witch is dead?
>
> But I heard that SUA does fork correctly.  Maybe it uses copy-on-right.
> Cygwin should see if it could do the same thing.

I went looking to see if the Windows 8 kernel added such a thing, but 
instead I came away with the impression that MS wants Win32 to DIAF.

In other words, "You're next, Cygwin."

I think a prerequisite for that unhappy event would be a complete 
iPadification of the consumer computing world, but that seems like a 
very real possibility to me.  Driven not by MS, but by Apple, as usual.

What I can't see happening is the iPadification of Windows Server.  I 
can see it now: Cygwin 1.9 running on Windows Server 2018 Nerd Edition.

  reply	other threads:[~2012-03-16 15:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-15 11:42 Andy Koppe
2012-03-15 12:48 ` Warren Young
2012-03-15 18:44   ` Christopher Faylor
2012-03-16 15:04     ` Warren Young [this message]
2012-03-16 18:24       ` David Eisner
2012-03-16 18:31         ` Warren Young

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=4F635682.6050500@etr-usa.com \
    --to=warren@etr-usa.com \
    --cc=cygwin-talk@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).