From owner-freebsd-current Mon Jan 4 03:18:40 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA00404 for freebsd-current-outgoing; Mon, 4 Jan 1999 03:18:40 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ceia.nordier.com (m2-10-dbn.dial-up.net [196.34.155.74]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA00399 for ; Mon, 4 Jan 1999 03:18:32 -0800 (PST) (envelope-from rnordier@nordier.com) Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id NAA00747; Mon, 4 Jan 1999 13:16:39 +0200 (SAT) From: Robert Nordier Message-Id: <199901041116.NAA00747@ceia.nordier.com> Subject: Re: Update bootblocks with dedicated disks? In-Reply-To: <19990104105719.A15320@sanyusan.se> from synker at "Jan 4, 99 10:57:20 am" To: synker@sanyusan.se (synker) Date: Mon, 4 Jan 1999 13:16:36 +0200 (SAT) Cc: rnordier@nordier.com, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG synker wrote: > Maybe I could also ask if it recommended to use 'dangerously dedicated' > disks on a FreeBSD server or not. > > Some ppl in both freebsd mailinglista and in news said that it is not > recommended to use the 'dangerrously dedicated' disks since there have been > some reported trouble with those? Anybody know of what kind of trouble? The trouble with "dangerously dedicated" disks is that they appear, to everything besides FreeBSD, to contain a corrupted "partition" table (slice table, in BSD terms). If you let some non-FreeBSD disk utility near the disk, it may decide to "fix" the damage. Also, according to the FAQ, some BIOSes may refuse to boot a disk if they believe the table is invalid. Folks who are more orientated to UNIX on non-PC hardware may prefer an unsliced (dangerously dedicated) disk for consistency. So, unless you are strongly in favor of unsliced disks, you probably don't want to use them. > > And if I should use 'standard' disks with slices instead how can I get FreeBSD > to boot? Last time I tried this 'BootEasy' popped up after reboot and showed: > > F1: BSD > F2: ???? or something... > > Since FreeBSd is the only OS on my boxes I couldnt boot by pressing F1. I had > to use a floppy and type in the kernel location by hand at the boot prompt. You probably want the sysinstall "Standard MBR" option, or the fdisk equivalent, rather than boot0/booteasy. With this option, the disk is dedicated to one OS, but not dangerously so. -- Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message