From owner-freebsd-current@FreeBSD.ORG Mon Aug 22 02:02:29 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 51048106564A; Mon, 22 Aug 2011 02:02:29 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-yi0-f54.google.com (mail-yi0-f54.google.com [209.85.218.54]) by mx1.freebsd.org (Postfix) with ESMTP id EB87C8FC08; Mon, 22 Aug 2011 02:02:28 +0000 (UTC) Received: by yib19 with SMTP id 19so3705134yib.13 for ; Sun, 21 Aug 2011 19:02:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=heSWDkDEt0HPut4F0ZF5brD3xE23pNXKr1/lqLUpIj8=; b=Nh8zc7WM03AoSF+WeYjztfw2EHuEGOhx+RzzLImcNFqdysB4IycvPZQjdrn5bJ8Cry Mp+wY8VbQ6gKO2UZGjnWSmclX2NOusELo6tZ7ToJrwNcpDPfIaeAC53GghmO8Uj8DkSR +PnzmEuO8XviNRlWwNXU9GsiuYouR73a/c3tM= MIME-Version: 1.0 Received: by 10.150.133.17 with SMTP id g17mr1087344ybd.272.1313978548181; Sun, 21 Aug 2011 19:02:28 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.150.145.21 with HTTP; Sun, 21 Aug 2011 19:02:27 -0700 (PDT) In-Reply-To: <0AF19658-2FA7-48EC-9EA2-67DC26DAC1D4@xcllnt.net> References: <4E4DB9A7.4040404@freebsd.org> <4E517978.2020705@freebsd.org> <64622705-80AB-4FEF-91E9-8F3041818B4E@xcllnt.net> <4E519C13.4060700@freebsd.org> <4E51B228.7030001@freebsd.org> <0AF19658-2FA7-48EC-9EA2-67DC26DAC1D4@xcllnt.net> Date: Mon, 22 Aug 2011 10:02:27 +0800 X-Google-Sender-Auth: Yxld9xvYdTTJbat_U1S5rAZ__9o Message-ID: From: Adrian Chadd To: Marcel Moolenaar Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: "freebsd-current@FreeBSD.org Current" , Nathan Whitehorn Subject: Re: Well, there goes Windows! 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: Mon, 22 Aug 2011 02:02:29 -0000 Honestly - if you're relying on doing anything that isn't read-only w/ GEOM right until "commit", I think you're doing it wrong. If anything, you should write something which manipulates geom tables in userland, and can have a geom database populated from the kernel. All of your subsequent tools (eg stuff which creates labels, raid devices, etc) should manipulate this table, not the kernel. Then when you're ready, you should write the updated table to disk. 2c, Adrian On 22 August 2011 09:48, Marcel Moolenaar wrote: > > On Aug 21, 2011, at 6:34 PM, Nathan Whitehorn wrote: >>> >>>> The regular partitioning editor only commits early in this particular = case, and asks about each subpartition tree separately with a big scary dia= log box. In the spirit of the autopartitioner, it makes one large scary dia= log, and always runs in early commit mode instead of potentially showing ma= ny scary dialogs about partitions the user doesn't necessarily even know ab= out. This behavior could be changed, but I think is the most friendly for t= he case in question: namely, "I want to blow away everything and let the in= staller handle all partitioning details by itself". >>> What about inserting a special class for doing commit/undo. The GEOM >>> simply keeps all modifications in memory and 1) forgets everything on >>> an undo operation or 2) writes all dirty sectors on a commit. This >>> could be used even instead of the gpart-private support, which also >>> removes the quirk for the null scheme. >>> >> >> Where would this class go? If it went below gpart (between gpart and use= rland), then it seems like we would lose the ability of gpart to validate i= ts parameters. Who would be responsible for inserting this GEOM into the st= ack? > > Between the disk GEOM and the gpart GEOM. The gpart utility would > still interact with the GEOM is before. > > -- > Marcel Moolenaar > marcel@xcllnt.net > > > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org= " >