From owner-freebsd-questions@FreeBSD.ORG Thu Dec 10 02:08:18 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 D5532106566B for ; Thu, 10 Dec 2009 02:08:18 +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 945A28FC15 for ; Thu, 10 Dec 2009 02:08:18 +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 B74AE1E461; Thu, 10 Dec 2009 03:08:17 +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 nBA28G3m002722; Thu, 10 Dec 2009 03:08:17 +0100 (CET) (envelope-from freebsd@edvax.de) Date: Thu, 10 Dec 2009 03:08:16 +0100 From: Polytropon To: Rolf Nielsen Message-Id: <20091210030816.152b05c9.freebsd@edvax.de> In-Reply-To: <4B204FDD.3070005@lazlarlyricon.com> References: <20091209002231.EB7D01065741@hub.freebsd.org> <675083.74248.qm@web65510.mail.ac4.yahoo.com> <20091210012256.7d2e8240@gumby.homeunix.com> <4B204FDD.3070005@lazlarlyricon.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:08:18 -0000 On Thu, 10 Dec 2009 02:33:17 +0100, 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. Primarily, it's called "dedicated" (only) because it describes a setting where a whole hard disk is dedicated to the FreeBSD operating system. The addition "dangerously" seems to describe the danger that other operating systems cannot handle such a disk layout, or may cause problems to them - but I don't know this for sure because I'm not a "multi-booter". :-) > Consequently, > newfs'ing a slice without first partitioning it can hardly be DD, since > that is what other systems do, right? If you run newfs inside a slice, you would create a partition covering the whole slice, and so it's still compatibility mode (the opposite of DD mode); DD mode implies the absence of a slice at all. da0 da0s1 da0s1c { [ (/) ] } Other systems operate on slice level, on a "DOS primary partition", where they create their file systems in a certain way, e. g. an msdos file system. In such a case, there are no partitions inside the slice because partitions are specific to operating systems like FreeBSD. da0 da0s1 da0s2 da0s3 da0s3a { [ C: ] [ D: ] [ (/) ] } msdosfs msdosfs ufs -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ...