gparted/README

345 lines
12 KiB
Plaintext
Raw Normal View History

GPARTED
2010-12-12 11:17:35 -07:00
=======
2014-04-04 12:27:48 -06:00
Gparted is the GNOME Partition Editor for creating, reorganizing, and
deleting disk partitions.
A hard disk is usually subdivided into one or more partitions. These
partitions are normally not re-sizable (making one smaller and the
adjacent one larger.) Gparted makes it possible for you to take a
hard disk and change the partition organization, while preserving the
partition contents.
2004-09-19 14:24:53 -06:00
More specifically, Gparted enables you to create, destroy, resize,
move, check, label, and copy partitions, and the file systems
contained within. This is useful for creating space for new operating
systems, reorganizing disk usage, and mirroring one partition with
another (disk imaging).
2004-09-19 14:24:53 -06:00
Gparted can also be used with storage devices other than hard disks,
such as USB flash drives, and memory cards.
Visit https://gparted.org for more information.
LICENSING
---------
GParted is released under the General Public License version 2, or (at
your option) any later version. (GPLv2+). All files are released under
the GPLv2+ unless explicitly licensed otherwise.
The GParted Manual is released under the GNU Free Documentation License
version 1.2 or any later version. (GFDLv1.2+).
Google Test C++ test framework is released under the 3-Clause BSD
License. (BSD-3-Clause).
See these files for more details:
COPYING - GNU General Public License version 2
COPYING-DOCS - GNU Free Documentation License version 1.2
lib/gtest/LICENSE
- 3-Clause BSD License
NEWS
----
Information about changes to this release, and past releases can be
found in the file:
NEWS
INSTALL
-------
a. Pre-built Binary
Many GNU/Linux distributions already provide a pre-built binary
package for GParted. Instructions on how to install GParted on
some distributions is given below:
CentOS/RHEL
-----------
su -
yum install gparted
Debian or Ubuntu
----------------
sudo apt-get install gparted
Fedora
------
su -
dnf install gparted
OpenSUSE
--------
sudo zypper install gparted
b. Building from Source
Briefly, build and install GParted into the default location of
/usr/local using:
./configure
make
sudo make install
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
sudo install -m 644 org.gnome.gparted.policy \
/usr/share/polkit-1/actions/org.gnome.gparted.local.policy
This assumes all the dependencies are already installed, builds the
default configuration and polkit is being used as the graphical su
program.
The following dependencies are required to build GParted from source:
g++
make
parted
gnome-common
gtkmm3
gettext
intltool
yelp-tools - required if help documentation is to be built
On CentOS/RHEL, these dependencies may be obtained by running the
following command as root:
yum install gnome-common yelp-tools glib2-devel intltool gcc-c++ \
libuuid-devel parted-devel gtkmm30-devel make
On Debian or Ubuntu, these dependencies may be obtained by running
one of the following commands:
Either;
sudo apt-get build-dep gparted
Or;
sudo apt-get install build-essential gnome-common yelp-tools \
libglib2.0-dev uuid-dev libparted-dev \
libgtkmm-3.0-dev
On Fedora, these dependencies may be obtained by running the
following command as root:
dnf install gnome-common yelp-tools glib2-devel intltool gcc-c++ \
libuuid-devel parted-devel gtkmm30-devel make
On openSUSE, these dependencies may be obtained by running the
following commands:
sudo zypper install gnome-common gcc-c++ libuuid-devel \
parted-devel gtkmm3-devel make
Again, build GParted with the default configuration and install into
the default location of /usr/local using:
./configure
make
sudo make install
If you wish to build this package without the help documentation use
the --disable-doc flag:
E.g., ./configure --disable-doc
If you wish to build this package to use native libparted /dev/mapper
dmraid support use the --enable-libparted-dmraid flag:
E.g., ./configure --enable-libparted-dmraid
If you wish to build this package with online resize support then
the following is required:
a) Linux kernel version 3.6 or higher.
b) Libparted with online resize support. Either:
i) Libparted version 3.2 or later which includes online
resize support as standard. In this case GParted is
automatically built with online resize support.
ii) Online resize support back ported into an earlier version
of libparted. This is only known to be included in Debian
and derived distributions with parted version 2.3-14 and
higher. In this case online resize support must be
specifically enabled with the --enable-online-resize flag:
E.g., ./configure --enable-online-resize
If you wish to build GParted to allow it to use xhost to grant root
access to the X11 server use the --enable-xhost-root flag. This is
required to allow GParted to display under Wayland.
./configure --enable-xhost-root
Please note that more than one configure flag can be used:
E.g., ./configure --disable-doc --enable-libparted-dmraid
The INSTALL file contains further GNU installation instructions.
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
c. Installing polkit's Action File
GParted needs to run as root therefore it needs a graphical switch
user program to allow normal users to run it. Most desktops now use
polkit as their preferred authorisation mechanism. Therefore
./configure looks for polkit's pkexec as the first choice with
fallbacks in order being: gksudo, gksu, kdesudo and finally xdg-su.
Also polkit reads action files only from directory
/usr/share/polkit-1/actions. Therefore it is likely that a polkit
action file will need to be installed into this directory.
To determine if polkit's pkexec program is being used as the
graphical privilege escalation program examine the output from
./configure. These lines report that pkexec is being used:
checking for pkexec >= 0.102... 0.112 found
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
Where as either of these lines of ./configure output report that
pkexec is not being used because either it was too old a version or
it was not found:
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
checking for pkexec >= 0.102... 0.96 found
checking for pkexec >= 0.102... not found
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
When GParted is configured with prefix /usr (using command
./configure --prefix=/usr) then make install will automatically
install the polkit action file into the correct directory and no
further steps need to be taken. This is typically the case for
distribution builds of GParted.
However when GParted is configured with the default prefix of
/usr/local, or any prefix other than /usr, then the polkit action
file has to be manually installed into the correct directory. Also
it should have a unique file name to avoid overwriting the action
file from the distribution's package. Install the polkit action file
with a unique name including an extra ".local" in the name:
sudo install -m 644 org.gnome.gparted.policy \
/usr/share/polkit-1/actions/org.gnome.gparted.local.policy
d. Building using a Specific (lib)parted Version
1) Download the parted version you wish to use (e.g., 3.2) from:
http://ftp.gnu.org/gnu/parted/
2) Build and install parted.
Extract parted tarball, configure, make, and sudo make install.
Note that by default this will install into /usr/local.
3) Set environment variables to inform the GParted build system to
use libparted from /usr/local:
export CPPFLAGS=-I/usr/local/include
export LDFLAGS=-L/usr/local/lib
export LD_RUN_PATH=/usr/local/lib
Fix configuration version mismatch when using custom install of libparted (#753525) When configuring GParted build with a custom install of libparted the configure script is using the wrong version number for the version of libparted. It uses the version of the system install of libparted, rather that the version of the specified custom install of libparted. For example configuring GParted build on CentOS 7 with system provided libparted 3.1 and custom install of libparted 3.2 from GIT in /tmp/parted-3.2-git: $ export CPPFLAGS=-I/tmp/parted-3.2-git/include $ export LDFLAGS=-L/tmp/parted-3.2-git/lib $ export LD_RUN_PATH=/tmp/parted-3.2-git/lib $ ./configure ... checking for libparted >= 1.7.1 (querying pkg-config)... 3.1 checking for 2.0 <= libparted <= 3.0 (loop table creation doesn't delete old partitions)... (cached) no checking for libparted >= 2.2 (improved pt re-read)... (cached) yes checking for ped_file_system_resize in -lparted... no checking for ped_file_system_resize in -lparted-fs-resize... yes checking for libparted >= 3.2 (online resize)... (cached) no ... $ make $ ldd src/gpartedbin | fgrep libparted libparted-fs-resize.so.0 => /tmp/parted-3.2-git/lib/libparted-fs-resize.so.0 (0x00007f9a460ee000) libparted.so.2 => /tmp/parted-3.2-git/lib/libparted.so.2 (0x00007f9a45ea3000) Configure script used version 3.1 as reported by pkg-config to make most of the decisions (those version related checks with cached results) but the executable was still linked with the custom libparted 3.2 install. Temporarily rename the system libparted pkg-config file out of the way: # cd /usr/lib64/pkgconfig # mv libparted.pc libparted.pc-NOT and reconfigure the GParted build: $ ./configure ... checking for libparted >= 1.7.1 (querying pkg-config)... not found checking for libparted >= 1.7.1 (querying libparted)... 3.2.25-5a92 checking for 2.0 <= libparted <= 3.0 (loop table creation doesn't delete old partitions)... (cached) no checking for libparted >= 2.2 (improved pt re-read)... (cached) yes checking for ped_file_system_resize in -lparted... no checking for ped_file_system_resize in -lparted-fs-resize... yes checking for libparted >= 3.2 (online resize)... (cached) yes ... Now configure is having to compile a program with the custom install of libparted and gets the correct version. Restore libparted pkg-config file: # mv libparted.pc-NOT libparted.pc and this time set environment variable PKG_CONFIG_PATH to inform pkg-config of the additional directory to search for .pc files before the default system location: $ export PKG_CONFIG_PATH=/tmp/parted-3.2-git/lib/pkgconfig $ ./configure ... checking for libparted >= 1.7.1 (querying pkg-config)... 3.2.25-5a92 checking for 2.0 <= libparted <= 3.0 (loop table creation doesn't delete old partitions)... (cached) no checking for libparted >= 2.2 (improved pt re-read)... (cached) yes checking for ped_file_system_resize in -lparted... no checking for ped_file_system_resize in -lparted-fs-resize... yes checking for libparted >= 3.2 (online resize)... (cached) yes ... Now configure is getting the correct version of the custom install of libparted when querying pkg-config and thus making the correct decisions. Update the README file to reflect the need to also set the PKG_CONFIG_PATH environment variable when building GParted with a custom install of libparted. Bug 753525 - Configuration issues when using non-system location or non-released versions of libparted
2015-08-11 11:18:54 -06:00
export PKG_CONFIG_PATH=/usr/local/lib/pkgconfig
4) Build gparted using steps listed above in "Building from Source".
Note that when you run ./configure you should see the specific
version of parted listed in the check for libparted >= 1.7.1.
You will also see the libparted version listed when running
gparted from the command line.
DIRECTORIES
------------
data - contains desktop icons
doc - contains manual page documentation
help - contains GParted Manual and international translations
include - contains source header files
lib/gtest
- contains Google Test C++ test framework libraries
m4 - contains macro files
po - contains international language translations
src - contains C++ source code
DISTRIBUTION NOTES
------------------
Document blkid command as a mandatory requirement (#753436) Update the README file to document the blkid command as a mandatory requirement for GParted. GParted will run without blkid but it is needed to detect a number of file systems which libparted doesn't and in a number of other situations. Blkid is needed to detect these file systems: exfat f2fs ReFS SWRaid ZFS Blkid also detects these file systems (for which GParted has simple internal detection but libparted, mostly, doesn't detect): btrfs (detected by libparted >= 3.2) LVM2 PV LUKS nilfs2 (detected by libparted >= 2.4) reiser4 Blkid is also needed for these commits: 1) f8faee637787329c07771e495c9b26abc9ac1603 Avoid whole disk FAT being detected as MSDOS partition table (#743181) (with libparted 1.9.0 to 2.3 inclusive) 2) 9e5e9f5627e0fb1b547f07cdaaac773c7b6035b9 Enhance file system detection to use FS_Info method - blkid (Detect file systems with sector sizes other than 512 bytes with libparted 2.2) Other changes to the DISTRIBUTION NOTES section of the README file: * Drop NOTE about vol_id and blkid being used to read volume labels for specific file systems and read the UUIDs. Vol_id was deprecated in May 2009 and is not included in any currently supported distribution. Blkid is now mandatory. List of optional commands at the end of the section seems to cover everything that is necessary. * Indent description of optional commands at the end of the section to match the indentation earlier in the section. * Line wrap the section at column 72 to match the rest of the file. Bug 753436 - Update documentation of GParted software dependencies
2015-08-10 04:30:46 -06:00
GParted uses GNU libparted to detect and manipulate devices and
partition tables. The blkid command is also required to detect those
file systems which libparted doesn't detect. (The blkid command should
be considered a mandatory requirement).
GParted also queries and manipulates the file systems within those
devices and partitions. When available, it uses each file system's
specific commands. The following optional file system specific packages
provide this support:
btrfs-progs / btrfs-tools
e2fsprogs
f2fs-tools
dosfstools
Document blkid command as a mandatory requirement (#753436) Update the README file to document the blkid command as a mandatory requirement for GParted. GParted will run without blkid but it is needed to detect a number of file systems which libparted doesn't and in a number of other situations. Blkid is needed to detect these file systems: exfat f2fs ReFS SWRaid ZFS Blkid also detects these file systems (for which GParted has simple internal detection but libparted, mostly, doesn't detect): btrfs (detected by libparted >= 3.2) LVM2 PV LUKS nilfs2 (detected by libparted >= 2.4) reiser4 Blkid is also needed for these commits: 1) f8faee637787329c07771e495c9b26abc9ac1603 Avoid whole disk FAT being detected as MSDOS partition table (#743181) (with libparted 1.9.0 to 2.3 inclusive) 2) 9e5e9f5627e0fb1b547f07cdaaac773c7b6035b9 Enhance file system detection to use FS_Info method - blkid (Detect file systems with sector sizes other than 512 bytes with libparted 2.2) Other changes to the DISTRIBUTION NOTES section of the README file: * Drop NOTE about vol_id and blkid being used to read volume labels for specific file systems and read the UUIDs. Vol_id was deprecated in May 2009 and is not included in any currently supported distribution. Blkid is now mandatory. List of optional commands at the end of the section seems to cover everything that is necessary. * Indent description of optional commands at the end of the section to match the indentation earlier in the section. * Line wrap the section at column 72 to match the rest of the file. Bug 753436 - Update documentation of GParted software dependencies
2015-08-10 04:30:46 -06:00
mtools - required to read and write FAT16/32 volume labels
and UUIDs
hfsutils
hfsprogs
jfsutils
nilfs-utils / nilfs-tools
ntfs-3g / ntfsprogs
reiser4progs
reiserfsprogs / reiserfs-utils / reiserfs
udftools
util-linux - required to create and check MINIX file systems
xfsprogs, xfsdump
For dmraid support, the following packages are required:
dmsetup - removes /dev/mapper entries
Document blkid command as a mandatory requirement (#753436) Update the README file to document the blkid command as a mandatory requirement for GParted. GParted will run without blkid but it is needed to detect a number of file systems which libparted doesn't and in a number of other situations. Blkid is needed to detect these file systems: exfat f2fs ReFS SWRaid ZFS Blkid also detects these file systems (for which GParted has simple internal detection but libparted, mostly, doesn't detect): btrfs (detected by libparted >= 3.2) LVM2 PV LUKS nilfs2 (detected by libparted >= 2.4) reiser4 Blkid is also needed for these commits: 1) f8faee637787329c07771e495c9b26abc9ac1603 Avoid whole disk FAT being detected as MSDOS partition table (#743181) (with libparted 1.9.0 to 2.3 inclusive) 2) 9e5e9f5627e0fb1b547f07cdaaac773c7b6035b9 Enhance file system detection to use FS_Info method - blkid (Detect file systems with sector sizes other than 512 bytes with libparted 2.2) Other changes to the DISTRIBUTION NOTES section of the README file: * Drop NOTE about vol_id and blkid being used to read volume labels for specific file systems and read the UUIDs. Vol_id was deprecated in May 2009 and is not included in any currently supported distribution. Blkid is now mandatory. List of optional commands at the end of the section seems to cover everything that is necessary. * Indent description of optional commands at the end of the section to match the indentation earlier in the section. * Line wrap the section at column 72 to match the rest of the file. Bug 753436 - Update documentation of GParted software dependencies
2015-08-10 04:30:46 -06:00
dmraid - lists dmraid devices and creates /dev/mapper
entries
For GNU/Linux distribution dmraid support, the following are required:
Document blkid command as a mandatory requirement (#753436) Update the README file to document the blkid command as a mandatory requirement for GParted. GParted will run without blkid but it is needed to detect a number of file systems which libparted doesn't and in a number of other situations. Blkid is needed to detect these file systems: exfat f2fs ReFS SWRaid ZFS Blkid also detects these file systems (for which GParted has simple internal detection but libparted, mostly, doesn't detect): btrfs (detected by libparted >= 3.2) LVM2 PV LUKS nilfs2 (detected by libparted >= 2.4) reiser4 Blkid is also needed for these commits: 1) f8faee637787329c07771e495c9b26abc9ac1603 Avoid whole disk FAT being detected as MSDOS partition table (#743181) (with libparted 1.9.0 to 2.3 inclusive) 2) 9e5e9f5627e0fb1b547f07cdaaac773c7b6035b9 Enhance file system detection to use FS_Info method - blkid (Detect file systems with sector sizes other than 512 bytes with libparted 2.2) Other changes to the DISTRIBUTION NOTES section of the README file: * Drop NOTE about vol_id and blkid being used to read volume labels for specific file systems and read the UUIDs. Vol_id was deprecated in May 2009 and is not included in any currently supported distribution. Blkid is now mandatory. List of optional commands at the end of the section seems to cover everything that is necessary. * Indent description of optional commands at the end of the section to match the indentation earlier in the section. * Line wrap the section at column 72 to match the rest of the file. Bug 753436 - Update documentation of GParted software dependencies
2015-08-10 04:30:46 -06:00
- kernel built with Device Mapping and Mirroring built. From
menuconfig, it is under Device Drivers -> <something> (RAID & LVM).
- dmraid drive arrays activated on boot (e.g., dmraid -ay).
For LVM2 Physical Volume support the following command is required:
lvm - LVM2 administration tool
And device-mapper support in the kernel.
For accurate detection and reporting of Linux Software RAID Arrays the
following command is required:
mdadm - SWRaid administration tool
For LUKS support the following commands are required:
cryptsetup - LUKS volume administration tool
dmsetup - Device-mapper administration tool
For attempt data rescue for lost partitions, the following package
is required:
gpart - guesses PC-type hard disk partitions
Document blkid command as a mandatory requirement (#753436) Update the README file to document the blkid command as a mandatory requirement for GParted. GParted will run without blkid but it is needed to detect a number of file systems which libparted doesn't and in a number of other situations. Blkid is needed to detect these file systems: exfat f2fs ReFS SWRaid ZFS Blkid also detects these file systems (for which GParted has simple internal detection but libparted, mostly, doesn't detect): btrfs (detected by libparted >= 3.2) LVM2 PV LUKS nilfs2 (detected by libparted >= 2.4) reiser4 Blkid is also needed for these commits: 1) f8faee637787329c07771e495c9b26abc9ac1603 Avoid whole disk FAT being detected as MSDOS partition table (#743181) (with libparted 1.9.0 to 2.3 inclusive) 2) 9e5e9f5627e0fb1b547f07cdaaac773c7b6035b9 Enhance file system detection to use FS_Info method - blkid (Detect file systems with sector sizes other than 512 bytes with libparted 2.2) Other changes to the DISTRIBUTION NOTES section of the README file: * Drop NOTE about vol_id and blkid being used to read volume labels for specific file systems and read the UUIDs. Vol_id was deprecated in May 2009 and is not included in any currently supported distribution. Blkid is now mandatory. List of optional commands at the end of the section seems to cover everything that is necessary. * Indent description of optional commands at the end of the section to match the indentation earlier in the section. * Line wrap the section at column 72 to match the rest of the file. Bug 753436 - Update documentation of GParted software dependencies
2015-08-10 04:30:46 -06:00
Several more commands are optionally used by GParted if found on the
system. These commands include:
blkid - [mandatory requirement] used to detect file systems
libparted doesn't, read UUIDs and volume labels
hdparm - used to query disk device serial numbers
udisks - used to prevent automounting of file systems
devkit-disks - used to prevent automounting of file systems
{filemanager} - used in attempt data rescue to display discovered
file systems. (e.g., nautilus, pcmanfm)
hal-lock - used to prevent automounting of file systems
pkexec - used to acquire root privileges in gparted shell
script wrapper, but only if available when gparted
source is configured
gksudo - alternatively used to acquire root privileges in
gparted shell script wrapper, second choice if
available when gparted source is configured
gksu - alternatively used to acquire root privileges in
gparted shell script wrapper, third choice if
available when gparted source is configured
kdesudo - alternatively used to acquire root privileges in
gparted shell script wrapper, fourth choice if
available when gparted source is configured
Document blkid command as a mandatory requirement (#753436) Update the README file to document the blkid command as a mandatory requirement for GParted. GParted will run without blkid but it is needed to detect a number of file systems which libparted doesn't and in a number of other situations. Blkid is needed to detect these file systems: exfat f2fs ReFS SWRaid ZFS Blkid also detects these file systems (for which GParted has simple internal detection but libparted, mostly, doesn't detect): btrfs (detected by libparted >= 3.2) LVM2 PV LUKS nilfs2 (detected by libparted >= 2.4) reiser4 Blkid is also needed for these commits: 1) f8faee637787329c07771e495c9b26abc9ac1603 Avoid whole disk FAT being detected as MSDOS partition table (#743181) (with libparted 1.9.0 to 2.3 inclusive) 2) 9e5e9f5627e0fb1b547f07cdaaac773c7b6035b9 Enhance file system detection to use FS_Info method - blkid (Detect file systems with sector sizes other than 512 bytes with libparted 2.2) Other changes to the DISTRIBUTION NOTES section of the README file: * Drop NOTE about vol_id and blkid being used to read volume labels for specific file systems and read the UUIDs. Vol_id was deprecated in May 2009 and is not included in any currently supported distribution. Blkid is now mandatory. List of optional commands at the end of the section seems to cover everything that is necessary. * Indent description of optional commands at the end of the section to match the indentation earlier in the section. * Line wrap the section at column 72 to match the rest of the file. Bug 753436 - Update documentation of GParted software dependencies
2015-08-10 04:30:46 -06:00
xdg-su - alternatively used to acquire root privileges in
gparted shell script wrapper, last choice if
available when gparted source is configured
Document blkid command as a mandatory requirement (#753436) Update the README file to document the blkid command as a mandatory requirement for GParted. GParted will run without blkid but it is needed to detect a number of file systems which libparted doesn't and in a number of other situations. Blkid is needed to detect these file systems: exfat f2fs ReFS SWRaid ZFS Blkid also detects these file systems (for which GParted has simple internal detection but libparted, mostly, doesn't detect): btrfs (detected by libparted >= 3.2) LVM2 PV LUKS nilfs2 (detected by libparted >= 2.4) reiser4 Blkid is also needed for these commits: 1) f8faee637787329c07771e495c9b26abc9ac1603 Avoid whole disk FAT being detected as MSDOS partition table (#743181) (with libparted 1.9.0 to 2.3 inclusive) 2) 9e5e9f5627e0fb1b547f07cdaaac773c7b6035b9 Enhance file system detection to use FS_Info method - blkid (Detect file systems with sector sizes other than 512 bytes with libparted 2.2) Other changes to the DISTRIBUTION NOTES section of the README file: * Drop NOTE about vol_id and blkid being used to read volume labels for specific file systems and read the UUIDs. Vol_id was deprecated in May 2009 and is not included in any currently supported distribution. Blkid is now mandatory. List of optional commands at the end of the section seems to cover everything that is necessary. * Indent description of optional commands at the end of the section to match the indentation earlier in the section. * Line wrap the section at column 72 to match the rest of the file. Bug 753436 - Update documentation of GParted software dependencies
2015-08-10 04:30:46 -06:00
udevinfo - used in dmraid to query udev name
udevadm - used in dmraid to query udev name
yelp - used to display help manual
xhost - used to grant root access to the X11 server, only
when configured to do so
2009-12-06 13:58:27 -07:00