gptfdisk-1.0.1.tar.gz

[Fernando de Oliveira]

​http://downloads.sourceforge.net/project/gptfdisk/gptfdisk/1.0.1/gptfdisk-1.0.1.tar.gz

​http://sourceforge.net/p/gptfdisk/code/ci/master/tree/NEWS?format=raw

1.0.1 (10/18/2015):
-------------------

- Created uninstall-fixparts and uninstall-gdisk scripts for OS X. As
  the names imply, these scripts remove the files installed by the
  fixparts and gdisk packages, respectively.

- Fixed bug that caused -N/--largest-new option to sgdisk to fail when
  fed a "0" option.

- Fixed bug that caused input glitches in EFI version of gdisk.

- Fixed bug that caused sgdisk to not return an appropriate error code
  when it encountered a write error when saving changes.

- Fixed bug that caused cgdisk's "Info" display to under-report the
  partition's size by one sector.

- OS X 10.11 includes new security features that prevent GPT fdisk from
  working unless these features are disabled. To do so, you must boot to
  a Recovery HD system, open a Terminal, type "csrutil disable", and
  reboot into the normal system. You can re-enable the security features
  by repeating the process, but specify "enable" rather than "disable".
  I've added a message pointing users to a Web page explaining how to
  disable this feature when gdisk detects that it can't write to the
  disk under OS X. If you know of a way around this (including code
  changes to gdisk), please contact me.

- I've updated the OS X installation location from the Unix-standard
  /usr/sbin (and related locations for documentation) to /usr/local/bin
  (and related locations for documentation). This is Just Plain Crazy
  from a Unix point of view, but Apple has to be Apple and do things
  just a little bit differently.

- I've updated my OS X environment to OS X 10.11 and LLVM 7.0.0. This
  has also meant installing fresh versions of popt and ncurses from
  MacPorts, which may require upgrading popt to get sgdisk working on
  some systems.  (gdisk, cgdisk, and fixparts should continue to work
  normally on all systems.) The OS X binaries are now "fat" (32- and
  64-bit) versions, which should have no noticeable effect unless you
  have a Mac with broken 32-bit support, in which case the binaries will
  now work.

- Changed the default name of 0xab00 partitions from "Apple boot" to
  "Recovery HD", since the latter is the name that Apple gives these
  partitions. Also, I discovered through painful experience that OS X
  flakes out and won't boot if the name is something other than
  "Recovery HD", so it really has to have the right name!

- Changed the OpenBSD type codes (0xa600 and 0xa601): 0xa600 is now
  824CC7A0-36A8-11E3-890A-952519AD3F61 (OpenBSD disklabel) and 0xa601 is
  now gone. Previously, 0xa600 was 516E7CB4-6ECF-11D6-8FF8-00022D09712B,
  a duplicate of the FreeBSD disklabel, and 0xa601 was
  824CC7A0-36A8-11E3-890A-952519AD3F61. OpenBSD is now officially
  supporting 824CC7A0-36A8-11E3-890A-952519AD3F61 as a disklabel type,
  though. It's unclear what, if anything, OpenBSD will use for
  non-disklabel type codes at the moment.

- Added GUID 0311FC50-01CA-4725-AD77-9ADBB20ACE98 (0xbc00) for Acronis
  Secure Zone backup partitions.

- Fixed bug that caused random crashes on ppc64el systems (and perhaps
  others).

- Added GUID C91818F9-8025-47AF-89D2-F030D7000C2C (0x3900) for Plan 9.

- Added GUID 69DAD710-2CE4-4E3C-B16C-21A1D49ABED3 (0x8307) for 32-bit
  ARM Linux root (/) partition, as per the Freedesktop.org Discoverable
  Partition Spec
  (http://www.freedesktop.org/wiki/Specifications/DiscoverablePartitionsSpec/).

- Edited man pages to clarify that default alignment is to 1MiB
  boundaries; this translates to 2048 sectors on disks with 512-byte
  sectors, but it will be something else on disks with other sector
  sizes.

- Changed behavior of -z/--zap and -Z/--zap-all options to sgdisk so
  that if a subsequent command causes changes, they'll be written to
  disk.  Previously, doing something like "sgdisk --zap-all --clear
  /dev/sdd" would wipe the disk but not create a partition table; to
  create a blank table you'd need to do "sgdisk --zap-all --clear
  --mbrtogpt /dev/sdd", which is a bit odd and counter-intuitive, to the
  point of arguably being a bug.

[bdubbs@…]

Fixed at revision 16553.