From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6b)
Description of problem:
Assume that fedora is being installed in an extended partition. All 3
volumes, /, boot and swap will be added in this extended partition.
Also assume there's already one volume existing already in this
extended partition and it's at the high end of the partition.
When fedora creates the necessary 3 volumes, it modifies the chain of
extended boot records for the extended partition. Instead of placing
the new volumes at the beginning of the chain (since they're the first
in the partition), they get linked at the end of the chain. Although
this produces no observable problems with Fedora, if a partition
editor such as BootIt NG is used to delete this Fedora partitions in
the future, the chain will be interpreted incorrectly due to the
misordering of the volumes. The symptom with BootIt NG will be that
after deleting the linux volumes, no free space will be shown in the
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.Follow the scenario in the description
Actual Results: EBR chain is in wrong order
Expected Results: New linux volumes should be first in the EBR chain.
This is perfectly legal according to how MSDOS partition tables are
specified. It's a bug in the third-party program if it can't handle
partition numbers being out of sequence.