From owner-freebsd-hackers@FreeBSD.ORG Mon Jan 12 02:00:42 2004 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B319016A4CE; Mon, 12 Jan 2004 02:00:42 -0800 (PST) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id F1C2443D31; Mon, 12 Jan 2004 02:00:40 -0800 (PST) (envelope-from phk@phk.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.12.10/8.12.10) with ESMTP id i0CA0YOl078216; Mon, 12 Jan 2004 11:00:39 +0100 (CET) (envelope-from phk@phk.freebsd.dk) To: Mark Linimon From: "Poul-Henning Kamp" In-Reply-To: Your message of "Mon, 12 Jan 2004 03:41:42 CST." <200401120341.42349.linimon@lonesome.com> Date: Mon, 12 Jan 2004 11:00:34 +0100 Message-ID: <78215.1073901634@critter.freebsd.dk> cc: Greg 'groggy' Lehey cc: hackers@FreeBSD.org Subject: Re: Future of RAIDFrame and Vinum (was: Future of RAIDFrame) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Jan 2004 10:00:42 -0000 In message <200401120341.42349.linimon@lonesome.com>, Mark Linimon writes: >But, in the real world of software engineering, He Who Breaketh It, >Must Fixeth It. If we are talking paid jobs, yes, then you can make rules like that because with the salary you control resource allocation and prioritization. My real life experience show that such rules invariably give way to other factors when push comes to shove, but they're nice as a starting point until the real real world rears its ugly head. In a free software project, you can take any rule like that an put it anywhere you like, in any font, size and color of your choice and it still wont work. If there are not enough people willing and able to actively maintain vinum, and in particular to make it keep pace with the kernel infrastructure then we are only talking about _when_, not _if_ it will die. What about vinum and locking ? Is anybody working on getting vinun out from under Giant ? Any piece of software in FreeBSD needs a minimum critical mass of developers, and judging from the probelms, both RF and vinum are below that threshold. If vinum means a lot to you, you should do something to get it above that threshold: start debugging/coding, learn to code if need be, donate money so somebody else can code if you can't do anything else. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence.