delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/2003/07/02/08:42:59

Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/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
Message-Id: <200307021242.h62CgfpK019230@ares.cs.Virginia.EDU>
From: "Mark R." <mcr2z AT cs DOT virginia DOT edu>
To: "'Gary R. Van Sickle'" <g DOT r DOT vansickle AT worldnet DOT att DOT net>,
<cygwin AT cygwin DOT com>
Subject: RE: Why do symlinks need to be system files
Date: Wed, 2 Jul 2003 08:42:41 -0400
MIME-Version: 1.0
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
In-Reply-To: <NCBBIHCHBLCMLBLOBONKKENMEEAA.g.r.vansickle@worldnet.att.net>

That does make sense. I've played around with using ln -s to create my own
symlinks. The odd thing is that these are all being created as shortcuts vs
this other method. Now that I'm in the "I'm just curious" mode - Does anyone
know why  the two different methods are used?

-Mark
 

-----Original Message-----
From: cygwin-owner AT cygwin DOT com [mailto:cygwin-owner AT cygwin DOT com] On Behalf Of
Gary R. Van Sickle
Sent: Wednesday, July 02, 2003 1:37 AM
To: cygwin AT cygwin DOT com
Subject: RE: Why do symlinks need to be system files

> Mark R. wrote:
> > Hello,
> >
> > I've been busy attempting to use WinInstaller LE to create an MSI 
> > package of cygwin so we can automatically deploy a customized build 
> > for our department. This works for the most part, however when I 
> > deploy this to a windows XP machine, all of the symlinks are broken. 
> > Ex/ vi doesn't work, however vim does.
> >
> > When I tracked down the problem, it appears that symlinks require 
> > the "system file" attribute to be set. Does anyone know why this is?
>
> Because that's part of how Cygwin recognizes them as symlinks.

To expand on that a bit, it's so Cygwin doesn't have to open and parse the
actual contents of every file it sees on a path to see if it's a symlink; it
only has to check those marked as system.  Since it's rare to find many
files marked system normally, this results in mega-savings speedwise.

Now if Microsoft would only get hip to this whole symlink thing....

--
Gary R. Van Sickle
Brewer.  Patriot.


--
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/

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019