Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin AT sources DOT redhat DOT com
Message-Id: <4.2.0.58.20000826224239.00996250@pop.jump.net>
X-Sender: gwalker AT pop DOT jump DOT net (Unverified)
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 
Date: Sat, 26 Aug 2000 22:55:32 -0500
To: <cygwin AT sourceware DOT cygnus DOT com>
From: Gregory Walker <gwalker AT jump DOT net>
Subject: RE: Why not mount / at C: ? 
In-Reply-To: <001401c00e21$b2b9bb00$5c8e42d8@raptor>
References: <200008241243 DOT OAA00184 AT dphdse DOT saclay DOT cea DOT fr>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed


> > 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.

Though I am a Cygwin newbie, I have developed software for 20 years
on Unix, embedded processors, Vax/VMS, and currently on Windows.
 From my experience, mounting Cygwin root at C: is to invite disaster.
The common Windows experience is to have the regsitry or DLL "pool"
corrupted by some rogue installation that "breaks" other programs.
Keeping Cygwin in a separate directory tree makes it a reliable,
self-contained subsystem.

My two-cents worth. :-)

Gregory Walker           gwalker AT jump DOT net


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com