From owner-freebsd-arch Mon Dec 10 17:37:51 2001 Delivered-To: freebsd-arch@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 0E8B837B416; Mon, 10 Dec 2001 17:37:49 -0800 (PST) Received: (from dillon@localhost) by apollo.backplane.com (8.11.6/8.9.1) id fBB1bm149878; Mon, 10 Dec 2001 17:37:48 -0800 (PST) (envelope-from dillon) Date: Mon, 10 Dec 2001 17:37:48 -0800 (PST) From: Matthew Dillon Message-Id: <200112110137.fBB1bm149878@apollo.backplane.com> To: Jordan Hubbard Cc: Robert Watson , Peter Wemm , Terry Lambert , freebsd-arch@FreeBSD.ORG Subject: Re: Proposed auto-sizing patch to sysinstall (was Re: Using a larger block size on large filesystems) References: <44607.1008027292@winston.freebsd.org> Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG : :The reason that it's there, and I disliked it too when I first thought :about it, is that since the partitions are not created until the very :end, you don't get the nice /dev/sd0s1f type of device names since the :label editor doesn't know this until it creates the chunks with Oh. It's REAL easy to create the partitions in real time. If you look at the code I comitted to -current to do the scale retry loop and then consider that I also added a flag to the Chunk structure indicating the automatically created chunks, all you have to do is maintain a temporary copy of your disk template and delete/regenerate the auto partitions every time someone makes a change. I think it's very important for the user to see what is going on in real time. :libdisk. The reason it doesn't create them initially is because :everything except the manually created filesystems are done :"speculatively" since it would be very expensive to create and delete :chunks when shuffling between profiles, and libdisk is also fragile It's inexpensive. A few microseconds per keystroke at most... nothing is actually going to disk after all, you are just manipulating a bunch of malloc()'d libdisk structures. :enough that I'd sort of expect that to break if you did it enough :times. So I thought the user might like the chance to actually see If so we'll fix the bugs. It's been fairly dependable in my tests. : :> If you haven't already, each profile needs to have a small paragraph :> associated with it documenting what it is designed to do. Then as you : :Not a paragraph, but a single line, yes. It's displayed at the bottom :of the screen whenever auto mode is invoked or the profile is switched. : :- Jordan -MAtt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message