From: dE <de.techno@gmail.com>
To: reiserfs-devel@vger.kernel.org
Subject: Re: ACL support.
Date: Thu, 27 Mar 2014 20:51:18 +0530 [thread overview]
Message-ID: <533441EE.4060107@gmail.com> (raw)
In-Reply-To: <53330886.30506@gmail.com>
On 03/26/14 22:34, Edward Shishkin wrote:
> On 03/26/2014 05:44 PM, dE wrote:
>> On 03/26/14 21:31, Edward Shishkin wrote:
>>> On 03/26/2014 04:42 PM, dE wrote:
>>>> On 03/26/14 16:04, Edward Shishkin wrote:
>>>>> On 03/26/2014 06:23 AM, dE wrote:
>>>>>> Does reiser4 support ACL?
>>>>>
>>>>> Nope for historical reasons.
>>>>> I'll provide hints how to implement this, if someone wants..
>>>>>
>>>>> Edward.
>>>>
>>>> Thanks for the response.
>>>>
>>>> I was just asking for educational purposes (my home dir recedes on
>>>> reiser4).
>>>>
>>>> And yes -- I got a major bug to report which cause FF to crash.
>>>> Duplicating ~/.firefox solved the problem. I've the bad ~/.firefox.
>>>>
>>>> What do I have to do to report the problem?
>>>
>>> 1) "bad" means what?
>>> 2) any kernel complaints?
>>> 3) results of checking the partition with fsck.reiser4
>>> 4) Is it possible to reproduce the problem?
>>>
>>> Thanks,
>>> Edward.
>>
>> I started having problems with FF which was diagnosed to contents of
>> ~/.firefox.
>
> Which kernel version?
> Do you use the new reiser4 transaction models announced not so long ago?
>
>> So renamed it to ~/.firefox_bad and copied ~/.firefox_bad to
>> ~/.firefox to solve the problem.
>>
>> So I still have ~/.firefox_bad; this problem occurred twice, and I
>> have both of the ~/.firefox_bad
>>
>> Yes -- the kernel showed a backtrace from some reiser4 sources.
>
> Could you send it, if possible?
>
> Thanks,
> Edward.
>
>>
>> fsck.reiser4 was done -- nothing was wrong.
>>
>> Yes -- I have the ~/.firefox_bad just for the purpose of bug reporting.
>
Kernel is 3.8.5. So no, it's an old one.
Yes, I'll send the bt. Wait.
next prev parent reply other threads:[~2014-03-27 15:21 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-26 5:23 ACL support dE
2014-03-26 10:34 ` Edward Shishkin
2014-03-26 15:42 ` dE
2014-03-26 16:01 ` Edward Shishkin
2014-03-26 16:44 ` dE
2014-03-26 17:04 ` Edward Shishkin
2014-03-27 15:21 ` dE [this message]
2014-03-29 3:42 ` dE
[not found] ` <CAJZSrNLHanHHgAV-E=1bpnbq4FvqYETQkOQhdsrEwLza+Yd90w@mail.gmail.com>
2014-04-13 22:22 ` Edward Shishkin
-- strict thread matches above, loose matches on Subject: below --
2004-04-01 16:50 ACL Support Mike Young
2004-04-01 17:11 ` Christian Mayrhuber
2004-04-01 19:05 ` Jeff Mahoney
2004-04-01 20:43 ` Mike Young
2004-04-01 21:48 ` Jeff Mahoney
2004-04-01 22:11 ` Mike Young
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=533441EE.4060107@gmail.com \
--to=de.techno@gmail.com \
--cc=reiserfs-devel@vger.kernel.org \
/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 NNTP newsgroup(s).