Package: parted / 3.2-17
Metadata
| Package | Version | Patches format |
|---|---|---|
| parted | 3.2-17 | 3.0 (quilt) |
Patch series
view the series file| Patch | File delta | Description |
|---|---|---|
| doc package.patch | (download) |
doc/C/parted.8 |
2 1 + 1 - 0 ! |
small documentation fixes |
| preserve hidden parts.patch | (download) |
libparted/labels/dos.c |
11 8 + 3 - 0 ! |
avoid overwriting empty or hidden partitions It changes the DOS partition rewriting code to avoid overwriting empty or hidden primary partitions so long as their entries aren't reused. This makes fatresize and similar front-ends safe to use in the presence of hidden partitions. |
| kfreebsd gnu.patch | (download) |
configure.ac |
8 6 + 2 - 0 ! |
add gnu/kfreebsd support |
| freebsd ufs.patch | (download) |
libparted/fs/ufs/ufs.c |
103 96 + 7 - 0 ! |
add freebsd ufs support This patch adds support for detection of FreeBSD UFS file systems and creation of the partition on DOS and GPT labels. It doesn't use the system of slices used by default on FreeBSD and places the partition directly in the dos label. This is something supported by the FreeBSD kernel, and the default on Debian GNU/kFreeBSD. Even on plain FreeBSD, some persons prefer to not use slices. This patch is used by debian-installer on Debian GNU/kFreeBSD for some months already. |
| zfs.patch | (download) |
libparted/fs/Makefile.am |
3 2 + 1 - 0 ! |
add zfs support |
| freebsd zvol.patch | (download) |
libparted/arch/freebsd.c |
40 40 + 0 - 0 ! |
detection of zfs volumes (zvol) ZFS volumes (ZVOL) are the ZFS equivalent of Logical Volumes in LVM. They implement a block device which can be used for swap or legacy filesystems. Bug-Debian: http://bugs.debian.org/635384 |
| freebsd geli.patch | (download) |
libparted/arch/freebsd.c |
6 6 + 0 - 0 ! |
detection of geom encryption devices (geli) Bug-Debian: http://bugs.debian.org/635393 |
| kfreebsd_lvm.patch | (download) |
libparted/arch/freebsd.c |
27 27 + 0 - 0 ! |
add lvm support on kfreebsd Patch-Name: kfreebsd_lvm.patch |
| hurd partition path.patch | (download) |
libparted/arch/gnu.c |
2 1 + 1 - 0 ! |
fix partition paths on gnu/hurd Patch-Name: hurd-partition-path.patch |
| hurd reread.patch | (download) |
libparted/arch/gnu.c |
84 78 + 6 - 0 ! |
implement partition table rereading on gnu/hurd Patch-Name: hurd-reread.patch |
| gptsync.patch | (download) |
libparted/labels/gpt.c |
430 420 + 10 - 0 ! |
gpt syncing for intel macs On Intel Mac systems, write a synced MBR rather than a protective MBR. |
| udevadm settle.patch | (download) |
libparted/arch/linux.c |
56 54 + 2 - 0 ! |
udev handling Run udevadm settle around partition table rereads, to avoid races. This should be replaced by a proper completion-notification mechanism between the kernel and udev. |
| fat resize large sectors.patch | (download) |
libparted/fs/r/fat/bootsector.c |
12 0 + 12 - 0 ! |
remove stray non-512-byte-logical-sector assertion for fat resizing This was removed from one copy of fat_boot_sector_analyse in 3.2, but not from the other. |
| align new partitions on fresh disks.patch | (download) |
libparted/disk.c |
3 2 + 1 - 0 ! |
align new partitions created on fresh disks Commit fa815ad05db248d78ef214ea79a78c22772a9ffe arranged to skip partition alignment while reading disks, but also has the effect of skipping partition alignment when creating a partition on a fresh disk, which is incorrect. The proper upstream fix probably involves adding a new member to PedDisk to keep track of whether we're in the middle of the initial read in ped_disk_new or not. To avoid changing ABI, we instead take this hacky approach of overloading an extra bit on PedDisk.needs_clobber. Bug-Ubuntu: https://bugs.launchpad.net/bugs/1352252 |
| probe lvs again.patch | (download) |
libparted/arch/linux.c |
4 2 + 2 - 0 ! |
probe lvm logical volumes again parted 3.2 stopped probing LVM logical volumes. This breaks debian-installer, which wants to be able to "partition" these, at least to the extent of being able to see them in the partitioner and operate on them somewhat like ordinary partitions. Revert to the old behaviour. Bug-Debian: http://bugs.debian.org/757417 |
| fat16 resize crash.patch | (download) |
libparted/fs/r/fat/resize.c |
12 9 + 3 - 0 ! |
lib-fs-resize: prevent crash resizing fat16 file systems Resizing FAT16 file system crashes in libparted/fs/r/fat/resize.c create_resize_context() because it was dereferencing NULL pointer fs_info->info_sector to copy the info_sector. Only FAT32 file systems have info_sector populated by fat_open() -> fat_info_sector_read(). FAT12 and FAT16 file systems don't have an info_sector so pointer fs_info->info_sector remains assigned NULL from fat_alloc(). When resizing a FAT file system create_resize_context() was always dereferencing fs_info->info_sector to memory copy the info_sector, hence it crashed for FAT12 and FAT16. Make create_resize_context() only copy the info_sector for FAT32 file systems. Reported by Christian Hesse in https://bugzilla.gnome.org/show_bug.cgi?id=735669 |
| fdasd update geometry handling.patch | (download) |
include/parted/fdasd.h |
4 3 + 1 - 0 ! |
fdasd: geometry handling updated from upstream s390-tools Remove the necessity for DASD-specific ioctls for partition handling. This allows to correctly handle DASD-backed virtio block devices. Note that this is necessary because virtio is just the transport. A DASD, even if provided via virtio, still has it's unique characteristics, which means that only traditional DASD partition table formats can be used (no MBR, GPT, or similar). Use bzero for initialization to make sure all struct members are properly cleared. Also changed partition list handling code to be more similar to upstream s390-tools fdasd. Further, enhanced error handling capabilities by providing a return code by fdasd_get_geometry. Code is largely backported from s390-tools project. Signed-off-by: Viktor Mihajlovski <mihajlov@linux.vnet.ibm.com> |
| dasd enhance probing.patch | (download) |
libparted/arch/linux.c |
85 70 + 15 - 0 ! |
dasd: enhance device probing Probe for all device/transport types as every block device could be a DASD on s390. Since the calculation of the minimum and optimum alignment |
| dm 512b sectors.patch | (download) |
libparted/arch/linux.c |
21 17 + 4 - 0 ! |
libparted: device mapper uses 512b sectors device mapper doesn't use the device's sector size when creating a table. It always uses 512b units. This causes partitions to be created 8x smaller than expected on devices with 4906b sectors. |
| fdasd check geometry.patch | (download) |
libparted/labels/fdasd.c |
11 9 + 2 - 0 ! |
fdasd.c: safeguard against geometry misprobing Fixes an issue with parted print being run against a logical volume realised by extents on a physical volume residing on a DASD. We must make sure that geometry, device blocksize and DASD attributes are present before we start format verifications If any of it is missing this is not a DASD. Signed-off-by: Viktor Mihajlovski <mihajlov@linux.vnet.ibm.com> Signed-off-by: Brian C. Lane <bcl@redhat.com> |
| tests move get sector size.patch | (download) |
libparted/tests/common.c |
14 14 + 0 - 0 ! |
libparted:tests: move get_sector_size() to common.c Moving get_sector_size() from disk.c to common.c allows us to use it in _implemented_disk_label() to test for 512-byte sectors. This change is required to be able to enable this test for atari partition tables for which support is added in a follow-up patch. Signed-off-by: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de> Bug: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=16134 Bug-Debian: https://bugs.debian.org/239816 |
| atari.patch | (download) |
libparted/labels/Makefile.am |
1 1 + 0 - 0 ! |
libparted: add support for atari partition tables Signed-off-by: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de> Bug: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=16134 Bug-Debian: https://bugs.debian.org/239816 |
