From owner-freebsd-arch Tue Nov 26 14:59:56 2002 Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5E9C937B401; Tue, 26 Nov 2002 14:59:55 -0800 (PST) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8725F43EA9; Tue, 26 Nov 2002 14:59:54 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.12.6/8.12.6) with ESMTP id gAQMxj76002080; Tue, 26 Nov 2002 23:59:45 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Robert Watson Cc: arch@FreeBSD.ORG Subject: Re: ABIs and 5.x branch: freeze kernel module ABI at 5.0 or 5.1? In-Reply-To: Your message of "Tue, 26 Nov 2002 17:50:26 EST." Date: Tue, 26 Nov 2002 23:59:45 +0100 Message-ID: <2079.1038351585@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message , Robe rt Watson writes: >As such, I think a reasonable strategy would be to avoid exactly that: >rather than making guarantees about the ABI for 5.0, simply assert that >the ABI for kernel drivers will not be frozen until 5.1, so vendors should >be aware that they may have to rebuild their driver. We've already >indicated that the 5.0 release will be for "early adopters"--I want to >avoid having things stand in the way of kicking the 5.x branch into shape >in as much as is possible. Any thoughts? It's very simple in my mind: we only freeze ABI's on -stable branches (and we actually even violated that for 4-stable I belive). Whenever we branch a new -stable from -current, that's when we freeze the ABI's for that branch. -- 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-arch" in the body of the message