From owner-freebsd-questions@FreeBSD.ORG Fri Aug 12 01:49:41 2005 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DD82A16A41F for ; Fri, 12 Aug 2005 01:49:41 +0000 (GMT) (envelope-from dpk@dpk.net) Received: from shared10.hosting.flyingcroc.net (shared10.hosting.flyingcroc.net [207.246.149.144]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5B5C143D45 for ; Fri, 12 Aug 2005 01:49:39 +0000 (GMT) (envelope-from dpk@dpk.net) Received: from shared10.hosting.flyingcroc.net (localhost [127.0.0.1]) by shared10.hosting.flyingcroc.net (8.12.9p2/8.12.10) with ESMTP id j7C1ncrR000187; Thu, 11 Aug 2005 18:49:38 -0700 (PDT) Received: from localhost (dpk@localhost) by shared10.hosting.flyingcroc.net (8.12.9p2/8.12.10/Submit) with ESMTP id j7C1ncXK000183; Thu, 11 Aug 2005 18:49:38 -0700 (PDT) X-Authentication-Warning: shared10.hosting.flyingcroc.net: dpk owned process doing -bs Date: Thu, 11 Aug 2005 18:49:38 -0700 (PDT) From: dpk X-X-Sender: dpk@shared10.hosting.flyingcroc.net To: Randy Schultz In-Reply-To: Message-ID: <20050811184137.R5643@shared10.hosting.flyingcroc.net> References: <20050811202852.69489.qmail@web53315.mail.yahoo.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: freebsd-questions@freebsd.org Subject: Re: wizard mode docs X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Aug 2005 01:49:42 -0000 On Thu, 11 Aug 2005, Randy Schultz wrote: > Hey all, > > Is there any documentation on wizard mode? I'm just wondering what the > scan function does. Looking at the source, I would guess that it counts how many 512 byte blocks there are on a device. It prints B: at the beginning and G: at the end of the device, I believe. It appears to be capable of handling multiple beginnings and ends, but I'm not sure how that works (would a read of the full disk device, at the end of a slice, not read a full 512 bytes? I don't know.)