Date: Mon, 13 Sep 1999 13:46:56 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: Laurynas Biveinis <lauras AT softhome DOT net>
cc: DJGPP Workers <djgpp-workers AT delorie DOT com>
Subject: Re: Symlinks
In-Reply-To: <37DA2DB8.D849969E@softhome.net>
Message-ID: <Pine.SUN.3.91.990913134630.8923O-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
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


On Sat, 11 Sep 1999, Laurynas Biveinis wrote:

> If we decide to symlink executables like regular files
> I have a question for those who know DJGPP better -
> where in the library I should intercept symlinks to 
> exes and replace argv[0] of called programs to symlink
> names ?

The function direct_exec_tail in src/libc/dos/process/dosexec.c seems
to be the right place.  But there are others: whenever dosexec.c
invokes a non-DJGPP program, like COMMAND.COM, you need to resolve
links in program names as well.

> About symlink status - almost done, only exes, debugging
> and recompiling lots and lots of packages left.

It would be interesting to know how much does it slow down programs
like GNU Find and GNU Ls that stat files a lot.