From: Andrey Repin <anrdaemon@yandex.ru>
To: L A Walsh <cygwin@tlinx.org>, cygwin@cygwin.com
Subject: Re: Treating Junctions consistently, as "normal dirs" as w/linux "bind"-type mount
Date: Fri, 10 Mar 2017 13:20:00 -0000 [thread overview]
Message-ID: <212519238.20170310161723@yandex.ru> (raw)
In-Reply-To: <58C1795B.5010809@tlinx.org>
Greetings, L A Walsh!
> Andrey Repin wrote:
>> I would argue against all junctions being treated blindly.
>> The difference with bind mounts in Linux is that in Linux
>> you don't have the
>> information available within the filesystem itself, and have
>> no other option,
>> than to treat them as regular directories.
>> Only direct volume junctions cause an issue, and this is what
>> should be fixed,
>> if possible, not sidetracked with questionable workarounds.
> ----
> Could you describe the benefits of your proposed solution?
> You do know that MS originally called junctions "mountpoints",
> right? So why would cygwin treating them as such be a "questionable
> workaround"?
How they are called, and how they behave is a two different questions.
> How would you want to treat them?
Easy way: As symlinks, just like now, unless it's a volume mount point that
can't be normalized to a disk letter.
Preferred way: Fix volume mounts accessibility
\\?\{UUID} -> /dev/disk/by-uuid/UUID
--
With best regards,
Andrey Repin
Friday, March 10, 2017 16:10:57
Sorry for my terrible english...
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2017-03-10 13:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-15 15:30 Cannot access volumes mounted with 'mklink /d' which point to a volume UUID Matt D.
2017-02-16 0:59 ` L. A. Walsh
2017-02-16 9:26 ` Corinna Vinschen
2017-02-24 21:49 ` L. A. Walsh
2017-02-28 21:43 ` Corinna Vinschen
2017-03-02 21:43 ` showing all JUNCTIONS as normal dirs as w/linux --bind (was Re: Cannot access volumes mounted with 'mklink...) L. A. Walsh
2017-03-09 4:17 ` Treating Junctions consistently, as "normal dirs" as w/linux "bind"-type mount L. A. Walsh
2017-03-09 13:50 ` Andrey Repin
2017-03-09 15:48 ` L A Walsh
2017-03-09 16:41 ` Corinna Vinschen
2017-03-09 19:13 ` L A Walsh
2017-03-10 13:20 ` Andrey Repin [this message]
2017-02-16 14:05 ` Cannot access volumes mounted with 'mklink /d' which point to a volume UUID 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=212519238.20170310161723@yandex.ru \
--to=anrdaemon@yandex.ru \
--cc=cygwin@cygwin.com \
--cc=cygwin@tlinx.org \
/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).