From: Edward Shishkin <edward.shishkin@gmail.com>
To: David Niklas <Hgntkwis@vfemail.net>
Cc: reiserfs-devel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: PROBLEM: Reiser4 hard lockup
Date: Tue, 27 Oct 2020 01:53:31 +0100 [thread overview]
Message-ID: <2e2f8dc4-a48e-f09c-3f41-5dfa7f9a6387@gmail.com> (raw)
In-Reply-To: <20201025210758.034aa947@Phenom-II-x6.niklas.com>
On 10/26/2020 02:07 AM, David Niklas wrote:
> I'll reply to both of you in this email.
>
> On Sun, 25 Oct 2020 02:04:22 -0700 (PDT)
> Metztli Information Technology <jose.r.r@metztli.com> wrote:
>> Niltze, David-
>>
>> A few observations are in order below:
>>
>> On Sat, Oct 24, 2020 at 1:39 PM David Niklas <Hgntkwis@vfemail.net>
>> wrote:
>>>
>>> Hello,
>>>
> <snip>
>> reiser4progs 1.1.x Software Framework Release Number (SFRN) 4.0.1 file
>> system utilities should not be used to check/fix media formatted 'a
>> priori' in SFRN 4.0.2 and vice-versa.
>
> Honestly, this is the first time I've heard about a Linux FS having
> versioning other than a major one
This is because, unlike other Linux file systems, reiser4 is a
framework.
In vanilla kernel having a filesystem-as-framework is discouraged for
ideological reasons. As they explained: "nobody's interested in
plugins". A huge monolithic mess without any internal structure -
welcome :)
next prev parent reply other threads:[~2020-10-27 0:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-25 9:04 PROBLEM: Reiser4 hard lockup Metztli Information Technology
2020-10-26 1:07 ` David Niklas
2020-10-27 0:53 ` Edward Shishkin [this message]
2020-10-27 19:36 ` Theodore Y. Ts'o
2020-10-28 1:04 ` Edward Shishkin
-- strict thread matches above, loose matches on Subject: below --
2020-10-26 10:42 Metztli Information Technology
2020-10-24 20:36 David Niklas
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=2e2f8dc4-a48e-f09c-3f41-5dfa7f9a6387@gmail.com \
--to=edward.shishkin@gmail.com \
--cc=Hgntkwis@vfemail.net \
--cc=linux-kernel@vger.kernel.org \
--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).