From owner-freebsd-stable Wed Jul 26 7:33:42 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 8736937B671 for ; Wed, 26 Jul 2000 07:33:38 -0700 (PDT) (envelope-from fred@veriohosting.com) Received: by gatekeeper.veriohosting.com; Wed, 26 Jul 2000 08:33:37 -0600 (MDT) Received: from unknown(192.168.1.7) by gatekeeper.veriohosting.com via smap (V3.1.1) id xma028956; Wed, 26 Jul 00 08:33:13 -0600 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 IAA62438; Wed, 26 Jul 2000 08:33:13 -0600 (MDT) Date: Wed, 26 Jul 2000 08:42:25 -0600 (MDT) From: Fred Clift X-Sender: fred@vespa.orem.iserver.com To: R Joseph Wright Cc: freebsd-stable@FreeBSD.org Subject: Re: No /boot/loader (dangerously dedicated) In-Reply-To: <20000725171302.B9956@manatee.mammalia.org> 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 On Tue, 25 Jul 2000, R Joseph Wright wrote: > On Tue, Jul 25, 2000 at 03:29:08PM -0600, Fred Clift wrote: > > On Sun, 23 Jul 2000, John Baldwin wrote: > > > > > the geometry of a disk. At the very least, dangerously dedicated mode > > > should specify a valid length for the slice the way that truly dedicated > Would you mind posting that script? I'd like to see it. I'm told that at least for some people that disklabel auto actually does this as recently as 4.0-RELEASE -- I've not had a chance to verify this but I know that using the da driver in 3.4 that this doesn't happen so I do approximately the following (from a C program, that runs from a pxe-like boot-rom booted kernel) note that only the important bits are shown and some pseudo-code for clarity fo = fopen(....... ... fprintf(fo, "\n\n\n\ny\n\n\n%d\n\ny\n\ny\n",driveInfo[disk].size); fclose(fo); /* driveInfo[disk].size is the number of sectors/unit as reported by disklabel */ /* and then this is done.... */ /sbin/fdisk -u da0 < /tmp/fdisk.in This gets the right numbers in the disk label for me to make my Intel ISP2150 boxes to work right (LB440GX+ based I believe). An interesting side note is that if I dd the stock boot0 (with the bogus partition table entry) onto _any_ disk in the system, regardless of what disk is the boot disk, then the machine wont boot at all, not a floppy, not any of the boot devices, nothing. I have to either low-level scsi format the disk or boot from our custom bootrom and nuke it from there... I would say that any machine that can be crippled by having corrupted data on a non-boot disk is by design broken. But, thats another discussion. Fred -- Fred Clift - fred@veriohosting.com -- 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