From: Doug Henderson <djndnbvg@gmail.com>
To: rainer-lists@emrich-ebersheim.de
Cc: cygwin <cygwin@cygwin.com>, Jon Turney <jon.turney@dronecode.org.uk>
Subject: Re: [ANNOUNCEMENT] Updated: setup (2.911)
Date: Thu, 30 Dec 2021 11:38:42 -0700 [thread overview]
Message-ID: <CAJ1FpuOESpovRZy1RN19df7EmaP4JdsOK9J7G7nx53Z_E+iAuQ@mail.gmail.com> (raw)
In-Reply-To: <38065ac8-19f1-6c9f-b2a1-a0796f1d126e@emrich-ebersheim.de>
On Thu, 30 Dec 2021 at 09:46, Rainer Emrich
<rainer-lists@emrich-ebersheim.de> wrote:
>
> Hi Jon,
> for me the new setup executables do not work, same for both:
In my analysis, setup is reporting for a non-elevated shell:
$ ./setup-x86_64
User has NO backup/restore rights
User has symlink creation right
note: Hand installation over to elevated child process.
for an elevated shell:
$ ./setup-x86_64
Starting cygwin install, version 2.911
User has backup/restore rights
User has symlink creation right
*** --symlink-type native requires SeCreateSymbolicLink privilege or
'Developer Mode'
I went through C:\Windows\System32\gpedit.msc to add the "admin" user
to have the "Create symbolic links" permission. (I had previously
given this permission to my user account)
I do not have 'Developer Mode' enabled as it is overkill unless necessary.
I suspect that setup-x86_64.exe is not correctly checking for the
"SeCreateSymbolicLink" and/or "Create symbolic links" permission.
Doug
--
Doug Henderson, Calgary, Alberta, Canada - from gmail.com
next prev parent reply other threads:[~2021-12-30 18:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-29 15:58 Jon Turney
2021-12-30 16:45 ` Rainer Emrich
2021-12-30 17:38 ` Jon Turney
2021-12-30 18:31 ` Rainer Emrich
2021-12-30 19:04 ` Rainer Emrich
2021-12-30 18:38 ` Doug Henderson [this message]
2021-12-31 14:38 ` Jon Turney
2021-12-31 15:02 ` Rainer Emrich
2022-01-01 14:15 ` © Fxzx mic
2022-01-01 15:14 ` Marco Atzeri
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=CAJ1FpuOESpovRZy1RN19df7EmaP4JdsOK9J7G7nx53Z_E+iAuQ@mail.gmail.com \
--to=djndnbvg@gmail.com \
--cc=cygwin@cygwin.com \
--cc=jon.turney@dronecode.org.uk \
--cc=rainer-lists@emrich-ebersheim.de \
/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).