X-Recipient: archive-cygwin@delorie.com
DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:mime-version:references:in-reply-to:from:date
	:message-id:subject:to:content-type; q=dns; s=default; b=wuoox5o
	J0OivgBo939oq4BaOI2gGm98jaBkMi4Lz6gC7gYKX/A6lVWyG/7AxhZzZ66c65Zu
	QifYlnflbsBk+LM423XAf/aEaf9zezMgyrcwRjyMOu6QEXdKTlcjexHWPPCfrgNT
	4sc19KLE2pUx+slp6BUu9iaReuPWE4cEBR6M=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:mime-version:references:in-reply-to:from:date
	:message-id:subject:to:content-type; s=default; bh=ctQpZUfVLEryY
	0PT2+t85wOoOjU=; b=oodzKH5uXTSJNQM+veJJ7fVD+P6lIN6eOHTkAMcvlOYho
	p5NG63L3nBYjdxW6j8Z+RlLJaZ5UOTrZ9FDtZjFc0zM00GklEA23MOKTbnIwS7CF
	KstddjRsRVSACceiLXNVEapovUm3HkFOghTdxvk6KdgB3BimD7zlY28dWvCzlM=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com
Authentication-Results: sourceware.org; auth=none
X-Spam-SWARE-Status: No, score=-0.0 required=5.0 tests=BAYES_20,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.2 spammy=Multiple, Repin, ACL, acl
X-HELO: mail-oi1-f182.google.com
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;        d=kmcardiff-com.20150623.gappssmtp.com; s=20150623;        h=mime-version:references:in-reply-to:from:date:message-id:subject:to;        bh=E5gh0lSMmJBgv4u45nrTjomIsZnJKbW3p63dNGbnSao=;        b=mQPxeeyR/yNxpnvsSOUo8S/53uRptgx59Rz/coKvA2dq1NUdce0drBVGDWT4mUVBL6         CJMDe1t8an8EA0ee8K9pnhQ9eLmm62ELNSUfXaB5nNKP/7H4BEtoNYiHXPj6K+V6Yj/B         AtnBQpM8zkzF/0aW1qM2jyzjuSsPsgWIHOY8sY3KY6rrDJRo3zUeAt+32Cugc6YGSdZQ         wybtOqSnhczYp+Xwrs4CL6zmu8ikS77qbGCXO5V2ccebG80lrkAcAagrjeteBiq1nNsx         s4x3kaZGSm6/x9CovTaSNcWNWAS4CHLPpN9DOQ80r+xNEL4DH6BQSkkxtFGDGzuEa6rf         rAdg==
MIME-Version: 1.0
References: <CAOC2fq_WRuenwF+KqVYH=NM=QS_EA-XW3hri+edSzXAxC+F-6g@mail.gmail.com> <164597258.20181022013753@yandex.ru>
In-Reply-To: <164597258.20181022013753@yandex.ru>
From: Michael Enright <mike@kmcardiff.com>
Date: Sun, 21 Oct 2018 18:08:51 -0700
Message-ID: <CAOC2fq8U3u46d+oa1C4BO+rtG+0aEWCq0ZREAE_7S3XWFKe+gw@mail.gmail.com>
Subject: Re: Multiple problems (probably) starting up new installation
To: cygwin@cygwin.com
Content-Type: text/plain; charset="UTF-8"
X-IsSubscribed: yes

On Sun, Oct 21, 2018 at 3:50 PM Andrey Repin  wrote:
>
> I would actually suggest renaming the system user, if possible.

All my previous setups used a silly name like "Mike" that was not
linked to a Microsoft account but still chosen automatically, or my
preferred username "menright" if I noticed the chance to set the name
myself during initial Windows setup. These setups don't seem to have
been as difficult to get started with.

It seems like everyone who faces this (based on more extensive
searching starting from your suggestion to rename the account) ends up
creating a local account with a well-chosen name.  The data have to be
transferred from one account to the other if there is anything to
transfer. The advantages, if there are any, of a link to a Microsoft
account apparently can be achieved by linking the local account to the
desired Microsoft account  after the local account is set up. I don't
see anything about actually renaming the account.

This seems like a good place to start:
https://superuser.com/questions/1129165/how-to-rename-a-user-account-that-is-already-linked-to-a-microsoft-account

>
> > ----rwx---+ 1 menright Mike Enright     0 Oct 21 15:02 CMakeLists.txt
>
> the "+" says that there's extended ACL present. So, nothing odd.
>

The Windows view of this set of permissions (070 plus whatever is in
the rest of the ACL) seems to be that Windows programs can't do very
much with this file. So it's odd from that POV and I wonder if that
was caused by my renaming the "Cygwin account". Using cacls I see the
Windows username in some of the entries and I don't see the cygwin
username in any. I know that I can get a workable ACL with chmod but I
can see that executables built by the compiler are not executable,
either by name from cygwin bash or by double click from Windows
Explorer. This is the first few lines from cacls:
$ cacls moneymaker
C:\cygwin64\home\menright\moneymaker NULL SID:(DENY)(special access:)
                                              READ_CONTROL
                                              FILE_READ_EA
                                              FILE_WRITE_EA
                                              FILE_EXECUTE
                                              FILE_DELETE_CHILD

--
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

