> Nick, was it you, who wrote this article?
> http://www.nicklowe.org/2012/02/understanding-case-sensitivity-in-windows-obcaseinsensitive-file_case_sensitive_search/
> Thanks for it, if so.
> But the more frustrating it makes your post, as article clearly states, that
I did, yes. I was trying to g
I do not think I explained myself properly, sorry: Cygwin would
previously read the
obcaseinsensitve value under Windows 2000 to emulate the case
insensitive behaviour of Windows XP and newer where obcaseinsensitive
was present in the registry.
The registry key does not represent the active state
Hi Corinna,
I notice you are still reading in obcaseinsensitive in cygcheck.cc but
this value is no longer used in Cygwin as you have dropped Windows
2000 support.
Would it make sense to change the code there to show the actual state
of case sensitivity?
Kind regards,
Nick
--
Problem reports:
will pertain to these functions
only.
On Fri, Dec 21, 2012 at 7:44 PM, Tom Honermann wrote:
> On 12/21/2012 07:15 AM, Nick Lowe wrote:
>>
>> Briefly casting my eye at the test case, as a general point, remember
>> that these termination APIs all complete asynchronously and I
Briefly casting my eye at the test case, as a general point, remember
that these termination APIs all complete asynchronously and I do not
believe it has ever been safe or correct to call another while one is
still pending - you are in undefined, edge case behaviour territory
here.
Win32's Termina
http://cygwin.com/
"The Cygwin DLL and utilities are Copyright © 2000, 2001, 2002, 2003,
2004, 2005, 2006, 2007, 2008, 2009, 2010, 2011, 2012 Red Hat, Inc"
> Wikipedia isn't the keeper of the information relevant to Cygwin. You
> can only find the truth at cygwin.com. Besides, companies do supp
To me, the key question is:
Would Red Hat have an objection in principle to signing Cygwin and its
packages given the history and ties.
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubs
Urgh! Hmm.. Do you see the same effect when running the process in
question under the Windows 8 operating system context?
If you manifest and include:
http://msdn.microsoft.com/en-us/library/windows/desktop/hh848036(v=vs.85).aspx
Does the odd behaviour still pers
>> Have you taken a Wireshark capture in both scenarios and looked for
>> differences?
>
> Wireshark capture of an encrypted stream is next to useless...
Is SMB encrypted in this case?
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documen
Have you taken a Wireshark capture in both scenarios and looked for differences?
Nick
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe
Are you waiting for the file handle to become signalled before
attempting a rename?
Nick
On Wed, May 16, 2012 at 11:46 AM, Václav Zeman wrote:
> Hi.
>
> This is unrelated to Cygwin directly. I am having problems in my
> library that renaming files sometimes fails right after the file is
> closed
Yeah - Sorry all for any misunderstanding on my part. I seem to
remember I was in a caustic mood at the time anyway over something
very unrelated!
Will take care to not derail threads in the future.
Regards,
Nick
--
Problem reports: http://cygwin.com/problems.html
FAQ: h
I forgot to add, it also needs to be signed by a trusted root for it
to be useful to most people.
On Sun, Apr 29, 2012 at 1:51 AM, Nick Lowe wrote:
> "I installed 2.772 on my systems as soon as it was available and I
> don't see any such issue using my local mirror. Did you try
"I installed 2.772 on my systems as soon as it was available and I
don't see any such issue using my local mirror. Did you try another
mirror?"
Quite, but the idea of corruption was implicit in that question. A
digital signature would rule that out. It was only a suggestion to
ensure that that wo
> It's bad etiquette to derail an email thread with unrelated questions.
I certainly didn't mean to derail it, the other points were ancillary
to the implicit point that I intended to make which is that if the
executable was digitally signed, any potential corruption would
immediately be flagged b
Is there a reason why the Cygwin executables, and certainly the
installer, are not digitally signed by Redhat?
Also, with reference to:
http://blogs.msdn.com/b/cjacks/archive/2009/03/27/manifesting-for-compatibility-on-windows-7.aspx
http://msdn.microsoft.com/en-us/library/dd371711%28v=vs.85%29.a
Dear Microsoft,
Which version did you test?
See the following thread:
http://cygwin.com/ml/cygwin-developers/2011-10/threads.html#5
"Re: Add support for Windows 8, first step"
Regards,
Nick
On Fri, Apr 27, 2012 at 1:05 AM, Anuja Singh (MP Tech Consulting LLC)
wrote:
> find_fast_cwd
--
Oh, sorry, yes.
I suspect that the AES-NI instructions are used 'silently' where
supported by the processor.
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cyg
In 1.0.1:
http://www.openssl.org/news/changelog.html
"Add RC4-MD5 and AESNI-SHA1 "stitched" implementations.
This work was sponsored by Intel.
[Andy Polyakov]"
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://c
rator or fails otherwise.
(I have only tested this under 64-bit Windows 7.)
Regards,
Nick
On Tue, Feb 21, 2012 at 10:26 AM, Nick Lowe wrote:
> I have just tested this and it works. It is faster, simpler and has
> less overheads than querying the registry for a potentially stale
&g
.
Regards,
Nick
On Tue, Feb 21, 2012 at 9:52 AM, Nick Lowe wrote:
> OK, fair enough, it is an edge case... I am a stickler for correctness! :P
>
> Looking at previous threads though actually, I notice that the
> following is documented by Microsoft regarding the obcaseinsensitive
>
OK, fair enough, it is an edge case... I am a stickler for correctness! :P
Looking at previous threads though actually, I notice that the
following is documented by Microsoft regarding the obcaseinsensitive
value:
"If this setting is enabled, case insensitivity is enforced for all
directory objec
t set."
Cheers,
Nick
On Tue, Feb 21, 2012 at 8:59 AM, Nick Lowe wrote:
> Dear Cygwin Developers,
>
> shared_info::init_obcaseinsensitive in shared.cc has, in my opinion,
> been implemented incorrectly.
>
> The value of the obcaseinsensitive value in the registry only
> represe
, obviously, that the
OBJ_CASE_INSENSITIVE flag is not set.
If the the NTSTATUS value is successful, the object manager is running
with case insensitivity, if not its running with case sensitivity.
With regards,
Nick Lowe
--
Problem reports: http://cygwin.com/problems.html
FAQ
24 matches
Mail list logo
