From owner-freebsd-current Wed Jan 6 15:14:07 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA20226 for freebsd-current-outgoing; Wed, 6 Jan 1999 15:14:07 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ceia.nordier.com (m1-54-dbn.dial-up.net [196.34.155.54]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA20221 for ; Wed, 6 Jan 1999 15:14:02 -0800 (PST) (envelope-from rnordier@nordier.com) Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id BAA03150; Thu, 7 Jan 1999 01:10:13 +0200 (SAT) From: Robert Nordier Message-Id: <199901062310.BAA03150@ceia.nordier.com> Subject: Re: Trouble booting from WinNT with new boot loader In-Reply-To: from Julian Elischer at "Jan 6, 99 01:09:43 pm" To: julian@whistle.com (Julian Elischer) Date: Thu, 7 Jan 1999 01:10:12 +0200 (SAT) Cc: rnordier@nordier.com, braukmann@tse-online.de, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Julian Elischer wrote: > This is exactly why at whistle we use the 2nd block of the first > disk to store this stuff. (see 'nextboot(8)') > the bootblocks on da0 load a default from da0-block1, > which specify: > da(1,........ I've come to quite like the nextboot concept, the more I've thought about it. One advantage seems that it's just much easier for external programs (which may not be UFS-aware) to set up the bootblocks, or maybe just pass arguments to them. > I am thinking of adding code to actually make the 2nd block require to be > in it's own slice type (not 165) so that it is marked as being in-use > rather than using a 'free' block like we do now.. > > I've added a 4th slice below that shows what it would look like.... > what do you think? > The data for partition 3 is: > sysid 201,(FreeBSD bootspec) > start 1, size 1 (0 Meg), flag 0 > beg: cyl 0/ sector 2/ head 0; > end: cyl 0/ sector 2/ head 0 It could have the advantage of warning off other software. Modern versions of fdisk should allocate slices aligned to head boundaries; and the IBM/Microsoft OSes have a convention of ignoring any slice smaller than 64 sectors, anyway. Though there seems to be a mostly-accepted convention that all of cyl=0 head=0 is reserved for the boot manager these days, so that might be the only thing to worry about. -- Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message