From owner-freebsd-current Thu Dec 2 19: 6:18 1999 Delivered-To: freebsd-current@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 4C17114FF7; Thu, 2 Dec 1999 19:06:12 -0800 (PST) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.1/8.9.1) with ESMTP id WAA18323; Thu, 2 Dec 1999 22:05:04 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.3/8.9.1) id WAA70771; Thu, 2 Dec 1999 22:04:33 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Thu, 2 Dec 1999 22:04:33 -0500 (EST) To: mjacob@feral.com Cc: Greg Lehey , Poul-Henning Kamp , current@FreeBSD.ORG Subject: Re: HEADS-UP: bdevs have been assimilated. In-Reply-To: References: <19991202202419.01433@mojave.sitaranetworks.com> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14407.12709.371848.954058@grasshopper.cs.duke.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Jacob writes: > > > Can't you boot from the old kernel? Or have you already wiped the > > I can boot the old kernel. A MAKEDEV using the new MAKEDEV has now wiped > all block devs, so swapon, etc. ,fail.. However, this is the conundrum- > it's not safe to do a 'make installworld' on a two week old kernel, but > the new kernel with old mount, fsck, etc., obviously cannot cope with the > new 'raw-only' devices. > > An experience like this will move users to OpenBSD. This kind of jump up > is completely unacceptable. Slow down. You are getting screwed by a combination of things. It isn't all phk's fault. The bdev elimination is one factor, but the most important one (the fsck/mount segv) is due to int/long breakage introduced version 1.85 of mount.h. This happened at the worst possible time (just after the bdev elimination). If I wasn't such a timid committer, I would have just committed the damned fix yesterday, before running it by Kirk & you wouldn't have had this problem. I tried to be vocal about it (messages to -alpha and -committers), but I guss that wasn't enought. Sorry, Drew ------------------------------------------------------------------------------ Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin Duke University Email: gallatin@cs.duke.edu Department of Computer Science Phone: (919) 660-6590 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message