Message-Id: <200006082310.TAA31524@delorie.com> Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT sourceware DOT cygnus DOT com Delivered-To: mailing list cygwin-developers AT sourceware DOT cygnus DOT com From: "Parker, Ron" To: cygdev Subject: RE: [RFD]: Using a new feature of Win2K for symlinks Date: Thu, 8 Jun 2000 18:07:00 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2448.0) Content-Type: text/plain; charset="iso-8859-1" > > 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.