From owner-freebsd-current@FreeBSD.ORG Sat Jan 10 21:04:53 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E439416A4D0; Sat, 10 Jan 2004 21:04:52 -0800 (PST) Received: from ozlabs.org (ozlabs.org [203.10.76.45]) by mx1.FreeBSD.org (Postfix) with ESMTP id 620CB43D49; Sat, 10 Jan 2004 21:04:49 -0800 (PST) (envelope-from grog@lemis.com) Received: from blackwater.lemis.com (blackwater.lemis.com [192.109.197.80]) by ozlabs.org (Postfix) with ESMTP id 1DAB42BD5A; Sun, 11 Jan 2004 16:04:47 +1100 (EST) Received: by blackwater.lemis.com (Postfix, from userid 1004) id 00B6551211; Sun, 11 Jan 2004 15:34:44 +1030 (CST) Date: Sun, 11 Jan 2004 15:34:44 +1030 From: Greg 'groggy' Lehey To: Scott Long Message-ID: <20040111050444.GJ7617@wantadilla.lemis.com> References: <40007D14.6090205@freebsd.org> <40008E4A.3060604@freebsd.org> <40007D14.6090205@freebsd.org> <3180.1073776377@critter.freebsd.dk> <20040111020459.5bbba56a@Magellan.Leidinger.net> <4000A2FC.2040400@freebsd.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="ho6OhzAHcBHHvqkB" Content-Disposition: inline In-Reply-To: <40008E4A.3060604@freebsd.org> <4000A2FC.2040400@freebsd.org> User-Agent: Mutt/1.4.1i Organization: The FreeBSD Project Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.FreeBSD.org/ X-PGP-Fingerprint: 9A1B 8202 BCCE B846 F92F 09AC 22E6 F290 507A 4223 cc: Alexander Leidinger cc: Poul-Henning Kamp cc: hackers@freebsd.org cc: current@freebsd.org cc: Dag-Erling =?iso-8859-1?Q?Sm=F8rgrav?= Subject: Re: Future of RAIDFrame X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 Jan 2004 05:04:53 -0000 --ho6OhzAHcBHHvqkB Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Saturday, 10 January 2004 at 18:12:28 -0700, Scott Long wrote: > Alexander Leidinger wrote: >> On Sun, 11 Jan 2004 00:12:57 +0100 >> "Poul-Henning Kamp" wrote: >> >> >>> As much as I would hate to see RF and Vinum disappar from our >>> source tree, maybe what we need to do is to kick them both into >>> "training-camp" in p4 while you and Greg look the other way. >> >> [...] >> >>> I'd say lets kick them both into perforce and let whoever wants >>> their hands have a go at them. >> >> RF isn't working today on -current, vinum is (please don't tell me >> something else, I don't want the system under my desk stop running on a >> vinum volume just because you say it has to :-)). Do you really want to >> throw your axe at vinum while it's still alive? > > Ok, stop right here. This is the third email so for that is attempting > the debate the merits of one over the other. Spending time arguing that > point is a waste of time. If working on RF is something that interests > you, then show your support and say so. On Saturday, 10 January 2004 at 16:44:10 -0700, Scott Long wrote: > Dag-Erling Sm=F8rgrav wrote: >> Scott Long writes: >> >>> I started RAIDframe three years ago with the hope of bringing a proven >>> and extensible RAID stack to FreeBSD. >> >> I'm having trouble seeing what RF does that Vinum (or at least a >> properly GEOMified Vinum) can't do... > > Please read the RAIDframe documents at http://www.pdl.cmu.edu/RAIDframe > before you ask again. People, I think we should make it clear that neither Vinum nor RAIDFrame are perfect. We shouldn't chuck either out at the moment, and it would be really nice, as phk suggests, to have people working on both. Both are rather old now, but they contain good ideas. It would certainly be an excellent idea to improve them both. We shouldn't be trying to compare their relative merits at the moment. Wait until they regain their strength. I'll answer phk's suggestions separately. Greg -- See complete headers for address and phone numbers. --ho6OhzAHcBHHvqkB Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.0 (FreeBSD) iD8DBQFAANlsIubykFB6QiMRAtSNAJsFO2+GgjevUzgP0i08UqwPy+IrLgCePHNy DE51aVSa2AnbOcwBlmSiaR0= =F48W -----END PGP SIGNATURE----- --ho6OhzAHcBHHvqkB--