> Borsenkow Andrej <[EMAIL PROTECTED]> writes: > > > I guess, diskdrake should warn at least (or even better refuse to do) > > changes if they result in existing partition numbers change. I presume > > that is exactly what happened for this poor guy: > > good idea. > > Such things happen when > - removing an extended partition (the logical partitions, not the main one) > when it's not the last one > - adding an extended partition at the beginning of the main extended > partition > It should not be too hard to detect those cases. > > > or maybe diskdrake could modify the lilo.conf or menu.lst?
+ fstab + raidtab + LVM + ... Besides how can you redo lilo configuration when partition you want to enter there not yet exists? No, you have to give user detailed explanation what is going to happen and (probably) leave it for him to decide. -andrej