Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com From: "Dave Korn" To: Subject: RE: Executable links? Date: Wed, 12 May 2004 10:38:48 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit In-Reply-To: <40A135C5.9060708@cs.york.ac.uk> Message-ID: X-OriginalArrivalTime: 12 May 2004 09:38:48.0710 (UTC) FILETIME=[ED659A60:01C43804] > -----Original Message----- > From: cygwin-owner On Behalf Of chris > Sent: 11 May 2004 21:21 > 4) Replace links to executables with a very small executable > which does > the linking process. I've been experimenting a little with > this and it > doesn't seem like a bad idea, except a) it involves hacking where you > want to link to into the executable (not too bad), b) the > shortcut is no > longer reckonised by ls / ln / etc (would this be hard to > fix?) and c) I > can't make a cygwin executable <10kish (this is still not that large, > and I'm sure someone better than me could make it smaller. > > Any comments / suggestions? 4) seems to me not worth the effort. It works for executables but isn't any use for any other filetype at all; it only works for executing those executables, not for reading them as ordinary files or ls'ing or rm'ing them; it seems like a bad kludge that introduces a lot of complications in exchange for which it only solves one limited case of one limited aspect of the general problem. cheers, DaveK -- Can't think of a witty .sigline today.... -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/