Date: Mon, 24 Nov 1997 13:44:53 +0200 (IST) From: Eli Zaretskii To: DJ Delorie cc: djgpp-workers AT delorie DOT com Subject: Corrections to `symlink' docs Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Precedence: bulk Robert's enhancements to `symlink' aren't documented. Here: *** src/libc/posix/unistd/symlink.t~0 Fri Sep 20 02:41:08 1996 --- src/libc/posix/unistd/symlink.txh Fri Nov 21 19:15:02 1997 *************** *** 11,29 **** MSDOS doesn't support symbolic links. However, DJGPP supports ``symlinks'' to DJGPP programs. This function simulates a symlink between two @file{.exe} files in the DJGPP style. It creates a program ! whose name is given by @var{*new} which, when run, will actually execute ! the program @var{*exists} passing it @var{*new} in @code{argv[0]} (some ! programs change their behavior depending on what's passed in ! @code{argv[0]}). The file referred to by @var{exists} doesn't really ! have to exist when this function is called. Both @var{*new} and ! @var{*exists} can point to a name with or without the @file{.exe} ! extension. ! Note that both @var{*exists} and @var{*new} must reside in the same directory (this is a restriction of the DJGPP ``symlinks''); the function will fail and set @code{errno} to @code{EXDEV} if they aren't. - Also note that this function does nothing to ensure that @var{*exists} - is actually a DJGPP program. This functions runs the @samp{stubify} and @samp{stubedit} programs, so they should be somewhere on your @samp{PATH} for the function to --- 11,32 ---- MSDOS doesn't support symbolic links. However, DJGPP supports ``symlinks'' to DJGPP programs. This function simulates a symlink between two @file{.exe} files in the DJGPP style. It creates a program ! whose name is pointed to by @var{new} which, when run, will actually ! execute the program @var{exists} passing it the string pointed by ! @var{new} in @code{argv[0]} (some programs change their behavior ! depending on what's passed in @code{argv[0]}). The file referred to by ! @var{exists} doesn't really have to exist when this function is called. ! If @var{exists} points to an @emph{existing} file, the function checks ! that it is a DJGPP executable; if not, the call will fail with ! @code{EXDEV}. ! Both @var{new} and @var{exists} can point to a name with or without the ! @file{.exe} extension. ! ! Note that both @var{exists} and @var{new} must specify file names which ! reside in the same directory (this is a restriction of the DJGPP ``symlinks''); the function will fail and set @code{errno} to @code{EXDEV} if they aren't. This functions runs the @samp{stubify} and @samp{stubedit} programs, so they should be somewhere on your @samp{PATH} for the function to