看板 FB_current 關於我們 聯絡資訊
On Aug 21, 2011, at 6:34 PM, Nathan Whitehorn wrote: >>=20 >>> The regular partitioning editor only commits early in this = particular case, and asks about each subpartition tree separately with a = big scary dialog box. In the spirit of the autopartitioner, it makes one = large scary dialog, and always runs in early commit mode instead of = potentially showing many scary dialogs about partitions the user doesn't = necessarily even know about. This behavior could be changed, but I think = is the most friendly for the case in question: namely, "I want to blow = away everything and let the installer 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. >>=20 >=20 > Where would this class go? If it went below gpart (between gpart and = userland), then it seems like we would lose the ability of gpart to = validate its parameters. Who would be responsible for inserting this = GEOM into the stack? Between the disk GEOM and the gpart GEOM. The gpart utility would still interact with the GEOM is before. --=20 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"