linux-kernel - Re: Question about Reiser4

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: <653402b90704231136x6f28c2b6i28a3a28dd840ab14@mail.gmail.com>
Date:	Mon, 23 Apr 2007 20:36:15 +0200
From:	"Miguel Ojeda" <maxextreme@...il.com>
To:	"Andrew Morton" <akpm@...ux-foundation.org>
Cc:	"Eric Hopper" <hopper@...ifarious.org>,
	linux-kernel@...r.kernel.org
Subject: Re: Question about Reiser4

On 4/23/07, Andrew Morton <akpm@...ux-foundation.org> wrote:
>
> To get it unstuck we'd need a general push, get people looking at and
> testing
> the code, get the vendors to have a serious think about it, etc.  We could
> do
> that - it'd require that the namesys people (and I) start making threatening
> noises about merging it, I guess.
>
> Or we could move all the reiser4 code into kernel/sched.c - that seems to
> get
> people fired up.
> -

Just an idea: And what about creating a new tree (like -r4),
maintained by namesys people, tested by several people, with dedicated
mailing list, etc.?

That way, the code could be patched, updated and cleaned over the time
(without firing up people), it could be tested without pain, people
would send more bug reports and every work would be centralized.
Reiser4 would get much more attention.

-- 
Miguel Ojeda
http://maxextreme.googlepages.com/index.htm
-
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/