From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: rm -f behavior
Date: Fri, 25 Apr 2014 19:59:00 -0000 [thread overview]
Message-ID: <20140425195856.GO5666@calimero.vinschen.de> (raw)
In-Reply-To: <535ABCDD.5020002@obj-sys.com>
[-- Attachment #1: Type: text/plain, Size: 884 bytes --]
On Apr 25 15:51, Douglas Coup wrote:
> On 4/25/2014 3:16 PM, Corinna Vinschen wrote:
> > Can you please try something else? I'm wondering if
> >that's not a problem analogue of the one described in
> >http://support.microsoft.com/kb/948252.
> >
> >The "fix" from that KB applied to your case:
> >
> >- Revert to the release Cygwin DLL.
> >
> >- Delete the .blf files and the .regtrans-ms files from your
> > %Windir%\System32\SMI\Store\Machine folder.
> >
> >- Try the failing rm -f scenario again.
> >
> >Does that fix the problem, too? If not, I'm back to blaming Perforce.
> I tried these steps, but the rm -f command still fails with the
> original cygwin1.dll in place.
Ok, thanks for testing,
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Red Hat
[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2014-04-25 19:59 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-23 20:43 Douglas Coup
2014-04-24 14:23 ` Corinna Vinschen
2014-04-24 15:35 ` Douglas Coup
2014-04-24 16:36 ` Corinna Vinschen
2014-04-24 16:45 ` Corinna Vinschen
2014-04-24 17:10 ` Douglas Coup
2014-04-25 12:16 ` Corinna Vinschen
2014-04-25 14:23 ` Douglas Coup
2014-04-25 14:50 ` Corinna Vinschen
2014-04-25 15:30 ` Douglas Coup
2014-04-25 15:47 ` Corinna Vinschen
2014-04-25 15:57 ` Corinna Vinschen
2014-04-25 18:12 ` Douglas Coup
2014-04-25 19:16 ` Corinna Vinschen
2014-04-25 19:52 ` Douglas Coup
2014-04-25 19:59 ` Corinna Vinschen [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140425195856.GO5666@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).