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 Message-ID: <39402CDC.C6A5E6A9@vinschen.de> Date: Fri, 09 Jun 2000 01:31:40 +0200 From: Corinna Vinschen 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" CC: cygdev , cygdev Subject: Re: [RFD]: Using a new feature of Win2K for symlinks References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit "Parker, Ron" wrote: > > > > > - The IO_REPARSE_TAG_SYMBOLIC_LINK is nice but completely useless > > > > at the moment or on a base W2K system (I don't know exactly). > > > > > I have checked that out last weekend. We would be able to use > > that as another method for implementing symlinks to regular files. > > Would be no problem but would have no sense, too, because that > > symlinks would be only visible for Cygwin apps. And we already > > have a solution for non transparent symlinks... > > The only sense there would be in using it is that on Windows 2000 our > symlinks would interoperate with non-cygwin Windows applications. However > this falls victim to the doesn't look like a symlink across a network share > I mentioned before. But as I wrote in my last mail, you don't have that problem. They are simple directories for other machines in the network. So it's transparent, too. Really, I tried that two days ago with a NT4 and a W98 client. Corinna -- Corinna Vinschen Cygwin Developer Cygnus Solutions, a Red Hat company