25 May 16 07:40, you wrote to me:

 ac>> Also, apparently you can't run server software with it. I haven't
 ac>> tried that yet, so I'm not sure if this means you can't use
 ac>> listen() to wait for connections, or if it just means the Linux
 ac>> emulation is firewalled from the Windows side to stop apps making
 ac>> TCP connections to it. I suspect the latter, and that someone will
 ac>> find a way around it...

 TL> I'm sure someone will find a way. ;)  Sounds like a ploy to force the
 TL> use of Microsoft servers.  Afterall, if someone could setup a LAMP stack
 TL> or similar on a Windows 10 box, there goes another sale of Windows
 TL> Server. ;)  And longer term, such an admin will one day say "Hey, I
 TL> might as well use Linux", and Microsoft does lose another customer.
 TL> Yes, I can see why they might firewall off incoming connections.  Guess
 TL> they're using some form of stateful firewall.
 TL> :)

There's nothing stopping anyone running a WAMP stack under Windows 10 right now
though. So I don't think that's the reason. Well not unless they wanted to be
petty. It wouldn't be the first time.

You're right about the risk Microsoft is taking potentially losing customers
(web developers spring to mind) once they become accustomed to the Linux
command-line. Not necessarily losing them to Linux either, but to OS X. But I'm
sure they've considered that.

I'm curious what their plans are for Windows Server now that Windows 10 is
essentially a "rolling release".

--- GoldED+/BSD 1.1.5-b20160201