From owner-freebsd-stable Mon Mar 16 05:35:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA10999 for freebsd-stable-outgoing; Mon, 16 Mar 1998 05:35:44 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA10974 for ; Mon, 16 Mar 1998 05:35:40 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.8.8/8.8.5) with ESMTP id FAA14802 for ; Mon, 16 Mar 1998 05:33:26 -0800 (PST) Message-Id: <199803161333.FAA14802@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: stable@FreeBSD.ORG Subject: ATTENTION: Call for opinion re: root device naming change Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 16 Mar 1998 05:33:25 -0800 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk This message is a call for submissions regarding the future of the changes committed to the RELENG_2_2 branch ("-stable") last week relating to the use of the canonical device when mounting the root filesystem. Whilst these changes improve overall consistency and remove a number of logical problems, they present a number of difficulties for users wishing to mix older configurations with the new scheme. To date, in the -stable forum, there has been very little support for these changes. This may simply be that those understanding and accepting them have not felt the need to complain. However, the complaints have been loud and persistent, and there are a number of unresolved issues inconsistent with the upcoming 2.2.6 release. At this point in time, where very few sites will have deployed the new code, it is practical to withdraw the changes from RELENG_2_2. Those sites that have addressed the issue already will not have any major problems in backing out, as they will be returning to a familiar configuration. In order to guage reaction to this, I am asking for persons with a vested interest or opinion to respond (either privately or to the list). Responses will be evaluated until approximiately midday Wednesday PST, at which point the indicated action will be summarily announced and adopted. When replying, please be brief. Backout or Keep, and why. No war stories, don't quote this entire message, don't quote someone else' reply and say "me too". Please bear in mind that this is a call for opinion rather than discussion. You can be even more succinct; there are a small set of common reasons: - Backout; the configuration change will be too expensive for us. - Backout; our configuration is pathological and the new code does not work. - Backout; slices are an abomonation and we never use them. - Keep; we have already deployed and changing back would be expensive. - Keep; the new approach allows us extra flexibility and consistency. - Keep; the compatibility slice is an abomination and we never use it. Note that the changes will remain in -current, as they are consistent with the developmental direction towards 3.0. Regards -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message