From owner-freebsd-questions@FreeBSD.ORG Thu Dec 10 02:12:47 2009 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E9987106566C for ; Thu, 10 Dec 2009 02:12:47 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mx02.qsc.de (mx02.qsc.de [213.148.130.14]) by mx1.freebsd.org (Postfix) with ESMTP id A6F068FC0A for ; Thu, 10 Dec 2009 02:12:47 +0000 (UTC) Received: from r55.edvax.de (port-92-195-228-22.dynamic.qsc.de [92.195.228.22]) by mx02.qsc.de (Postfix) with ESMTP id A5E4D24AE1; Thu, 10 Dec 2009 03:12:46 +0100 (CET) Received: from r55.edvax.de (localhost [127.0.0.1]) by r55.edvax.de (8.14.2/8.14.2) with SMTP id nBA2CjwJ002742; Thu, 10 Dec 2009 03:12:45 +0100 (CET) (envelope-from freebsd@edvax.de) Date: Thu, 10 Dec 2009 03:12:45 +0100 From: Polytropon To: Maxim Khitrov Message-Id: <20091210031245.3fd58187.freebsd@edvax.de> In-Reply-To: <26ddd1750912091741g60fb428ape15225c12e9d8c8b@mail.gmail.com> References: <20091209002231.EB7D01065741@hub.freebsd.org> <675083.74248.qm@web65510.mail.ac4.yahoo.com> <20091210012256.7d2e8240@gumby.homeunix.com> <4B204FDD.3070005@lazlarlyricon.com> <26ddd1750912091741g60fb428ape15225c12e9d8c8b@mail.gmail.com> Organization: EDVAX X-Mailer: Sylpheed 2.4.7 (GTK+ 2.12.1; i386-portbld-freebsd7.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: freebsd-questions@freebsd.org Subject: Re: Dangerously Dedicated X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Polytropon List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Dec 2009 02:12:48 -0000 On Wed, 9 Dec 2009 20:41:40 -0500, Maxim Khitrov wrote: > On Wed, Dec 9, 2009 at 8:33 PM, Rolf Nielsen > wrote: > > As far as I understand it, it's called Dangerously Dedicated because it may > > cause other systems not to recognise the disk. Consequently, newfs'ing a > > slice without first partitioning it can hardly be DD, since that is what > > other systems do, right? > > That is correct. That slice will not be bootable, but you can use it > to store data. Being bootable is a matter of what the MBR boot block says. In a DD setting, it refers to the first partition (that's not within a slice), e. g. ad0a. Especially in a multi-OS setting, the use of slices seems to be strongly recommended so all operating systems behave in the required way (due to compatibility reasons, see "DOS primary partitions"), which limits the number of slices to 4. For plain storage, it's not needed to encapsulate the partition with the file system inside a slice, e. g. ad1 ad1s1 ad1s1e { [ (/data) ] } in comparison to ad1 ad1c { (/data) } And as it is known, the "c" can be omitted, as in # mount /dev/ad1 /data -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ...