From owner-freebsd-hackers Sun Apr 9 18:28:27 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id B224F37B67B for ; Sun, 9 Apr 2000 18:28:21 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id TAA17343 for ; Sun, 9 Apr 2000 19:28:20 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id TAA15168 for ; Sun, 9 Apr 2000 19:28:15 -0600 (MDT) Message-Id: <200004100128.TAA15168@harmony.village.org> To: hackers@freebsd.org Subject: How hard would it be... Date: Sun, 09 Apr 2000 19:28:15 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ... to get FreeBSD to boot off a BSD partition that wasn't labeled as 0xa5? I'm looking for a way to create a disk that a certain picky BIOS will like and boot off of, and I think I have to create it with a certain ID and then it will be happy. I suspect that it involves hacking the boot blocks, the boot loader and the kernel's idea of the BSD partition number in disk*subr.c. Are there other things that are needed? I may be barking up the wrong tree in trying to get around this BIOS's pickiness, but I thought I'd at least ask. Yes, this is for a well-known, cheap internet device, which shall remain nameless. I've already OPENed mine up. a real lookER. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message