From owner-freebsd-current Sat Apr 21 11:35:19 2001 Delivered-To: freebsd-current@freebsd.org Received: from mass.dis.org (mass.dis.org [216.240.45.41]) by hub.freebsd.org (Postfix) with ESMTP id 8AA6737B43C; Sat, 21 Apr 2001 11:35:17 -0700 (PDT) (envelope-from msmith@mass.dis.org) Received: from mass.dis.org (msmith@localhost [127.0.0.1]) by mass.dis.org (8.11.3/8.11.2) with ESMTP id f3LIdGC01045; Sat, 21 Apr 2001 11:39:18 -0700 (PDT) (envelope-from msmith@mass.dis.org) Message-Id: <200104211839.f3LIdGC01045@mass.dis.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: John Baldwin Cc: "David W. Chapman Jr." , imp@FreeBSD.org, freebsd-current@FreeBSD.org Subject: Re: kernel core In-reply-to: Your message of "Sat, 21 Apr 2001 10:26:45 PDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 21 Apr 2001 11:39:16 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > You need to rebuild fsck and install it and fsck your filesystems. This is the > dirpref changes biting you. Warner, we probably need an entry in UPDATING for > the dirpref changes that warn people to build and install a new fsck before > booting a dirpref kernel. Er. This really isn't very good; I can see all sorts of opportunities here for disk migration between -stable and -current systems causing massive headaches. I assume there's a better fix in the works, so that a "dirpref-touched" disk can be moved back to a pre-dirpref system? -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message