X-Spam-Check-By: sourceware.org
To: cygwin AT cygwin DOT com
From: mwoehlke <mwoehlke AT tibco DOT com>
Subject:  Re: cygwin, Coda and symbolic links
Date:  Thu, 03 Aug 2006 17:57:29 -0500
Lines: 36
Message-ID: <eatv0p$noo$1@sea.gmane.org>
References:  <44D27B36 DOT 1090400 AT andrew DOT cmu DOT edu>
Mime-Version:  1.0
Content-Type:  text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding:  7bit
User-Agent: Thunderbird 1.5.0.5 (X11/20060719)
In-Reply-To: <44D27B36.1090400@andrew.cmu.edu>
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

Adam Wolbach wrote:
> I'm a new subscriber looking to get some information relevant to the 
> Coda File System development at Carnegie Mellon University, which uses 
> cygwin as a platform to run on Windows 2000/WinXP. We rely heavily on 
> symbolic links for a number of different features, most significantly 
> representing conflicts within the file system. Conflicts are 
> inconsistent file system objects which are represented as "dangling" or 
> "broken" symlinks pointing to the file identifier of the inconsistent 
> object, e.g., if "foo" fell into conflict:
> 
> [host]# ls -l foo
> lr--r--r-- 1 root nfsnobody [date/time] foo -> 
> @xxxxxxxx DOT yyyyyyyy DOT zzzzzzzz AT realmname
> 
> Coda's current symlink support in cygwin is nonexistent, but we are 
> looking to support symlinks in the same manner cygwin appears to -- as 
> special Windows shortcuts that cygwin can interpret as symlinks. 
> Allowing cygwin to see our conflicts as broken symlinks would be a big 
> win for our repair mechanisms. We looked at the internals of a Windows 
> .lnk shortcut file and (of course) part appears binary; we assume 
> somewhere along the line that the cygwin developers reverse-engineered 
> the contents of these files to hijack them for their own purposes.
> 
> First question, I've hunted for this information around the website, in 
> the past mailing-list archives and the web, and it doesn't appear 
> readily available. Is there anyone on the list who knows more about the 
> internals of Windows shortcuts and could clue the Coda developers in? 
> Also, how these shortcuts should be crafted to appear as symlinks to 
> cygwin?

Maybe you could look at Cygwin's source code where it writes .lnk files? 
Or don't bother, link against Cygwin, and use "symlink()".

-- 
Matthew
And now back to your regularly scheduled e-mail.


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/