From owner-freebsd-stable Tue Mar 17 03:25:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA19152 for freebsd-stable-outgoing; Tue, 17 Mar 1998 03:25:55 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.119.24.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA19144 for ; Tue, 17 Mar 1998 03:25:51 -0800 (PST) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [194.198.43.36]) by ns1.yes.no (8.8.7/8.8.7) with ESMTP id LAA00374; Tue, 17 Mar 1998 11:24:53 GMT Received: (from eivind@localhost) by bitbox.follo.net (8.8.6/8.8.6) id MAA07690; Tue, 17 Mar 1998 12:24:48 +0100 (MET) Message-ID: <19980317122447.16138@follo.net> Date: Tue, 17 Mar 1998 12:24:47 +0100 From: Eivind Eklund To: Studded , Mike Smith Cc: stable@FreeBSD.ORG Subject: Re: ATTENTION: Call for opinion re: root device naming change References: <199803161333.FAA14802@dingo.cdrom.com> <350DE4EC.7ECE44C@dal.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <350DE4EC.7ECE44C@dal.net>; from Studded on Mon, Mar 16, 1998 at 06:50:20PM -0800 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk On Mon, Mar 16, 1998 at 06:50:20PM -0800, Studded wrote: > Strong vote for keeping it in. In my mind (and with all due respect to > those involved) the problems we've seen were caused by too little > notice, too little regression testing, and too few people reading the > right lists at all. It seems to me that the bugs have been worked out of > the thing, and we have an opportunity to shout the news from the > mountaintops before 2.2.6 goes golden. That combined with the "Important > upgrade info" page that is going to go into production prior to 2.2.6 > should put us in a good position. I would really hate to take a step > backward at this point, especially if there's a chance there will be > another release in the 2.2 branch. > > That said, I did think of another way to handle the problem of a > mismatch between a new kernel and an old mount. Put the test for most up > to date mount version that someone suggested previously into > /usr/sbin/config. If the user is about to do damage, config should bomb > loud and ugly with the appropriate information. In fact, this method > could be extensible to other cases in the future with a little thought. > :) I'm having a hard time seeing how this can be considered generic; e.g, I'm building most of my stuff for use on _other_ machines, and what I have installed locally is of little concern to the build. Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message