From owner-freebsd-current@FreeBSD.ORG  Sun Jun  1 12:46:24 2003
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
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 8459D37B401; Sun,  1 Jun 2003 12:46:24 -0700 (PDT)
Received: from silver.he.iki.fi (silver.he.iki.fi [193.64.42.241])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 628B743F3F; Sun,  1 Jun 2003 12:46:23 -0700 (PDT)
	(envelope-from pete@he.iki.fi)
Received: from PETEX31 (h81.vuokselantie10.fi [193.64.42.129])
	by silver.he.iki.fi (8.12.9/8.11.4) with SMTP id h51JkMk8006875;
	Sun, 1 Jun 2003 22:46:22 +0300 (EEST)
	(envelope-from pete@he.iki.fi)
Message-ID: <00b501c32876$74502fd0$812a40c1@PETEX31>
From: "Petri Helenius" <pete@he.iki.fi>
To: "Tim Robbins" <tjr@FreeBSD.ORG>
References: <3ED9E8AB.5060106@he.iki.fi>
	<20030601232426.A43338@dilbert.robbins.dropbear.id.au>
Date: Sun, 1 Jun 2003 22:46:11 +0300
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
cc: freebsd-current@FreeBSD.ORG
Subject: Re: raidframe
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 01 Jun 2003 19:46:24 -0000

> RAIDframe is non-functional in 5.1 and -current [kern/50541] and it would be
> unwise to use it in 5.0 for anything other than experimentation. Hopefully it
> will be fixed before 5.2.
> 
Makes one wonder how broken code ever got into the tree in the first place...

Pete