On Wed, Feb 28, 2007 at 03:54:42PM +0100, Frans Pop wrote: > On Friday 23 February 2007 16:27, Colin Watson wrote: > > I think it would make partman a bit easier to use if we added a check.d > > directory run before we ask the user to confirm changes and then run > > commit.d (only when preparing to exit partman, not e.g. when committing > > changes in order to configure LVM) and moved all the finish.d scripts > > with numbers less than 20 there. > > The basic idea and changes in the partman script seem sane enough to me. > Maybe checks that can only be performed after committing (if there are > any) could stay in finish.d.
Right, there's no harm in them staying there even e.g. if there's some doubt. > Feel free to investigate further and set up a migration path. Migration path is easy: do partman-base first and then do everything else, marking them as needing partman-base for migration to testing. Cheers, -- Colin Watson [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
