Bug#217503: Evil autopartkit should _NEVER_ _NEVER_ try to overwrite an unknown partition table
Am Sam, den 25.10.2003 schrieb Sven Luther um 11:29:
> Package: autopartkit
> Version: 0.62
> Severity: critical
> Justification: causes serious data loss
>
> Ok, i am trying to make debian-installer work on the pegasos, and to my
> surprise, yesterday, autopartkit without really giving me the choice
> (but then, i might have missed something with the garbled console i
> got), just proceeded to overwrite my partition table and something
> started to format a partition. So no more powerpc kernel work, no more
> parted patches, no more changes to debian-installer. No more anything i
> had on that disk, which was not even the disk i was doing the
> installation tests on.
I know that partitioner is broken for ppc at the moment, because of the
wrong path to archdetect (fixed in CVS).
To really trak down the problem it would be usefull to have some more
information. Did you ever see the "This will destroy your data!"
warning? Autopartkit sould always show that at least.
There's an other bug that autopartkit and partconf-mkfstab both provide
"created-fstab". We should find a way to avoid showing autopartkit as an
option to only create the fstab. I don't know if partconf-mkfstab is
able to create an fstab if partitions are made with autopartkit. If
that's possible we could drop fstab creation from autopartkit.
> It is also not only pegasos related, but will break on m68k/amiga as
> well as ppc/amiga, as well as all the not yet supported by libparted
> partition schemes.
Probably there shoulb be a test for supported partition tables in
"isinstallable" which fails if the default partition table for the arch
is not supported by parted.
Friendly
Gaudenz
Reply to: