From owner-freebsd-stable Mon Mar 16 06:33:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA23151 for freebsd-stable-outgoing; Mon, 16 Mar 1998 06:33:02 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from shrimp.dataplex.net (shrimp.dataplex.net [208.2.87.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA23146 for ; Mon, 16 Mar 1998 06:32:56 -0800 (PST) (envelope-from rkw@dataplex.net) Received: from [208.2.87.4] (user4.dataplex.net [208.2.87.4]) by shrimp.dataplex.net (8.8.8/8.8.5) with ESMTP id IAA05124; Mon, 16 Mar 1998 08:32:34 -0600 (CST) X-Sender: rkw@mail.dataplex.net Message-Id: In-Reply-To: <199803161333.FAA14802@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Mon, 16 Mar 1998 08:32:19 -0600 To: Mike Smith From: Richard Wackerbarth Subject: Re: ATTENTION: Call for opinion re: root device naming change Cc: stable@FreeBSD.ORG Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk > - Backout; our configuration is pathological and the new code does not work. I should not be "frozen out" of the 2.2 branch on my production machines with no upgrade path short of reformatting the HD's. 2.2 is not yet dead, and should not die until 3.0 (or 2.3, should it happen instead) has proven itself "production-stable". If 1) there is a solution that does not require a total rebuild of the disk and 2) it gets adequately documented (and perhaps supported by a configuration analysis script), then I don't object to having to alter fstab in order to track the changes. Richard Wackerbarth To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message