On Wed, 2009-09-16 at 14:43 +0200, Joel Granados Moreno wrote: > * storage/partitioning.py (doPartitioning): By default we run both the > grow code and the allocation code. We could, If we were very careful, > avoid running either the allocation or the grow parts. This still makes me very uncomfortable. It seems like a pretty big change to the process for a limited value-add. Is the purpose of this so that you can toggle growth on demand or is it so you can identify free space between initial allocation and growth? I have a patch waiting to go into post-F12 rawhide that completely reimplements growPartitions. If the endgame of this patch is to find out if there is free space before partitions are grown, there are much less disruptive ways to do that. Here's a link to the current patch, just in case you want to take a look: http://dlehman.fedorapeople.org/20090915-grow-partitions.patch Dave _______________________________________________ Anaconda-devel-list mailing list Anaconda-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/anaconda-devel-list
