From: Dave Korn <dave.korn.cygwin@googlemail.com>
To: The Acme Cygwin-Talk Maiming List <cygwin-talk@cygwin.com>
Subject: Re: Permission problems in release-2
Date: Sat, 13 Jun 2009 11:41:00 -0000 [thread overview]
Message-ID: <4A33932E.2040101@gmail.com> (raw)
In-Reply-To: <20090613022951.GA28983@ednor.casa.cgf.cx>
Christopher Faylor wrote:
> On Sat, Jun 13, 2009 at 03:25:20AM +0100, Dave Korn wrote:
>> Christopher Faylor wrote:
>>> On Fri, Jun 12, 2009 at 11:25:21AM +0200, Corinna Vinschen wrote:
>>>> On Jun 11 21:09, Christopher Faylor wrote:
>>>>> On Thu, Jun 11, 2009 at 07:56:27PM -0500, Yaakov (Cygwin/X) wrote:
>>>>>> On 11/06/2009 11:04, Christopher Faylor wrote:
>>>>>>> After checking the mount man page, I found an option that can be used
>>>>>>> to control umask on a per-mount setting. I just made '002' the default
>>>>>>> for the release-2 directory so this should no longer be a problem.
>>>>>> The side effect of this is that all files are executable. I don't know
>>>>>> if that really matters, but at least I had no problem moving pcre into
>>>>>> place this evening.
>>>>> Ok, so the option doesn't seem to work as advertised. I've removed it.
>>>>>
>>>>> Anyone who creates files in release-2 should set their umask to 2.
>>>>> That seems to work as it should.
>>>> Not when using cpio -dump, unfortunately.
>>>>
>>>> I'm wondering about the reason for this new permission problem. Can't
>>>> we just return to the old behaviour?
>>> I AM trying to reinstate the old behavior.
>>>
>>> We had a system crash last week. I'm assuming that the new behavior is
>>> due to that. Probably we started running new version of fuse which
>>> caused this change.
>>>
>>> It's either that or I'm just being mean, made an arbitrary change, and
>>> am gloating over all of the inconvenience I've caused.
>> Shouldn't you be twirling your mustachios and cackling fiendishly
>> before disappearing with a dramatic swirl of your cloak in that case?
>
> Unfortunately I'm still growing my mustache out after an unfortunate
> encounter with an Acme Blow Torch. Somebody distracted me and turned
> the nozzle around while I wasn't looking.
>
> Hmm. I think I may be conflating Snidely Whiplash with Elmer Fudd here.
>
> cgf
Surely if you're an Acme customer and their inventions keep blowing up in
your face, you must be Wile E. Coyote?
cheers,
DaveK
next prev parent reply other threads:[~2009-06-13 11:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4A308FF5.10108@users.sourceforge.net>
[not found] ` <20090611142929.GE4566@ednor.casa.cgf.cx>
[not found] ` <20090611160456.GA4849@ednor.casa.cgf.cx>
[not found] ` <4A31A7BB.7070005@users.sourceforge.net>
[not found] ` <20090612010945.GB6021@ednor.casa.cgf.cx>
[not found] ` <20090612092521.GD5039@calimero.vinschen.de>
[not found] ` <20090612141040.GB26444@ednor.casa.cgf.cx>
2009-06-13 2:13 ` Dave Korn
2009-06-13 2:30 ` Christopher Faylor
2009-06-13 11:41 ` Dave Korn [this message]
2009-06-15 16:38 ` Warren Young
2009-06-17 0:37 ` Dave Korn
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=4A33932E.2040101@gmail.com \
--to=dave.korn.cygwin@googlemail.com \
--cc=cygwin-talk@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).