Mailing-List: contact cygwin-apps-help AT cygwin DOT com; run by ezmlm Sender: cygwin-apps-owner AT cygwin DOT com List-Subscribe: List-Archive: List-Post: List-Help: , Mail-Followup-To: cygwin-apps AT cygwin DOT com Delivered-To: mailing list cygwin-apps AT cygwin DOT com content-class: urn:content-classes:message Subject: RE: ITP: netpbm MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Sun, 28 Apr 2002 03:40:33 +1000 X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: From: "Robert Collins" To: "Charles Wilson" , "Gareth Pearce" Cc: Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id g3RHeau21352 > -----Original Message----- > From: Charles Wilson [mailto:cwilson AT ece DOT gatech DOT edu] > Sent: Sunday, April 28, 2002 2:46 AM ... > But cygwin is used on > both NTFS and > FAT... Which is the killer question: is adding a directory to the search path more or less of a performance hog than adding x-100 .exes and/or .dll's to the /usr/bin directory. And will the inevitable 'my dos script can't find netpbm foobar tool' questions be worth it? Well my system32 directory here has 1971 files. Adding a coupla hundred optional files doesn't seem all that bad to me. And hey, if FAT is too slow, folk can always install the windows ext2 driver. Rob