From: Sam Edge <sam.edge@gmx.com>
To: cygwin@cygwin.com
Subject: Re: objects created in a dir w/cygwin mangled perms; inherit no-access
Date: Thu, 15 Jul 2021 09:23:39 +0100 [thread overview]
Message-ID: <c6b5c350-18ba-f772-5284-2a27a84846d9@gmx.com> (raw)
In-Reply-To: <60EFDD84.8040401@tlinx.org>
On 15/07/2021 08:02, L A Walsh wrote:
>
>
> On 2021/07/07 11:43, Andrey Repin wrote:
>>
>>> Sorta, actually the cygtree mounted at 'C:\'.
>>
>> Ugh. Been there twenty years ago. Had a lot of unexpected issues and
>> finally opted out of it.
>
> If you have ever boot to a rescue system running from
> your hard drive -- you have the choice of using all your cygwin
> tools to recover your system, or to just use Windows tools.
>
After wading through the unsolicited self-congratulation a few observations.
1. You want support from the Cygwin community for problems you're having
despite having installed it in a way that is expressly discouraged.
(https://cygwin.com/faq.html#faq.setup.c) Good luck with that.
2. You've not bothered to search the archives or even read the manual,
specifically https://cygwin.com/cygwin-ug-net/ntsec.html#ntsec-files but
instead immediately assume a flaw in the code. Not very scientific ...
or polite.
(By the way, the permission workaround is another good reason for not
installing in system root if advice from the authors of Cygwin - Corinna
et al - isn't enough for you.)
3. Installing Cygwin under, say, C:\cygwin64 does not prevent you from
using it for recovery.
PEBCAK
--
Sam Edge
next prev parent reply other threads:[~2021-07-15 8:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-04 5:44 L A Walsh
2021-07-04 14:20 ` Andrey Repin
2021-07-06 13:55 ` L A Walsh
2021-07-07 18:43 ` Andrey Repin
2021-07-15 7:02 ` L A Walsh
2021-07-15 8:23 ` Sam Edge [this message]
2021-08-23 19:31 ` L A Walsh
2021-08-24 6:19 ` Sam Edge
2021-07-16 4:44 ` Andrey Repin
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=c6b5c350-18ba-f772-5284-2a27a84846d9@gmx.com \
--to=sam.edge@gmx.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).