Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932471AbVISPph (ORCPT ); Mon, 19 Sep 2005 11:45:37 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S932472AbVISPpg (ORCPT ); Mon, 19 Sep 2005 11:45:36 -0400 Received: from 69.50.231.10.ip.nectartech.com ([69.50.231.10]:49897 "EHLO newton.ctyme.com") by vger.kernel.org with ESMTP id S932471AbVISPpg (ORCPT ); Mon, 19 Sep 2005 11:45:36 -0400 Message-ID: <432EDD17.3080107@perkel.com> Date: Mon, 19 Sep 2005 08:45:27 -0700 From: Marc Perkel User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.10) Gecko/20050716 X-Accept-Language: en-us, en MIME-Version: 1.0 To: linux-kernel@vger.kernel.org Subject: Reiser 4 - the BIG picture - (think BIG picture) Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Maindomain: perkel.com X-Spam-filter-host: newton.ctyme.com - http://www.junkemailfilter.com Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1022 Lines: 26 OK - lets reset on the personal attacks stuff. I know there are people who like to goat people into fighting about this but STOP IT. The question that should be answered is - is Reiser4 ready yet - and that should be answered only by people who actually know what they are talking about. Someone saying "I had Reiser 3 in 2001 and it crashed my drive man" has nothing to do with this decision. So - may I ask .... Does Reiser 4 break anything? What is the down side of including it? Does Reiser 4 lack anything that is required? Has it met the criteria for inclusion? If Reiser 4 isn't ready then what specifically needs to be done to get it ready? Let's post a list. How ready is Reiser 4 compared to other file systems at the point of inclusion? Is it ripe yet? - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/