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]

Message-ID: <44CA126C.7050403@namesys.com>
Date:	Fri, 28 Jul 2006 07:34:36 -0600
From:	Hans Reiser <reiser@...esys.com>
To:	David Masover <ninja@...phack.com>
CC:	Linus Torvalds <torvalds@...l.org>,
	"Horst H. von Brand" <vonbrand@....utfsm.cl>,
	Jeff Garzik <jeff@...zik.org>, Andrew Morton <akpm@...l.org>,
	Theodore Tso <tytso@....edu>,
	LKML <linux-kernel@...r.kernel.org>,
	ReiserFS List <reiserfs-list@...esys.com>
Subject: Re: metadata plugins (was Re: the " 'official' point of view" expressed
 by kernelnewbies.org regarding reiser4 inclusion)

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.

-
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/