Mirrors
/
gparted
mirror of https://gitlab.gnome.org/GNOME/gparted.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
gparted/po/POTFILES.in

71 lines
1.4 KiB
Plaintext
Raw Normal View History

Added "sv" to ALL_LINGUAS. Added an entry. Added comment. Added Swedish 2004-09-23 Christian Rose <menthos@menthos.com> * configure.in: Added "sv" to ALL_LINGUAS. * po/.cvsignore: Added an entry. * po/POTFILES.in: Added comment. * po/sv.po: Added Swedish translation.
2004-09-22 17:06:54 -06:00
# List of source files containing translatable strings.
# Please keep this file sorted alphabetically.
Add an AppData file (#709164) For more information on AppData see: AppData Specification http://people.freedesktop.org/~hughsient/appdata/ Application metadata with AppData http://lwn.net/Articles/569034/ Bug #709164 - Please include an AppData file
2013-10-01 02:09:42 -06:00
gparted.appdata.xml.in
Fixed bug #324220 with the following changes: - Removed gparted-disable-automount.fdi handling. - Renamed gparted binary to gpartedbin to permit a calling script to be named gparted. - Added new calling script gparted.in to permit using hal-lock to acuiqre device locks to prevent automounting while executing gpartedbin. - Renamed gparted.desktop.in to gparted.desktop.in.in to permit parsing installdir. svn path=/trunk/; revision=826
2008-04-21 09:22:00 -06:00
gparted.desktop.in.in
Add required polkit action file (#776437) An action file is always needed with polkit to describe the privileged actions that are available to the subject (client program). For GParted the only available action is to run the gparted shell script as root. Note that the polkit action file will be installed into location $(prefix)/share/polkit-1/actions. This is required by the GNU Coding Standards [1] and to prevent 'make distcheck' from failing [2]. However polkit only uses /usr/share/polkit-1/actions for it's action files [3]. This dilemma was discussed in this Bugzilla bug 776437 and on the general Automake discussion email list [4]. The solution is to simply document in the README file that a manual additional installation step may be required. The action file is marked as translatable with the underscore (_) of the _description and _message tags identifying the string to be translated. Use of INTLTOOL_POLICY_RULE in Makefile.am to merge translations into the polkit action file necessitates increasing the minimum version of intltool to 0.36.0 where it was first introduced in intltool.m4. This will prevent GParted building on RedHat/CentOS 5 which only has intltool 0.35.0. But that doesn't matter because RedHat/CentOS 5 reached end of life on 31st March 2017. [1] GNU Coding Standards, 7.2.5 Variables for Installation Directories https://www.gnu.org/prep/standards/standards.html#Directory-Variables [2] Automake Manual, 27.10 Installing to Hard-Coded Locations https://www.gnu.org/software/automake/manual/automake.html#Hard_002dCoded-Install-Paths "My package needs to populate the installation directory of another package at install-time. I can easily compute that installation directory in configure, but if I install files therein, 'make distcheck' fails. How else should I do?" [3] polkit(8), Declaring Actions https://www.freedesktop.org/software/polkit/docs/latest/polkit.8.html#polkit-declaring-actions "A mechanism need to declare a set of actions in order to use polkit. Actions correspond to operations that clients can request the mechanism to carry out and are defined in XML files that the mechanism installs into the /usr/share/polkit-1/actions directory." [4] Not installing to hard-coded locations vs polkit's fixed location http://lists.gnu.org/archive/html/automake/2017-08/msg00015.html Bug 776437 - GParted fails to run as root under Wayland
2017-06-24 03:39:37 -06:00
org.gnome.gparted.policy.in.in
Implement changing UUID for NTFS (#667278) Part 4 of 4 to provide new UUID support for NTFS. Closes Bug #667278 - Add support for setting UUID
2012-01-30 11:33:33 -07:00
include/Utils.h
Report busy status of bcache (#183) Make (format as) bcache backing device (-B) and cache device (-C) and implicitly attach the backing device to the cache to enable caching, all in one. # bcache make -B /dev/sdb1 -C /dev/sdc1 # bcache show Name Type State Bname AttachToDev /dev/sdb1 1 (data) clean(running) bcache0 /dev/sdc1 /dev/sdc1 3 (cache) active N/A N/A After experimenting with 'bcache unregister', 'bcache register' and stracing 'bcache show' the bcache kernel module creates the sysfs directory /sys/block/DEV[/PTN]/bcache and it's contents only when the bcache device is registered with the kernel (bcache component is active). Use this to identify whether any bcache device (component) should be displayed as active or not in GParted. # ls -ld /sys/block/sd?/sd?1/bcache drwxr-xr-x. 6 root root 0 Jan 7 10:08 /sys/block/sdb/sdb1/bcache drwxr-xr-x. 2 root root 0 Jan 7 10:08 /sys/block/sdc/sdc1/bcache Closes #183 - Basic support for bcache
2022-01-07 03:08:20 -07:00
src/BCache_Info.cc
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
src/BlockSpecial.cc
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
src/CopyBlocks.cc
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
src/DialogPasswordEntry.cc
initial import
2004-09-20 11:51:25 -06:00
src/Dialog_Base_Partition.cc
P (special thanks to mantiena-baltix for bringing this issue to my * Harddisks without disklabel are now properly initizalized and shown in the menu. When one tries to create a new partition on such a disk a dialog pops up with some blabla about disklabels and offers to create a disklabel. sweet :P (special thanks to mantiena-baltix for bringing this issue to my attention) * fixed minor annoyance with refreshing detailed deviceinfo after a 'deep refresh'
2004-11-27 16:31:19 -07:00
src/Dialog_Disklabel.cc
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
src/Dialog_FileSystem_Label.cc
initial import
2004-09-20 11:51:25 -06:00
src/Dialog_Partition_Copy.cc
src/Dialog_Partition_Info.cc
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
src/Dialog_Partition_Name.cc
initial import
2004-09-20 11:51:25 -06:00
src/Dialog_Partition_New.cc
src/Dialog_Partition_Resize_Move.cc
src/Dialog_Progress.cc
disabled resizing of this dialog renamed 'Filesystems' to 'Features' in * src/DialogManageFlags.cc: disabled resizing of this dialog * include/DialogFeatures.h, include/Makefile.am, include/Win_GParted.h, src/DialogFeatures.cc, src/Makefile.am, src/Win_GParted.cc: renamed 'Filesystems' to 'Features' in the featuredialog to better reflect the actual functionality * include/Dialog_Filesystems.h, src/Dialog_Filesystems.cc: removed
2006-04-05 03:33:04 -06:00
src/DialogFeatures.cc
added DialogManageFlags.cc * POTFILES.in: added DialogManageFlags.cc
2006-04-01 00:14:20 -07:00
src/DialogManageFlags.cc
Added src/DMRaid.cc file svn path=/trunk/; revision=1101
2009-03-20 19:03:59 -06:00
src/DMRaid.cc
Add files for translation to POTFILES.in The file src/FileSystem.cc now contains translatable text. Also added src/nilfs2.cc to handle any future translatable text.
2012-01-11 13:01:10 -07:00
src/FileSystem.cc
availability of 'tune2fs' command wasn't detected correctly. fixed make * src/ext3.cc: availability of 'tune2fs' command wasn't detected correctly. fixed * src/fat32.cc: make use of dosfs tools (mkdosfs -F32) instead of libparted's Fat-creator. * po/POTFILES.in: added src/GParted_Core.cc
2004-11-17 07:12:18 -07:00
src/GParted_Core.cc
Replaced std::abs with llabs (see #357691) added support for reading of * src/GParted_Core: Replaced std::abs with llabs (see #357691) * src/hfs.cc, src/xfs.cc: added support for reading of volumelabel * src/reiserfs.cc: added Fixme
2006-10-01 07:08:57 -06:00
src/HBoxOperations.cc
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
src/LVM2_PV_Info.cc
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
src/LUKS_Info.cc
prepare-for-gtk3: Prepare for removal of Gtk::Menu_Helpers::Element (#7) Gtk::Menu_Helpers::Element class and subclasses help in Gtk::MenuItem widgets and also automate tasks like registering keyboard accelerators when parented to a top-level window [1][2]. Gtk::Menu_Helpers::Element class and subclasses were removed in Gtkmm3 [3]. Provide compatible implementations under the namespace GParted::Menu_Helpers. References: [1] gtkmm: Gtk::Menu_Helpers Namespace Reference https://developer.gnome.org/gtkmm/2.24/namespaceGtk_1_1Menu__Helpers.html [2] gtkmm: Gtk::Menu_Helpers::Element Class Reference https://developer.gnome.org/gtkmm/2.24/classGtk_1_1Menu__Helpers_1_1Element.html [3] Gtkmm 3 commit "MenuShell: Remove items()." removed the code https://gitlab.gnome.org/GNOME/gtkmm/commit/c8e47b0db5505db0e10e74ce1d7286c2230958b5 Closes #7 - Port to Gtk3
2018-07-31 07:36:11 -06:00
src/MenuHelpers.cc
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
src/Mount_Info.cc
Add support for setting UUID (#667278) Add the ability to set a new random UUID on file systems that provide the appropriate tools to perform this action. Update the help manual to include this new functionality. Also add reference links to "setting a partition label" and "changing a partition UUID" in the "copying and pasting a partition" section. This patch does not include setting the UUID on an NTFS file system. Bug #667278 - Add support for setting UUID Bug #608308 - fix documentation - Copying and Pasting a Partition
2012-01-22 13:49:52 -07:00
src/OperationChangeUUID.cc
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
src/OperationCopy.cc
added src/OperationCheck.cc * POTFILES.in: added src/OperationCheck.cc
2006-11-26 07:29:21 -07:00
src/OperationCheck.cc
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
src/OperationCreate.cc
src/OperationDelete.cc
Make OperationDetail no_more_children bug message translatable (#790842) To be consistent with all previous bug messages being translatable. Also only mark the bug as a warning instead of an error because the bug doesn't cause any disk drive operations to fail. Bug 790842 - Report libparted messages into operation details at the point at which they occur
2017-12-03 03:32:26 -07:00
src/OperationDetail.cc
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
src/OperationFormat.cc
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
src/OperationLabelFileSystem.cc
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
src/OperationNamePartition.cc
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
src/OperationResizeMove.cc
modern-gtk2: Introduce OptionComboBox class (!17) Gtk::OptionMenu is a combobox type widget that is constructed from a Gtk::Menu rather than a Gtk::TreeModel. However Gtk::OptionMenu was deprecated in gtkmm 2.4.1. In GParted the Gtk::OptionMenu widget is used for: - partition alignment combobox - partition type combobox - file system combobox While they consist only of text we cannot use Gtk::ComboBoxText because it doesn't expose functionality in its interface to make items inactive. Create OptionComboBox helper class that builds a combobox consisting of only text items, much like Gtk::ComboBoxText, but has the added functionality to set items as inactive. References: https://developer.gnome.org/gtkmm/2.24/classGtk_1_1OptionMenu.html#details https://gitlab.gnome.org/GNOME/gtkmm/blob/GTKMM_2_10_1/ChangeLog#L3515 https://gitlab.gnome.org/GNOME/gtkmm/commit/bba503b0473413e474d9b6d297226479d29fd47f https://developer.gnome.org/gtkmm/2.24/classGtk_1_1ComboBoxText.html Closes !17 - Gtk2 modernisation
2018-07-30 02:24:18 -06:00
src/OptionComboBox.cc
added ../src/Partition.cc
2004-09-27 01:38:34 -06:00
src/Partition.cc
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
src/PartitionLUKS.cc
Use pointers to Partitions in PartitionVector class (#759726) The PartitionVector class is now internally using pointers to Partition objects and taking on management of their lifetimes. It therefore has to implement the Big 3: destructor, copy constructor and copy assignment operator [1][2]. This is because the implicitly-defined copy constructor and assignment operator perform memberwise "shallow copying" and the destructor does nothing. This not correct for classes which contain non-class types such as raw pointers. The semantics of the interface still copies each Partition object into the PartitionVector when they are added with push_back() and insert(). Note that a PartitionVector object is explicitly copy assigned in Win_GParted::Refresh_Visual(). They are also implicitly copied when (1) the implementing vector is resized larger to allow it to hold more pointers to Partition objects than it previously had capacity for; and (2) a Partition object is copied including the logicals PartitionVector member. [1] The rule of three/five/zero http://en.cppreference.com/w/cpp/language/rule_of_three [2] Rule of Three https://en.wikipedia.org/wiki/Rule_of_three_%28C%2B%2B_programming%29 Bug 759726 - Implement Partition object polymorphism
2015-06-16 15:34:59 -06:00
src/PartitionVector.cc
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
src/PasswordRAMStore.cc
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
src/ProgressBar.cc
Split FILESYSTEMS and FILESYSTEM_MAP into separate module (!49) GParted_Core::FILESYSTEMS and ::FILESYSTEM_MAP and the methods that query and manipulate them are self-contained. Therefore move them into a separate SupportedFileSystems module. Also having a single class maintaining all FileSystem interface objects will make testing all the file system types much easier as there will be no need to duplicate this functionality in the test. Closes !49 - Add file system interface tests
2019-07-16 06:01:07 -06:00
src/SupportedFileSystems.cc
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
src/SWRaid_Info.cc
initial import
2004-09-20 11:51:25 -06:00
src/TreeView_Detail.cc
replaced the inline Utils functions with static functions. This shaves a * replaced the inline Utils functions with static functions. This shaves a few kbytes (24 in fact) off the binary and is a bit cleaner code-wise (imho).
2005-12-13 14:30:13 -07:00
src/Utils.cc
initial import
2004-09-20 11:51:25 -06:00
src/Win_GParted.cc
Add bcachefs creation (!123) Set the minimum file system size to 16 MiB as creating a bcachefs that size succeeds: $ truncate -s $((16*1024*1024)) /tmp/disk.img $ bcachefs format /tmp/disk.img ... initializing new filesystem going read-write initializing freespace $ echo $? 0 Where as creating a smaller file system fails for most sizes below that: $ rm /tmp/disk.img $ truncate -s $((15*1024*1024)) /tmp/disk.img $ bcachefs format /tmp/disk.img ... mounting version 1.6: btree_subvolume_children initializing new filesystem going read-write bch2_trans_mark_dev_sb(): error ENOSPC_disk_reservation bch2_fs_initialize(): error marking superblocks ENOSPC_disk_reservation bch2_fs_initialize(): error ENOSPC_disk_reservation bch2_fs_start(): error starting filesystem ENOSPC_disk_reservation error opening /tmp/disk.img: ENOSPC_disk_reservation $ echo $? 1 Closes !123 - Add support for bcachefs, single device file systems only
2024-02-28 09:35:22 -07:00
src/bcachefs.cc
Add missing file systems to POTFILES.in Specifically btrfs, ext4, and ufs.
2011-10-22 12:07:22 -06:00
src/btrfs.cc
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
src/exfat.cc
added a few files (i should run 'intltool-update -m' more often ;) ) * POTFILES.in: added a few files (i should run 'intltool-update -m' more often ;) )
2006-01-22 17:37:23 -07:00
src/ext2.cc
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
src/f2fs.cc
added a few files (i should run 'intltool-update -m' more often ;) ) * POTFILES.in: added a few files (i should run 'intltool-update -m' more often ;) )
2006-01-22 17:37:23 -07:00
src/fat16.cc
src/hfs.cc
added src/hfsplus.cc * POTFILES.in: added src/hfsplus.cc
2006-04-09 01:22:34 -06:00
src/hfsplus.cc
added a few files (i should run 'intltool-update -m' more often ;) ) * POTFILES.in: added a few files (i should run 'intltool-update -m' more often ;) )
2006-01-22 17:37:23 -07:00
src/jfs.cc
src/linux_swap.cc
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
src/lvm2_pv.cc
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
src/luks.cc
added ../src/main.cc
2004-09-24 19:55:35 -06:00
src/main.cc
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
src/minix.cc
added a few files (i should run 'intltool-update -m' more often ;) ) * POTFILES.in: added a few files (i should run 'intltool-update -m' more often ;) )
2006-01-22 17:37:23 -07:00
src/ntfs.cc
Add files for translation to POTFILES.in The file src/FileSystem.cc now contains translatable text. Also added src/nilfs2.cc to handle any future translatable text.
2012-01-11 13:01:10 -07:00
src/nilfs2.cc
added a few files (i should run 'intltool-update -m' more often ;) ) * POTFILES.in: added a few files (i should run 'intltool-update -m' more often ;) )
2006-01-22 17:37:23 -07:00
src/reiser4.cc
src/reiserfs.cc
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
src/udf.cc
added a few files (i should run 'intltool-update -m' more often ;) ) * POTFILES.in: added a few files (i should run 'intltool-update -m' more often ;) )
2006-01-22 17:37:23 -07:00
src/xfs.cc