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: <200307012134.h61LYMpK002558@ares.cs.Virginia.EDU>
From: "Mark R." <mcr2z AT cs DOT virginia DOT edu>
To: <cygwin AT cygwin DOT com>
Subject: Why do symlinks need to be system files
Date: Tue, 1 Jul 2003 17:34:22 -0400
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mimeole: Produced By Microsoft MimeOLE V6.00.2800.1165

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? Windows XP
appears to be removing the System flag on my install.

Has anyone else built an MSI of cygwin using WinInstall LE (the free version
that comes with windows 2000) where the symlinks work successfully when
installed under Windows XP?

-Mark R
University of Virginia


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