From owner-freebsd-current Mon Jan 4 01:58:59 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA23892 for freebsd-current-outgoing; Mon, 4 Jan 1999 01:58:59 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from enterprise.sanyusan.se (enterprise.sanyusan.se [195.24.160.51]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA23883 for ; Mon, 4 Jan 1999 01:58:54 -0800 (PST) (envelope-from synker@enterprise.sanyusan.se) Received: (from synker@localhost) by enterprise.sanyusan.se (8.8.8/8.8.8) id KAA15343; Mon, 4 Jan 1999 10:57:20 +0100 (CET) (envelope-from synker) Date: Mon, 4 Jan 1999 10:57:20 +0100 From: synker To: Robert Nordier Cc: current@FreeBSD.ORG Subject: Re: Update bootblocks with dedicated disks? Message-ID: <19990104105719.A15320@sanyusan.se> References: <19990104100315.B14764@sanyusan.se> <199901040944.LAA02842@ceia.nordier.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i In-Reply-To: =?iso-8859-1?Q?=3C199901040944=2ELAA02842=40ceia=2Enordier=2Ecom=3E=3B_f?= =?iso-8859-1?Q?rom_Robert_Nordier_on_M=E5n=2C_Jan_04=2C_1999_at_11:44:48?= =?iso-8859-1?Q?am_+0200?= Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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? 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. Best regards, === synker - synker@sanyusan.se To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message