From:	Martin Stromberg <Martin DOT Stromberg AT lu DOT erisoft DOT se>
Message-Id:	<200008221352.PAA27753@lws256.lu.erisoft.se>
Subject:	Re: Patch to features.txi about symlink
To:	djgpp-workers AT delorie DOT com
Date:	Tue, 22 Aug 2000 15:51:57 +0200 (MET DST)
In-Reply-To:	<39A272B2.D1810EB5@softhome.net> from "Laurynas Biveinis" at Aug 22, 2000 02:31:46 PM
X-Mailer:	ELM [version 2.5 PL3]
MIME-Version:	1.0
Reply-To:	djgpp-workers AT delorie DOT com
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	djgpp-workers AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

English is not my native language, so I might be wrong.

> Index: features.txi
> ===================================================================
> RCS file: /cvs/djgpp/djgpp/src/docs/kb/features.txi,v
> retrieving revision 1.2
> diff -u -r1.2 features.txi
> --- features.txi	1999/05/12 10:36:51	1.2
> +++ features.txi	2000/08/22 12:27:02
> @@ -273,10 +273,16 @@
>  @cindex Symlinks, emulation
>  DOS doesn't support hard and symbolic links.  However, @sc{djgpp}
>  emulates them to some extent.  The @code{link} library function
> -simulates hard links by copying.  The @code{symlink} library function
> -simulates a symbolic link for executable programs only, by creating a
> -2KB stub which is set up to run the COFF image from the target of the
> -link.  Thus, @samp{ln -s grep fgrep} does what you'd expect.
> +simulates hard links by copying.  Symbolic links are fully emulated by most 
> +file handling functions in the library.  Also, symlink support API you would 
... API _that_ you would ...

> +expect find only on UNIX (such as @code{readlink}) is present. Function 

... expect to find only ...

> +@code{symlink} creates files with special size and format which are 
> +transparently to user recognized by other library functions.  Because DOS 

Remove "to user"?


Right,

						MartinS

- Raw text -