From owner-freebsd-current Mon Feb 12 13:19:49 2001 Delivered-To: freebsd-current@freebsd.org Received: from harmony.village.org (rover.village.org [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id D6E7E37B491 for ; Mon, 12 Feb 2001 13:19:44 -0800 (PST) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.11.1/8.11.1) with ESMTP id f1CLJaW31538; Mon, 12 Feb 2001 14:19:36 -0700 (MST) (envelope-from imp@harmony.village.org) Message-Id: <200102122119.f1CLJaW31538@harmony.village.org> To: Daniel Eischen Subject: Re: -CURRENT is bad for me... Cc: John Indra , freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Mon, 12 Feb 2001 07:59:03 EST." References: Date: Mon, 12 Feb 2001 14:19:36 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG To be blunt, the FILE * changes go too far, even for -current. Changes of this magnitude require a bump of the major number, even though we've already done that in -current. It breaks nearly everything, including the upgrade path. Alternatively, the locking changes need to be backed out. Alternatively, the upgrade path must be fixed. We've managed to avoid extra special instructions in the vast majority of cases, and I don't want to start introducing them now. It is the road to madness. We tried that once before and the support load was too high. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message