From owner-freebsd-current Thu Mar 23 17:20:50 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id RAA03450 for current-outgoing; Thu, 23 Mar 1995 17:20:50 -0800 Received: from goof.com (root@goof.com [198.82.204.15]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id RAA03444 for ; Thu, 23 Mar 1995 17:20:48 -0800 Received: (from mmead@localhost) by goof.com (8.6.11/8.6.9) id UAA00277 for current@freebsd.org; Thu, 23 Mar 1995 20:20:31 -0500 From: "matthew c. mead" Message-Id: <199503240120.UAA00277@goof.com> Subject: tonight's kernel To: current@FreeBSD.org Date: Thu, 23 Mar 1995 20:20:30 -0500 (EST) X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 2819 Sender: current-owner@FreeBSD.org Precedence: bulk A kernel supped around 7:30 EST yields the following messages at boot: Mar 23 20:12:30 goof /kernel: sd0s1: start 0, end = 32767, size 2053880 Mar 23 20:12:30 goof /kernel: sd0s1: C/H/S end 32767 != end 2053879: invalid Mar 23 20:12:30 goof /kernel: sd1s1: start 32, end = 204799, size 204768: OK Mar 23 20:12:30 goof /kernel: sd1s2: start 204800, end = 2053879, size 1849080: OK Mar 23 20:12:30 goof /kernel: sd1: rejecting partition in BSD label: it isn't entirely within the slice Mar 23 20:12:30 goof /kernel: sd1: start 204800, end 2053879, size 1849080 Mar 23 20:12:30 goof /kernel: sd1d: start 0, end 2053879, size 2053880 Mar 23 20:12:30 goof /kernel: sd1: rejecting partition in BSD label: it isn't entirely within the slice Mar 23 20:12:30 goof /kernel: sd1e: start 32, end 204799, size 204768 Mar 23 20:12:30 goof /kernel: sd0s1: start 0, end = 32767, size 2053880 Mar 23 20:12:30 goof /kernel: sd0s1: C/H/S end 32767 != end 2053879: invalid Mar 23 20:12:30 goof /kernel: bpf: lo0 attached Mar 23 20:12:30 goof /kernel: sd0s1: start 0, end = 32767, size 2053880 Mar 23 20:12:31 goof /kernel: sd0s1: C/H/S end 32767 != end 2053879: invalid Mar 23 20:12:31 goof /kernel: sd1s1: start 32, end = 204799, size 204768: OK Mar 23 20:12:31 goof /kernel: sd1s2: start 204800, end = 2053879, size 1849080: OK Mar 23 20:12:31 goof /kernel: sd1: rejecting partition in BSD label: it isn't entirely within the slice Mar 23 20:12:31 goof /kernel: sd1: start 204800, end 2053879, size 1849080 Mar 23 20:12:31 goof /kernel: sd1d: start 0, end 2053879, size 2053880 Mar 23 20:12:31 goof /kernel: sd1: rejecting partition in BSD label: it isn't entirely within the slice Mar 23 20:12:31 goof /kernel: sd1e: start 32, end 204799, size 204768 Mar 23 20:12:31 goof /kernel: sd1s1: start 32, end = 204799, size 204768: OK Mar 23 20:12:31 goof /kernel: sd1s2: start 204800, end = 2053879, size 1849080: OK Mar 23 20:12:31 goof /kernel: sd1: rejecting partition in BSD label: it isn't entirely within the slice Mar 23 20:12:31 goof /kernel: sd1: start 204800, end 2053879, size 1849080 Mar 23 20:12:31 goof /kernel: sd1d: start 0, end 2053879, size 2053880 Mar 23 20:12:31 goof /kernel: sd1: rejecting partition in BSD label: it isn't entirely within the slice Mar 23 20:12:31 goof /kernel: sd1e: start 32, end 204799, size 204768 Did we change back to slice partitioning in the way that disklabel wants, or is it still going to be done the way sysinstall does things. If so, why do I get these messages, now? -matt -- Matthew C. Mead -> Virginia Tech Center for Transportation Research - -> Multiple Platform System and Network Administration Work Related -> mmead@ctr.vt.edu | mmead@goof.com <- All Other ---- ------- WWW -> http://www.goof.com/~mmead --- -----