X-Recipient: archive-cygwin@delorie.com X-SWARE-Spam-Status: No, hits=-2.8 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_LOW X-Spam-Check-By: sourceware.org Mime-Version: 1.0 (Apple Message framework v753.1) In-Reply-To: <20100304114902.GC7980@calimero.vinschen.de> References: <20100304094847.GZ17293@calimero.vinschen.de> <20100304114902.GC7980@calimero.vinschen.de> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Alfred von Campe Subject: Re: Strange symlink behaviour Date: Tue, 9 Mar 2010 10:11:38 -0500 To: cygwin@cygwin.com X-IsSubscribed: yes Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Here is an update from my experiments (sorry for the delay). As Corinna explained, symlinks created in Cygwin are only recognized by Cygwin, so what I wanted to do wasn't really possible. However, we still wanted to be able to update the share from Windows (a GUI application was written for the operator to update the share when a new release is available), so I really wanted to figure out a way to make this work on Windows. The solution was to use hard links in the tar file (which doesn't use up any more space), and when it was untar'ed on Windows, everything worked as expected. Thanks for all the help, Alfred -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple