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 Date: Tue, 23 Jul 2002 10:22:49 +0100 Message-ID: <4262-Tue23Jul2002102249+0100-starksb@ebi.ac.uk> From: David Starks-Browning MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: cygwin AT cygwin DOT com Subject: Re: Any gotcha's in moving cygwin? In-Reply-To: <3D3D149D.6E02BAE4@iee.org> References: <20020722235720 DOT GA4728 AT butch DOT jgcomp DOT com> <3D3D149D DOT 6E02BAE4 AT iee DOT org> On Tuesday 23 Jul 02, Don Sharp writes: > Despite the warnings from setup, I have been running a dedicated cygwin > drive with / as its top level for years without problems that weren't > subsequently cleared up. I think that there are two prerequisites > > 1) / shouldn't be at the top level of your windows drive > 2) The drive should be dedicated to the cygwin directory structure > > I believe that the problems of / at the root of the drive are seen as > arising when any of the above conditions are ignored. Long ago there was a genuine bug in Cygwin such that having / at C: would cause problems with certain commands. This has long since been fixed. The remaining problem with mounting C: as / is that some other application or package with UNIX-y origins might have an implicit equivalence between C: and /, creating C:/usr/bin (for example) and populating it. This would obviously cause problems. Even if you have no such conflict now, who knows what you might install in the future. Given that, I think Don's assessment is correct. Regards, David -- 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/