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: Wed, 15 Dec 2004 13:37:50 -0500 From: Christopher Faylor 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 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline 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/