#1107 Issue closed: Get rid of using "sfdisk"¶
Labels: enhancement, cleanup, won't fix / can't fix / obsolete
jsmeix opened issue at 2016-12-06 09:35:¶
I think we should try to get rid of using partitioning tools
that do not support GPT and large partitions because
otherwise I fear there will be and endless sequence
of more and more problems in ReaR in the future.
In particular "man sfdisk" reads:
sfdisk doesn't understand the GUID Partition Table (GPT) format and it is not designed for large partitions. In these cases use the more advanced GNU parted(8).
Cf.
https://github.com/rear/rear/issues/1106#issuecomment-265088912
Currently "sfdisk" is called in
usr/share/rear/layout/save/GNU/Linux/200_partition_layout.sh
usr/share/rear/finalize/Linux-ppc64/200_install_yaboot.sh
usr/share/rear/finalize/SUSE_LINUX/ppc64/200_install_yaboot.sh
and "sfdisk" is mentioned in comments in
usr/share/rear/lib/mkrescue-functions.sh
and "sfdisk" is listed as REQUIRED_PROGS or PROGS in
usr/share/rear/conf/Linux-i386.conf
usr/share/rear/conf/Linux-ia64.conf
usr/share/rear/conf/Linux-ppc64.conf
usr/share/rear/conf/Linux-ppc64le.conf
gozora commented at 2016-12-06 10:01:¶
Btw. same applies to fdisk (which seems not to be currently used in
ReaR code ;-) )
fdisk does not understand GUID partition tables
(GPTs) and it is not designed for large partitions.
In these cases, use the more advanced GNU parted(8).
jsmeix commented at 2016-12-13 15:55:¶
Probably "sfdisk" is still needed for NTFS support
to get NTFS related data from a 'msdos' partitioned disk
and sgdisk could be used for a 'gpt' partitioned disk, cf.
https://github.com/rear/rear/issues/1078#issuecomment-266386136
gozora commented at 2016-12-13 16:14:¶
Yes, at least until we have complete code for that NTFS/Windows stuff, I'd put this "on hold".
[Export of Github issue for rear/rear.]