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 From: To: Subject: RE: Why not mount / at C: ? Date: Thu, 24 Aug 2000 16:19:06 -0700 Message-ID: <001401c00e21$b2b9bb00$5c8e42d8@raptor> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 In-reply-to: <200008241243.OAA00184@dphdse.saclay.cea.fr> X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Importance: Normal > Anyway, the risk of confusion, that you mention, between packages > seems very low : it's very unlikely to find c:/bin, c:/lib, > c:/home ... in a pure Windows installation. Usually Win stuff > goes into C:\Program Files, or c:\WINNT. Moreover, being an > experienced Unixian, I ( generally ;) realize what are the > files I'm manipulating ! It would be nice if that were so, but I need to point out that in my experience, it has just not necessarily been the case. I have worked on a surprising number of systems that have had exactly that convention installed on the Windows Drive. A fair amount of Windows software ignores convention, and installs itself that way. The simple fact is that a lot of Windows programmers learned to program in UN*X first, and still do things the way they started. Cheers, ~Neil -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com