This is the mail archive of the
mailing list for the Cygwin project.
Re: native Linux userland in Windows 10
- From: Andrey Repin <anrdaemon at yandex dot ru>
- To: Warren Young <wyml at etr-usa dot com>, cygwin at cygwin dot com
- Date: Thu, 14 Apr 2016 21:28:25 +0300
- Subject: Re: native Linux userland in Windows 10
- Authentication-results: sourceware.org; auth=none
- References: <70rpgbh81o3fkrdgh8ldh2hmon25ihnr1s at 4ax dot com> <570CF112 dot 6060405 at gmail dot com> <20160412134132 dot GP9870 at calimero dot vinschen dot de> <f56f65b748e89d00723d1a3aa0b5535a at www dot ds dot net> <g8aqgb9hktdquq1ul0prq8kd769olbecpg at 4ax dot com> <570D4AFB dot 4000906 at cs dot umass dot edu> <6103A4A6-C242-4D4E-AA1E-7774BFB66D96 at etr-usa dot com> <1273817198 dot 20160413182530 at yandex dot ru> <E7E04FDC-F30C-42BF-8B9C-838DEB77C1D7 at etr-usa dot com>
- Reply-to: cygwin at cygwin dot com
Greetings, Warren Young!
> On Apr 13, 2016, at 9:25 AM, Andrey Repin <firstname.lastname@example.org> wrote:
>>> On Apr 12, 2016, at 1:22 PM, Eliot Moss <email@example.com> wrote:
>>>> It will be interesting to see how they map identities and permissions!
>>> They don’t map identities at all, a fact that is clear from this presentation:
>> In other words, this is a useless bullshit?
> Cygwin didn’t have AD/SAM integration until about a year ago. So, Cygwin
> was useless until last year, too?
That's not exactly true.
Cygwin did not have direct AD integration, but it did not prevent using it in
AD, and SAM integration is what allowed it. Yes, it wasn't perfect. But it
> Ubuntu for Windows is as useful today as pre-Cygwin 1.7.34 with a nearly
> empty /etc/passwd file,
Remove "nearly", and you get it right.
> containing only the user’s POSIX UID to Windows SID mapping. Which is to
> say, not useless at all.
It doesn't work even that far, as has been demonstrated in a nearby thread.
> The fact that it has limitations merely means it isn’t going to wipe Cygwin
> off the map immediately. When/if Microsoft fixes all the limitations w.r.t. Cygwin, Cygwin is in deep yogurt.
>> No SSHD, no cron, no… nothing?
> sshd is currently broken because they have no pty layer to speak of.
> Anything else that depends heavily on ptys is broken for the same reason, such as tmux.
> As for cron, I see no reason why that wouldn’t work, at least for a single
> user. If you mean that you don’t get a system-wide cron service, so you can
> schedule jobs to run as SYSTEM or similar, then yes, I wouldn’t expect that
> to work any time soon, if ever.
I can't schedule cron jobs even as user, if I can't have it running at the
With best regards,
Thursday, April 14, 2016 21:24:33
Sorry for my terrible english...