From: Sam Edge <sam.edge.cygwin@gmx.com>
To: cygwin@cygwin.com
Subject: Re: objects created in a dir w/cygwin mangled perms; inherit no-access
Date: Tue, 24 Aug 2021 07:19:42 +0100 [thread overview]
Message-ID: <55097e53-ceed-f4b8-dbec-c6c9ab9570c8@gmx.com> (raw)
In-Reply-To: <6123F79C.5030809@tlinx.org>
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
next prev parent reply other threads:[~2021-08-24 6:19 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
2021-08-23 19:31 ` L A Walsh
2021-08-24 6:19 ` Sam Edge [this message]
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=55097e53-ceed-f4b8-dbec-c6c9ab9570c8@gmx.com \
--to=sam.edge.cygwin@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).