X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f
X-Recipient: djgpp AT delorie DOT com
Date: Sun, 16 Aug 2020 17:35:28 +0300
Message-Id: <83k0xyirpr.fsf@gnu.org>
From: "Eli Zaretskii (eliz AT gnu DOT org) [via djgpp AT delorie DOT com]" <djgpp AT delorie DOT com>
To: djgpp AT delorie DOT com
In-Reply-To:
	<CALPW7mThGYONxqrBoX865aD537-g3rMxDBjNGep0AC8qb0J0bA AT mail DOT gmail DOT com>
	(djgpp AT delorie DOT com)
Subject: Re: Symlinks with executable extensions (suffixes)
References: <CALPW7mSjUHyEefptCgD34HfB4RaG60untb-e4uK9Un9XmO2Abg AT mail DOT gmail DOT com>
 <83wo1ziwex DOT fsf AT gnu DOT org> <CALPW7mThGYONxqrBoX865aD537-g3rMxDBjNGep0AC8qb0J0bA AT mail DOT gmail DOT com>
Reply-To: djgpp AT delorie DOT com

> From: "A. Wik (awik32 AT gmail DOT com) [via djgpp AT delorie DOT com]" <djgpp AT delorie DOT com>
> Date: Sun, 16 Aug 2020 08:01:13 +0000
> 
> > > What can I do about DJGPP-symlinks getting accidentally executed (eg.
> > > by COMMAND.COM) as binary executables because they have .exe or .com
> > > extensions?  It can easily hang the machine.
> >
> > Don't create symlinks with those extensions?
> 
> I don't do it deliberately.  They are created by eg. "make install".

I guess some porting is required of those Makefiles.

> > DJGPP already has an alternative mechanism for "links" to its
> > executables (via 'stubedit'), which avoids this problem.  Would it
> > solve the problem to use that alternative for links to executables?
> 
> Partially.  But then "ls" won't list them as links, right?

It won't, correct.