From owner-freebsd-hackers Mon Jan 23 11:23:44 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id LAA07808 for hackers-outgoing; Mon, 23 Jan 1995 11:23:44 -0800 Received: from goof.com (root@goof.com [198.82.204.15]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id LAA07796 for ; Mon, 23 Jan 1995 11:23:41 -0800 Received: (from mmead@localhost) by goof.com (8.6.9/8.6.9) id OAA03201; Mon, 23 Jan 1995 14:23:29 -0500 From: "matthew c. mead" Message-Id: <199501231923.OAA03201@goof.com> Subject: Re: writing bootcode; need a method To: terry@cs.weber.edu (Terry Lambert) Date: Mon, 23 Jan 1995 14:23:28 -0500 (EST) Cc: hackers@FreeBSD.org In-Reply-To: <9501231851.AA08997@cs.weber.edu> from "Terry Lambert" at Jan 23, 95 11:51:41 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 971 Sender: hackers-owner@FreeBSD.org Precedence: bulk Terry Lambert wrote: > Examining a disk: [ good description of how partitions, slices, mbrs work omitted ] > For right now, you are required to have a disklabel before proceeding. This unfortunately isn't the problem. The problem lies in the fact that the sysinstall does not require BSD partitions to begin and end on cylinder boundaries, whereas the disklabel program does. Thus, the disklabel program, when told to write boot code, finds what it considers to be errors with the disklabel, because sysinstall has made partitions that don't begin/end on cylinder boundaries, and does not write out the new boot code, thus hd(1,a)/kernel can NOT be made the default, again, simply because disklabel never writes the boot code. -matt -- Matthew C. Mead -- System/Network Administration, User Support, Software Devel. Virginia Tech Center for Transportation Research Work Related: mmead@ctr.vt.edu | All Other: mmead@goof.com WWW: http://www.goof.com:/~mmead