From owner-freebsd-current Fri Mar 12 1:26: 8 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 7B05415305 for ; Fri, 12 Mar 1999 01:24:24 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id BAA06749; Fri, 12 Mar 1999 01:24:44 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: "John W. DeBoskey" Cc: freebsd-current@FreeBSD.ORG Subject: Re: 4.0-19990311-SNAP bootblock install weirdness In-reply-to: Your message of "Fri, 12 Mar 1999 00:18:36 EST." <199903120518.AAA84687@bb01f39.unx.sas.com> Date: Fri, 12 Mar 1999 01:24:44 -0800 Message-ID: <6747.921230684@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > to wipe out the front-end of the boot disk. I then re-installed > the 4.0 system a 3rd time and it now boots normally. I am unable to > explain why this happened, but hope that someone with more experience > with the sysinstall/boot code can shed some light on it. No, that's just pretty weird. :-) I wonder if the geometry was calculated differently in the two cases, did you manage to compare numbers in the fdisk screen in the before-and-after case? Now that you've zero'd it, it makes analysis of the original condition a little more difficult. :) > lrwxrwxrwx 1 2035 207 19 Feb 12 04:09 compat22 -> ../current/compat22 Yep, if you're mirroring these bits, you need to fetch "through" that link and populate compat22. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message