Sender: root AT delorie DOT com
Message-ID: <37C1619D.28A46850@inti.gov.ar>
Date: Mon, 23 Aug 1999 11:58:37 -0300
From: salvador <salvador AT inti DOT gov DOT ar>
Organization: INTI
X-Mailer: Mozilla 4.6 [en] (X11; I; Linux 2.0.36 i686)
X-Accept-Language: es-AR, en, es
MIME-Version: 1.0
To: djgpp-workers AT delorie DOT com
Subject: Re: Real symlinks for DJGPP?
References: <37BFECBA DOT 57BFBD27 AT softhome DOT net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Reply-To: djgpp-workers AT delorie DOT com

Laurynas Biveinis wrote:

> Hello,
>
> Are there any obstacles for implementing real symlinks for
> DJGPP using regular files? I think that -
>
> 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'.
>
> 2) open function checks for symlink file format, and if
> the file appears to be symlink, open real file instead.

It should call the function in a "recursive way" so symlinks to symlinks works
OK.
I thinked about it in the past but never had time to experiment and see the real
world problems.
What about using some special attributes? like System+Read-Only or something
like that.

SET

--
Salvador Eduardo Tropea (SET). (Electronics Engineer)
Visit my home page: http://welcome.to/SetSoft or
http://www.geocities.com/SiliconValley/Vista/6552/
Alternative e-mail: set-soft AT usa DOT net set AT computer DOT org
                    set AT ieee DOT org set-soft AT bigfoot DOT com
Address: Curapaligue 2124, Caseros, 3 de Febrero
Buenos Aires, (1678), ARGENTINA Phone: +(5411) 4759 0013