Mirrors
/
gparted
mirror of https://gitlab.gnome.org/GNOME/gparted.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
gparted/include/Makefile.am

72 lines
1.4 KiB
Makefile
Raw Normal View History

Initial revision
2004-09-19 14:24:53 -06:00
gparted_includedir = $(pkgincludedir)
removed INSTALL some fixes to make 'make dist' work (thanks to Daniel * removed INSTALL * compose/.cvsignore, compose/Makefile.am, Makefile.am, configure.in, include/Makefile.am: some fixes to make 'make dist' work (thanks to Daniel Holbach)
2005-10-05 16:37:17 -06:00
EXTRA_DIST = \
Create BlockSpecial class and use in LVM2_PV_Info (#767842) In some cases creating an LVM2 Physical Volume on top of a DMRaid array reports no usage information and this partition warning: Unable to read the contents of this file system! Because of this some operations may be unavailable. The cause might be a missing software package. The following list of software packages is required for lvm2 pv file system support: lvm2. For example on Ubuntu 14.04 LTS (with GParted built with --enable-libparted-dmraid) create an LVM2 PV in a DMRaid array partition. GParted uses this command: # lvm pvcreate -M 2 /dev/mapper/isw_bacdehijbd_MyArray0p2 But LVM reports the PV having a different name: # lvm pvs PV VG Fmt Attr PSize PFree /dev/disk/by-id/dm-name-isw_bacdehijbd_MyArray0p2 lvm2 a-- 1.00g 1.00g This alternate name is loaded into the LVM2_PV_Info module cache. Hence when GParted queries partition /dev/mapper/isw_bacdehijbd_MyArray0p2 it has no PV information against that name and reports unknown usage. However they are actually the same block special device; major 252, minor 2: # ls -l /dev/mapper/isw_bacdehijbd_MyArray0p2 brw-rw---- 1 root disk 252, 2 Jul 2 11:09 /dev/mapper/isw_bacdehijbd_MyArray0p2 # ls -l /dev/disk/by-id/dm-name-isw_bacdehijbd_MyArray0p2 lrwxrwxrwx 1 root root 10 Jul 2 11:09 /dev/disk/by-id/dm-name-isw_bacdehijbd_MyArray0p2 -> ../../dm-2 # ls -l /dev/dm-2 brw-rw---- 1 root disk 252, 2 Jul 2 11:09 /dev/dm-2 To determine if two names refer to the same block special device their major, minor numbers need to be compared, instead of string comparing their names. Implement class BlockSpecial which encapsulates the name and major, minor numbers for a block special device. Also performs comparison as needed. See bug 767842 comments 4 and 5 for further investigation and decision for choosing to implement a class. Replace name strings in the LVM2_PV_Info module with BlockSpecial objects performing correct block special device comparison. Bug 767842 - File system usage missing when tools report alternate block device names
2016-06-22 10:32:01 -06:00
BlockSpecial.h \
Rename file and class to CopyBlocks (#775932) Files were named Block_Copy and the class was named block_copy. Change to the primary naming convention of CamelCase class name and matching file names. Also make CopyBlocks::copy_block() a private method as it is only used internally within the class. Bug 775932 - Refactor mostly applying of operations
2016-11-04 07:02:28 -06:00
CopyBlocks.h \
Restore compilation order of source files Restore the order of the source files so that they are once again compiled in order A-Z, a-z. Order is obtained with: fgrep .cc src/Makefile.am | LANG=C sort fgrep .h include/Makefile.am | LANG=C sort
2013-03-20 06:08:18 -06:00
DMRaid.h \
Device.h \
DialogFeatures.h \
DialogManageFlags.h \
Add password entry dialog and attempt LUKS unlock once (#795617) Initial addition of a password entry dialog. Looks like: +------------------------------------------------+ | LUKS Passphrase /dev/sdb1 | +------------------------------------------------+ | Enter LUKS passphrase to open /dev/sdb1 | | Passphrase: [ ] | | | | [ Cancel ] [ Unlock ] | +------------------------------------------------+ A standard Gtk Dialog is used to accept the password once, with any errors displayed in a separate error dialog afterwards. This is poor UI design. A password dialog should remain open for all authentication attempts and only close when successful or the dialog is cancelled or closed. This UI design issue will be improved in following commits. Bug 795617 - Implement opening and closing of LUKS mappings
2017-10-22 12:52:12 -06:00
DialogPasswordEntry.h \
sorted filelistings. * include/Makefile.am, src/Makefile.am: sorted filelistings.
2006-03-09 13:25:57 -07:00
Dialog_Base_Partition.h \
Restore compilation order of source files Restore the order of the source files so that they are once again compiled in order A-Z, a-z. Order is obtained with: fgrep .cc src/Makefile.am | LANG=C sort fgrep .h include/Makefile.am | LANG=C sort
2013-03-20 06:08:18 -06:00
Dialog_Disklabel.h \
Rename class to Dialog_FileSystem_Label (#741424) class Dialog_Partition_Label -> Dialog_FileSystem_Label file Dialog_Partition_Label.h -> Dialog_FileSystem_Label.h file Dialog_Partition_Label.cc -> Dialog_FileSystem_Label.cc Bug 741424 - Add support for GPT partition names
2014-12-19 14:08:28 -07:00
Dialog_FileSystem_Label.h \
sorted filelistings. * include/Makefile.am, src/Makefile.am: sorted filelistings.
2006-03-09 13:25:57 -07:00
Dialog_Partition_Copy.h \
Restore compilation order of source files Restore the order of the source files so that they are once again compiled in order A-Z, a-z. Order is obtained with: fgrep .cc src/Makefile.am | LANG=C sort fgrep .h include/Makefile.am | LANG=C sort
2013-03-20 06:08:18 -06:00
Dialog_Partition_Info.h \
Add support for GPT partition names (#741424) Embedded devices (Android) use GPT partition names to identify partitions, instead of file system labels. Add support for viewing and changing them. As partition names are used to provide unique identification they are never copied when copying the contents of one partition to another. Note that GNU/Linux uses file system labels, UUIDs or device names for identification during the boot process and afterwards so while partition names can be used, they are optional and purely for user information. Bug 741424 - Add support for GPT partition names
2014-12-12 00:00:02 -07:00
Dialog_Partition_Name.h \
Restore compilation order of source files Restore the order of the source files so that they are once again compiled in order A-Z, a-z. Order is obtained with: fgrep .cc src/Makefile.am | LANG=C sort fgrep .h include/Makefile.am | LANG=C sort
2013-03-20 06:08:18 -06:00
Dialog_Partition_New.h \
Dialog_Partition_Resize_Move.h \
Dialog_Progress.h \
Dialog_Rescue_Data.h \
DrawingAreaVisualDisk.h \
FS_Info.h \
FileSystem.h \
Created 2 files to support ext4 operations. Support for ext4 is planned for version 2.6.28 of the Linux kernel. svn path=/trunk/; revision=1004
2008-12-18 15:07:06 -07:00
Frame_Resizer_Base.h \
sorted filelistings. * include/Makefile.am, src/Makefile.am: sorted filelistings.
2006-03-09 13:25:57 -07:00
Frame_Resizer_Extended.h \
Restore compilation order of source files Restore the order of the source files so that they are once again compiled in order A-Z, a-z. Order is obtained with: fgrep .cc src/Makefile.am | LANG=C sort fgrep .h include/Makefile.am | LANG=C sort
2013-03-20 06:08:18 -06:00
GParted_Core.h \
HBoxOperations.h \
Cache results from querying all LVM2 PVs (#160787) Cache results from querying all LVM2 PVs in one go to minimise the number of times lvm commands are executed. Take inspiration from caching performed by FS_Info and Proc_Partitions_Info. Bug #160787 - lvm support
2012-01-28 07:25:31 -07:00
LVM2_PV_Info.h \
Add initial loading of LUKS mapping details (#760080) Load basic details of active Device-mapper encryption mappings from the kernel. Use dmsetup active targets. # cryptsetup luksFormat /dev/sdb5 # cryptsetup luksFormat /dev/sdb6 # cryptsetup luksOpen /dev/sdb6 sdb6_crypt # ls -l /dev/mapper/sdb6_crypt /dev/dm-0 lrwxrwxrwx. 1 root root 7 Nov 15 09:03 /dev/mapper/sdb6_crypt -> ../dm-0 brw-rw----. 1 root disk 253, 0 Nov 15 09:03 /dev/dm-0 # ls -l /dev/sdb6 brw-rw----. 1 root disk 8, 22 Nov 15 09:02 /dev/sdb6 # dmsetup table --target crypt sdb6_crypt: 0 1044480 crypt aes-cbc-essiv:sha256 0000000000000000000000000000000000000000000000000000000000000000 0 8:22 4096 So far just load the mapping name and underlying block device reference (path or major, minor pair). Note that all supported kernels appear to report the underlying block device as major, minor pair in the dmsetup output. Underlying block device paths are added to the cache when found during a search to avoid stat(2) call on subsequent searches for the same path. Prints debugging to show results, like this: # ./gpartedbin ====================== libparted : 2.4 ====================== DEBUG: /dev/sdb5: LUKS closed DEBUG: /dev/sdb6: LUKS open mapping /dev/mapper/sdb6_crypt Bug 760080 - Implement read-only LUKS support
2015-04-16 12:50:56 -06:00
LUKS_Info.h \
Split mount_info and fstab_info maps into separate Mount_Info module The GParted_Core::mount_info and GParted_Core::fstab_info maps and the methods that manipulate them are self-contained. Therefore move them to a separate Mount_Info module and reduce the size of the monster GParted_Core slightly.
2016-07-13 06:12:22 -06:00
Mount_Info.h \
Restore compilation order of source files Restore the order of the source files so that they are once again compiled in order A-Z, a-z. Order is obtained with: fgrep .cc src/Makefile.am | LANG=C sort fgrep .h include/Makefile.am | LANG=C sort
2013-03-20 06:08:18 -06:00
Operation.h \
OperationChangeUUID.h \
added 'check' operation. The functionality was already there, but it was * include/Makefile.am, include/Operation.h, include/Win_GParted.h, src/GParted_Core.cc, src/Makefile.am, src/Win_GParted.cc, include/OperationCheck.h (new), src/OperationCheck.cc (new): added 'check' operation. The functionality was already there, but it was not possible yet to activate it from the gui.
2006-11-26 07:27:16 -07:00
OperationCheck.h \
Restore compilation order of source files Restore the order of the source files so that they are once again compiled in order A-Z, a-z. Order is obtained with: fgrep .cc src/Makefile.am | LANG=C sort fgrep .h include/Makefile.am | LANG=C sort
2013-03-20 06:08:18 -06:00
OperationCopy.h \
lots of cleanups in operationhandling. This resulted in cleaner/less code * lots of cleanups in operationhandling. This resulted in cleaner/less code and the fixing of some longstanding issues.
2006-03-24 12:08:41 -07:00
OperationCreate.h \
OperationDelete.h \
small fix to pass 'make distcheck' * include/Makefile.am: small fix to pass 'make distcheck'
2006-08-09 13:33:51 -06:00
OperationDetail.h \
lots of cleanups in operationhandling. This resulted in cleaner/less code * lots of cleanups in operationhandling. This resulted in cleaner/less code and the fixing of some longstanding issues.
2006-03-24 12:08:41 -07:00
OperationFormat.h \
Rename class to OperationLabelFileSystem (#741424) class OperationLabelPartition -> OperationLabelFileSystem file OperationLabelPartition.h -> OperationLabelFileSystem.h file OperationLabelPartition.cc -> OperationLabelFileSystem.cc Bug 741424 - Add support for GPT partition names
2014-12-19 13:41:08 -07:00
OperationLabelFileSystem.h \
Add support for GPT partition names (#741424) Embedded devices (Android) use GPT partition names to identify partitions, instead of file system labels. Add support for viewing and changing them. As partition names are used to provide unique identification they are never copied when copying the contents of one partition to another. Note that GNU/Linux uses file system labels, UUIDs or device names for identification during the boot process and afterwards so while partition names can be used, they are optional and purely for user information. Bug 741424 - Add support for GPT partition names
2014-12-12 00:00:02 -07:00
OperationNamePartition.h \
Restore compilation order of source files Restore the order of the source files so that they are once again compiled in order A-Z, a-z. Order is obtained with: fgrep .cc src/Makefile.am | LANG=C sort fgrep .h include/Makefile.am | LANG=C sort
2013-03-20 06:08:18 -06:00
OperationResizeMove.h \
Partition.h \
Add PartitionLUKS class and create objects (#760080) Absolute minimum implementation of a PartitionLUKS class which can be constructed, polymorphically copied and destroyed. Contains an "encrypted" member of type Partition to represent the encrypted file system within the LUKS format. Create PartitionLUKS objects instead of base Partition objects when a LUKS formatted partition is found. Only the base Partition object member values have been populated, and the "encrypted" member remains blank at this point. Bug 760080 - Implement read-only LUKS support
2015-11-11 14:12:39 -07:00
PartitionLUKS.h \
Create PartitionVector class (#759726) Just creates PartitionVector class and includes it in partition.h so that it is built and validated by the compiler. Not used anywhere yet. Implementation strategy is to create a PartitionLUKS class derived from the Partition class. This implies polymorphism of Partition objects, which in C++ requires using pointers and references to objects, and not using objects directly. (See C++ object slicing). Later this PartitionVector class will be modified to use pointers to Partition objects and act as the owner of the pointed to Partition objects. Bug 759726 - Implement Partition object polymorphism
2015-05-22 14:01:59 -06:00
PartitionVector.h \
Add PasswordRAMStore module (#795617) Application level requirements for secure password management were set out in "LUKS password handling, threats and preventative measures" [1]. The requirements are: 1) Passwords are stored in RAM and are not allowed to be paged to swap. (However hibernating with GParted still running will write all of RAM to swap). 2) Passwords are wiped from RAM when no longer needed. When each password is no longer needed and when GParted closes. 3) Passwords are referenced by unique key. Recommend using LUKS UUIDs as the unique key. (Each LUKS password should only ever need to be entered once for each execution of GParted. Therefore the passwords can't be stored in any of the existing data structures such as Partitions or LUKS_Info cache because all of these are cleared and reloaded on each device refresh). There seems to be two possible implementation methods: use an existing library to provide secure memory handling, or write our own. Libgcrypt [2] and libsodium [3] cryptographic libraries both provide secure memory handling. (Secure memory is quite simple really, some virtual memory locked into RAM which is zeroed when no longer needed). Linking to an encryption library just to provide secure memory seems like using a sledge hammer to crack a nut. Also because of requirement (3) above a module is needed to "own" the pointers to the passwords in the secure memory. Managing the secure memory ourselves is probably no more code that that needed to interface to libgcrypt. Therefore handle the secure memory ourselves. So far the module is only compiled. It is not used anywhere in GParted. [1] LUKS password handling, threats and preventative measures https://bugzilla.gnome.org/show_bug.cgi?id=627701#c56 [2] libgcrypt general purpose cryptographic library, as used in GNU Privacy Guard https://gnupg.org/related_software/libgcrypt/ [3] libsodium crypto library https://download.libsodium.org/doc/ Bug 795617 - Implement opening and closing of LUKS mappings
2017-10-06 13:50:41 -06:00
PasswordRAMStore.h \
Restore compilation order of source files Restore the order of the source files so that they are once again compiled in order A-Z, a-z. Order is obtained with: fgrep .cc src/Makefile.am | LANG=C sort fgrep .h include/Makefile.am | LANG=C sort
2013-03-20 06:08:18 -06:00
PipeCapture.h \
Proc_Partitions_Info.h \
Write a generic progress bar class (#760709) Write a generic progress bar class. Has the following features: * Has separate progress and target numbers, rather than a single completion fraction, to enable the the next feature. * Optionally generates text reporting the amount of data copied using the progress and target numbers like this: "1.00 MiB of 16.00 MiB copied" * After running for 5 seconds, also add estimated remaining time. (Waits to allow the data copying rate to settle down a little before estimating the remaining time). Looks like this: "1.00 MiB of 16.00 MiB copied (00:01:59) remaining)" The ProgressBar class is not driving the visual progress bar yet. It has just been added into the internal block copy algorithm and generates debug messages showing the progress bar is operating correctly. Debugging looks like this: DEBUG: ProgressBar::start(target=2.0636e+09, text_mode=PROGRESSBAR_TEXT_COPY_BYTES) DEBUG: ProgressBar::update(progress=1.30023e+08) m_fraction=0.0630081 m_text="124.00 MiB of 1.92 GiB copied" DEBUG: ProgressBar::update(progress=2.67387e+08) m_fraction=0.129573 m_text="255.00 MiB of 1.92 GiB copied" DEBUG: ProgressBar::update(progress=4.0475e+08) m_fraction=0.196138 m_text="386.00 MiB of 1.92 GiB copied" ... DEBUG: ProgressBar::update(progress=1.13351e+09) m_fraction=0.549289 m_text="1.06 GiB of 1.92 GiB copied (00:00:04 remaining)" DEBUG: ProgressBar::update(progress=1.26249e+09) m_fraction=0.611789 m_text="1.18 GiB of 1.92 GiB copied (00:00:04 remaining)" DEBUG: ProgressBar::update(progress=1.39041e+09) m_fraction=0.67378 m_text="1.29 GiB of 1.92 GiB copied (00:00:03 remaining)" ... DEBUG: ProgressBar::update(progress=1.97552e+09) m_fraction=0.957317 m_text="1.84 GiB of 1.92 GiB copied (00:00:00 remaining)" DEBUG: ProgressBar::update(progress=2.0636e+09) m_fraction=1 m_text="1.92 GiB of 1.92 GiB copied" DEBUG: ProgressBar::stop() Bug 760709 - Add progress bars to XFS and EXT2/3/4 file system specific copy methods
2016-01-11 05:19:05 -07:00
ProgressBar.h \
Detect Linux SWRaid members by querying mdadm (#756829) Detection of Linux SWRaid members currently fails in a number of cases: 1) Arrays which use metadata type 0.90 or 1.0 store the super block at the end of the partition. So file system signatures in at least linear and mirrored arrays occur at the same offsets in the underlying partitions. As libparted only recognises file systems this is what is detected, rather than an SWRaid member. # mdadm -E -s -v ARRAY /dev/md/1 level=raid1 metadata=1.0 num-devices=2 UUID=15224a42:c25bbcd9:15db6000:4e5fe53a name=chimney:1 devices=/dev/sda1,/dev/sdb1 ... # wipefs /dev/sda1 offset type ---------------------------------------------------------------- 0x438 ext4 [filesystem] LABEL: chimney-boot UUID: 10ab5f7d-7d8a-4171-8b6a-5e973b402501 0x1fffe000 linux_raid_member [raid] LABEL: chimney:1 UUID: 15224a42-c25b-bcd9-15db-60004e5fe53a # parted /dev/sda print Model: ATA VBOX HARDDISK (scsi) Disk /dev/sda: 34.4GB Sector size (logical/physical): 512B/512B Partition Table: msdos Number Start End Size Type File system Flags 1 1049kB 538MB 537MB primary ext4 boot, raid ... 2) Again with metadata type 0.90 or 1.0 arrays blkid may report the contained file system instead of an SWRaid member. Have a single example of this configuration with a mirrored array containing the /boot file system. Blkid reports one member as ext4 and the other as SWRaid! # blkid | egrep 'sd[ab]1' /dev/sda1: UUID="10ab5f7d-7d8a-4171-8b6a-5e973b402501" TYPE="ext4" LABEL="chimney-boot" /dev/sdb1: UUID="15224a42-c25b-bcd9-15db-60004e5fe53a" UUID_SUB="0a095e45-9360-1b17-0ad1-1fe369e22b98" LABEL="chimney:1" TYPE="linux_raid_member" Bypassing the blkid cache gets the correct result. # blkid -c /dev/null /dev/sda1 /dev/sda1: UUID="15224a42-c25b-bcd9-15db-60004e5fe53a" UUID_SUB="d0460f90-d11a-e80a-ee1c-3d104dae7e5d" LABEL="chimney:1" TYPE="linux_raid_member" However this can't be used because if a user has a floppy configured in the BIOS but no floppy attached, GParted will wait for minutes as the kernel tries to access non-existent hardware on behalf of the blkid query. See commit: 18f863151c82934fe0a980853cc3deb1e439bec2 Fix long scan problem when BIOS floppy setting incorrect 3) Old versions of blkid don't recognise SWRaid members at all so always report the file system when found. Occurs with blkid v1.0 on RedHat / CentOS 5. The only way I can see how to fix all these cases is to use the mdadm command to query the configured arrays. Then use this information for first choice when detecting partition content, making the order: SWRaid members, libparted, blkid and internal. GParted shell wrapper already creates temporary blank udev rules to prevent Linux Software RAID arrays being automatically started when GParted refreshes its device information[1]. However an administrator could manually stop or start arrays or change their configuration between refreshes so GParted must load this information every refresh. On my desktop with 4 internal hard drives and 3 testing Linux Software RAID arrays, running mdadm adds between 0.20 and 0.30 seconds to the device refresh time. [1] a255abf3432ad106fac9c766f0816ada20be8e42 Prevent GParted starting stopped Linux Software RAID arrays (#709640) Bug 756829 - SWRaid member detection enhancements
2015-10-20 13:52:19 -06:00
SWRaid_Info.h \
Restore compilation order of source files Restore the order of the source files so that they are once again compiled in order A-Z, a-z. Order is obtained with: fgrep .cc src/Makefile.am | LANG=C sort fgrep .h include/Makefile.am | LANG=C sort
2013-03-20 06:08:18 -06:00
TreeView_Detail.h \
Utils.h \
Win_GParted.h \
Make btrfs support a normal part of gparted Remove need to configure with the --enable-btrfs option in order to include btrfs support in gparted.
2010-10-18 15:26:07 -06:00
btrfs.h \
Add detection of exfat file systems (#639760) Note that util-linux v2.18 or higher is required to detect exfat file systems. Part of Bug #639760 - exfat / fat64 support
2011-10-22 10:50:34 -06:00
exfat.h \
sorted filelistings. * include/Makefile.am, src/Makefile.am: sorted filelistings.
2006-03-09 13:25:57 -07:00
ext2.h \
Add f2fs file system support (#695396) Only supports detection and creation of f2fs file systems. Requires f2fs-tools and a blkid with f2fs support, util-linux > 2.22.2. f2fs-tools v1.1.0 only supports file system creation. Currently requires util-linux directly from the git repository as f2fs support was only committed on 5 Feb 2013 and it has not yet been released. Closes Bug #695396 - Please apply f2fs patch
2013-03-16 14:56:02 -06:00
f2fs.h \
Restore compilation order of source files Restore the order of the source files so that they are once again compiled in order A-Z, a-z. Order is obtained with: fgrep .cc src/Makefile.am | LANG=C sort fgrep .h include/Makefile.am | LANG=C sort
2013-03-20 06:08:18 -06:00
fat16.h \
hfs.h \
hfsplus.h \
sorted filelistings. * include/Makefile.am, src/Makefile.am: sorted filelistings.
2006-03-09 13:25:57 -07:00
i18n.h \
Restore compilation order of source files Restore the order of the source files so that they are once again compiled in order A-Z, a-z. Order is obtained with: fgrep .cc src/Makefile.am | LANG=C sort fgrep .h include/Makefile.am | LANG=C sort
2013-03-20 06:08:18 -06:00
jfs.h \
linux_swap.h \
Report space usage of LVM2 PVs (#160787) Add minimal support for just reporting the space usage of LVM2 PVs. Accept libparted / blkid detection of LVM2 PVs first, falling back on GParted's specific detection code otherwise. Maintain LVM not supported warning message. Bug #160787 - lvm support
2011-11-28 05:33:51 -07:00
lvm2_pv.h \
Add busy detection of LUKS mapping (#760080) Provide a minimal implementation of a luks file system class which only does busy detection. NOTE: For now, read-only LUKS support, a LUKS partition will be busy when a dm-crypt mapping exists. Later when read-write LUKS support is added GParted will need to look at the busy status of the encrypted file system within the open LUKS partition and map LUKS partition busy status to encryption being open or closed. Bug 760080 - Implement read-only LUKS support
2015-11-15 03:07:42 -07:00
luks.h \
Add support for minix file system (!12) Util-linux package, at least as far back as version 2.23.2 as found on CentOS 7, provides the mkfs.minix and fsck.minix commands. Also blkid from the same package, recognises minix file systems. Create version 3 file systems because MINIX 3 [1] is the only supported version and that reportedly uses version 3 of the file system [2]. [1] MINIX 3 / History https://en.wikipedia.org/wiki/MINIX_3#History [2] Regarding MINIX 3 file system https://groups.google.com/forum/#!topic/minix3/3-TeHR_23X8 "MINIX 3 uses Minix File System (MFS). More precisely MFS V3." Closes !12 - Add minix file system support
2018-08-19 06:08:55 -06:00
minix.h \
Add nilfs2 support (#642842) Requires libparted 2.4 or higher, or blkid from utils-linux 2.20 or higher for nilfs2 file system detection. Requires nilfs-utils for nilfs2 file system support. Closes Bug #642842 - nilfs is not detected
2011-12-08 05:45:12 -07:00
nilfs2.h \
Restore compilation order of source files Restore the order of the source files so that they are once again compiled in order A-Z, a-z. Order is obtained with: fgrep .cc src/Makefile.am | LANG=C sort fgrep .h include/Makefile.am | LANG=C sort
2013-03-20 06:08:18 -06:00
ntfs.h \
reiser4.h \
reiserfs.h \
Add support for UDF file system (#784533) Add support for detecting UDF file systems and formatting hard disks with revision 2.01 UDF file systems using udftools. Formatting optical disks or any other media types is not supported yet. Changing label or UUID after formatting is not supported as the tools do not yet exist. Bug 784533 - Add support for UDF file system
2017-07-04 18:15:35 -06:00
udf.h \
Restore compilation order of source files Restore the order of the source files so that they are once again compiled in order A-Z, a-z. Order is obtained with: fgrep .cc src/Makefile.am | LANG=C sort fgrep .h include/Makefile.am | LANG=C sort
2013-03-20 06:08:18 -06:00
xfs.h