public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Andrey Repin <anrdaemon@yandex.ru>
To: Warren Young <wyml@etr-usa.com>, cygwin@cygwin.com
Subject: Re: native Linux userland in Windows 10
Date: Wed, 13 Apr 2016 15:35:00 -0000	[thread overview]
Message-ID: <1273817198.20160413182530@yandex.ru> (raw)
In-Reply-To: <6103A4A6-C242-4D4E-AA1E-7774BFB66D96@etr-usa.com>

Greetings, Warren Young!

> On Apr 12, 2016, at 1:22 PM, Eliot Moss <moss@cs.umass.edu> 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:

>   https://channel9.msdn.com/Events/Build/2016/C906

> They’re clearly saying that the Ubuntu world will have a completely
> different user set from your Windows desktop.  The inverse is clear from the
> fact that every native user that wants to have Ubuntu for Windows available installs their own separate copy.

> This is what I meant in my previous comments about “no AD/SAM integration”.

In other words, this is a useless bullshit?
No SSHD, no cron, no… nothing?


-- 
With best regards,
Andrey Repin
Wednesday, April 13, 2016 18:24:49

Sorry for my terrible english...

  reply	other threads:[~2016-04-13 15:35 UTC|newest]

Thread overview: 51+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-12 12:51 Andrew Schulman
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 [this message]
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=1273817198.20160413182530@yandex.ru \
    --to=anrdaemon@yandex.ru \
    --cc=cygwin@cygwin.com \
    --cc=wyml@etr-usa.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).