Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com Date: Thu, 22 Feb 2001 21:53:26 +0100 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: [ANNOUNCEMENT]: Important change to symbolic link functionali ty Message-ID: <20010222215326.A908@cygbert.vinschen.de> Mail-Followup-To: cygwin AT cygwin DOT com References: <17B78BDF120BD411B70100500422FC6309E210 AT IIS000> <20010222184404 DOT S908 AT cygbert DOT vinschen DOT de> <3A955952 DOT 6FF234D4 AT ece DOT gatech DOT edu> <20010222140454 DOT F13561 AT redhat DOT com> <3A957332 DOT FD98DFF6 AT ece DOT gatech DOT edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3A957332.FD98DFF6@ece.gatech.edu>; from cwilson@ece.gatech.edu on Thu, Feb 22, 2001 at 03:14:42PM -0500 On Thu, Feb 22, 2001 at 03:14:42PM -0500, Charles S. Wilson wrote: > Here's the FAQ entry: > > --------------------------------- > My symlinks seem to point to different locations when accessed via > Explorer/DOS or BASH. > > Symlinks contain both a dos path and a cygwin path. The cygwin path is > interpreted using the current mount table every time the symlink is > accessed from a cygwin program. The dos path is determined from the > cygwin path ONLY AT SYMLINK CREATION. So, if you have changed your > mount tables > after creating the symlinks, it is possible that the internal dos path > and the cygwin path are 'out of sync'. To fix this, you can run the > "fix-symlinks" program -- but be prepared for a long wait...it takes a > while. > > fix-symlinks / Nice :-) > --------------------------------- > I just thought of another problem though -- if I put together a distro > tarball that contains symlinks, the dos paths will match MY system, and > not the user's system. Unless part of the postinstall script is to run > fix-symlinks on the symlinks included in the installed package... No. Obviously not. Since Cygwin tar reads and saves the POSIX path in the tarball, it is absolutely correctly recreated when unpacked on the target system even when the links are absolute links, say /usr/include/foo or alike. Consider - it's _not_ the *.lnk file which is saved in the tarball but the attribute to be a symlink. You would be right in case of using WinZip when creating an archive. But that's unfair because it's only a native Windows tool... Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Developer mailto:cygwin AT cygwin DOT com Red Hat, Inc. -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple