From: David Rothenberger <daveroth@acm.org>
To: cygwin@cygwin.com, cygwin@cygwin.com
Subject: Re: [BUG 1.7] Read-only files are not.
Date: Thu, 01 Jan 2009 01:17:00 -0000 [thread overview]
Message-ID: <495C1998.3010700@acm.org> (raw)
In-Reply-To: <20081231235814.GA23121@ednor.casa.cgf.cx>
On 12/31/2008 3:58 PM, Christopher Faylor wrote:
> On Wed, Dec 31, 2008 at 03:31:43PM -0800, David Rothenberger wrote:
>> It seems that read-only files in Cygwin 1.7 are not truly
>> read-only. The sequence of steps below shows that "chmod 444 file1"
>> does not make the file read-only in Cygwin 1.7, while it does in
>> Cygwin 1.5. It may have something to do with the Read Only DOS
>> attribute. This is set by Cygwin 1.5 but not by Cygwin 1.7. If I
>> manually set it for Cygwin 1.7, the file does become read-only.
>>
>> (This issue was brought to my attention by a failing subversion test
>> after building for 1.7.)
>
> Hmm. I can duplicate this but this is all Corinna's code so it might
> take a while to track down.
>
> It's a pretty serious bug though. Would you be willing to see if this
> is a recent 1.7 problem by trying some older DLLs?
Apparently it is an old problem (if indeed it is a problem and not
intentional as Eric suggests). The 2008-08-01 does not have the
"problem" while 2008-08-17 does. 08-01 sets the read-only DOS attribute
while 08-17 does not.
--
David Rothenberger ---- daveroth@acm.org
"Jesus saves...but Gretzky gets the rebound!"
-- Daniel Hinojosa (hinojosa@hp-sdd)
--
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/
next prev parent reply other threads:[~2009-01-01 1:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-31 23:32 David Rothenberger
2008-12-31 23:59 ` Christopher Faylor
2009-01-01 1:17 ` David Rothenberger [this message]
2009-01-01 0:07 ` Eric Blake
2009-01-01 0:57 ` David Rothenberger
2009-01-01 3:39 ` Christopher Faylor
2009-01-07 14:31 ` Corinna Vinschen
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=495C1998.3010700@acm.org \
--to=daveroth@acm.org \
--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).