Debian Squeeze now has this behaviour too.
What actually happens is that the lower bound of the extended container,
which is based on a cylinder boundary when created with eCOmStation's (OS/2) LVM disktool,
is moved upwards to a MiB boundary by the Debian Squeeze / Ubuntu 10.04+ installation process.
This causes the eComStation Logical Volume Management system to fail,
as it expects the extended container to start on a cylinder boundary.
It would be very neighbourly if the Linux people would respect eComStations disk-layout
and not touch the extended container.
Since the extended container can potentially contain other bootable operating systems,
this Linux installer behaviour could be considered quite anti-social, since it has no business
messing with the extended container.
There already exists a company that messes with parts of the disk it does not own for
more that decades.
Debian Squeeze now has this behaviour too.
What actually happens is that the lower bound of the extended container,
which is based on a cylinder boundary when created with eCOmStation's (OS/2) LVM disktool,
is moved upwards to a MiB boundary by the Debian Squeeze / Ubuntu 10.04+ installation process.
This causes the eComStation Logical Volume Management system to fail,
as it expects the extended container to start on a cylinder boundary.
It would be very neighbourly if the Linux people would respect eComStations disk-layout
and not touch the extended container.
Since the extended container can potentially contain other bootable operating systems,
this Linux installer behaviour could be considered quite anti-social, since it has no business
messing with the extended container.
There already exists a company that messes with parts of the disk it does not own for
more that decades.
Please don't duplicate this behaviour.