Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com Message-Id: <4.3.1.2.20010926104927.016fb790@pop.ma.ultranet.com> X-Sender: lhall AT pop DOT ma DOT ultranet DOT com X-Mailer: QUALCOMM Windows Eudora Version 4.3.1 Date: Wed, 26 Sep 2001 10:57:46 -0400 To: "Keith Starsmeare" , From: "Larry Hall (RFK Partners, Inc)" Subject: Re: //c - Ouch! In-Reply-To: <000501c14699$b9d46690$5d754789@edinstonehaven> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" At 10:44 AM 9/26/2001, Keith Starsmeare wrote: >I just updated a colleagues cygwin and couldn't immediately figure out why >it was going so very slowly. The reason - //c references in the path. Every >time a command was issued that searched past that reference it would freeze >because it now scans the network. Ouch! > >Also, this opens the (remote) possibility of unscrupulous, twisted people >calling their machines 'C' to catch people out! > >I guess we knew this was going to happen, but I wish that there was a way to >temporarily issue some kind of big, unmissable warning somewhere! (But I'm >not volunteering, I can't think of where would be the best place - setup, >bash maybe?) The problems you state are exactly the reasons for removing this syntax for accessing drives. It's too dangerous and problematic. Larry Hall lhall AT rfk DOT com RFK Partners, Inc. http://www.rfk.com 118 Washington Street (508) 893-9779 - RFK Office Holliston, MA 01746 (508) 893-9889 - FAX -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/