From owner-freebsd-hackers Sun Jan 22 18:26:53 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id SAA18231 for hackers-outgoing; Sun, 22 Jan 1995 18:26:53 -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 SAA18224 for ; Sun, 22 Jan 1995 18:26:48 -0800 Received: (from mmead@localhost) by goof.com (8.6.9/8.6.9) id VAA08808 for hackers@freebsd.org; Sun, 22 Jan 1995 21:26:26 -0500 From: "matthew c. mead" Message-Id: <199501230226.VAA08808@goof.com> Subject: writing bootcode; need a method To: hackers@FreeBSD.org Date: Sun, 22 Jan 1995 21:26:25 -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: 810 Sender: hackers-owner@FreeBSD.org Precedence: bulk Does anyone know how to write the FreeBSD bootcode despite the fact that disklabel doesn't like the way sysinstall sets up the drives? My setup is this: I have an IDE drive (for a couple doom games and such), so I still want FreeBSD to boot off sd0. I need to put the bootmanager on the wd0 drive, and then to run FreeBSD, point it to disk 2. Then I've got to manually type in hd(1,a)/kernel each time it boots. I know how to modify the bootcode and rebuild it, but disklabel won't write the bootcode, cause it doesn't like how sysinstall set things up... Any ideas? -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