From owner-freebsd-stable Mon Oct 30 12:13:59 2000 Delivered-To: freebsd-stable@freebsd.org Received: from clmboh1-smtp1.columbus.rr.com (clmboh1-smtp1.columbus.rr.com [65.24.0.110]) by hub.freebsd.org (Postfix) with ESMTP id C6E4237B479; Mon, 30 Oct 2000 12:13:53 -0800 (PST) Received: from columbus.rr.com (dhcp065-024-012-043.columbus.rr.com [65.24.12.43]) by clmboh1-smtp1.columbus.rr.com (8.9.3/8.9.3) with ESMTP id PAA02143; Mon, 30 Oct 2000 15:10:46 -0500 (EST) Message-ID: <39FDD797.47B18AC7@columbus.rr.com> Date: Mon, 30 Oct 2000 15:18:31 -0500 From: Bill Moran X-Mailer: Mozilla 4.72 [en] (X11; I; FreeBSD 4.1-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: John Baldwin , FreeBSD-stable@FreeBSD.ORG Subject: Dangerously dedicated (was Re: Really odd "BTX halted" problem booting FreeBSD on VALinux h) References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John Baldwin wrote: > It is kind of semantic. However, on the alpha it is hardly dangerous. Nor > do we fake a MBR on the alpha (which is what makes it dangerous). The alpha > architecture doesn't use MBR's, but the PC arch does. Thus, having a disklabel > on the alpha is normal, having one at the start of a PC disk requires ugly > hacks that break the PC arch, hence the difference. Do I understand you correctly? Are you saying there are potential problems with a "dangerously dedicated" HDD on a PC? I don't use Micros~1 products on any of my machines (acutally, I use nothing but FreeBSD) so I've assumed that there's no reason to do anything other than "dangerously dedicated". Am I wrong is thinking that?? Is this one of those issues where "if it boots, it'll be fine" or is it something that could bite me later?? -Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message