From owner-freebsd-current Tue Nov 24 10:40:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA22584 for freebsd-current-outgoing; Tue, 24 Nov 1998 10:40:47 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alpha.xerox.com (alpha.Xerox.COM [13.1.64.93]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id KAA22579 for ; Tue, 24 Nov 1998 10:40:45 -0800 (PST) (envelope-from fenner@parc.xerox.com) Received: from mango.parc.xerox.com ([13.1.102.232]) by alpha.xerox.com with SMTP id <52088(2)>; Tue, 24 Nov 1998 10:40:34 PST Received: (from fenner@localhost) by mango.parc.xerox.com (8.8.8/8.8.8) id KAA24530; Tue, 24 Nov 1998 10:40:32 -0800 (PST) (envelope-from fenner) Date: Tue, 24 Nov 1998 10:40:32 PST From: Bill Fenner Message-Id: <199811241840.KAA24530@mango.parc.xerox.com> To: fenner@parc.xerox.com, jdp@polstra.com Subject: Re: Is fsck broken for autoboot? Cc: current@FreeBSD.ORG In-Reply-To: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I don't know when -stable switched to real slices, but I was experiencing this problem when I was booting a mix of 2.2.2 (required compatibility slice) and 2.2.6 (required real slice) kernels on the same machine - if I put the "compatible" device in fstab, the 2.2.6 kernel would fail to mount / if fsck had to fix it. Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message