From owner-freebsd-hackers Wed Jun 6 0:10:19 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by hub.freebsd.org (Postfix) with ESMTP id DACCF37B405; Wed, 6 Jun 2001 00:10:16 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.3/8.11.3) with ESMTP id f567A5178086; Wed, 6 Jun 2001 09:10:05 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Ruslan Ermilov Cc: hackers@FreeBSD.ORG Subject: Re: MFC'ing new md(4) functionality? In-Reply-To: Your message of "Wed, 06 Jun 2001 09:56:00 +0300." <20010606095600.A37378@sunbay.com> Date: Wed, 06 Jun 2001 09:10:05 +0200 Message-ID: <78084.991811405@critter> From: Poul-Henning Kamp Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <20010606095600.A37378@sunbay.com>, Ruslan Ermilov writes: >On Tue, Jun 05, 2001 at 07:43:38PM +0200, Poul-Henning Kamp wrote: >> In message <20010605102017.E48590@dragon.nuxi.com>, "David O'Brien" writes: >> >On Tue, Jun 05, 2001 at 06:33:17PM +0200, Poul-Henning Kamp wrote: >> >> Others see it differently, it would seriously break a lot of >> >> people who are using -stable in embedded applications. >> > >> >Can you expand on this? I assume you know we are not talking about >> >disabling vn(4). >> >> We already have a previous form of md(4) in stable, -current's md(4) >> is not compatible with that older version. >> >And that older version doesn't even work (at least when loaded as the >module): While true, it is not really relevant to the issue of API/ABI breakage in -stable... -- 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. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message