This is the mail archive of the cygwin mailing list for the Cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Cannot access volumes mounted with 'mklink /d' which point to a volume UUID

On Feb 24 13:49, L. A. Walsh wrote:
> Corinna Vinschen wrote:
> > This type of directory symlink to a GUID volume path isn't supported
> > at all yet in Cygwin.
> As I mentioned, symlinks don't support volume destinations
> under windows, but Junctions should be used instead.  They
> half-way work under Cygwin (junctions to volumes look like
> mounted file systems look under linux, but junctions to
> pathnames get converted by cygwin to symlinks -- losing
> information when such junctions are restored.
> Corinna -- could you _please_ re-look at supporting both
> types of junctions as mount points?  Then Cygwin could have
> "mount-parity" with linux! ;-)

That's not easily possible.  Mount points in Cygwin are virtual entries
stored in the per-user session, in-memory mount table.  You can't easily
fetch all dir junctions on a volume, and the mount table is also
restricted in size.  Volume junctions look like mount points because the
device id changes below the reparse point, while they don't for dir
junctions to the same volume.  If you want them handled as mount points,
add the path as a Cygwin mount point to /etc/fstab or /etc/fstab.d/$USER


Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

Attachment: signature.asc
Description: PGP signature

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]