From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin-apps@cygwin.com
Subject: Re: [Bug] setup regression #2
Date: Wed, 09 Nov 2022 19:25:26 +0100 [thread overview]
Message-ID: <875yfokmsp.fsf@Rainer.invalid> (raw)
In-Reply-To: <8a811ecf-38e7-a631-c09e-92ca4d439cc2@dronecode.org.uk> (Jon Turney's message of "Tue, 8 Nov 2022 16:21:44 +0000")
Jon Turney writes:
> On 08/10/2022 17:56, Achim Gratz wrote:
>> I think that setup was essentially treating the install as "for this
>> user only" since it was created and maintained by a script that can't
>> affect that option and the fact it was also in group Adminsitroators
>> didn't actually register until now.
>
> Yeah, that seems possible, since some of these changes fix what are
> arguably bugs in how that works (i.e. I suspect that previously, even
> when elevated, if only the registry key
> HKEY_CURRENT_USER\\Software\\Cygwin\\setup\rootdir exists (and not the
> same key under HKLM), we're going to install for "Just Me",
> irrespective of what the UI says)
I haven't checked that.
>> The DACL on the server install changed from conferring access to "Everyone" to
>> just the install user and SYSTEM IIRC. It doesn't do that on the
>> (non-domain) build machine at home that runs Win10 Pro.
>
> That makes less sense to me. We should always creating an entry in
> the DACL for 'Everyone' to hold the POSIX permissions for 'other'
> users.
Well, it wasn't there and whichever way it ended up that way, it was an
inconvenient enough fix that I don'*t want to try it again on a
productive system.
> I wrote some code for this option (attached), but I have a hard time
> seeing how it's functionally different from using '-B/'--no-admin'.
>
> So, I guess a question is, does running with that option work as
> expected in your problematic instance?
I'm not having enough time for checking right now, but I might test this
hypothesis later on.
Regard,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
SD adaptation for Waldorf Blofeld V1.15B11:
http://Synth.Stromeko.net/Downloads.html#WaldorfSDada
next prev parent reply other threads:[~2022-11-09 18:25 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-22 17:14 Achim Gratz
2022-10-01 15:37 ` Jon Turney
2022-10-03 19:23 ` Achim Gratz
2022-10-08 15:18 ` Jon Turney
2022-10-08 16:56 ` Achim Gratz
2022-11-08 16:21 ` Jon Turney
2022-11-09 18:25 ` Achim Gratz [this message]
2022-11-13 12:47 ` Achim Gratz
2022-11-20 17:16 ` Jon Turney
2022-11-20 19:05 ` Achim Gratz
2022-11-21 12:32 ` Corinna Vinschen
2022-11-21 12:39 ` ASSI
2022-11-21 12:47 ` Corinna Vinschen
2022-11-29 21:37 ` Jon Turney
2022-11-30 21:22 ` Christian Franke
2022-12-01 19:50 ` Achim Gratz
2023-02-02 16:00 ` Jon Turney
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=875yfokmsp.fsf@Rainer.invalid \
--to=stromeko@nexgo.de \
--cc=cygwin-apps@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).