linux-kernel - Re: metadata plugins (was Re: the " 'official' point of view" expressed by kernelnewbies.org regarding reiser4 inclusion)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Sat, 29 Jul 2006 12:30:44 +0200
From:	Łukasz Mierzwa <prymitive@...erwis.net>
To:	LKML <linux-kernel@...r.kernel.org>
Subject: Re: metadata plugins (was Re: the " 'official' point of view" expressed by kernelnewbies.org regarding reiser4 inclusion)

Dnia Fri, 28 Jul 2006 15:34:36 +0200, Hans Reiser <reiser@...esys.com>
napisał:

> Let me put it from my perspective and stop pretending to be unbiased, so
> others can see where I am coming from.  No one was interested in our
> plugins.  We put the design on a website, spoke at conferences, no one
> but users were interested.  No one would have conceived of having
> plugins if not for us.  Our plugins affect no one else.  Our
> self-contained code should not be delayed because other people delayed
> getting interested in our ideas and now they don't want us to have an
> advantage from leading.  If they want to some distant day implement
> generic plugins, for which they have written not one line of code to
> date, fine, we'll use it when it exists, but right now those who haven't
> coded should get out of the way of people with working code.  It is not
> fair or just to do otherwise.  It also prevents users from getting
> advances they could be getting today, for no reason.  Our code will not
> be harder to change once it is in the kernel, it will be easier, because
> there will be more staff funded to work on it.
>
> As for this "we are all too grand to be bothered with money to feed our
> families" business, building a system in which those who contribute can
> find a way to be rewarded is what managers do.   Free software
> programmers may be willing to live on less than others, but they cannot
> live on nothing, and code that does not ever ship means living on  
> nothing.
>
> If reiser4 is delayed enough, for reasons that have nothing to do with
> its needs, and without it having encumbered anyone else, it won't be
> ahead of the other filesystems when it ships.
>

It just hited me that 90% of mails (those I've read and remember) in which
You guys are talking why r4 should or should not be merged did not contain
a patch or not even a line of code as a reference, most of complains feels
so abstract and ahead of time, there is nothing wrong with planing ahead
but does it still makes sense when nobody else actually said that he would
want to use it in future? Can't it be pusshed up to vfs later if it proves
itself and there is demand for it?
My question is what does it break now? It's been in mm for some time now,
what troubles does it couse? Did anyone complained that it breaks mm and
should be dropped?
I'm just a end user and have no idea of linux internals, but all the fuzz
about r4 seems so political and it's not just me who things so.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/