Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm
Sender: cygwin-owner@sources.redhat.com
Message-Id: <4.3.1.2.20010222165543.02f359a8@pop.ma.ultranet.com>
Date: Thu, 22 Feb 2001 16:57:04 -0500
To: "Robert Collins" <robert.collins@itdomain.com.au>, <cygwin@cygwin.com>
From: "Larry Hall (RFK Partners, Inc)" <lhall@rfk.com>
Subject: Re: [ANNOUNCEMENT]: Important change to symbolic 
  linkfunctionali ty
In-Reply-To: <023301c09d19$6de0b4c0$0200a8c0@lifelesswks>
References: <3A957332.FD98DFF6@ece.gatech.edu>
 <17B78BDF120BD411B70100500422FC6309E210@IIS000>
 <20010222184404.S908@cygbert.vinschen.de>
 <3A955952.6FF234D4@ece.gatech.edu>
 <20010222140454.F13561@redhat.com>
 <3A957332.FD98DFF6@ece.gatech.edu>
 <4.3.1.2.20010222155316.02f226c8@pop.ma.ultranet.com>
 <4.3.1.2.20010222163130.02f24e40@pop.ma.ultranet.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"

At 04:50 PM 2/22/2001, Robert Collins wrote:
>As I understand cygwin's tar's behaviour, it stores a file, with the
>symlink bit set in that tarball, and the content the path to the new
>file - just as gnu tar on linux does. then when it's extracted onto
>whatever platform, tar requests a symlink, and the platform takes care
>of creating a platform specific symlink.

OK, so this is effectively tar functionality.  Got it.  It just wasn't
clear to me what the mechanism for this was and where it came from.  I'm
educated now.

Thanks,


Larry Hall                              lhall@rfk.com
RFK Partners, Inc.                      http://www.rfk.com
118 Washington Street                   (508) 893-9779 - RFK Office
Holliston, MA 01746                     (508) 893-9889 - FAX


--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple