Re: Treating Junctions consistently, as "normal dirs" as w/linux "bind"-type mount
- Date: Thu, 09 Mar 2017 11:13:49 -0800
- From: L A Walsh <cygwin@xxxxxxxxx>
- Subject: Re: Treating Junctions consistently, as "normal dirs" as w/linux "bind"-type mount
Corinna Vinschen wrote:
He's right. The mount point handling in Cygwin is based on the
in-memory mount table.
I'm not wanting a mount point fake. Just wanting it to look
like a normal dir just like the mountvol-junctions.
There's no reasonable way to fake some
reparse point to look like a mount point. We can either handle it
as normal dir, or as symlink. Handling it as normal dir is
problematic in terms of find/rsync
T All of the core utils are loop-protected in that respect.
same-dev file systems already exist on linux and cygwin.
File system loops are already present just using mountvol:
/mountedVol> mkdir remounted
# note, next "2" lines are really 1 wrapped line:
/mountedVol> mountvol remounted
So the same volume is mounted at C:\mountedVol and at
etc, bacause the cross-device
check would fail and files are potentially visited multiple times.
That isn't what happens right now with mountvol:
/> find mountedVol/ -type d
find: File system loop detected; ‘mountedVol/remounted’ is part of the
same file system loop as ‘mountedVol/’.
mountedVol/System Volume Information
I.e. 'find' (and other coreutils) detect the loop even though
they are the same file system.
Sure, you can find program(s) that are broken and don't detect
such loops, but at least the core utils do check -- and besides,
no one HAS to create junctions -- they can use symlinks as they do
today and no risk of such problems.
But treating linkd-junctions the same as mountvol-junctions allows
those bind-style mounts that are supported on linux and Windows
to be supported on Cygwin.
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple