Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-developers-subscribe AT sourceware DOT cygnus DOT com>
List-Archive: <http://sourceware.cygnus.com/ml/cygwin-developers/>
List-Post: <mailto:cygwin-developers AT sourceware DOT cygnus DOT com>
List-Help: <mailto:cygwin-developers-help AT sourceware DOT cygnus DOT com>, <http://sourceware.cygnus.com/ml/#faqs>
Sender: cygwin-developers-owner AT sourceware DOT cygnus DOT com
Delivered-To: mailing list cygwin-developers AT sourceware DOT cygnus DOT com
Message-ID: <39402CD9.AD09B7FE@vinschen.de>
Date: Fri, 09 Jun 2000 01:31:37 +0200
From: Corinna Vinschen <corinna AT vinschen DOT de>
Reply-To: cygdev <cygwin-developers AT sourceware DOT cygnus DOT com>
Organization: Cygnus Solutions, a Red Hat company
X-Mailer: Mozilla 4.73 [en] (X11; I; Linux 2.2.14 i686)
X-Accept-Language: de, en
MIME-Version: 1.0
To: "Parker, Ron" <rdparker AT butlermfg DOT com>
CC: cygdev <cygwin-developers AT sourceware DOT cygnus DOT com>
Subject: Re: [RFD]: Using a new feature of Win2K for symlinks
References: <E130BR5-00002p-00 AT mx03 DOT kundenserver DOT de>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

"Parker, Ron" wrote:
> 
> > > FWIW, this only works on local drive resources, but not to network
> > > directories.  That is a function of DFS.
> >
> > Right but this doesn't influence symlinks in Cygwin at all.
> > As I mentioned, my patch falls back if the reparse point
> > algorithm fails. This could be still tuned.
> 
> I know. It was just FYI for anyone that wasn't familiar with reparse points
> so they would have some idea of when this would come into play.  I guess I
> should have said that.
> 
> > > How about using IO_REPARSE_TAG_MOUNT_POINT tags to implement mount
> > > functionality for local resources on Windows 2000.  I know
> > its not as sexy
> > > as OS support for real symlinks, but it is a start.
> >
> > You already have that functionality thru logical drive
> > manager and that is transparent to all apps including Cygwin,
> > too. For that, we don't need to implement anything.
> 
> I didn't know if we wanted to use it for our mount facility on cygwin under
> Windows 2000.  I thought it might speed up the path handling.  It would at
> least push it to the operating system and under Windows 2000 we would have
> to check a path against fewer cygwin managed mounts.

Ah, you don't talk about volume mount points but about
directory symlinks which should be used instead of self
managed mount points in the registry, isn't it?

Hmm, this would be another nice feature. `mount' would check
the ability of the file system to manage reparse points and
`umount' would check if the given mount point is a reparse
point and it could use the reparse point code instead of the
registry in that case.

Good point.

Corinna

-- 
Corinna Vinschen
Cygwin Developer
Cygnus Solutions, a Red Hat company