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

214 lines
9.7 KiB
C
Raw Normal View History

Cleanup file copyright entries Restore copyright entries by original author to those of his last known repository commit titled "released gparted-0.3.4 on LarryT's request." on Feb 25, 2007. Add my own copyright entries for files in which I changed source code. Files in which I only made spelling changes do not have my copyright entry added.
2009-11-05 11:08:32 -07:00
/* Copyright (C) 2004 Bart
Enable new fs resize library available with parted-3.1 (#668281) The parted-3.1 release brings back FAT16/FAT32 and HFS/HFS+ file system resize capabilities in a new libparted fs resize library. The following operations are again available when GParted is linked with parted-3.1: FAT16 - grow and shrink FAT32 - grow and shrink HFS - shrink HFS+ - shrink Note that there is a difference in how move actions are handled for FAT16/FAT32 file systems based on parted version. When GParted is linked with parted >= 3.0: FAT16 - move performed internally by GParted FAT32 - move performed internally by GParted When GParted is linked with parted < 3.0: FAT16 - move performed by libparted FAT32 - move performed by libparted Thanks goes to Jim Meyering for restoring these file system resizing capabilities in Parted 3.1 with a new libparted fs resize library. Closes Bug #668281 - minimal file-system resize API? (FAT and HFS* only)
2012-03-03 11:47:39 -07:00
* Copyright (C) 2008, 2009, 2010, 2011, 2012 Curtis Gedak
P) It still needs a lot of love, but the foundations are laid =) * Rewrote a large part of gparteds internal code. Filesystemssupport is now much more separated from the rest of gparted and adding support for other filesystems should be a piece of cake now (hope that's true :P) It still needs a lot of love, but the foundations are laid =)
2004-11-17 06:00:25 -07:00
*
* This program is free software; you can redistribute it and/or modify
* it under the terms of the GNU General Public License as published by
* the Free Software Foundation; either version 2 of the License, or
* (at your option) any later version.
*
* This program is distributed in the hope that it will be useful,
* but WITHOUT ANY WARRANTY; without even the implied warranty of
* MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
Replace obsolete FSF postal address in copyright notices (#721565) This is part of parent bug: Bug #721455 - Obsolete info in license text on multiple modules and GNOME Goal: https://wiki.gnome.org/Initiatives/GnomeGoals/Proposals * verify all source files to make sure they have a license and a copyright, and that both are up-to-date Bug #721565 - License text contains obsolete FSF postal address
2014-01-23 03:59:48 -07:00
* GNU General Public License for more details.
P) It still needs a lot of love, but the foundations are laid =) * Rewrote a large part of gparteds internal code. Filesystemssupport is now much more separated from the rest of gparted and adding support for other filesystems should be a piece of cake now (hope that's true :P) It still needs a lot of love, but the foundations are laid =)
2004-11-17 06:00:25 -07:00
*
* You should have received a copy of the GNU General Public License
Replace obsolete FSF postal address in copyright notices (#721565) This is part of parent bug: Bug #721455 - Obsolete info in license text on multiple modules and GNOME Goal: https://wiki.gnome.org/Initiatives/GnomeGoals/Proposals * verify all source files to make sure they have a license and a copyright, and that both are up-to-date Bug #721565 - License text contains obsolete FSF postal address
2014-01-23 03:59:48 -07:00
* along with this program; if not, see <http://www.gnu.org/licenses/>.
P) It still needs a lot of love, but the foundations are laid =) * Rewrote a large part of gparteds internal code. Filesystemssupport is now much more separated from the rest of gparted and adding support for other filesystems should be a piece of cake now (hope that's true :P) It still needs a lot of love, but the foundations are laid =)
2004-11-17 06:00:25 -07:00
*/
Make include guards unique (#539297) Include guards need to be unique within GParted code and all included library header files. http://en.wikipedia.org/wiki/Include_guard#Difficulties Use this model for all include guards: #ifndef GPARTED_FILE_NAME_H #define GPARTED_FILE_NAME_H ... #endif /* GPARTED_FILE_NAME_H */ Closes Bug #539297 - Make include guards unique
2013-05-27 05:20:16 -06:00
#ifndef GPARTED_GPARTED_CORE_H
#define GPARTED_GPARTED_CORE_H
P) It still needs a lot of love, but the foundations are laid =) * Rewrote a large part of gparteds internal code. Filesystemssupport is now much more separated from the rest of gparted and adding support for other filesystems should be a piece of cake now (hope that's true :P) It still needs a lot of love, but the foundations are laid =)
2004-11-17 06:00:25 -07:00
added ufs filesystemclass * include/Dialog_Filesystems.h, include/GParted_Core.h, include/Makefile.am, include/ufs.h, src/GParted_Core.cc, src/Makefile.am, src/ufs.cc: added ufs filesystemclass
2006-04-02 08:35:21 -06:00
#include "../include/FileSystem.h"
P) It still needs a lot of love, but the foundations are laid =) * Rewrote a large part of gparteds internal code. Filesystemssupport is now much more separated from the rest of gparted and adding support for other filesystems should be a piece of cake now (hope that's true :P) It still needs a lot of love, but the foundations are laid =)
2004-11-17 06:00:25 -07:00
#include "../include/Operation.h"
p * added detailed progressfeedback. It still needs some polishing, but is already far better then the old situation. And what's more, it's finally threadsafe :p
2006-01-19 12:15:15 -07:00
#include <parted/parted.h>
P) It still needs a lot of love, but the foundations are laid =) * Rewrote a large part of gparteds internal code. Filesystemssupport is now much more separated from the rest of gparted and adding support for other filesystems should be a piece of cake now (hope that's true :P) It still needs a lot of love, but the foundations are laid =)
2004-11-17 06:00:25 -07:00
#include <vector>
#include <fstream>
namespace GParted
{
class GParted_Core
{
public:
Display pop up dialog on libparted exceptions We used to just log libparted exceptions without handling them. This patch changes the exception handler to display a modal dialog box and return the chosen action to libparted.
2012-01-04 17:30:28 -07:00
static Glib::Thread *mainthread;
catch libparted exceptions and display them in the operationdetails if an * include/GParted_Core.h, src/GParted_Core.cc: catch libparted exceptions and display them in the operationdetails if an operation has failed. * src/Dialog_Progress.cc: small cosmetic change to the errordialog.
2006-02-25 09:30:43 -07:00
GParted_Core() ;
fixed another minor memleak (yeah i'm playing with valgrind ;) ) * include/GParted_Core.h, src/GParted_Core.cc: fixed another minor memleak (yeah i'm playing with valgrind ;) )
2006-03-28 12:01:20 -07:00
~GParted_Core() ;
restructured the core a bit, over time it had become very messy. * restructured the core a bit, over time it had become very messy.
2006-06-17 14:52:25 -06:00
Initialise file system objects only once The code used to unnecessarily destroy and re-create the file system objects on every scan for file system support tools. Instead only create the file system objects once and just call each object's get_filesystem_support() method on each rescan.
2014-03-23 17:09:07 -06:00
void init_filesystems() ;
catch libparted exceptions and display them in the operationdetails if an * include/GParted_Core.h, src/GParted_Core.cc: catch libparted exceptions and display them in the operationdetails if an operation has failed. * src/Dialog_Progress.cc: small cosmetic change to the errordialog.
2006-02-25 09:30:43 -07:00
void find_supported_filesystems() ;
added support for commandline arguments (#329414) * include/GParted_Core.h, include/Win_GParted.h, src/GParted_Core.cc, src/Win_GParted.cc, src/main.cc: added support for commandline arguments (#329414)
2006-02-02 06:50:37 -07:00
void set_user_devices( const std::vector<Glib::ustring> & user_devices ) ;
some more cleanups, should be finished now :) * include/GParted_Core.h, src/GParted_Core.cc, src/Win_GParted.cc: some more cleanups, should be finished now :)
2006-06-18 02:50:17 -06:00
void set_devices( std::vector<Device> & devices ) ;
Reduce threading (#685740) Win_Gparted and Dialog_Progress were creating threads to perform most functions in the background. Most of the time, the only reason the threads blocked was to execute an external command. The external command execution has been changed to spawn the command asynchronously and wait for completion with a nested main loop. While waiting for completion, the pipe output is captured via events. In the future, this will allow for it to be parsed in real time to obtain progress information. Those tasks in GParted_Core that still block now spawn a background thread and wait for it to complete with a nested main loop to avoid hanging the gui. Part of Bug #685740 - Refactor to use asynchronous command execution
2013-02-21 17:57:33 -07:00
void set_devices_thread( std::vector<Device> * pdevices );
Added support to lost data recovery using gpart
2011-01-28 11:09:21 -07:00
void guess_partition_table(const Device & device, Glib::ustring &buff);
Removed bool Get_Any_Busy() in favor of public bool busy which is set in * include/Device.h, src/Device.cc: Removed bool Get_Any_Busy() in favor of public bool busy which is set in gparted_core. This also fixed a small bug with incorrect mountdetection of logical partitions. Also added a Reset() function to properly reset the contents of a device. to zero/empty . * include/GParted_Core.h, src/GParted_Core.cc: 'busyness' of a device is now determined in get_devices(). Renamed get_partitions() to set_device_partitions to reflect its proper function. When a new partition is created to contain a copied filesystem the size is now properly set. This fixes a very annoying bug which no one knew about except for me =) . * src/Win_GParted.cc: use boolean busy from device instead of Get_Any_Busy() .
2004-11-19 04:55:38 -07:00
perform some checks before adding a new operation to the list. made * include/GParted_Core.h, src/GParted_Core.cc, src/Win_GParted.cc: perform some checks before adding a new operation to the list. * src/Partition.cc: made get_length() a bit safer
2006-07-20 13:14:44 -06:00
bool snap_to_cylinder( const Device & device, Partition & partition, Glib::ustring & error ) ;
Add partition alignment option to align to MiB (#617409) Make align to MiB the default setting instead of align to cylinder. Migrate logic for alignment to cylinder into its own method snap_to_cylinder, and place common logic in snap_to_alignment. Add alignment checks for situations where space is needed for Master Boot Record or Extended Boot Record. Adjust ranges on spin buttons according to required boot record space. Copy fix for off by one sector (#596552) from Dialog_Partition_New::Get_New_Partition to Dialog_Base_Partition::Get_New_Partition Enhance resize / move logic for checking locations of nearby logical partitions to not depend on the partition ordering. Note: This commit does not include limiting graphic movement according to required boot record space.
2010-05-20 10:00:14 -06:00
bool snap_to_mebibyte( const Device & device, Partition & partition, Glib::ustring & error ) ;
bool snap_to_alignment( const Device & device, Partition & partition, Glib::ustring & error ) ;
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
bool apply_operation_to_disk( Operation * operation );
Erase file system signatures before creating a partition table (#743181) When writing "loop" partition table over the top of some whole disk device file system types GParted continued to show those whole disk device file systems rather than the virtual unknown partition from the "loop" partition table. This affected btrfs, jfs, reiser4 and reiserfs. It occurred because of several factors: 1) Libparted only zeroed the first and last 9.5 KiB (assuming 512 byte sectors) of the device before writing a new partition table. See ped_disk_clobber(). 2) These file systems have their super blocks and therefore signatures after the first 9.5 KiB. 3) Whole disk device file system detection is performed using blkid before checking for a libparted "loop" partition table. See GParted_Core::set_devices_thread(). Ref: libparted 3.2: disk.c:ped_disk_clobber() http://git.savannah.gnu.org/cgit/parted.git/tree/libparted/disk.c?id=v3.2#n302 Fix by always erasing any possible file system signatures on the device before creating a new "loop" partition table. NOTE: This is typically taking up to 0.5 seconds in my testing on a 5400 RPM hard drive, during which time the GParted UI is hung and the create partition table dialog shows the apply button pressed but no other progress indication. Bug 743181 - Add unpartitioned drive read-write support
2015-02-14 13:49:45 -07:00
bool set_disklabel( const Device & device, const Glib::ustring & disklabel );
Fix failure to recognise whole disk file systems in certain cases (#743181) When the following conditions were met GParted would fail to recognise a newly created whole disk device file system, and instead show an unknown file system filling the disk: 1) Disk was previously partitioned and contained at least one partition. 2) Using libparted version 2.0 to 3.0 inclusive. Initial status: # blkid | fgrep sdc # fgrep sdc /proc/partitions 8 32 976762584 sdc 8 33 104857600 sdc1 # parted /dev/sdc GNU Parted 2.4 Using /dev/sdc Welcome to GNU Parted! Type 'help' to view a list of commands. (parted) print Model: ATA ST1000LM024 HN-M (scsi) Disk /dev/sdc: 1000GB Sector size (logical/physical): 512B/4096B Partition Table: msdos Number Start End Size Type File system Flags 1 1049kB 107GB 107GB primary When creating the loop partition table libparted would not inform the kernel to delete the old partitions. /proc/partitions still contained the details of the old partitions. (parted) mktable loop Warning: The existing disk label on /dev/sdc will be destroyed and all data on this disk will be lost. Do you want to continue? Yes/No? Yes (parted) print Model: ATA ST1000LM024 HN-M (scsi) Disk /dev/sdc: 1000GB Sector size (logical/physical): 512B/4096B Partition Table: loop Number Start End Size File system Flags (parted) quit # fgrep sdc /proc/partitions 8 32 976762584 sdc 8 33 104857600 sdc1 Creation of the whole disk device file system goes unnoticed by blkid because the kernel and therefore blkid's cache have stale partition information. # mkfs.xfs -f /dev/sdc # blkid | fgrep sdc NOTE: On a Linux Software RAID array, as opposed to a hard disk, blkid does notice creation of the whole disk device file system. However the kernel still has old partition details. This was fixed in libparted 3.1 by commit: http://git.savannah.gnu.org/cgit/parted.git/commit/?id=f5c909c0cd50ed52a48dae6d35907dc08b137e88 libparted: remove has_partitions check to allow loopback partitions Fix by deleting old partitions before creating the loop table when compiled with a broken version of libparted. The GParted UI provides no feedback while a new partition table is created, and with some versions of GTK the UI become unresponsive too, so it is important to be as fast as possible. Evaluated three different methods, deleting 15 and 22 MSDOS partitions on a physical 5400 RPM hard drive using libparted 2.4: M1) Delete and commit one partition at a time. Takes up to 24 seconds to delete 15 partitions. With 22 partitions libparted always reports finding some of the partitions busy and unable to inform the kernel about the modifications. Too slow and doesn't work. M2) Delete all partitions in one go and commit once. Takes up to 1.4 seconds to delete either 15 or 22 partitions. Never removes partitions 17 and higher from the kernel. Doesn't work. M3) Write GPT table (letting libparted delete any old partitions). Takes up to 0.8 seconds to delete either 15 or 22 partitions. Fast and works. Use method 3 - write a GPT table thus using libparted code to inform the kernel of the old partition deletions. Bug 743181 - Add unpartitioned drive read-write support
2015-02-21 09:43:42 -07:00
bool new_disklabel( const Glib::ustring & device_path, const Glib::ustring & disklabel,
bool recreate_dmraid_devs = true );
restructured the core a bit, over time it had become very messy. * restructured the core a bit, over time it had become very messy.
2006-06-17 14:52:25 -06:00
bool toggle_flag( const Partition & partition, const Glib::ustring & flag, bool state ) ;
added movesupport, atm in experimental state and needs lots of cleaning. * include/GParted_Core.h, src/GParted_Core.cc, src/ext2.cc: added movesupport, atm in experimental state and needs lots of cleaning. only enabled for ext2, but should work for all filesystems. * src/DialogFeatures.cc: added alternating rowcolours (see #342682)
2006-05-31 14:03:49 -06:00
const std::vector<FS> & get_filesystems() const ;
const FS & get_fs( GParted::FILESYSTEM filesystem ) const ;
Display partition table types in order (#711098) In the Create Partition Table dialog display the entries in the combobox in order. Previously the default of MSDOS or GPT was moved to the first item in the combobox. Now the partition table types remain in order with just either MSDOS or GPT being selected as as the default as required. The partition table types are displayed in the order supplied by libparted, which is alphabetic except with "loop" last. Bug #711098 - Default partition table can not handle > 2 TiB disks
2014-01-03 13:56:57 -07:00
static std::vector<Glib::ustring> get_disklabeltypes() ;
Add is_dev_mounted() to expose core partition is mounted test (#723842) Add static member function GParted_Core::is_dev_mounted() so that other modules can determine if a particular partition contains a mounted file system or not. Make it a static member function so that it can be called without needing the gparted_core object. Extend to make the group of manipulated variables (mount_info, fstab_info) and manipulating functions (init_maps(), read_mountpoints_from_file(), read_mountpoints_from_file_swaps(), get_all_mountpoints()) static too. Bug #723842 - GParted resizes the wrong filesystem (does not pass the devid to btrfs filesystem resize)
2014-02-16 06:29:33 -07:00
static bool is_dev_mounted( const Glib::ustring & path ) ;
static std::vector<Glib::ustring> get_all_mountpoints() ;
added movesupport, atm in experimental state and needs lots of cleaning. * include/GParted_Core.h, src/GParted_Core.cc, src/ext2.cc: added movesupport, atm in experimental state and needs lots of cleaning. only enabled for ext2, but should work for all filesystems. * src/DialogFeatures.cc: added alternating rowcolours (see #342682)
2006-05-31 14:03:49 -06:00
std::map<Glib::ustring, bool> get_available_flags( const Partition & partition ) ;
added libparted version string to details export. * include/Dialog_Progress.h, include/GParted_Core.h, src/Dialog_Progress.cc, src/GParted_Core.cc, src/Win_GParted.cc: added libparted version string to details export.
2006-12-01 06:01:46 -07:00
Glib::ustring get_libparted_version() ;
Added set and get thread status message methods. Added thread status message updates in set_devices(). svn path=/trunk/; revision=943
2008-10-30 12:50:38 -06:00
Glib::ustring get_thread_status_message() ;
Add supported_filesystem() predicate method (#738471) Helper to check whether a recognised file system type is supported by GParted or not. Supported means there is an implementation class and will appear in the File System Support dialog. Make supported_filesystem() a static member function so that it can be called without a class object so that GParted_Core::GParted_Core() initialiser isn't called multiple times. This requires FILESYSTEM_MAP to become a static member variable too. Bug #738471 - ReFS file system is not recognised
2014-10-13 06:03:47 -06:00
static FileSystem * get_filesystem_object( FILESYSTEM filesystem );
static bool supported_filesystem( FILESYSTEM fstype );
Disallow resizing of LVM2 PVs which are members of exported VGs (#670171) When an inactive LVM2 Volume Group is exported it makes it unknown to the local system, ready for moving the member Physical Volumes to another system, where the VG can be imported and used. In this state a PV can't be resized. # lvm pvresize /dev/sda10 Volume group Test-VG1 is exported Unable to read volume group "Test-VG1". 0 physical volume(s) resized / 1 physical volume(s) not resized # echo $? 5 Fix this by preventing resizing of such a PV. This has been coded in a generic way using new function filesystem_resize_disallowed() to determine whether a file system is allowed to be resized or not. For a file system which can be resized, but is currently not allowed to be resized, the behaviour is as follows: 1) Pasting into unallocated space is limited to creating a new partition which is the same size as the copied partition. 2) Resizing the partition is disallowed, only moving the partition is allowed. 3) Pasting into an existing partition will only copy the file system. If the destination partition is larger a warning will report that growing the file system is not currently allowed. 4) Checking a partition will also report a warning that growing the file system is not currently allowed. This is exactly the same behaviour as for a file system which does not implement resizing, except for a different warning message. Bug #670171 - Add LVM PV read-write support
2012-08-25 13:49:10 -06:00
static bool filesystem_resize_disallowed( const Partition & partition ) ;
added movesupport, atm in experimental state and needs lots of cleaning. * include/GParted_Core.h, src/GParted_Core.cc, src/ext2.cc: added movesupport, atm in experimental state and needs lots of cleaning. only enabled for ext2, but should work for all filesystems. * src/DialogFeatures.cc: added alternating rowcolours (see #342682)
2006-05-31 14:03:49 -06:00
private:
restructured the core a bit, over time it had become very messy. * restructured the core a bit, over time it had become very messy.
2006-06-17 14:52:25 -06:00
//detectionstuff..
Add is_dev_mounted() to expose core partition is mounted test (#723842) Add static member function GParted_Core::is_dev_mounted() so that other modules can determine if a particular partition contains a mounted file system or not. Make it a static member function so that it can be called without needing the gparted_core object. Extend to make the group of manipulated variables (mount_info, fstab_info) and manipulating functions (init_maps(), read_mountpoints_from_file(), read_mountpoints_from_file_swaps(), get_all_mountpoints()) static too. Bug #723842 - GParted resizes the wrong filesystem (does not pass the devid to btrfs filesystem resize)
2014-02-16 06:29:33 -07:00
static void init_maps() ;
Added set and get thread status message methods. Added thread status message updates in set_devices(). svn path=/trunk/; revision=943
2008-10-30 12:50:38 -06:00
void set_thread_status_message( Glib::ustring msg ) ;
Add is_dev_mounted() to expose core partition is mounted test (#723842) Add static member function GParted_Core::is_dev_mounted() so that other modules can determine if a particular partition contains a mounted file system or not. Make it a static member function so that it can be called without needing the gparted_core object. Extend to make the group of manipulated variables (mount_info, fstab_info) and manipulating functions (init_maps(), read_mountpoints_from_file(), read_mountpoints_from_file_swaps(), get_all_mountpoints()) static too. Bug #723842 - GParted resizes the wrong filesystem (does not pass the devid to btrfs filesystem resize)
2014-02-16 06:29:33 -07:00
static void read_mountpoints_from_file( const Glib::ustring & filename,
Fallback to reading mount command output instead of /etc/mtab (#723842) With linux 3.5 and later, the device used to mount a btrfs file system is updated in /proc/mounts when the previous mounting device is removed from the file system. Most recent distributions make /etc/mtab a symbolic link to /proc/mounts. However some still have /etc/mtab as a plain file only updated by mount and umount, thus showing the old device name which is no longer part of the file system. On Ubuntu 13.10, which has /etc/mtab as a plain file managed by mount and umount: # mkfs.btrfs /dev/sdb1 # mount /dev/sdb1 /mnt/1 # btrfs device add /dev/sdb2 /mnt/1 # btrfs device delete /dev/sdb1 /mnt/1 # sync # btrfs filesystem show /dev/sdb1 # btrfs filesystem show /dev/sdb2 Label: none uuid: e47775a6-e5ad-4fb4-9ea4-1570aa5b4009 Total devices 2 FS bytes used 28.00KB devid 2 size 2.00GB used 272.00MB path /dev/sdb2 # fgrep btrfs /proc/mounts /dev/sdb2 /mnt/1 btrfs rw,relatime,space_cache 0 0 # ls -l /etc/mtab -rw-r--r-- 1 root root 842 Apr 15 19:41 /etc/mtab # fgrep btrfs /etc/mtab /dev/sdb1 /mnt/1 btrfs rw 0 0 This causes GParted to report /dev/sdb1 as busy and mounted at /mnt/1 when it is no longer mounted. This effects recent releases of Ubuntu, 13.04, 13.10 and 14.04. Either /etc/mtab is a symlink and is identical to /proc/mounts or /etc/mtab is a plain file with wrong information. Fix by not reading mounted file systems from /etc/mtab. However old distributions only contain 'rootfs' and '/dev/root' device names for the / (root) file system with '/dev/root' being a block device rather than a symlink to the true device. For example from CentOS 5.x: # fgrep ' / ' /proc/mounts rootfs / rootfs rw 0 0 /dev/root / ext3 rw,data=ordered 0 0 # ls -l /dev/root brw------- 1 root root 8, 3 Jun 4 2013 /dev/root This prevents identification, and therefore busy detection, of the device containing the / (root) file system. Used to read /etc/mtab to get the root file system device name. # fgrep ' / ' /etc/mtab /dev/sda3 / ext3 rw 0 0 # ls -l /dev/sda3 brw-r----- 1 root disk 8, 3 Jun 4 2013 /dev/sda3 As per commit: 409096f739118af95e3bff4484fdedb7885c97a2 improved scanning for root mountpoint (/) ... but, as discussed above, this contains an out of date device name after the mounting device has been dynamically removed from a multi-device btrfs, thus identifying the wrong device as busy. Instead fall back to reading mounted file systems from the output of the mount command, but only when required. # mount | fgrep ' / ' /dev/sda3 on / type ext3 (rw) Bug #723842 - GParted resizes the wrong filesystem (does not pass the devid to btrfs filesystem resize)
2014-04-14 08:21:55 -06:00
std::map< Glib::ustring, std::vector<Glib::ustring> > & map ) ;
static void add_node_and_mountpoint( std::map< Glib::ustring, std::vector<Glib::ustring> > & map,
Glib::ustring & node,
Glib::ustring & mountpoint ) ;
Add is_dev_mounted() to expose core partition is mounted test (#723842) Add static member function GParted_Core::is_dev_mounted() so that other modules can determine if a particular partition contains a mounted file system or not. Make it a static member function so that it can be called without needing the gparted_core object. Extend to make the group of manipulated variables (mount_info, fstab_info) and manipulating functions (init_maps(), read_mountpoints_from_file(), read_mountpoints_from_file_swaps(), get_all_mountpoints()) static too. Bug #723842 - GParted resizes the wrong filesystem (does not pass the devid to btrfs filesystem resize)
2014-02-16 06:29:33 -07:00
static void read_mountpoints_from_file_swaps( const Glib::ustring & filename,
Fallback to reading mount command output instead of /etc/mtab (#723842) With linux 3.5 and later, the device used to mount a btrfs file system is updated in /proc/mounts when the previous mounting device is removed from the file system. Most recent distributions make /etc/mtab a symbolic link to /proc/mounts. However some still have /etc/mtab as a plain file only updated by mount and umount, thus showing the old device name which is no longer part of the file system. On Ubuntu 13.10, which has /etc/mtab as a plain file managed by mount and umount: # mkfs.btrfs /dev/sdb1 # mount /dev/sdb1 /mnt/1 # btrfs device add /dev/sdb2 /mnt/1 # btrfs device delete /dev/sdb1 /mnt/1 # sync # btrfs filesystem show /dev/sdb1 # btrfs filesystem show /dev/sdb2 Label: none uuid: e47775a6-e5ad-4fb4-9ea4-1570aa5b4009 Total devices 2 FS bytes used 28.00KB devid 2 size 2.00GB used 272.00MB path /dev/sdb2 # fgrep btrfs /proc/mounts /dev/sdb2 /mnt/1 btrfs rw,relatime,space_cache 0 0 # ls -l /etc/mtab -rw-r--r-- 1 root root 842 Apr 15 19:41 /etc/mtab # fgrep btrfs /etc/mtab /dev/sdb1 /mnt/1 btrfs rw 0 0 This causes GParted to report /dev/sdb1 as busy and mounted at /mnt/1 when it is no longer mounted. This effects recent releases of Ubuntu, 13.04, 13.10 and 14.04. Either /etc/mtab is a symlink and is identical to /proc/mounts or /etc/mtab is a plain file with wrong information. Fix by not reading mounted file systems from /etc/mtab. However old distributions only contain 'rootfs' and '/dev/root' device names for the / (root) file system with '/dev/root' being a block device rather than a symlink to the true device. For example from CentOS 5.x: # fgrep ' / ' /proc/mounts rootfs / rootfs rw 0 0 /dev/root / ext3 rw,data=ordered 0 0 # ls -l /dev/root brw------- 1 root root 8, 3 Jun 4 2013 /dev/root This prevents identification, and therefore busy detection, of the device containing the / (root) file system. Used to read /etc/mtab to get the root file system device name. # fgrep ' / ' /etc/mtab /dev/sda3 / ext3 rw 0 0 # ls -l /dev/sda3 brw-r----- 1 root disk 8, 3 Jun 4 2013 /dev/sda3 As per commit: 409096f739118af95e3bff4484fdedb7885c97a2 improved scanning for root mountpoint (/) ... but, as discussed above, this contains an out of date device name after the mounting device has been dynamically removed from a multi-device btrfs, thus identifying the wrong device as busy. Instead fall back to reading mounted file systems from the output of the mount command, but only when required. # mount | fgrep ' / ' /dev/sda3 on / type ext3 (rw) Bug #723842 - GParted resizes the wrong filesystem (does not pass the devid to btrfs filesystem resize)
2014-04-14 08:21:55 -06:00
std::map< Glib::ustring, std::vector<Glib::ustring> > & map ) ;
static bool have_rootfs_dev( std::map< Glib::ustring, std::vector<Glib::ustring> > & map ) ;
static void read_mountpoints_from_mount_command( std::map< Glib::ustring, std::vector<Glib::ustring> > & map ) ;
Create new method get_partition_path This method will be used as an entry point to the libparted function ped_partition_get_path
2010-08-15 14:14:04 -06:00
Glib::ustring get_partition_path( PedPartition * lp_partition ) ;
Remove lp_device and lp_disk from GParted_Core (#683149) They were used like global variables. Now they are moved to the functions that actually use them to make clearer how the data flow is. Bug #683149 - Cleanup(?): Remove lp_device and lp_disk from GParted_Core
2012-10-30 03:30:49 -06:00
void set_device_partitions( Device & device, PedDevice* lp_device, PedDisk* lp_disk ) ;
Display whole disk file systems via partition table "none" (#741430) For file systems which libparted recognises, when found on the whole disk device, it reports with partition table "loop" and a partition covering the whole disk. GParted duly displays this to the user. For file systems which libparted doesn't recognise it reports "unrecognised disk label". As of the latest libparted 3.2, these file system aren't recognised and can't currently be shown when on the whole disk device: BitLocker, Crypt LUKS, exFAT, F2FS, LVM2 Physical Volume, Linux Software RAID, ReFS, Reiser 4 So only when libparted doesn't recognise a file system on the whole disk device and GParted does, either via blkid or it's internal code, display this with partition table "none". Bug 741430 - GParted cannot recognise LVM signature on unpartitioned drive
2014-12-27 07:10:54 -07:00
void set_device_one_partition( Device & device, PedDevice * lp_device, FILESYSTEM fstype,
std::vector<Glib::ustring> & messages );
Create helper function set_partition_label_and_uuid() (#741430) Move code which queries the file system label and UUID of a partition into a separate helper function. Bug 741430 - GParted cannot recognise LVM signature on unpartitioned drive
2014-12-27 06:46:38 -07:00
void set_partition_label_and_uuid( Partition & partition );
Refactor GParted internal file system signature detection (#741430) Refactor GParted internal file system signature detection to remove code duplication. There were 5 separate copies of code to: allocate a buffer, open, read and close the device, free the buffer and compare the signature. Bug 741430 - GParted cannot recognise LVM signature on unpartitioned drive
2014-12-23 11:22:04 -07:00
static FILESYSTEM recognise_filesystem_signature( PedDevice * lp_device, PedPartition * lp_partition );
Remove GParted_Core::partition_temp (#683149) Bug #683149 - Cleanup(?): Remove lp_device and lp_disk from GParted_Core
2012-09-01 04:58:41 -06:00
GParted::FILESYSTEM get_filesystem( PedDevice* lp_device, PedPartition* lp_partition,
std::vector<Glib::ustring>& messages ) ;
Renamed set_label and get_label methods to write_label and read_label respectively. svn path=/trunk/; revision=957
2008-11-08 16:55:17 -07:00
void read_label( Partition & partition ) ;
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
void read_uuid( Partition & partition ) ;
store flags in a list instead of a string. cleanups * include/GParted_Core.h, include/Partition.h, src/Dialog_Partition_Info.cc, src/GParted_Core.cc, src/Partition.cc, src/TreeView_Detail.cc: store flags in a list instead of a string. * Makefile.am, src/Makefile.am: cleanups
2006-02-17 16:20:28 -07:00
void insert_unallocated( const Glib::ustring & device_path,
std::vector<Partition> & partitions,
Sector start,
Sector end,
Set sector size and add to operation and dialog methods This change is in preparation for supporting sectors sizes > 512 bytes.
2010-04-19 19:22:31 -06:00
Byte_Value sector_size,
store flags in a list instead of a string. cleanups * include/GParted_Core.h, include/Partition.h, src/Dialog_Partition_Info.cc, src/GParted_Core.cc, src/Partition.cc, src/TreeView_Detail.cc: store flags in a list instead of a string. * Makefile.am, src/Makefile.am: cleanups
2006-02-17 16:20:28 -07:00
bool inside_extended ) ;
some more cleanups, should be finished now :) * include/GParted_Core.h, src/GParted_Core.cc, src/Win_GParted.cc: some more cleanups, should be finished now :)
2006-06-18 02:50:17 -06:00
void set_mountpoints( std::vector<Partition> & partitions ) ;
Display mount points for multi-device btrfs file systems (#723842) Linux can only show a single device name in /proc/mounts and /etc/mtab for each mounted btrfs, even if it is a multi-device file system. So GParted only shows a mount point for one of the devices in the btrfs, no matter how many devices are part of the file system. # mkfs.btrfs /dev/sdb1 /dev/sdb2 # btrfs filesystem show /dev/sdb1 Label: none uuid: 36eb51a2-2927-4c92-820f-b2f0b5cdae50 Total devices 2 FS bytes used 156.00KB devid 2 size 2.00GB used 512.00MB path /dev/sdb2 devid 1 size 2.00GB used 240.75MB path /dev/sdb1 # mount /dev/sdb1 /mnt/1 # grep btrfs /proc/mounts /dev/sdb1 /mnt/1 btrfs rw,seclabel,relatime,ssd,space_cache 0 0 GParted only shows the mount point for /dev/sdb1 as /mnt/1, but nothing for /dev/sdb2. Make GParted report the same mount point for all devices included in a multi-device btrfs file system. Add btrfs specific get_mount_device() method to report the mounting device, if any, for the btrfs file system in the occupying the device in question. Uses the existing cache of btrfs file system device membership. Also extract common code from GParted_Core:: set_mountpoints() into set_mountpoints_helper(). Bug #723842 - GParted resizes the wrong filesystem (does not pass the devid to btrfs filesystem resize)
2014-03-25 17:03:30 -06:00
bool set_mountpoints_helper( Partition & partitions, const Glib::ustring & path ) ;
Make partition busy detection method selectable per file system (#723842) GParted's primary inbuilt busy detection method is "is the partition mounted?". A custom method is used for LVM2 PV because its not a mounted file system. Make busy detection selectable per file system type. .fs.busy = FS::NONE (default) No busy detection. .fs.busy = FS::GPARTED Use internal GParted method which checks if the partition is mounted. .fs.busy = FS:EXTERNAL Call the file system type's member function is_busy(). LVM2 PV busy detection changes from a special case to just electing to call the lvm2_pv::is_busy() method. Linux Software RAID remains a special case because it's only recognised, but not otherwise supported. Bug #723842 - GParted resizes the wrong filesystem (does not pass the devid to btrfs filesystem resize)
2014-02-14 18:26:32 -07:00
bool is_busy( FILESYSTEM fstype, const Glib::ustring & path ) ;
Remove lp_device and lp_disk from GParted_Core (#683149) They were used like global variables. Now they are moved to the functions that actually use them to make clearer how the data flow is. Bug #683149 - Cleanup(?): Remove lp_device and lp_disk from GParted_Core
2012-10-30 03:30:49 -06:00
void set_used_sectors( std::vector<Partition> & partitions, PedDisk* lp_disk ) ;
Make mounted partition usage method selectable per file system (#683255) Each file system class can now choose how the size and free space of the file system is determined when it is mounted. .fs.online_read = FS::NONE (default) Do nothing. Don't get the file system size and free space. .fs.online_read = FS::GPARTED Use internal GParted method which calls statvfs() system call on the mounted file system. .fs.online_read = FS::EXTERNAL Call the file system's member function set_used_sectors(). This is the same function as called when the file system is not mounted. It can determine if the file system is mounted or not by testing partition.busy and acting accordingly. This means that determining the size and free space of active LVM2 Physical Volumes is no longer a special case. Instead the lvm2_pv class just elects to have its set_used_sectors() method called for both the active and deactive cases. Bug #683255 - ext2: statvfs differs from dumpe2fs (x MB unallocated space within the partition)
2012-09-10 09:41:58 -06:00
void mounted_set_used_sectors( Partition & partition ) ;
Enable new fs resize library available with parted-3.1 (#668281) The parted-3.1 release brings back FAT16/FAT32 and HFS/HFS+ file system resize capabilities in a new libparted fs resize library. The following operations are again available when GParted is linked with parted-3.1: FAT16 - grow and shrink FAT32 - grow and shrink HFS - shrink HFS+ - shrink Note that there is a difference in how move actions are handled for FAT16/FAT32 file systems based on parted version. When GParted is linked with parted >= 3.0: FAT16 - move performed internally by GParted FAT32 - move performed internally by GParted When GParted is linked with parted < 3.0: FAT16 - move performed by libparted FAT32 - move performed by libparted Thanks goes to Jim Meyering for restoring these file system resizing capabilities in Parted 3.1 with a new libparted fs resize library. Closes Bug #668281 - minimal file-system resize API? (FAT and HFS* only)
2012-03-03 11:47:39 -07:00
#ifdef HAVE_LIBPARTED_FS_RESIZE
Remove lp_device and lp_disk from GParted_Core (#683149) They were used like global variables. Now they are moved to the functions that actually use them to make clearer how the data flow is. Bug #683149 - Cleanup(?): Remove lp_device and lp_disk from GParted_Core
2012-10-30 03:30:49 -06:00
void LP_set_used_sectors( Partition & partition, PedDisk* lp_disk ) ;
Enable compile and link with libparted 3.0 (#651559) The release of (lib)parted 3.0 includes a change to the Application Programing Interface - API. Most importantly, libparted 3.0 removes many file system specific function calls, and hence the capabilities provided by these functions. In order for GParted to compile and link with libparted 3.0, this libparted functionality is lost. Specifically, the functionality that is lost when GParted is compiled and linked with libparted 3.0 is as follows: - Loss of ability to grow and shrink FAT16 and FAT32 file systems - Loss of ability to shrink HFS and HFS+ file systems - Loss of ability to determine used and unused sectors in HFS and HFS+ file systems - Loss of ability to erase file system signatures on partition create and format It is hoped that other free software projects will include some or all of the above lost functionality, which can then be added back to GParted. This commit includes a change in how FAT16 and FAT32 file systems are moved. Specifically the move is now performed internally by GParted when linked with libparted 3.0. The move functionality is provided by libparted for prior libparted versions (e.g. less than 3.0). This is the final enhancement in a series of commits that enable GParted to compile with libparted version 3.0. Closes Bug #651559 - Doesn't compile against parted 3.0
2011-06-09 09:59:41 -06:00
#endif
Remove lp_partition from GParted_Core (#683149) Bug #683149 - Cleanup(?): Remove lp_device and lp_disk from GParted_Core
2012-10-30 03:43:46 -06:00
void set_flags( Partition & partition, PedPartition* lp_partition ) ;
Added set and get thread status message methods. Added thread status message updates in set_devices(). svn path=/trunk/; revision=943
2008-10-30 12:50:38 -06:00
restructured the core a bit, over time it had become very messy. * restructured the core a bit, over time it had become very messy.
2006-06-17 14:52:25 -06:00
//operationstuff...
Remove unused device parameter from a few GParted_Core methods resize_move() and move() stopped using the device parameter in this commit from 2006-07-23: d663c3c277f60da2ac1785c039f25f7920a315e9 removed cylindersize buffering during resize from the filesystems. It is create() stopped using the device parameter in this commit from 2006-03-19: ad9f2126e7fc92c16fffe839847dfe1c520146c8 fixed issues with copying (see also #335004) cleanups + added FIXME added For reference most other operation methods had the device parameter removed in this earlier commit from 2005-12-07: 642f0a145bc4b45a774dbf39e9cad4eb66afe56a from now on each partition has a reference to it's device. make use of new
2015-01-18 08:46:10 -07:00
bool create( Partition & new_partition, OperationDetail & operationdetail );
changed progressfeedbackhandling a bit. Because this affected * changed progressfeedbackhandling a bit. Because this affected OperationDetail i had to make changes in almost every file.
2006-08-20 03:33:54 -06:00
bool create_partition( Partition & new_partition, OperationDetail & operationdetail, Sector min_size = 0 ) ;
bool create_filesystem( const Partition & partition, OperationDetail & operationdetail ) ;
restructured the core a bit, over time it had become very messy. * restructured the core a bit, over time it had become very messy.
2006-06-17 14:52:25 -06:00
changed progressfeedbackhandling a bit. Because this affected * changed progressfeedbackhandling a bit. Because this affected OperationDetail i had to make changes in almost every file.
2006-08-20 03:33:54 -06:00
bool format( const Partition & partition, OperationDetail & operationdetail ) ;
restructured the core a bit, over time it had become very messy. * restructured the core a bit, over time it had become very messy.
2006-06-17 14:52:25 -06:00
changed progressfeedbackhandling a bit. Because this affected * changed progressfeedbackhandling a bit. Because this affected OperationDetail i had to make changes in almost every file.
2006-08-20 03:33:54 -06:00
bool Delete( const Partition & partition, OperationDetail & operationdetail ) ;
Add file system specific remove() methods (#670171) This commit only adds a remove() method to every file system and an optional call to it in the relevant operations. All remove() methods are no operations and not enabled. The remove() method provides explicit controlled removal of a file system before the partition is deleted or overwritten by being formatted or pasted into. When implemented, it appears as an extra step in the relevant operation. The file system specific remove() method is explicitly allowed to fail and stop the operations currently being applied. This is different to the existing erase_filesystem_signatures() which wipes any previous file system signatures immediately before a new file system is written to ensure there is no possibility of the partition containing two or more different file system signatures. It never fails or reports anything to the user. NOTE: Most file systems should NOT implement a remove() method as it will prevent recovery from accidental partition deletion. Bug #670171 - Add LVM PV read-write support
2012-07-25 14:05:33 -06:00
bool remove_filesystem( const Partition & partition, OperationDetail & operationdetail ) ;
Rename methods in GParted_Core and Win_GParted classes (#741424) class GParted_Core: label_partition() -> label_filesystem() class Win_GParted: allow_label_partition() -> allow_label_filesystem() activate_label_partition() -> activate_label_filesystem() Bug 741424 - Add support for GPT partition names
2014-12-18 15:18:33 -07:00
bool label_filesystem( const Partition & partition, OperationDetail & operationdetail );
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
bool name_partition( const Partition & partition, OperationDetail & operationdetail );
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
bool change_uuid( const Partition & partition, OperationDetail & operation_detail ) ;
Remove unused device parameter from a few GParted_Core methods resize_move() and move() stopped using the device parameter in this commit from 2006-07-23: d663c3c277f60da2ac1785c039f25f7920a315e9 removed cylindersize buffering during resize from the filesystems. It is create() stopped using the device parameter in this commit from 2006-03-19: ad9f2126e7fc92c16fffe839847dfe1c520146c8 fixed issues with copying (see also #335004) cleanups + added FIXME added For reference most other operation methods had the device parameter removed in this earlier commit from 2005-12-07: 642f0a145bc4b45a774dbf39e9cad4eb66afe56a from now on each partition has a reference to it's device. make use of new
2015-01-18 08:46:10 -07:00
bool resize_move( const Partition & partition_old,
Partition & partition_new,
OperationDetail & operationdetail );
bool move( const Partition & partition_old,
const Partition & partition_new,
OperationDetail & operationdetail );
did more work on moving * include/GParted_Core.h, src/GParted_Core.cc: did more work on moving
2006-06-18 13:27:52 -06:00
bool move_filesystem( const Partition & partition_old,
added FIXME: decoupled libparted partition and filesystemresizing. This * src/Win_GParted.cc: added FIXME: * include/GParted_Core.h, src/GParted_Core.cc, src/fat32.cc: decoupled libparted partition and filesystemresizing. This resulted in a much more consistent core. This also affected several other aspects of resizing/moving in a positive way.
2006-07-23 03:58:45 -06:00
const Partition & partition_new,
changed progressfeedbackhandling a bit. Because this affected * changed progressfeedbackhandling a bit. Because this affected OperationDetail i had to make changes in almost every file.
2006-08-20 03:33:54 -06:00
OperationDetail & operationdetail ) ;
Enable new fs resize library available with parted-3.1 (#668281) The parted-3.1 release brings back FAT16/FAT32 and HFS/HFS+ file system resize capabilities in a new libparted fs resize library. The following operations are again available when GParted is linked with parted-3.1: FAT16 - grow and shrink FAT32 - grow and shrink HFS - shrink HFS+ - shrink Note that there is a difference in how move actions are handled for FAT16/FAT32 file systems based on parted version. When GParted is linked with parted >= 3.0: FAT16 - move performed internally by GParted FAT32 - move performed internally by GParted When GParted is linked with parted < 3.0: FAT16 - move performed by libparted FAT32 - move performed by libparted Thanks goes to Jim Meyering for restoring these file system resizing capabilities in Parted 3.1 with a new libparted fs resize library. Closes Bug #668281 - minimal file-system resize API? (FAT and HFS* only)
2012-03-03 11:47:39 -07:00
#ifdef HAVE_LIBPARTED_FS_RESIZE
added FIXME: decoupled libparted partition and filesystemresizing. This * src/Win_GParted.cc: added FIXME: * include/GParted_Core.h, src/GParted_Core.cc, src/fat32.cc: decoupled libparted partition and filesystemresizing. This resulted in a much more consistent core. This also affected several other aspects of resizing/moving in a positive way.
2006-07-23 03:58:45 -06:00
bool resize_move_filesystem_using_libparted( const Partition & partition_old,
const Partition & partition_new,
changed progressfeedbackhandling a bit. Because this affected * changed progressfeedbackhandling a bit. Because this affected OperationDetail i had to make changes in almost every file.
2006-08-20 03:33:54 -06:00
OperationDetail & operationdetail ) ;
Enable compile and link with libparted 3.0 (#651559) The release of (lib)parted 3.0 includes a change to the Application Programing Interface - API. Most importantly, libparted 3.0 removes many file system specific function calls, and hence the capabilities provided by these functions. In order for GParted to compile and link with libparted 3.0, this libparted functionality is lost. Specifically, the functionality that is lost when GParted is compiled and linked with libparted 3.0 is as follows: - Loss of ability to grow and shrink FAT16 and FAT32 file systems - Loss of ability to shrink HFS and HFS+ file systems - Loss of ability to determine used and unused sectors in HFS and HFS+ file systems - Loss of ability to erase file system signatures on partition create and format It is hoped that other free software projects will include some or all of the above lost functionality, which can then be added back to GParted. This commit includes a change in how FAT16 and FAT32 file systems are moved. Specifically the move is now performed internally by GParted when linked with libparted 3.0. The move functionality is provided by libparted for prior libparted versions (e.g. less than 3.0). This is the final enhancement in a series of commits that enable GParted to compile with libparted version 3.0. Closes Bug #651559 - Doesn't compile against parted 3.0
2011-06-09 09:59:41 -06:00
#endif
removed cylindersize buffering during resize from the filesystems. It is * include/FileSystem.h, include/GParted_Core.h, src/FileSystem.cc, src/GParted_Core.cc, src/ext2.cc, src/ext3.cc, src/ntfs.cc, src/reiserfs.cc: removed cylindersize buffering during resize from the filesystems. It is not needed anymore now we calculate the new position before calling this. Also added some extra progressfeedback in the core
2006-07-23 12:43:15 -06:00
bool resize( const Partition & partition_old,
more work on moving/resizing sequence * include/GParted_Core.h, src/GParted_Core.cc: more work on moving/resizing sequence
2006-07-23 10:51:38 -06:00
const Partition & partition_new,
changed progressfeedbackhandling a bit. Because this affected * changed progressfeedbackhandling a bit. Because this affected OperationDetail i had to make changes in almost every file.
2006-08-20 03:33:54 -06:00
OperationDetail & operationdetail ) ;
renamed resize_partition to resize_move_partition to better reflect its * include/GParted_Core.h, src/GParted_Core.cc: renamed resize_partition to resize_move_partition to better reflect its functionality.
2006-06-18 13:38:29 -06:00
bool resize_move_partition( const Partition & partition_old,
added FIXME: decoupled libparted partition and filesystemresizing. This * src/Win_GParted.cc: added FIXME: * include/GParted_Core.h, src/GParted_Core.cc, src/fat32.cc: decoupled libparted partition and filesystemresizing. This resulted in a much more consistent core. This also affected several other aspects of resizing/moving in a positive way.
2006-07-23 03:58:45 -06:00
const Partition & partition_new,
changed progressfeedbackhandling a bit. Because this affected * changed progressfeedbackhandling a bit. Because this affected OperationDetail i had to make changes in almost every file.
2006-08-20 03:33:54 -06:00
OperationDetail & operationdetail ) ;
restructured the core a bit, over time it had become very messy. * restructured the core a bit, over time it had become very messy.
2006-06-17 14:52:25 -06:00
bool resize_filesystem( const Partition & partition_old,
const Partition & partition_new,
changed progressfeedbackhandling a bit. Because this affected * changed progressfeedbackhandling a bit. Because this affected OperationDetail i had to make changes in almost every file.
2006-08-20 03:33:54 -06:00
OperationDetail & operationdetail,
restructured the core a bit, over time it had become very messy. * restructured the core a bit, over time it had become very messy.
2006-06-17 14:52:25 -06:00
bool fill_partition = false ) ;
changed progressfeedbackhandling a bit. Because this affected * changed progressfeedbackhandling a bit. Because this affected OperationDetail i had to make changes in almost every file.
2006-08-20 03:33:54 -06:00
bool maximize_filesystem( const Partition & partition, OperationDetail & operationdetail ) ;
restructured the core a bit, over time it had become very messy. * restructured the core a bit, over time it had become very messy.
2006-06-17 14:52:25 -06:00
bool copy( const Partition & partition_src,
check if dest >= src before starting a copy * include/GParted_Core.h, src/GParted_Core.cc: check if dest >= src before starting a copy
2006-09-03 12:24:09 -06:00
Partition & partition_dst,
Enhance copy methods for sector sizes > 512 bytes
2010-04-07 11:33:21 -06:00
Byte_Value min_size,
changed progressfeedbackhandling a bit. Because this affected * changed progressfeedbackhandling a bit. Because this affected OperationDetail i had to make changes in almost every file.
2006-08-20 03:33:54 -06:00
OperationDetail & operationdetail ) ;
Use ped_device_read and ped_device_write instead of 'dd' to copy * Use ped_device_read and ped_device_write instead of 'dd' to copy filesystems. Modified progressdetails to provide more detailed feedback about a process. Basicly these were all changes to the infrastructure to make the incorporation of the 'move-code' a bit easier. ( sorry, not in the mood to list all affected files ;)
2006-05-23 15:17:34 -06:00
bool copy_filesystem( const Partition & partition_src,
make sure progressfraction stays between 0.0 and 1.0 implemented rollback * src/Dialog_Progress.cc: make sure progressfraction stays between 0.0 and 1.0 * include/GParted_Core.h, src/GParted_Core.cc: implemented rollback in case of failed move of overlapping filesystems. Together with the readonly test moving should be quite save now :)
2006-09-10 06:17:33 -06:00
const Partition & partition_dst,
added test_overlap() perform a readonly testrun before the actual move if * include/Partition.h, src/Partition.cc: added test_overlap() * include/GParted_Core.h, src/GParted_Core.cc: perform a readonly testrun before the actual move if destination overlaps source.
2006-09-07 14:31:05 -06:00
OperationDetail & operationdetail,
Add proper cancel support (#601239) Interested operations can now connect a signal to their OperationDetail to be notified of a cancelation request. The internal copy/move code will now cleanly stop on cancelation, allowing the partition to be rolled back to its previous state. This makes canceling a move perfectly safe. After clicking cancel, the button changes to "Force Cancel" and is disabled for 5 seconds. Operations that are safe to cancel will do so and those that are not will continue to run. Clicking force cancel asks operations to cancel, even if doing so is unsafe. For the internal copy/move algorithm, canceling is always safe because an error results in a rollback operation. Canceling the rollback is unsafe. For external commands, filesystem modules may indicate that the command is safe to cancel or not. Canceled commands will be terminated with SIGINT. As a result of the new safe cancel vs force cancel distinction, the scary warning about cancl causing corruption has been moved to after clicking the force cancel button. Part of Bug #601239 - Please allow 'Cancel after current operation'
2013-01-20 19:50:55 -07:00
bool cancel_safe );
make sure progressfraction stays between 0.0 and 1.0 implemented rollback * src/Dialog_Progress.cc: make sure progressfraction stays between 0.0 and 1.0 * include/GParted_Core.h, src/GParted_Core.cc: implemented rollback in case of failed move of overlapping filesystems. Together with the readonly test moving should be quite save now :)
2006-09-10 06:17:33 -06:00
bool copy_filesystem( const Partition & partition_src,
const Partition & partition_dst,
OperationDetail & operationdetail,
Add proper cancel support (#601239) Interested operations can now connect a signal to their OperationDetail to be notified of a cancelation request. The internal copy/move code will now cleanly stop on cancelation, allowing the partition to be rolled back to its previous state. This makes canceling a move perfectly safe. After clicking cancel, the button changes to "Force Cancel" and is disabled for 5 seconds. Operations that are safe to cancel will do so and those that are not will continue to run. Clicking force cancel asks operations to cancel, even if doing so is unsafe. For the internal copy/move algorithm, canceling is always safe because an error results in a rollback operation. Canceling the rollback is unsafe. For external commands, filesystem modules may indicate that the command is safe to cancel or not. Canceled commands will be terminated with SIGINT. As a result of the new safe cancel vs force cancel distinction, the scary warning about cancl causing corruption has been moved to after clicking the force cancel button. Part of Bug #601239 - Please allow 'Cancel after current operation'
2013-01-20 19:50:55 -07:00
Byte_Value & total_done,
bool cancel_safe );
make sure progressfraction stays between 0.0 and 1.0 implemented rollback * src/Dialog_Progress.cc: make sure progressfraction stays between 0.0 and 1.0 * include/GParted_Core.h, src/GParted_Core.cc: implemented rollback in case of failed move of overlapping filesystems. Together with the readonly test moving should be quite save now :)
2006-09-10 06:17:33 -06:00
bool copy_filesystem( const Glib::ustring & src_device,
const Glib::ustring & dst_device,
Sector src_start,
Sector dst_start,
Enhance copy_filesystem method to work with sector sizes This change is in preparation for supporting sectors sizes > 512 bytes.
2010-04-26 11:35:30 -06:00
Byte_Value src_sector_size,
Byte_Value dst_sector_size,
Enhance copy methods for sector sizes > 512 bytes
2010-04-07 11:33:21 -06:00
Byte_Value src_length,
make sure progressfraction stays between 0.0 and 1.0 implemented rollback * src/Dialog_Progress.cc: make sure progressfraction stays between 0.0 and 1.0 * include/GParted_Core.h, src/GParted_Core.cc: implemented rollback in case of failed move of overlapping filesystems. Together with the readonly test moving should be quite save now :)
2006-09-10 06:17:33 -06:00
OperationDetail & operationdetail,
Add proper cancel support (#601239) Interested operations can now connect a signal to their OperationDetail to be notified of a cancelation request. The internal copy/move code will now cleanly stop on cancelation, allowing the partition to be rolled back to its previous state. This makes canceling a move perfectly safe. After clicking cancel, the button changes to "Force Cancel" and is disabled for 5 seconds. Operations that are safe to cancel will do so and those that are not will continue to run. Clicking force cancel asks operations to cancel, even if doing so is unsafe. For the internal copy/move algorithm, canceling is always safe because an error results in a rollback operation. Canceling the rollback is unsafe. For external commands, filesystem modules may indicate that the command is safe to cancel or not. Canceled commands will be terminated with SIGINT. As a result of the new safe cancel vs force cancel distinction, the scary warning about cancl causing corruption has been moved to after clicking the force cancel button. Part of Bug #601239 - Please allow 'Cancel after current operation'
2013-01-20 19:50:55 -07:00
Byte_Value & total_done,
bool cancel_safe ) ;
make sure progressfraction stays between 0.0 and 1.0 implemented rollback * src/Dialog_Progress.cc: make sure progressfraction stays between 0.0 and 1.0 * include/GParted_Core.h, src/GParted_Core.cc: implemented rollback in case of failed move of overlapping filesystems. Together with the readonly test moving should be quite save now :)
2006-09-10 06:17:33 -06:00
void rollback_transaction( const Partition & partition_src,
Enhance copy methods for sector sizes > 512 bytes
2010-04-07 11:33:21 -06:00
const Partition & partition_dst,
OperationDetail & operationdetail,
Byte_Value total_done ) ;
restructured the core a bit, over time it had become very messy. * restructured the core a bit, over time it had become very messy.
2006-06-17 14:52:25 -06:00
changed progressfeedbackhandling a bit. Because this affected * changed progressfeedbackhandling a bit. Because this affected OperationDetail i had to make changes in almost every file.
2006-08-20 03:33:54 -06:00
bool check_repair_filesystem( const Partition & partition, OperationDetail & operationdetail ) ;
restructured the core a bit, over time it had become very messy. * restructured the core a bit, over time it had become very messy.
2006-06-17 14:52:25 -06:00
changed progressfeedbackhandling a bit. Because this affected * changed progressfeedbackhandling a bit. Because this affected OperationDetail i had to make changes in almost every file.
2006-08-20 03:33:54 -06:00
bool set_partition_type( const Partition & partition, OperationDetail & operationdetail ) ;
restructured the core a bit, over time it had become very messy. * restructured the core a bit, over time it had become very messy.
2006-06-17 14:52:25 -06:00
more fixes related to moving.. * include/GParted_Core.h, src/GParted_Core.cc: more fixes related to moving..
2006-09-03 08:24:05 -06:00
bool calibrate_partition( Partition & partition, OperationDetail & operationdetail ) ;
added FIXME: decoupled libparted partition and filesystemresizing. This * src/Win_GParted.cc: added FIXME: * include/GParted_Core.h, src/GParted_Core.cc, src/fat32.cc: decoupled libparted partition and filesystemresizing. This resulted in a much more consistent core. This also affected several other aspects of resizing/moving in a positive way.
2006-07-23 03:58:45 -06:00
bool calculate_exact_geom( const Partition & partition_old,
Partition & partition_new,
^) restructured resize_move() to be more robust. This will hopefully * happy 24th birthday Johannes! :^) * include/GParted_Core.h, src/GParted_Core.cc: restructured resize_move() to be more robust. This will hopefully tackle a couple of issues which came up during the public testing.
2006-08-27 02:41:25 -06:00
OperationDetail & operationdetail ) ;
Use wipefs to clear old signatures before creating new file systems (#688882) Previously the function erase_filesystem_signatures() was used to clear file system signatures when a new partition was created and when an existing partition was formatted with a file system. However this was only available with libparted <= 2.4 and then only for the file systems which libparted supports. Having multiple different file system signatures on a partition leads to misidentification of file system. For example creating a nilfs2 over the top of a fat32 file system is detected as a fat32, not nilfs2. This shows that old file system signatures must be cleared before a new file system is created. Fix by always using "wipefs -a /dev/PARTITION" command to clear all old file system signatures rather than libparted API calls. Failure from wipefs is only considered a warning so doesn't fail the file system creation. (This doesn't yet fully meet the "MUST be cleared" requirement above. Will be fully met later in this patchset). Output from the wipefs command is displayed as a new sub-step which looks like this: v Format /dev/sda7 as xfs 00:00:05 > calibrate /dev/sda14 00:00:01 v clear old file system signatures in /dev/sda7 00:00:01 [NEW] > wipefs -a /dev/sda7 [NEW] > set partition type on /dev/sda7 00:00:02 v create new xfs file system 00:00:01 > mkfs.xfs -f -L "" /dev/sda7 Also signatures are only cleared immediately before a new file system is written and not when an unformatted partition is created. This allows recovery from accidental partition deletion by re-creating the deleted partition as unformatted. Bug #688882 - Improve clearing of file system signatures
2012-12-01 05:49:29 -07:00
bool erase_filesystem_signatures( const Partition & partition, OperationDetail & operationdetail ) ;
update ntfsbootsector after first sector has changed. This is necessary to * include/GParted_Core.h, src/GParted_Core.cc: update ntfsbootsector after first sector has changed. This is necessary to let windows boot correctly afterwards. * src/ntfs.cc: added FIXME
2006-09-04 13:18:44 -06:00
bool update_bootsector( const Partition & partition, OperationDetail & operationdetail ) ;
restructured the core a bit, over time it had become very messy. * restructured the core a bit, over time it had become very messy.
2006-06-17 14:52:25 -06:00
//general..
Flush devices when scanning to prevent reading stale signatures (#723842) While one partition is busy, reformat another partition from the command line. Afterwards parted/libparted still detects the original file system and GParted shows errors from the file system specific tools reporting the new file system doesn't exist. Only limitation is that the new new file system must be recognised by libparted (or by GParted's fallback file system signature detection). Case #1, File system reformatting: # parted /dev/sdb print Model: ATA SAMSUNG SSD UM41 (scsi) Disk /dev/sdb: 8012MB Sector size (logical/physical): 512B/512B Partition Table: msdos Number Start End Size Type File system Flags 1 1049kB 2149MB 2147MB primary ext2 2 2149MB 4296MB 2147MB primary ext2 # mount | fgrep sdb /dev/sdb1 on /mnt/1 type ext2 (rw) # mkfs.xfs -f /dev/sdb2 # blkid /dev/sdb2 /dev/sdb2: UUID="c31823a2-b81b-46fa-8246-0a59695e4834" TYPE="xfs" # parted /dev/sdb print Model: ATA SAMSUNG SSD UM41 (scsi) Disk /dev/sdb: 8012MB Sector size (logical/physical): 512B/512B Partition Table: msdos Number Start End Size Type File system Flags 1 1049kB 2149MB 2147MB primary ext2 2 2149MB 4296MB 2147MB primary ext2 # e2label /dev/sdb2 e2label: Bad magic number in super-block while trying to open /dev/sdb2 Couldn't find valid filesystem superblock. # dumpe2fs /dev/sdb2 dumpe2fs 1.41.12 (17-May-2010) dumpe2fs: Bad magic number in super-block while trying to open /dev/sdb2 Couldn't find valid filesystem superblock. Case #2, Removing device from multi-device btrfs: # btrfs filesystem show /dev/sdb1 Label: none uuid: a05db434-efd5-4e8c-902f-05f89a88b610 Total devices 2 FS bytes used 156.00KB devid 2 size 2.00GB used 512.00MB path /dev/sdb2 devid 1 size 2.00GB used 240.75MB path /dev/sdb1 # mount /dev/sdb1 /mnt/1 # btrfs device delete /dev/sdb2 # btrfs filesystem show /dev/sdb1 Label: none uuid: a05db434-efd5-4e8c-902f-05f89a88b610 Total devices 1 FS bytes used 92.00KB devid 1 size 2.00GB used 714.25MB path /dev/sdb1 # btrfs filesystem show /dev/sdb2 and GParted reports this error for partition /dev/sdb2: 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 btrfs file system support: btrfs-tools. This is another case of libparted reading from the whole disk device (/dev/sdb) yet the file system tools use the partition specific block device (/dev/sdb2), and the Linux buffer cache not providing cache coherency. Previous scenario was fixed with: 797f0b8eeb61f81da1791c3cf048b5c0abf9a550 Flush device after wiping a file system (#688882) This affects libparted 2.0 to 3.1 inclusive and is fixed by: http://git.savannah.gnu.org/cgit/parted.git/commit/?id=fb99ba5ebd0dc34204fc9f1014131d5d494805bc Revert "linux-commit: do not unnecessarily open partition device nodes" Fix by calling ped_device_sync() to guarantee cache coherency for each device during scanning. Bug #723842 - GParted resizes the wrong filesystem (does not pass the devid to btrfs filesystem resize)
2014-03-23 15:11:13 -06:00
bool flush_device( PedDevice * lp_device ) ;
Split get_device_and_disk() into two (#743181) get_device_and_disk() basically calls libparted to get a PedDevice object representing a disk device and a PedDisk object representing a partition table. Re-implement get_device_and_disk() using two separate functions, get_device() and get_disk(), to get one of these objects each. No functionality changes with this commit. It enables future commits to incrementally add support for whole disk devices into GParted without needing libparted to recognise the contents and create a virtual "loop" partition table. Bug 743181 - Add unpartitioned drive read-write support
2015-01-07 13:07:02 -07:00
bool get_device( const Glib::ustring & device_path, PedDevice *& lp_device, bool flush = false );
bool get_disk( PedDevice *& lp_device, PedDisk *& lp_disk, bool strict = true );
Refactor and rename GParted_Core::open/close_device_and_disk() These functions in GParted_Core: open_device() open_device_and_disk() close_disk() close_device_and_disk() call the following functions in the libparted API: ped_device_get() ped_disk_new() ped_disk_destroy() ped_device_destroy() which don't open or close anything. Instead they allocate and deallocate PedDevice and PedDisk memory structures which describe block devices and partition tables respectively. Rename functions: open_device_and_disk() -> get_device_and_disk() close_device_and_disk() -> destroy_device_and_disk() and merge open_device() and open_device() as each only wrapped one libparted function and was only called from a single place.
2013-02-25 10:28:07 -07:00
bool get_device_and_disk( const Glib::ustring & device_path,
Flush devices when scanning to prevent reading stale signatures (#723842) While one partition is busy, reformat another partition from the command line. Afterwards parted/libparted still detects the original file system and GParted shows errors from the file system specific tools reporting the new file system doesn't exist. Only limitation is that the new new file system must be recognised by libparted (or by GParted's fallback file system signature detection). Case #1, File system reformatting: # parted /dev/sdb print Model: ATA SAMSUNG SSD UM41 (scsi) Disk /dev/sdb: 8012MB Sector size (logical/physical): 512B/512B Partition Table: msdos Number Start End Size Type File system Flags 1 1049kB 2149MB 2147MB primary ext2 2 2149MB 4296MB 2147MB primary ext2 # mount | fgrep sdb /dev/sdb1 on /mnt/1 type ext2 (rw) # mkfs.xfs -f /dev/sdb2 # blkid /dev/sdb2 /dev/sdb2: UUID="c31823a2-b81b-46fa-8246-0a59695e4834" TYPE="xfs" # parted /dev/sdb print Model: ATA SAMSUNG SSD UM41 (scsi) Disk /dev/sdb: 8012MB Sector size (logical/physical): 512B/512B Partition Table: msdos Number Start End Size Type File system Flags 1 1049kB 2149MB 2147MB primary ext2 2 2149MB 4296MB 2147MB primary ext2 # e2label /dev/sdb2 e2label: Bad magic number in super-block while trying to open /dev/sdb2 Couldn't find valid filesystem superblock. # dumpe2fs /dev/sdb2 dumpe2fs 1.41.12 (17-May-2010) dumpe2fs: Bad magic number in super-block while trying to open /dev/sdb2 Couldn't find valid filesystem superblock. Case #2, Removing device from multi-device btrfs: # btrfs filesystem show /dev/sdb1 Label: none uuid: a05db434-efd5-4e8c-902f-05f89a88b610 Total devices 2 FS bytes used 156.00KB devid 2 size 2.00GB used 512.00MB path /dev/sdb2 devid 1 size 2.00GB used 240.75MB path /dev/sdb1 # mount /dev/sdb1 /mnt/1 # btrfs device delete /dev/sdb2 # btrfs filesystem show /dev/sdb1 Label: none uuid: a05db434-efd5-4e8c-902f-05f89a88b610 Total devices 1 FS bytes used 92.00KB devid 1 size 2.00GB used 714.25MB path /dev/sdb1 # btrfs filesystem show /dev/sdb2 and GParted reports this error for partition /dev/sdb2: 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 btrfs file system support: btrfs-tools. This is another case of libparted reading from the whole disk device (/dev/sdb) yet the file system tools use the partition specific block device (/dev/sdb2), and the Linux buffer cache not providing cache coherency. Previous scenario was fixed with: 797f0b8eeb61f81da1791c3cf048b5c0abf9a550 Flush device after wiping a file system (#688882) This affects libparted 2.0 to 3.1 inclusive and is fixed by: http://git.savannah.gnu.org/cgit/parted.git/commit/?id=fb99ba5ebd0dc34204fc9f1014131d5d494805bc Revert "linux-commit: do not unnecessarily open partition device nodes" Fix by calling ped_device_sync() to guarantee cache coherency for each device during scanning. Bug #723842 - GParted resizes the wrong filesystem (does not pass the devid to btrfs filesystem resize)
2014-03-23 15:11:13 -06:00
PedDevice*& lp_device, PedDisk*& lp_disk, bool strict = true, bool flush = false ) ;
Refactor and rename GParted_Core::open/close_device_and_disk() These functions in GParted_Core: open_device() open_device_and_disk() close_disk() close_device_and_disk() call the following functions in the libparted API: ped_device_get() ped_disk_new() ped_disk_destroy() ped_device_destroy() which don't open or close anything. Instead they allocate and deallocate PedDevice and PedDisk memory structures which describe block devices and partition tables respectively. Rename functions: open_device_and_disk() -> get_device_and_disk() close_device_and_disk() -> destroy_device_and_disk() and merge open_device() and open_device() as each only wrapped one libparted function and was only called from a single place.
2013-02-25 10:28:07 -07:00
void destroy_device_and_disk( PedDevice*& lp_device, PedDisk*& lp_disk ) ;
Remove lp_device and lp_disk from GParted_Core (#683149) They were used like global variables. Now they are moved to the functions that actually use them to make clearer how the data flow is. Bug #683149 - Cleanup(?): Remove lp_device and lp_disk from GParted_Core
2012-10-30 03:30:49 -06:00
bool commit( PedDisk* lp_disk ) ;
bool commit_to_os( PedDisk* lp_disk, std::time_t timeout ) ;
Refactor some logic into separate settle_device method
2009-05-02 10:49:49 -06:00
void settle_device( std::time_t timeout ) ;
hmmz, lots of shimmery internals.. Instead of using a boolean to indicate * hmmz, lots of shimmery internals.. Instead of using a boolean to indicate support for certain features i now use and enum (NONE, LIBPARTED, EXTENDED). This allowed me to clean up some stuff that annoyed me ;) Still.. the core could use a bit more love...
2005-11-26 17:57:11 -07:00
catch libparted exceptions and display them in the operationdetails if an * include/GParted_Core.h, src/GParted_Core.cc: catch libparted exceptions and display them in the operationdetails if an operation has failed. * src/Dialog_Progress.cc: small cosmetic change to the errordialog.
2006-02-25 09:30:43 -07:00
static PedExceptionOption ped_exception_handler( PedException * e ) ;
P) It still needs a lot of love, but the foundations are laid =) * Rewrote a large part of gparteds internal code. Filesystemssupport is now much more separated from the rest of gparted and adding support for other filesystems should be a piece of cake now (hope that's true :P) It still needs a lot of love, but the foundations are laid =)
2004-11-17 06:00:25 -07:00
std::vector<FS> FILESYSTEMS ;
Add supported_filesystem() predicate method (#738471) Helper to check whether a recognised file system type is supported by GParted or not. Supported means there is an implementation class and will appear in the File System Support dialog. Make supported_filesystem() a static member function so that it can be called without a class object so that GParted_Core::GParted_Core() initialiser isn't called multiple times. This requires FILESYSTEM_MAP to become a static member variable too. Bug #738471 - ReFS file system is not recognised
2014-10-13 06:03:47 -06:00
static std::map< FILESYSTEM, FileSystem * > FILESYSTEM_MAP ;
support partitions with multiple mountpoints (see also #330327) * include/GParted_Core.h, include/Partition.h, src/Dialog_Partition_Info.cc, src/GParted_Core.cc, src/Partition.cc, src/TreeView_Detail.cc, src/Win_GParted.cc: support partitions with multiple mountpoints (see also #330327)
2006-02-15 15:32:54 -07:00
std::vector<PedPartitionFlag> flags;
added support for commandline arguments (#329414) * include/GParted_Core.h, include/Win_GParted.h, src/GParted_Core.cc, src/Win_GParted.cc, src/main.cc: added support for commandline arguments (#329414)
2006-02-02 06:50:37 -07:00
std::vector<Glib::ustring> device_paths ;
bool probe_devices ;
Added set and get thread status message methods. Added thread status message updates in set_devices(). svn path=/trunk/; revision=943
2008-10-30 12:50:38 -06:00
Glib::ustring thread_status_message; //Used to pass data to show_pulsebar method
Added support to lost data recovery using gpart
2011-01-28 11:09:21 -07:00
Glib::RefPtr<Glib::IOChannel> iocInput, iocOutput; // Used to send data to gpart command
P) It still needs a lot of love, but the foundations are laid =) * Rewrote a large part of gparteds internal code. Filesystemssupport is now much more separated from the rest of gparted and adding support for other filesystems should be a piece of cake now (hope that's true :P) It still needs a lot of love, but the foundations are laid =)
2004-11-17 06:00:25 -07:00
};
} //GParted
Make include guards unique (#539297) Include guards need to be unique within GParted code and all included library header files. http://en.wikipedia.org/wiki/Include_guard#Difficulties Use this model for all include guards: #ifndef GPARTED_FILE_NAME_H #define GPARTED_FILE_NAME_H ... #endif /* GPARTED_FILE_NAME_H */ Closes Bug #539297 - Make include guards unique
2013-05-27 05:20:16 -06:00
#endif /* GPARTED_GPARTED_CORE_H */