DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 45C963858C2C
Subject: Re: objects created in a dir w/cygwin mangled perms; inherit no-access
References: <60E14AAA.4000404@tlinx.org> <514405575.20210704172015@yandex.ru>
 <60E460C7.7010203@tlinx.org> <685980612.20210707214357@yandex.ru>
 <60EFDD84.8040401@tlinx.org>
 <c6b5c350-18ba-f772-5284-2a27a84846d9@gmx.com>
 <6123F79C.5030809@tlinx.org>
To: cygwin@cygwin.com
Message-ID: <55097e53-ceed-f4b8-dbec-c6c9ab9570c8@gmx.com>
Date: Tue, 24 Aug 2021 07:19:42 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101
 Thunderbird/78.13.0
MIME-Version: 1.0
In-Reply-To: <6123F79C.5030809@tlinx.org>
Content-Language: en-GB
Precedence: list
From: Sam Edge via Cygwin <cygwin@cygwin.com>
Reply-To: Sam Edge <sam.edge.cygwin@gmx.com>
Content-Type: text/plain; charset="utf-8"; Format="flowed"
Errors-To: cygwin-bounces+archive-cygwin=delorie.com@cygwin.com
Sender: "Cygwin" <cygwin-bounces+archive-cygwin=delorie.com@cygwin.com>
Content-Transfer-Encoding: 8bit

On 23/08/2021 20:31, L A Walsh wrote:
 >
 > On 2021/07/15 01:23, Sam Edge via Cygwin wrote:
 >> (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.)
 > ---
 >     Except that at one point, most of the cygwin developers installed
cygwin at '/'.  That you don't know that shows how long you've
 > been using cygwin.

For the record, I've been using Cygwin for twenty years or more. For
that entire period the recommendation has been not to install in C:\ or
the root of any other drive. (I've been using UNIX since 1983 by the way
and Windows since version 3.0 not that it makes any difference to the
discussion.)

 >     I have other reasons for my setup.  My windows system has most
 > of my files on a remote, linux system.

Which can be accessed using //host/path (using S4NFS or SMB) or via
Cygwin fstab mounts regardless of where Cygwin is installed locally.

 > When I'm using the linux
 > shell, for example, I can bring up explorer for the directory I'm
 > in by typing 'explore [opt. path]'.  My Doc dir, among others is the
 > same on Windows as on Linux ~/Documents or /d/.  If I'm running
 > a prog on linux, and it asks for a browser, it launches my browser
 > on Windows.

You're not using a Linux shell. You're using a POSIX-like shell compiled
for Cygwin. It's different. For example '//path' on Cygwin accesses
remote filesystems whereas on Linux it doesn't.

If you're running a program on Linux it'll launch whatever it is
configured to launch.

If you're running a Cygwin program it'll do the same, which with
appropriate use of cygpath can launch Windows Explorer (explorer.exe) or
your browser. For example my EDITOR variable launches Notepad++ and 'git
difftool' launches Windows native KDiff3 and they work for any Cygwin
path not just my C drive, converting to Windows when assembling the
command line to pass to the native applications.

I think Andrey covered the rest of your arguments fairly comprehensively.

--
Sam Edge

-- 
Problem reports:      https://cygwin.com/problems.html
FAQ:                  https://cygwin.com/faq/
Documentation:        https://cygwin.com/docs.html
Unsubscribe info:     https://cygwin.com/ml/#unsubscribe-simple