From owner-freebsd-stable Wed Nov 22 20:56:52 2000 Delivered-To: freebsd-stable@freebsd.org Received: from gatekeeper.veriohosting.com (gatekeeper.veriohosting.com [192.41.0.2]) by hub.freebsd.org (Postfix) with ESMTP id 4597537B479; Wed, 22 Nov 2000 20:56:50 -0800 (PST) Received: by gatekeeper.veriohosting.com; Wed, 22 Nov 2000 21:56:49 -0700 (MST) Received: from unknown(192.168.1.7) by gatekeeper.veriohosting.com via smap (V3.1.1) id xma021813; Wed, 22 Nov 00 21:56:30 -0700 Received: from vespa.orem.iserver.com (vespa.orem.iserver.com [192.168.1.144]) by orca.orem.veriohosting.com [Verio Web Hosting, Inc. 801.437.0200] (8.8.8) id VAA20458; Wed, 22 Nov 2000 21:56:30 -0700 (MST) Date: Wed, 22 Nov 2000 22:15:11 -0700 (MST) From: Fred Clift X-Sender: fred@vespa.orem.iserver.com To: "Chad R. Larson" Cc: Roman Shterenzon , msmith@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: Dangerously Dedicated In-Reply-To: <200011210417.VAA07691@freeway.dcfinc.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Simple solution? Don't use DD. > > Slightly less simple? Don't use DD on drives that are in any way > involved with the boot process, but go ahead on data-only drives. heh -- intel's LB440GX+ motherboards with recent bioses wont boot if _any_ drive in the system has 0xAA55 on the end of the sector 0, but then not valid information on the disk -- ie take any disk in the box - including non-boot disks and dd boot1 onto sector 0. The box will now no longer boot untill you remove the disk. Fortunately, PXE booting still works and you can remotely recover from problems like this if you have it set up... :) Now thats what I call and improved bios. ugh. Fred -- Fred Clift - fclift@verio.net -- Remember: If brute force doesn't work, you're just not using enough. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message