From owner-freebsd-stable Wed Mar 22 20: 1:14 2000 Delivered-To: freebsd-stable@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 3228737C29A for ; Wed, 22 Mar 2000 20:01:10 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id VAA31397; Wed, 22 Mar 2000 21:01:08 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id VAA36386; Wed, 22 Mar 2000 21:01:07 -0700 (MST) Message-Id: <200003230401.VAA36386@harmony.village.org> To: Doug Barton Subject: Re: "dangerously dedicated" Cc: Vivek Khera , stable@FreeBSD.ORG In-reply-to: Your message of "Wed, 22 Mar 2000 19:53:44 PST." <38D99548.3201BC6D@gorean.org> References: <38D99548.3201BC6D@gorean.org> <14552.57732.739752.665443@onceler.kcilink.com> <4.3.2.20000321160347.00ad9b20@207.227.119.2> <38D50DBC.88FA8E4D@glue.umd.edu> <38D3AB72.366D851D@glue.umd.edu> <200003152159.OAA89926@harmony.village.org> <38D03E64.3D17FC34@glue.umd.edu> <200003190433.VAA04863@harmony.village.org> <200003212255.PAA26291@harmony.village.org> <200003222301.QAA34410@harmony.village.org> Date: Wed, 22 Mar 2000 21:01:07 -0700 From: Warner Losh Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <38D99548.3201BC6D@gorean.org> Doug Barton writes: : I'm curious, what kind of problems have you had, and how is using the : compatability slice an improvement? I've always used "dangerously : dedicated" on my freebsd-only disks, and I've never had a problem. I've had two classes of problems. First, I've needed to set a special disk geometry in the fdisk partition. I'm not sure why it matters, but it seems to make a big difference on some of my isa scsi machines. I've also had problems with partitions starting at offset 0. While ufs does offset things by 16 blocks, and the boot1 bootblock seems to have the fdisk partition table encoded in it (well, at least it seems to preserve what's there, if anything), I've had some problems that went away when I went to having a fdisk partition and starting at an offset of 16 or so. Most of these experiences were in the 1.x and 2.0 days. Bruce's slice code has vastly improved the situation. The second class of problems came into play when I later desided to install Win95 on some of may machines. Its installation program did bad things to the dangerously dedicated disks. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message