** New features
+ parted now recognizes ATA over Ethernet (AoE) devices
+
+** Bug fixes
+
+ libparted's msdos_partition_is_flag_available function now always reports
+ that the "hidden" flag is not available for an extended partition.
+ Similarly, msdos_partition_get_flag(p,PED_PARTITION_HIDDEN) always returns 0
+ for an extended partition.
+
+
+* Noteworthy changes in release 2.2 (2010-02-26) [stable]
+
+** Changes in behavior
+
+ The default alignment (--align option) for newly created partitions has
+ been changed to optimal.
+
+** New features
+
The ped_device_get_*_alignment() functions now return a sane default
value instead of NULL when the so called topology information is incomplete.
The default minimum alignment aligns to physical sector size, the default
Parted no longer uses a physical sector size of 0 or of any other
value smaller than the logical sector size.
+ dos: creating an HFS or HFS+ partition in an msdos partition table
+ used to set the partition type to 0x83. That is wrong. The required
+ number is 0xaf, and that is what is used now.
+
gpt: read-only operation could clobber MBR part of hybrid GPT+MBR table
[bug introduced in parted-2.1]
+ gpt: a read-only operation like "parted $dev print" would overwrite $dev's
+ protective MBR when exactly one of the primary and backup GPT tables was
+ found to be corrupt.
+ [bug introduced prior to parted-1.8.0]
+
+ sun: the version, sanity and nparts VTOC fields were ignored by libparted.
+ Those fields are properly initialized now. The nparts (number of partitions)
+ field is initialized to 8 (max. number of sun partitions) rather that to a
+ real number of partitions. This solution is compatible with Linux kernel
+ and Linux fdisk.
+
"make install" no longer installs tests programs named disk and label
+ libparted: try harder to inform kernel of partition changes.
+ Previously when editing partitions, occasionally the kernel would
+ fail to be informed of partition changes. When this happened future
+ problems would occur because the kernel had incorrect information.
+ For example, if this problem arose when resizing or creating a
+ new partition, then an incorrect partition size might be displayed
+ or a user might encounter a failure to format or delete a newly
+ created partition, respectively.
+
+ libparted: committing a disk that was returned by ped_disk_duplicate
+ would always result in ped_disk_clobber being called (and thus the first
+ and last 9KiB of the disk being zeroed), even if the duplicated disk,
+ was not returned by ped_disk_fresh().
+
* Noteworthy changes in release 2.1 (2009-12-20) [stable]
OSDN Git Service
