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: Thu, 10 Jul 2003 10:19:18 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: mount managed warnings! Message-ID: <20030710141918.GA1208@redhat.com> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.1i I should have put some stronger caveats in the release announcement about the use of the -o managed option to mount. As people have discovered, it is not ready for prime time. And, even if it was ready for prime time, it is definitely not something that you want to use on all of your directories. You should only use it for directories that are initially unpopulated and are due to be completely managed by cygwin (hence the name). So, the best use would be to create an empty directory, mount it, and then add files to it. Do not try this on existing directories as it will probably confuse cygwin. I may make this a requirement for mount. If mount notices that you are mounting a non-empty directory initially, it will issue a warning. I will fix the currently reported problems in the next cygwin snapshot if people want to play with this. I do appreciate bug reports but now that I've laid out the ground rules, please lets not hear about how this doesn't work right in your root directory. 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/