Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Date: Fri, 29 Apr 2005 10:46:27 -0400
From: Christopher Faylor <cgf-no-personal-reply-please AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: 1.5.16: Filename case sensitivity problem
Message-ID: <20050429144627.GE7328@trixie.casa.cgf.cx>
Reply-To: cygwin AT cygwin DOT com
References: <001201c54c59$b5926e00$fe01a8c0 AT dellpc> <42719236 DOT 44C9FFBB AT dessent DOT net> <000e01c54c64$168c9640$fe01a8c0 AT dellpc> <4271A58F DOT 73BF92C4 AT dessent DOT net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4271A58F.73BF92C4@dessent.net>
User-Agent: Mutt/1.5.8i

On Thu, Apr 28, 2005 at 08:10:07PM -0700, Brian Dessent wrote:
>Zhuang Jianmin wrote:
>
>> HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\mounts v2\/usr/src
>>   (default) = `e:\cygwin\usr\src'
>>   flags = 0x0000080a
>
>This mount is a managed mount.  The MOUNT_ENC bitflag is 0x800...
>
>> e:\cygwin\usr\src  /usr/src   system  binmode
>
>...although it appears that cygcheck does not report this flag in its
>output.  Still, if you run "mount -m" it should show the option "-o
>managed" next to the command that would create that mount.  You can find
>more information on the -o flags that mount takes in "man mount".
>
>I am not sure how this mount came to be if you did not create it.  I was
>under the impression that neither setup.exe nor any packages enable
>managed mounts.  It looks like that is not the case.

Anyone want to submit a patch which ensures that all of the mount flags
are represented correctly by cygcheck?

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/