Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , 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: <00bc01c3401c$9f0a7330$9b67883e@pomello> From: "Max Bowsher" To: "Mark R." , References: <200307012134 DOT h61LYMpK002558 AT ares DOT cs DOT Virginia DOT EDU> Subject: Re: Why do symlinks need to be system files Date: Tue, 1 Jul 2003 23:03:34 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 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. Max. -- 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/