Re: Request for Junctions be treated consistently

2014-04-09 Thread Linda Walsh
Corinna Vinschen wrote: No, it's not. There's a major difference between mount points and symlinks, which is, mount points are handled inside the kernel, while symlinks are filesystem objects. Reparse points are very certainly filesystem objects. And bind mounts in Cygwin are handled in the "k

Re: Request for Junctions be treated consistently

2014-04-09 Thread Corinna Vinschen
On Apr 9 05:07, Linda Walsh wrote: > Forgive me if this posts a 2nd time, but I haven't seen it come > back after 6+ hours, so not sure where it went. > > Corinna Vinschen wrote: > > > >No, it's not. There's a major difference between mount points and > >symlinks, which is, mount points are hand

Re: Request for Junctions be treated consistently

2014-04-09 Thread Linda Walsh
Forgive me if this posts a 2nd time, but I haven't seen it come back after 6+ hours, so not sure where it went. Corinna Vinschen wrote: No, it's not. There's a major difference between mount points and symlinks, which is, mount points are handled inside the kernel, while symlinks are filesyste

Re: Request for Junctions be treated consistently

2014-04-08 Thread Linda Walsh
Corinna Vinschen wrote: . No, it's not. There's a major difference between mount points and symlinks, which is, mount points are handled inside the kernel, while symlinks are filesystem objects. Reparse points are very certainly filesystem objects. And bind mounts in Cygwin are handled in the

Re: Request for Junctions be treated consistently

2014-04-08 Thread Corinna Vinschen
On Apr 7 22:04, Andrey Repin wrote: > Greetings, Corinna Vinschen! > > >> I don't think your original concern is as big a problem as you > >> think, as is indicated by the above setup on linux. > >> > >> I.e. is there some other reason to not treat "linkd" mounts > >> the same as "mountvol" moun

Re: Request for Junctions be treated consistently

2014-04-07 Thread Christopher Faylor
On Tue, Apr 08, 2014 at 09:52:02AM +1000, Duncan Roe wrote: >On Mon, Apr 07, 2014 at 11:34:02AM -0700, Linda Walsh wrote: >> Corinna Vinschen wrote: >> >Look, directory reparse points are, by and large, symlinks to another, >> >real directory entry. The directory has a primary path, which is its >

Re: Request for Junctions be treated consistently

2014-04-07 Thread Duncan Roe
On Mon, Apr 07, 2014 at 11:34:02AM -0700, Linda Walsh wrote: > Corinna Vinschen wrote: > >Look, directory reparse points are, by and large, symlinks to another, > >real directory entry. The directory has a primary path, which is its > >own path under which it has been created, and the reparse poin

Re: Request for Junctions be treated consistently

2014-04-07 Thread Linda Walsh
Corinna Vinschen wrote: Look, directory reparse points are, by and large, symlinks to another, real directory entry. The directory has a primary path, which is its own path under which it has been created, and the reparse point is just a pointer to this directory. If that's not a symlink, what

Re: Request for Junctions be treated consistently

2014-04-07 Thread Andrey Repin
Greetings, Corinna Vinschen! >> I don't think your original concern is as big a problem as you >> think, as is indicated by the above setup on linux. >> >> I.e. is there some other reason to not treat "linkd" mounts >> the same as "mountvol" mounts -- in a manner equivalent to linux's >> 'bind' m

Re: Request for Junctions be treated consistently

2014-04-07 Thread Corinna Vinschen
On Apr 5 04:13, Linda Walsh wrote: > Corinna Vinschen wrote: > >On Apr 1 09:39, Linda Walsh wrote: > >>If I mount a device using mount vol in 2 different places, will they > >>have different device numbers the same? > > > >The same, just as on Linux. > --- > Why special case junctions creat

Re: Request for Junctions be treated consistently

2014-04-05 Thread Linda Walsh
Corinna Vinschen wrote: On Apr 1 09:39, Linda Walsh wrote: If I mount a device using mount vol in 2 different places, will they have different device numbers the same? The same, just as on Linux. --- Why special case junctions created with 'linkd' to return as symlinks but not 'mount

Re: Request for Junctions be treated consistently

2014-04-02 Thread Corinna Vinschen
On Apr 1 09:39, Linda Walsh wrote: > Corinna Vinschen wrote: > >On Mar 29 05:53, Linda Walsh wrote: > >>Linda Walsh wrote: > >>>If you use the 'mountvol' you a *local* root folder > >>>mounted at some drive letter that can be maintained over > >>>boots. is listed as a JUNCTION and treated by cygwi

Re: Request for Junctions be treated consistently

2014-04-01 Thread Linda Walsh
Corinna Vinschen wrote: On Mar 29 05:53, Linda Walsh wrote: Linda Walsh wrote: If you use the 'mountvol' you a *local* root folder mounted at some drive letter that can be maintained over boots. is listed as a JUNCTION and treated by cygwin as a regular dir. For some reason the other type of d

Re: Request for Junctions be treated consistently

2014-03-31 Thread Corinna Vinschen
On Mar 29 05:53, Linda Walsh wrote: > Linda Walsh wrote: > >If you use the 'mountvol' you a *local* root folder > >mounted at some drive letter that can be maintained over > >boots. is listed as a JUNCTION and treated by cygwin > >as a regular dir. > > > >For some reason the other type of directory

Re: Request for Junctions be treated consistently

2014-03-29 Thread Linda Walsh
Linda Walsh wrote: If you use the 'mountvol' you a *local* root folder mounted at some drive letter that can be maintained over boots. is listed as a JUNCTION and treated by cygwin as a regular dir. For some reason the other type of directory hookup made by "linkd" which also created a JUNKTION

Request for Junctions be treated consistently

2014-03-29 Thread Linda Walsh
If you use the 'mountvol' you a *local* root folder mounted at some drive letter that can be maintained over boots. is listed as a JUNCTION and treated by cygwin as a regular dir. For some reason the other type of directory hookup made by "linkd" which also created a JUNKTION vs. (mklink creating