Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
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:	Wed, 15 Dec 2004 13:37:50 -0500
From:	Christopher Faylor <cgf-no-personal-reply-please AT cygwin DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: Managed mount point question(s)?
Message-ID:	<20041215183750.GC15175@trixie.casa.cgf.cx>
Reply-To:	cygwin AT cygwin DOT com
References:	<0I8S00AE208UJM AT pmismtp02 DOT mcilink DOT com>
Mime-Version:	1.0
In-Reply-To:	<0I8S00AE208UJM@pmismtp02.mcilink.com>
User-Agent:	Mutt/1.4.1i

On Wed, Dec 15, 2004 at 11:19:42AM -0700, Mark Paulus wrote:
>In general, does it make sense to mount c:/cygwin as
>/ in managed mode?

No.

>Is there some reason this would not be a good idea?

Since you are supposed to first create an empty directory, then mount it
as managed mount, and then populate it, it doesn't make sense to do this
with the cygwin directory unless you want to first create a normal cygwin
directory, then create a managed directory and then move everything from
the cygwin directory to it.

Mounting a non-empty directory as managed is asking for trouble.

cgf

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -