From owner-freebsd-current@FreeBSD.ORG Tue Feb 17 19:58:54 2009 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 46EF71065676 for ; Tue, 17 Feb 2009 19:58:54 +0000 (UTC) (envelope-from phk@critter.freebsd.dk) Received: from phk.freebsd.dk (phk.freebsd.dk [130.225.244.222]) by mx1.freebsd.org (Postfix) with ESMTP id 0AB188FC0C for ; Tue, 17 Feb 2009 19:58:53 +0000 (UTC) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (critter.freebsd.dk [192.168.61.3]) by phk.freebsd.dk (Postfix) with ESMTP id 0D42C3F130; Tue, 17 Feb 2009 19:58:53 +0000 (UTC) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.14.3/8.14.3) with ESMTP id n1HJwulq015553; Tue, 17 Feb 2009 19:58:56 GMT (envelope-from phk@critter.freebsd.dk) To: Marcel Moolenaar From: "Poul-Henning Kamp" In-Reply-To: Your message of "Tue, 17 Feb 2009 10:59:57 PST." <9FE792C6-8560-4C64-BD74-CD70DF5EBBF5@mac.com> Date: Tue, 17 Feb 2009 19:58:56 +0000 Message-ID: <15552.1234900736@critter.freebsd.dk> Sender: phk@critter.freebsd.dk Cc: "Bjoern A. Zeeb" , FreeBSD current mailing list , Ulf Lilleengen Subject: Re: boot0cfg -s vs. GEOM_PART_*? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Feb 2009 19:58:54 -0000 In message <9FE792C6-8560-4C64-BD74-CD70DF5EBBF5@mac.com>, Marcel Moolenaar wri tes: >That won't be as easy as boot0cfg. Both fdisk and bsdlabel >do all partitioning operations in memory and then expect to >dump/write the blob. This is not how gpart works, so there's >a mismatch in paradigm. The reason for that modus operandi, was that the kernel only needed code to read the metadata, the software that formatted and wrote the metadata could be contained entirely in userland thus not bloating the kernel. Your choice is legit as well, with today RAM sizes I doubt the difference is measureable. But not updating boot0cfg to support the new API got you a bad mark in my book. I would prefer if fdisk and bsdlabel also kept working or at least gave some guidance on what to do. Poul-Henning -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence.