X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Message-Id: <200808240233.m7O2XXHR003368@mx1.cs.umb.edu> To: cygwin AT cygwin DOT com Subject: What happens to managed mounts in cygwin 1.7? Reply-To: rouilj AT ieee DOT org ZReturn-Receipt-To: rouilj AT cs DOT umb DOT edu ZDisposition-Notification-To: rouilj AT cs DOT umb DOT edu Date: Sat, 23 Aug 2008 22:33:33 -0400 From: "John P. Rouillard" Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: 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 Hello: I have read a couple of comments (one from cfg IIRC) that managed mounts are dissapearing from cygwin in version 1.7. So I guess I have two questions: 1) if I have a managed mount point working well under 1.5, how do I use the data in the mount point under 1.7? 2) what happens if I have to represent an illegal (to windows) file name on a fat formatted filesystem (e.g. cygwin on a stick), or NTFS? IIRC managed mounts allow the files "config" and "Config" to exist at the same level in a directory. Is this natively supported under 1.7 using the NT filesystem API? aTdHvAaNnKcSe -- -- rouilj John Rouillard =========================================================================== My employers don't acknowledge my existence much less my opinions. -- 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/