From: Martin Stromberg <Martin DOT Stromberg AT lu DOT erisoft DOT se>
Message-Id: <199911220950.KAA04920@propus.lu.erisoft.se>
Subject: Re: Symlinks...
To: djgpp-workers AT delorie DOT com (DJGPP-WORKERS)
Date: Mon, 22 Nov 1999 10:50:41 +0100 (MET)
In-Reply-To: <Pine.SUN.3.91.991121100931.25798K-100000@is> from "Eli Zaretskii" at Nov 21, 99 10:09:54 am
X-Mailer: ELM [version 2.4 PL24]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Reply-To: djgpp-workers AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk

Eli said:
> On Fri, 19 Nov 1999, Martin Stromberg wrote:
> 
> > Something hit me: will they work if a .ZIP is made containing symlinks
> > on a LFN aware platform and then unpacked on a non-LFN aware platform?
> > And vice versa?
> 
> I don't see any reason they won't, provided that the symlink is
> created with the long name.  Care to tell why did you think this might
> not work?

In this case it's the numerical tail that worries me. What will happen
when a user tries to follow it in plain DOZE (it was unzipped in
WINDOZE)?

> And vice versa? ;-)

This case will probably work. It would be hard to create a symlink to
a LFN when there aren't any. Or would it? What will happen if "ln -s
a_short.nam a_very_long_name.with.multiple_long_extensions" is done in plain
DOZE?


Pettersson, Symphony 7,

							MartinS