From owner-freebsd-questions Sat Jun 17 19:52: 3 2000 Delivered-To: freebsd-questions@freebsd.org Received: from john.baldwin.cx (john.geekhouse.net [64.81.6.51]) by hub.freebsd.org (Postfix) with ESMTP id 49D4E37B919 for ; Sat, 17 Jun 2000 19:51:44 -0700 (PDT) (envelope-from john@baldwin.cx) Received: (from john@localhost) by john.baldwin.cx (8.9.3/8.9.3) id TAA04361; Sat, 17 Jun 2000 19:51:33 -0700 (PDT) (envelope-from john) Message-Id: <200006180251.TAA04361@john.baldwin.cx> X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20000618041447.A631@hades.hell.gr> Date: Sat, 17 Jun 2000 19:51:33 -0700 (PDT) Organization: BSD, Inc. From: John Baldwin To: Giorgos Keramidas Subject: Re: reinstalling boot blocks... Cc: questions@FreeBSD.ORG, Shawn Ramsey Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 18-Jun-00 Giorgos Keramidas wrote: > On Fri, Jun 16, 2000 at 05:41:16PM -0700, Shawn Ramsey wrote: >> What is the easiest/safest way to re install the boot blocks on a >> 3.4-RELEASE machine? Can I just use the boot disks, and write out the >> changes in fdisk? (being sure the newfs flag is N! ) ? > > What you want is boot0cfg. Just run on the disks you want to install > the boot loader the command 'boot0cfg -B' and according to the manpage > of boot0cfg the MBR will be replaced by a new boot block, without > affecting the existing slice table. That just updates the MBR. FreeBSD's actual boot blocks are boot1, boot2, and the loader. The loader is loaded from /boot/loader, so a simple make world updates it. The other boot blocks (boot1 and boot2) have to be installed using 'disklabel -B'. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.cslab.vt.edu/~jobaldwi/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message