Message-ID: <37C021D1.46CF6EC@softhome.net>
Date: Sun, 22 Aug 1999 18:14:09 +0200
From: Laurynas Biveinis <lauras AT softhome DOT net>
X-Mailer: Mozilla 4.61 [en] (Win98; I)
X-Accept-Language: lt,en
MIME-Version: 1.0
To: djgpp-workers AT delorie DOT com
Subject: Re: Real symlinks for DJGPP?
References: <199908221345 DOT PAA00707 AT father DOT ludd DOT luth DOT se>
Content-Type: text/plain; charset=iso-8859-4
Content-Transfer-Encoding: 7bit
Reply-To: djgpp-workers AT delorie DOT com

Martin Str|mberg wrote:
> 
> Laurynas said:
> > 1) symlink function creates a new file and writes path to
> > linked file here. To avoid clashes between symlink and
> > non-symlink files, it should have prefix and postfix, e.g.
> > two ASCII chars from 0-31 or 128-255, string 'DJGPP symlink',
> > path itself, newline, 'DJGPP symlink'.
> 
> Nice. Are the WINDOZE shortcuts equivalent to symlinks? If so perhaps
> that format should be used?

That format is little bit overkill for DJGPP symlink - it
contains fields about icons, hot keys for accessing, 16 bytes
for GUID, network info, volume info and so on, and so on...  
I think my suggestion is better because it is simpler.

Maybe it is good idea to add their support in open(), but
symlink() should not generate them.

> (
> > I'm waiting for advices. In fact, I've started writing
> > some code.
> 
> Well, _are_ you waiting for advice or not?)

:) I'm writing code and accepting advices.

Laurynas Biveinis