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.
>
> cgf
Shouldn't you be twirling your mustachios and cackling fiendishly before
disappearing with a dramatic swirl of your cloak in that case?
cheers,
DaveK
