public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Michael Enright <mike@kmcardiff.com>
To: cygwin@cygwin.com
Subject: Re: Multiple problems (probably) starting up new installation
Date: Mon, 22 Oct 2018 01:09:00 -0000	[thread overview]
Message-ID: <CAOC2fq8U3u46d+oa1C4BO+rtG+0aEWCq0ZREAE_7S3XWFKe+gw@mail.gmail.com> (raw)
In-Reply-To: <164597258.20181022013753@yandex.ru>

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

  reply	other threads:[~2018-10-22  1:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-21 22:25 Michael Enright
2018-10-21 22:50 ` Andrey Repin
2018-10-22  1:09   ` Michael Enright [this message]
2018-10-22 12:05     ` Andrey Repin
2018-10-22 14:43 ` cyg Simple

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=CAOC2fq8U3u46d+oa1C4BO+rtG+0aEWCq0ZREAE_7S3XWFKe+gw@mail.gmail.com \
    --to=mike@kmcardiff.com \
    --cc=cygwin@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).