Pixel <[EMAIL PROTECTED]> writes:
>
> Here is the why of these problems:
>
> - eraseBadPartitions was on
> - somewhere, the partition table could be written with no warning (silly me :( )
>
- and also eraseBadPartitions did not set the flag isDirty
(otherwise diskdrake.pm would have warned, that was the thing i didn't
understand, now all is clear!)
> that way i may be able to find the main problem, that is diskdrake not being
> able to understand your partition table and blanking it...
>
alas that one is still to be fixed ;-(
cu Pixel.
