From owner-freebsd-stable Tue Mar 17 05:11:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA09595 for freebsd-stable-outgoing; Tue, 17 Mar 1998 05:11:05 -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 FAA09587 for ; Tue, 17 Mar 1998 05:11:01 -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 HAA27672; Tue, 17 Mar 1998 07:09:54 -0600 (CST) X-Sender: rkw@mail.dataplex.net Message-Id: In-Reply-To: <350DE4EC.7ECE44C@dal.net> References: <199803161333.FAA14802@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Tue, 17 Mar 1998 07:06:14 -0600 To: Studded From: Richard Wackerbarth Subject: Re: ATTENTION: Call for opinion re: root device naming change Cc: Mike Smith , stable@FreeBSD.ORG Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk At 8:50 PM -0600 3/16/98, 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 I believe that this is incorrect. I, am I am sure others who might not be so vocal, have a configuration that I don't know how to use with the new kernel. As I understand it, Mike understands the problem but does not (yet) have a solution short of reformatting the HD. > 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. >:) This is not a version mismatch problem. I have the latest (-stable) of everything. This includes the "mount", MAKEDEV, and kernel changes. All imagined sd0 entries are in /dev, etc. At a MINIMUM, I think that we need a script which will examine the HD's, the /dev tree and fstab and tell us what to change BEFORE we try to use it. Richard Wackerbarth To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message