summaryrefslogtreecommitdiff
path: root/NEWS
Commit message (Collapse)AuthorAgeFilesLines
* gpt: Add no_automount partition flagMike Fleetwood2022-12-131-0/+2
| | | | | | | | | | | | | | | | | | | | | | | | | Add user requested support for GPT partition type attribute bit 63 [1] so the no-auto flag in the systemd originated Discoverable Partitions Specification [2] can be manipulated. The UEFI specification [3] says partition attribute bits 48 to 63 are partition type specific, however the DPS [2] and Microsoft [4] use the bit 63 to mean no automounting / assign no drive letter and apply it to multiple partition types so don't restrict its application. [1] Request for GPT partition attribute bit 63 "no automount" editing support https://gitlab.gnome.org/GNOME/gparted/-/issues/214 [2] The Discoverable Partitions Specification (DPS), Partition Attribute Flags https://uapi-group.org/specifications/specs/discoverable_partitions_specification/ [3] UEFI Specification, version 2.8, Table 24. Defined GPT Partition Entry - Attributes https://uefi.org/sites/default/files/resources/UEFI_Spec_2_8_final.pdf [4] CREATE_PARTITION_PARAMETERS structure (vds.h) https://learn.microsoft.com/en-gb/windows/win32/api/vds/ns-vds-create_partition_parameters Signed-off-by: Mike Fleetwood <mike.fleetwood@googlemail.com> Signed-off-by: Brian C. Lane <bcl@redhat.com>
* parted: add type commandArvin Schnell2022-05-131-0/+3
| | | | | | | | | Include the partition type-id and type-uuid in the JSON output. Also add the the command 'type' to set them. Remove redundant flags from DosPartitionData and use only the system variable. Signed-off-by: Brian C. Lane <bcl@redhat.com>
* maint: post-release administriviaBrian C. Lane2022-04-181-0/+3
| | | | | | * NEWS: Add header line for next release. * .prev-version: Record previous version. * cfg.mk (old_NEWS_hash): Auto-update.
* version 3.5v3.5Brian C. Lane2022-04-181-1/+1
| | | | * NEWS: Record release date.
* NEWS: Mention gnulib updateBrian C. Lane2022-04-181-0/+3
|
* maint: post-release administriviaBrian C. Lane2022-04-051-0/+3
| | | | | | * NEWS: Add header line for next release. * .prev-version: Record previous version. * cfg.mk (old_NEWS_hash): Auto-update.
* version 3.4.64.2v3.4.64.2Brian C. Lane2022-04-051-1/+1
| | | | * NEWS: Record release date.
* NEWS: Mention bugfixBrian C. Lane2022-04-051-0/+3
|
* maint: post-release administriviaBrian C. Lane2022-03-301-0/+3
| | | | | | * NEWS: Add header line for next release. * .prev-version: Record previous version. * cfg.mk (old_NEWS_hash): Auto-update.
* version 3.4.64v3.4.64Brian C. Lane2022-03-301-1/+1
| | | | * NEWS: Record release date.
* NEWS: Add new features and bugsBrian C. Lane2022-03-291-0/+31
|
* maint: Update copyright statements to 2022Brian C. Lane2022-03-231-1/+1
| | | | By running make update-copyright
* maint: post-release administriviaBrian C. Lane2021-01-271-0/+3
| | | | | | * NEWS: Add header line for next release. * .prev-version: Record previous version. * cfg.mk (old_NEWS_hash): Auto-update.
* version 3.4v3.4Brian C. Lane2021-01-271-1/+1
| | | | * NEWS: Record release date.
* NEWS: Mention the non-public gnulib commitBrian C. Lane2021-01-271-0/+3
|
* maint: Update copyright statements to 2021Brian C. Lane2021-01-181-1/+1
| | | | By running make update-copyright
* maint: post-release administriviaBrian C. Lane2020-12-141-0/+3
| | | | | | * NEWS: Add header line for next release. * .prev-version: Record previous version. * cfg.mk (old_NEWS_hash): Auto-update.
* version 3.3.52v3.3.52Brian C. Lane2020-12-141-1/+1
| | | | * NEWS: Record release date.
* maint: Update copyright statements to 2020Brian C. Lane2020-12-111-1/+1
| | | | By running make update-copyright
* NEWS: Add bls_boot to new featuresBrian C. Lane2019-12-201-0/+4
|
* libparted: Add ChromeOS Kernel partition flagAlper Nebi Yasak2019-12-201-0/+5
| | | | | | | | | | | | | | | | | | | | This adds a GPT-only partition type flag, chromeos_kernel, for use on Chrome OS machines, with GUID FE3A2A5D-4F32-41A7-B725-ACCC3285A309. The firmware/bootloader in these machines relies on special images being written to partitions of this type. Among multiple such partitions, it decides which one it will boot from based on the GUID-specific partition attributes. This patch is not intended to and does not manipulate these bits. Google refers to these partitions as "ChromeOS kernel" partitions. They also define partitions for rootfs, firmware, and a reserved one; but these are not necessary for the boot flow and are not included here. Relevant ChromiumOS documentation: https://www.chromium.org/chromium-os/chromiumos-design-docs/disk-format Signed-off-by: Alper Nebi Yasak <alpernebiyasak@gmail.com>
* maint: post-release administriviaBrian C. Lane2019-10-101-0/+3
| | | | | | * NEWS: Add header line for next release. * .prev-version: Record previous version. * cfg.mk (old_NEWS_hash): Auto-update.
* version 3.3v3.3Brian C. Lane2019-10-101-1/+1
| | | | * NEWS: Record release date.
* NEWS: Note the fix for the s390 bugBrian C. Lane2019-10-101-0/+5
|
* maint: post-release administriviaBrian C. Lane2019-08-121-0/+3
| | | | | | * NEWS: Add header line for next release. * .prev-version: Record previous version. * cfg.mk (old_NEWS_hash): Auto-update.
* version 3.2.153v3.2.153Brian C. Lane2019-08-121-1/+1
| | | | * NEWS: Record release date.
* maint: Move NEWS template to line 3Brian C. Lane2019-08-121-2/+2
|
* maint: Update copyright statements to 2019Brian C. Lane2019-08-121-1/+1
| | | | By running make update-copyright
* libparted: Add support for MBR id, GPT GUID and detection of UDF filesystemPali Rohár2018-10-161-0/+2
| | | | | | | | | | | | | | | This is needed for libparted based applications (like Gparted) to correctly choose MBR id and GPT GUID for UDF filesystem. MBR id for UDF is 0x07 and GPT GUID is Microsoft Basic Data, see why: https://serverfault.com/a/829172 Without registering a new libparted fs code it is not possible to assign MBR id or GPT GUID. Detection of UDF filesystem is done by checking presence of UDF VSD (NSR02 or NSR03 identifier) and UDF AVDP at expected locations (blocks 256, -257, -1, 512). Signed-off-by: Brian C. Lane <bcl@redhat.com>
* Fix atari label false positivesPhillip Susi2018-06-121-0/+2
| | | | | The atari label gets false positives easily, so probe it after all other labels have said no.
* Lift 512 byte restriction on fat resizePhillip Susi2018-06-051-0/+2
| | | | | | As Colin Watson pointed out way back in 2014, when I removed the 512 byte sector size restriction from the fs recognition code, I missed the same from the fat resize code.
* Fix resizepart iec unit end sectorPhillip Susi2018-06-051-0/+4
| | | | | | Fix resizepart to adjust the end to be -1 sector when using iec power of 2 units so that the next partition can start immediately following the new end, just like mkpart does.
* mkpart: Allow negative start value when FS-TYPE is not givenNiklas Hambüchen2018-06-051-0/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | The manual had long documented that negative values are allowed for both start and end values, but until now negative start values were rejected if FS-TYPE was not given. Example: # parted --script -a optimal /dev/loop0 -- mklabel gpt mkpart primary ext4 -5MiB 100% (succeeds) # parted --script -a optimal /dev/loop0 -- mklabel gpt mkpart primary -5MiB 100% parted: invalid token: -5MiB Error: Expecting a file system type. This commit fixes the latter error. The issue was an insufficient lookahead in command line parsing, looking only for digits when skipping over FS-TYPE. The fix is including the minus '-' in the lookahead. Originally reported as Debian bug #880035: "parted: fails to use negative start value for 'mkpart' command without specyfying FS-TYPE" https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=880035 Signed-off-by: Niklas Hambüchen <mail@nh2.me>
* Fix set and disk_set to not crash when no flags are supportedPhillip Susi2018-06-051-0/+2
| | | | | | | | Loop labels and file images support no flags. set and disk_set would prompt for a flag and accept any string since the list of flags was empty, then fail to look up an actual flag value, then throw an exception with a null string for the name of the flag, which would bug.
* Add support for NVDIMM devicesSebastian Parschauer2017-12-191-1/+1
| | | | | | | | | | | | | | | | | | | Recognize NVDIMM devices, so that "parted -s /dev/pmem7 p" now prints "Model: NVDIMM Device (pmem)" instead of "Model: Unknown (unknown)". In order for a device to be recognized as NVDIMM, it has to have a 'blkext' major number. But since this major can be used also by other device types, we also check that the device path contains 'pmem' as a substring. * NEWS: Mention the change * include/parted/device.h.in(PedDeviceType): Add PED_DEVICE_PMEM * libparted/arch/linux.c(_device_probe_type): Recognize NVDIMM devices. * libparted/arch/linux.c(linux_new): Handle NVDIMM devices. * parted/parted.c(do_print): Add "pmem" to list of transports. Signed-off-by: Sebastian Parschauer <sparschauer@suse.de>
* libparted: Fix udev cookie leak in _dm_resize_partitionBrian C. Lane2017-06-061-0/+3
| | | | Add a NEWS entry.
* Add support for RAM drivesSebastian Parschauer2017-05-011-1/+1
| | | | | | | | | | | | | | | | | | | Recognize RAM drives, so "parted -s /dev/ram0 p" now prints "RAM Drive (brd)" instead of "Model: Unknown (unknown)". In order for a device to be recognized as RAM drive, it has to have major number 1. Also the BLKFLSBUF ioctl shouldn't be used on RAM drives as it is used to zero the device. * NEWS: Mention the change * include/parted/device.h.in(PedDeviceType): Add PED_DEVICE_RAM. * libparted/arch/linux.c(RAM_MAJOR): New define. * libparted/arch/linux.c(_device_probe_type): Recognize RAM drives. * libparted/arch/linux.c(linux_new): Handle RAM drives. * libparted/arch/linux.c(_flush_cache): Skip RAM drives. * parted/parted.c(do_print): Add "brd" to list of transports. Signed-off-by: Sebastian Parschauer <sparschauer@suse.de>
* Fix crash when localizedPhillip Susi2017-04-171-0/+1
| | | | | | The _() macro is only for translating string literals. It was incorrectly applied to a runtime string representing the name of a partition and this sometimes caused a gettext crash.
* libparted: only IEC units are treated as exactPetr Uzel2016-09-301-0/+4
| | | | | | | | | | | | | | | | | | | | If the user specifies start/end of the partition as a unit, whose size happens to be power of two, we treat that as exact address with exact placement. Recently, commit 01900e056ec25083 added an exception for percent units. This logic however can fail also for cylinders, e.g. on DASD FBA disks, which report CHS=(*, 128, 16) geometry, hence once cylinder is 1 MiB. With cylinders as units, exact placement is not what the user wants. Instead of adding cylinders to the blacklist, let's instead whitelist units which should trigger exact placement. * libparted/unit.c (is_power_of_2): Remove now unused function. (ped_unit_parse_custom): Specify which units trigger exact placement. * NEWS (Bug Fixes): Mention this.
* Add support for NVMe devicesPetr Uzel2016-06-231-0/+2
| | | | | | | | | | | | | | | | | | | | Recognize NVMe Devices, so "parted -s /dev/nvme0n1" now prints "NVMe Device (nvme)" instead of "Model: Unknown (unknown)". In order for a device to be recognized as NVMe, it has to have a 'blkext' major number. But since this major can be used also by other device types, we also check the device path contains 'nvme' as a substring. * NEWS: Mention the change * include/parted/device.h.in(PedDeviceType): Add PED_DEVICE_NVME * libparted/arch/linux.c(BLKEXT_MAJOR): New define. * libparted/arch/linux.c(_is_blkext_major): New function. * libparted/arch/linux.c(_device_probe_type): Recognize NVMe devices. * libparted/arch/linux.c(linux_new): Handle NVMe devices. * parted/parted.c(do_print): Add "nvme" to list of transports. Signed-off-by: Brian C. Lane <bcl@redhat.com>
* Add NEWS entry for fat resize fixPhillip Susi2016-04-141-0/+3
|
* parted: fix the rescue commandPhillip Susi2016-04-101-0/+4
| | | | | | | The rescue command often failed to locate a filesystem due to it leaving cylinder alignment on, which snapped the allowed bounds of the filesystem down to the next lower cylinder boundary, causing the detected filesystem to be rejected due to not fitting.
* lib-fs-resize: Prevent crash resizing FAT with very deep directoriesMike Fleetwood2016-03-071-0/+3
| | | | | | | | | | | | Resizing a FAT file system crashes in libparted/fs/r/fat/count.c flag_traverse_dir() if the length of any path name in the file system overflows the 512 byte file_name local buffer. Increase buffer to 4096, PATH_MAX on Linux. Reported in https://bugzilla.gnome.org/show_bug.cgi?id=762448 Signed-off-by: Brian C. Lane <bcl@redhat.com>
* libparted: device mapper uses 512b sectorsBrian C. Lane2015-02-061-0/+4
| | | | | | 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.
* parted: don't crash in disk_set when disk label not foundPhillip Susi2015-01-131-0/+2
| | | | | | Due to a typeo in commit 7eac058 "parted: don't reload partition table on every command", the disk_set command would crash if a disk label was not found.
* lib-fs-resize: Prevent crash resizing FAT16 file systemsMike Fleetwood2014-10-271-0/+4
| | | | | | | | | | | | | | | | | | | 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
* maint: post-release administriviaPhillip Susi2014-07-281-0/+3
| | | | | | * NEWS: Add header line for next release. * .prev-version: Record previous version. * cfg.mk (old_NEWS_hash): Auto-update.
* version 3.2v3.2Phillip Susi2014-07-281-1/+1
| | | | * NEWS: Record release date.
* parted: make _partition_warn_busy actually a warning instead of an errorPhillip Susi2014-06-151-0/+3
| | | | | | This function was throwing a PED_EXCEPTION_ERROR with only the PED_EXCEPTION_CANCEL option. Converted to a PED_EXCEPTION_WARNING with the option to continue anyhow.
* libparted: Add support for partition resizePhillip Susi2014-06-151-1/+2
| | | | | | | | When resizing a partition ( same partition number, same start sector, different end sector ), try to use the new BLKPG_RES_PARTITION request to update the kernel partition table with the new size. Also handle resizing devmapper targets.
View Lorry Controller Status