DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; q=dns; s=
	default; b=RLAP8aSBC5HKe0VTI4ZJPFIoQhrmvQy0ViVKgy7yLCN+0voC90sdV
	ilMXE90Yk7RdrxP/FXUPjyvt9RJGA9n2zQhQHmUVhkpPuqRBRX/cfRQTzxlsZUqn
	E2LTh5BVB1fmW62DaZ7MpcWUzaFSxKNIRLfvz3KkL4mSjAZA/hxTqA=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Date: Fri, 25 Apr 2014 17:47:02 +0200
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: rm -f behavior
Message-ID: <20140425154702.GH5666@calimero.vinschen.de>
Reply-To: cygwin@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
References: <5358260B.90807@obj-sys.com> <20140424142304.GT2339@calimero.vinschen.de> <53592F15.4040309@obj-sys.com> <20140424163624.GU2339@calimero.vinschen.de> <20140425121614.GB5666@calimero.vinschen.de> <535A6FF9.90004@obj-sys.com> <20140425145036.GE5666@calimero.vinschen.de> <535A7F9B.5020804@obj-sys.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;	protocol="application/pgp-signature"; boundary="OpLPJvDmhXTZE4Lg"
Content-Disposition: inline
In-Reply-To: <535A7F9B.5020804@obj-sys.com>
User-Agent: Mutt/1.5.21 (2010-09-15)

--OpLPJvDmhXTZE4Lg
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable


Please don't top-post.  Thanks.


On Apr 25 11:30, Douglas Coup wrote:
> I downloaded the x86/cygwin-inst-20140425.tar.xz file.  I assume all
> I need to do is run tar xvf against this file?  From the output it
> certainly looked like it installed the files.

No.  Just download the DLL and only install the DLL in place of the old
DLL.  Installing the tar inst file under Cygwin doesn't effectively
replace the Cygwin DLL.  You should exit all(!) Cygwin processes, mopve
the release DLL out of the way, and move the new DLL in place.

> But I'm not seeing any difference.  I'm still seeing the permission
> denied error on rm -f in the scenarios I've described.
>=20
> Incidentally, the sequence below should have nothing to do with Perforce.
>=20
> $ touch dac.txt
> $ chmod 444 dac.txt
> $ rm -f dac.txt
>=20
> This is being done completely outside of any Perforce workspaces.

Sorry, this isn't helpful.  Make sure you're *really* using the correct
Cygwin DLL from the snapshot (uname -a), and if the above sequence
really fails to work, first call `attrib dac.txt' before calling rm to
see if the R/O attribute is set, then call rm under strace again and
send the strace.  Also, if the R/O attribute gets set in the above
sequence, I have to know where it comes from.  As I said, Cygwin does
not set the flag at all for normal files, not even in chmod.


Corinna

--=20
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

--OpLPJvDmhXTZE4Lg
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBAgAGBQJTWoN2AAoJEPU2Bp2uRE+gmqQP/AknRf+Yvq+pDrE2RWWkn2gI
2WuNji1OSjCFONvsCoAnW8Qr3fyTJK/ELHQW48+deScPryhHGrCpbW8ltSdR31tP
0QoCLey1CISoPeg4zthhXtwhzg0NvGJFOYDDDum4CdBk2x3Ip46SdIlbK7aeAA2Z
tS5GciLJB4+BZd3MhG4wSaXGvVh7l57alQ+pkOK/mP4v/Top8onrDGSj2RwVxk/Z
Ri0HB1sIQ1VIuDF+jm1Qlb5W1YG8+MxGuPHpgtftJb3MifT6guDMefMumudasb9b
codbm/QgZ/bkKf8f3M6HeVj8bw1+oeqlP/t9GzuPaRBAue0j8GS41d8AQLf9PMFs
LidMmHUEQT9bhax54q+LzYMj/Dy9LC6QlUwiEAD0GSIyzIx3srrQyWf6QqAtw6ht
XQSNLTE17mXsazGkjfTkH9OxA/JYE6U32jo7e50HkAPc8s68M8/Khn9wX+wwcV3n
lyS3PPLsw2y77ODMIM2bwoBOK7NT0EzFYsDT7ngQ8SZxUKlh1LwgE4jspJmAZml2
nJ0ahxBWX+16X7nu/hL5zvsktUL4vqZ42lWumq5vKQ1cyplE3fRd8IT4TyBJGkit
UrZk53sXqpLv5NU3q4mhDNE7WtLpH8aQaHhD4/7U3/ecfOnspYRfhGaVZk8pJSxW
d5zEumLVPLy6gOPf2cSl
=98r/
-----END PGP SIGNATURE-----

--OpLPJvDmhXTZE4Lg--