diff --git a/doc/CMakeLists.txt b/doc/CMakeLists.txt
new file mode 100644
index 0000000..dd75aec
--- /dev/null
+++ b/doc/CMakeLists.txt
@@ -0,0 +1 @@
+kde4_create_handbook(index.docbook INSTALL_DESTINATION ${HTML_INSTALL_DIR}/en)
diff --git a/doc/appendix.docbook b/doc/appendix.docbook
new file mode 100644
index 0000000..27b3b6e
--- /dev/null
+++ b/doc/appendix.docbook
@@ -0,0 +1,156 @@
+
+ Installation
+
+
+ How to obtain &partman;
+
+
+ The main website for &partman; is www.partitionmanager.org. For
+ the most current version, this is the place to go.
+
+
+
+
+ Requirements
+
+
+ In order to successfully use &partman;, you need &kde; 4.1 or later and &Qt; 4.4.0 or later. You do however not need to be logged into &kde; to use it: &partman; will run just fine under any other desktop environment as long as you have the basic &kde; libraries installed.
+
+
+
+ For a large part of its basic functionality &partman; relies on libparted. To generate UUIDs for copied file systems, it uses libuuid, which is part of e2fsprogs. Both of these are required to build or run &partman;.
+
+
+
+ &partman; makes extensive use of external tools to support a wide range of file systems. A specific tool is only required if you need the support for an operation it provides for a certain file system. For example, if you have no need to resize NTFS file systems you do not require to have ntfsresize
installed. None of these tools are required to build &partman; from sources.
+
+
+
+ Here is a list of all external tools &partman; can make use of:
+
+
+
+
+
+ &debugfsreiser4;: Reads usage information and file system labels for reiser4 file systems. Part of the reiser4progs utility suite that can be downloaded from .
+
+
+
+
+
+ &debugreiserfs;: Reads usage information and file system labels for reiserfs file systems. Part of the reiserfsprogs utility suite that can be downloaded from .
+
+
+
+
+
+ &dumpe2fs;: Reads usage information for ext2 and ext3 file systems. Part of the e2fsprogs utility suite that can be downloaded from .
+
+
+
+
+
+ &e2label;: Reads and writes file system labels for ext2 and ext3 file systems. Part of the e2fsprogs utility suite that can be downloaded from .
+
+
+
+
+
+ &fsckmsdos;: Reads usage information and checks FAT16 and FAT32 file systems. Part of the dosfstools utility suite that can be downloaded from .
+
+
+
+
+
+ &hfsck;: Reads file system labels and checks HFS file systems. Part of the hfsutils utility suite that can be downloaded from .
+
+
+
+
+
+ &hpfsck;: Checks HFS+ file systems. Part of the hfsplusutils utility suite that can be downloaded from .
+
+
+
+
+
+ &jfsdebugfs;: Reads usage information for JFS file systems. Part of the jfsutils utility suite that can be downloaded from .
+
+
+
+
+
+ &jfstune;: Reads and writes file system labels for JFS file systems. Part of the jfsutils utility suite that can be downloaded from .
+
+
+
+
+
+ &ntfslabel;: Reads and writes file system labels for NTFS file systems. Part of the ntfsprogs utility suite that can be downloaded from .
+
+
+
+
+
+ &ntfsresize;: Reads usage information, checks and resizes NTFS file systems. Part of the ntfsprogs utility suite that can be downloaded from .
+
+
+
+
+
+ &swapoff;: Deactivates swap file systems. Part of the util-linux utility suite that can be downloaded from .
+
+
+
+
+
+ &swapon;: Activates swap file systems. Part of the util-linux utility suite that can be downloaded from .
+
+
+
+
+
+ &volid;: Reads file system labels for linuxswap file systems. Part of udev that can be downloaded from .
+
+
+
+
+
+ &xfsdb;: Reads usage information and reads and writes file system labels for XFS file systems. Part of the xfsprogs utility suite that can be downloaded from .
+
+
+
+
+
+
+ Compilation and Installation
+ &install.compile.documentation;
+
+
+
+ Further Reading
+
+
+
+
+ The Linux Information Project has a ton of information on many aspects of Linux. Their article on partitions is very informative. But also see their entries on partition tables, hard disk devices and file systems.
+
+
+
+
+
+ The Linkux Partition HOWTO is a basic overview of handling and partitioning disk devices on Linux and the native linux file systems. It also covers swap partitions.
+
+
+
+
+
+ Wikipedia has an entry on disk partitioning.
+
+
+
+
+
+
+
+
diff --git a/doc/copy_howto_1.png b/doc/copy_howto_1.png
new file mode 100644
index 0000000..76828f1
Binary files /dev/null and b/doc/copy_howto_1.png differ
diff --git a/doc/copy_howto_2.png b/doc/copy_howto_2.png
new file mode 100644
index 0000000..db53a16
Binary files /dev/null and b/doc/copy_howto_2.png differ
diff --git a/doc/copyhowto.docbook b/doc/copyhowto.docbook
new file mode 100644
index 0000000..a963a06
--- /dev/null
+++ b/doc/copyhowto.docbook
@@ -0,0 +1,50 @@
+
+ How-To: Copying a Partition
+
+
+ This how-to describes copying a partition. We will assume the intention is to copy a partition from one device to another and overwriting an existing target partition, but the general procedure would not be much different when copying to the same device or to some unallocated area.
+
+
+
+ The following screenshot shows how the source device looks like:
+
+
+
+
+
+
+ Main window with source device
+
+
+
+
+
+ The source partition in our example will be sdb1
which is currently mounted, indicated by the lock-icon next to the mount point name in the screen shot. A mounted partition can not be copied, thus you first need to unmount it: Click on it then select .
+
+
+
+ After unmounting the partition the lock icon has gone and it is now possible to select . This puts sdb1
in &partman;'s clipboard; in other words: sdb1
is now the partition that will be inserted when you select .
+
+
+
+ The destination device for copying in this how-to is /dev/sdc
. Click on it in the Devices panel. This is how the device looks like before copying:
+
+
+
+
+
+
+ Main window with destination device before copying
+
+
+
+
+
+ The partition to overwrite is sdc5
. To paste the copied partition into it, click on it and select . You will see the operation to copy the partition has been added to the list of pending operations. Note that there is no dialog box required to insert the partition as would be the case if you pasted into an unallocated area: Beginning and end of the pasted partition are determined by the overwritten partition.
+
+
+
+ Now select and the partition will be copied. See the how-to on resizing partitions for details about applying operations.
+
+
+
diff --git a/doc/credits.docbook b/doc/credits.docbook
new file mode 100644
index 0000000..66bbcaa
--- /dev/null
+++ b/doc/credits.docbook
@@ -0,0 +1,19 @@
+
+ Credits and License
+
+ &partman;
+
+
+ Program copyright 2008 Volker Lanz
+ vl@fidra.de
+
+
+ Documentation Copyright © 2008 Volker Lanz.
+ vl@fidra.de
+
+
+
+
+ &underFDL;
+ &underGPL;
+
diff --git a/doc/faq.docbook b/doc/faq.docbook
new file mode 100644
index 0000000..22bb362
--- /dev/null
+++ b/doc/faq.docbook
@@ -0,0 +1,151 @@
+
+ Questions and Answers
+
+ &reporting.bugs;
+ &updating.documentation;
+
+
+
+
+ How dangerous is &partman; for my data?
+
+
+
+ First of all, you should never perform any destructive operations (delete, move, resize) without first making a complete backup of everything affected.
+
+
+ Having said that, &partman; is safe to use. It performs extensive checks before and after every operation. It calls external tools written and supported by the file system authors. And it has been tested extensively.
+
+
+ There is always the risk of data loss due to an unknown bug. &partman;'s authors try to minimize this risk, but there are of course no guarantees.
+
+
+
+
+
+ I have installed all recommended external file system support packages and still do not get support for all operations on all file systems.
+
+
+
+ Not everything &partman; can do in principle can be done with all file systems.
+
+
+ One example is performing a file system check on linuxswap: It is just not possible. There are other limitations like that inherent in some file systems. You cannot shrink JFS or XFS file systems because neither of the two supports shrinking at all, with or without &partman;.
+
+
+
+
+
+ Why can't I see any meaningful progress information when resizing a partition?
+
+
+
+ &partman; can only show progress information when it knows how long the jobs in an operation will take. Unfortunately this is usually not the case when resizing partitions because the by far longest job when doing so is resizing the file system on the partition. Resizing file systems is in most cases something an external tool will do on behalf of &partman; and these external tools do not provide useful progress information to &partman;, so there's nothing to report while they are running.
+
+
+
+
+
+ Why can't I resize the root partition? How can I resize the partition /home is on?
+
+
+
+ To modifiy a partition it must not be mounted. You can however not unmount the root partition. Neither will you be able to unmount the home partition if the home directory of the currently logged in user is on it.
+
+
+ The solution for this problem is to boot from a Linux Live CD that comes with &partman; and modify these partitions from there.
+
+
+
+
+
+ I'm getting a warning message in the log output about something that a partition cannot be created with the size I requested and that it will instead be smaller. What happened?
+
+
+
+ On MS-DOS partition tables, partitions have to begin and end on cylinder boundaries. This is mainly for historical reasons. &partman; will deal with this internally and try not to bother the user with that limitation.
+
+
+ Under rare circumstances, &partman; will however not be able to set up an operation in the way the user requested it due to this limitation. For example, if one cylinder on a device is 8 MiB large and you try to resize a partition by 6 MiB, this will not work.
+
+
+ You might also encounter this message if you have a device and partition table where the partitions are, for whatever reason, not correctly snapped to cylinder boundaries and you try to move or copy these partitions for the first time.
+
+
+ The message itself is harmless and only exists to inform the user that something can not be done quite exactly the way the user expects. Your partitions and data will not be negatively affected in any way if you see this message.
+
+
+
+
+
+ How can I set a file system label when creating a new partition?
+
+
+
+ This cannot be done directly in the dialog to create the partition but you can easily open the partition properties for the new partition and set a file system label there.
+
+
+
+
+
+ How many operations can I add to the list of pending operations?
+
+
+
+ There is no limit.
+
+
+ It is however not recommended to add too many operations to the list. There is always a small chance an operation might fail with an error, in which case &partman; will stop executing operations. In that case it is a lot easier to find out what happened (and to re-add all the operations that could not be executed) if the list of pending operations was not exceedingly long.
+
+
+
+
+
+ Resizing an ext2 or ext3 file system failed with something in the report about no space left on device
. What happened? Is my data corrupted now?
+
+
+
+ This is a problem of the e2resize command and the underlying ext2/3 file system. If a file system is nearly full, e2resize cannot make it any smaller even though that should be possible from the number of free sectors left. &partman; can unfortunately not know beforehand if e2resize will abort with this error for a given file system or not. If it happens nothing will be done at all and your data will not be negatively affected.
+
+
+ There is no real workaround for this problem right now.
+
+
+
+
+
+ Why can't I format my floppy disk with &partman;? Why is there no support for CD writing or DVD burning?
+
+
+
+ None of this is what &partman; has been designed to do: It is an application that deals with partitions and the file systems on these partitions. Floppy disks, CDs or DVDs do not need or use partitions.
+
+
+
+
+
+ Why can't I modify partitions on a device with an amiga or bsd partition table?
+
+
+
+ &partman; currently only allows read-only access to any other partition table type than MS-DOS. This is for safety reasons: Support in &partman; for this partition table types is not really there and what is there (or just incidentally works) has not been tested enough to use it with confidence.
+
+
+ Of course you can still create a new MS-DOS partition table on the device in question, but that is probably not what you want.
+
+
+
+
+
+
+
diff --git a/doc/filesystemsupport.png b/doc/filesystemsupport.png
new file mode 100644
index 0000000..f63e768
Binary files /dev/null and b/doc/filesystemsupport.png differ
diff --git a/doc/glossary.docbook b/doc/glossary.docbook
new file mode 100644
index 0000000..dcc332a
--- /dev/null
+++ b/doc/glossary.docbook
@@ -0,0 +1,236 @@
+
+
+
+ Command
+
+
+ In &partman; commands are what jobs are made up of. These are very low level steps being taken, often executed by an external tool, and only visible in the detailed progress report.
+
+
+ The user normally does not have to bother with commands at all.
+
+
+
+
+
+
+
+ Cylinder
+
+
+ A unit used to divide up a device. Some operating systems and many disk tools require partitions to begin and end on a cylinder. &partman; therefore automatically snaps partitions to cylinder boundaries when changing their start or end.
+
+
+
+
+
+
+
+ Cylinder Size
+
+
+ The number of sectors per cylinder on a device. Calculated as the number of heads multiplied by the number of sectors per track.
+
+
+
+
+
+ Device
+
+
+ A physical disk device. Physical disk devices are divided into logical sections called partitions with the use of partition tables.
+
+
+
+
+
+ Disk Label
+
+
+ Another name for a partition table stemming from the SUN/BSD world.
+
+
+
+ They are easy to mix up, but a disk label has nothing to do with a file system label.
+
+
+ See this Wikipedia entry for details on the name.
+
+
+
+
+
+
+
+ Extended Partition
+
+
+ A partition that contains other partitions. Extended partitions can only be primary partitions themselves. Whether extended partitions are available or not depends on the partition table type used. MS-DOS partition tables allow one extended partition per device.
+
+
+
+
+
+
+
+ File System
+
+
+ A file system defines how the storage of data (files with their metadata, folders and their metadata, free space) is organized within a partition. There are various different types of file systems, some coming originally from the Unix/Linux world, some not. Examples for commonly used file systems on Unix/Linux are ext2, ext3, reiserfs and xfs.
+
+
+
+
+
+ File System Label
+
+
+ A title of a file system. Some file systems (among them ext2/3, FAT16/32 and NTFS) support setting a label for the file system so it can be identified in tools like &partman; or other applications.
+
+
+ They are easy to mix up, but a file system label has nothing to do with a disk label.
+
+
+
+
+
+ Flag
+
+
+
+
+ Head
+
+
+ A unit used to divide up a device.
+
+
+
+
+
+
+
+ Job
+
+
+ In &partman; a number of jobs is what operations are made up of. You normally do not have to bother with jobs at all; it only becomes apparent when applying the list of pending operations: &partman; will then show a progress dialog that is made up of all operations and their jobs and show which operation and which job is currently being executed.
+
+
+
+
+
+
+
+ Label
+
+
+
+
+
+ Logical Partition
+
+
+ A partition inside an extended partition.
+
+
+
+
+
+
+
+ Operation
+
+
+ &partman; divides the work it does up in operations, jobs and commands.
+
+
+ Operations are the most visible of the three. If you pick an action in the graphical user interface, this will likely result in a new operation being added to the list of pending operations. The idea behind that is: You will most probably want to set up quite a number of steps to transform the current state of your disk devices to the state you have in mind. Some of these steps may take quite a long time to execute (like copying a large file system of resizing a file system that is nearly full). To save you from having to sit in front of your computer for a long time waiting for one step to finish and then starting the next one, operations allow you to exactly specify how the computer's devices should look like once everything is finished, then let &partman; apply the operations and come back when it has executed all of them.
+
+
+ Operations are kept in a list of pending operations. As long as an operation has not been applied it can still be taken back easily and nothing will have been modified.
+
+
+
+
+
+
+
+ Partition
+
+
+ A section of a hard disk device that can hold a file system or other partitions. Without at least one valid partition, a device can not be used.
+
+
+
+
+
+
+
+
+
+
+ Partition Flag
+
+
+ A marker for a partition. The availability of these flags depends on the type of partition table used.
+
+
+
+
+
+ Partition Table
+
+
+ A small section at the beginning of a device used to store information about the layout of the device's partitions. There are different types of partition tables, each with their own limitations.
+
+
+ Sometimes also referred to as disk label
.
+
+
+
+
+
+ Primary Partition
+
+
+ A partition directly inside a partition table, as opposed to logical partitions, which are in extended partitions.
+
+
+ Partition tables usually impose restrictions on the maximum number of primary partitions that can be created on a device. For MS-DOS type partition tables, for example, this maximum number is four.
+
+
+
+
+
+
+
+ Sector
+
+
+ A unit used to divide up a device. Partitions must always begin and end on a sector.
+
+
+
+
+
+
+
+ Sector Size
+
+
+ The number of bytes per sector on a device. The sector size of most devices in use today is 512 bytes.
+
+
+
+
+
+
+
diff --git a/doc/index.docbook b/doc/index.docbook
new file mode 100644
index 0000000..0abb46d
--- /dev/null
+++ b/doc/index.docbook
@@ -0,0 +1,96 @@
+
+
+KDE Partition Manager">
+
+
+
+
+
+
+
+
+
+
+
+
+ debugfs.reiser4">
+ debugreiserfs">
+ dumpe2fs">
+ e2label">
+ fsck.msdos">
+ hfsck">
+ hpfsck">
+ jfs_debugfs">
+ jfs_tune">
+ ntfslabel">
+ ntfsresize">
+ swapoff">
+ swapon">
+ vol_id">
+ xfs_db">
+
+
+
+
+
+]>
+
+
+
+ The &partman; Handbook
+
+
+ Volker
+ Lanz
+
+
+
+
+
+
+ 2008
+ Volker Lanz
+
+
+
+
+ &FDLNotice;
+
+
+ 2008-10-02
+ 0.80.00
+
+
+ Manage your disks, partitions and file systems.
+
+
+
+ KDE
+ sysadmin
+ partition
+ manager
+ disk
+ device
+ filesystem
+
+
+
+
+ &partman-introduction;
+
+ &partman-usermanual;
+
+ &partman-referencemanual;
+
+ &partman-faq;
+
+ &partman-credits;
+
+ &partman-appendix;
+
+ &partman-glossary;
+
+ &documentation.index;
+
+
\ No newline at end of file
diff --git a/doc/installos_howto_1.png b/doc/installos_howto_1.png
new file mode 100644
index 0000000..97fb03c
Binary files /dev/null and b/doc/installos_howto_1.png differ
diff --git a/doc/installos_howto_2.png b/doc/installos_howto_2.png
new file mode 100644
index 0000000..fa761d0
Binary files /dev/null and b/doc/installos_howto_2.png differ
diff --git a/doc/installos_howto_3.png b/doc/installos_howto_3.png
new file mode 100644
index 0000000..d7a05e7
Binary files /dev/null and b/doc/installos_howto_3.png differ
diff --git a/doc/installos_howto_4.png b/doc/installos_howto_4.png
new file mode 100644
index 0000000..8320743
Binary files /dev/null and b/doc/installos_howto_4.png differ
diff --git a/doc/installos_howto_5.png b/doc/installos_howto_5.png
new file mode 100644
index 0000000..1ec3df7
Binary files /dev/null and b/doc/installos_howto_5.png differ
diff --git a/doc/installos_howto_6.png b/doc/installos_howto_6.png
new file mode 100644
index 0000000..2158bd2
Binary files /dev/null and b/doc/installos_howto_6.png differ
diff --git a/doc/installos_howto_7.png b/doc/installos_howto_7.png
new file mode 100644
index 0000000..62ce68a
Binary files /dev/null and b/doc/installos_howto_7.png differ
diff --git a/doc/installoshowto.docbook b/doc/installoshowto.docbook
new file mode 100644
index 0000000..ed17635
--- /dev/null
+++ b/doc/installoshowto.docbook
@@ -0,0 +1,131 @@
+
+ How-To: Installing a New Operating System
+
+
+ This how-to describes the preparation of a new hard disk device for an OS installation: Suppose you bought a new hard disk and now intend to use it as a replacement for the old one that currently holds your OS and data partitions. You would also like to take this oppurtunity to install a new operation system. Several steps will have to be taken to make the transition from the old to the new system and drive.
+
+
+
+ In the following, /dev/sdb
is the old hard disk and /dev/sdc
is the new one. This screenshot shows the situation on the source device:
+
+
+
+
+
+
+ Main window with source device
+
+
+
+
+
+ The new device will look like this. Note that it doesn't yet have valid partition table, thus the first step to take is to create one by selecting :
+
+
+
+
+
+
+ Main window with destination device
+
+
+
+
+
+ After confirming the warning dialog you can begin creating partitions on the new device by clicking the extended partition and selecting . Begin with an extended partition at the end of the device to later hold the home and swap partitions:
+
+
+
+
+
+
+ Creating an extended partition
+
+
+
+
+
+ Click OK and the operation to create this extended partition is added to the list.
+
+
+
+ Now create a primary partition on the rest of the device where the new OS will be installed. Make it as large as the unallocated area in front of the extended partition:
+
+
+
+
+
+
+ Creating a primary partition
+
+
+
+
+
+ Click OK in the dialog to accept your choice. The operation to create the new primary partition is then added to the operation list.
+
+
+
+ Now it is time to copy the home partition from the old device to the extended partition on the new device. Select the old device in the Device List panel, click on partition sdb5
and pick .
+
+
+
+ Then go back to the new device and click the extended partition. Select . The following dialog will come up:
+
+
+
+
+
+
+ Pasting the home partition
+
+
+
+
+
+ This already looks mostly okay but you already know that you will not need that much free space after the home partition because you will later create a swap partition there. And a swap partition of more than 3 GiB is a little large.
+
+
+
+ So grab the right resize handle in the dialog's resizer widget and move it to the right until the free space after the pasted partition is only about 1.5 GiB in size:
+
+
+
+
+
+
+ Resizing a pasted partition
+
+
+
+
+
+ This looks fine. Click OK to accept and close the dialog. A new operation to paste the copied partition to the extended partition on sdc
is added to the operation list. Note that this operation will also set the new size.
+
+
+
+ Finally you will want to create a new swap partition at the end of the extended partition on sdc
. There is no need to copy the existing swap partition from sdb
because swap does not hold any permanent information worth keeping. Simply create a new partition with type linuxswap that fills the whole of the unallocated area after the new home partition.
+
+
+
+ The main window with all operations and the preview of how sdc
will look like once they are applied now looks like this:
+
+
+
+
+
+
+ Main window after setting up all operations
+
+
+
+
+
+ This looks great so select , confirm the warning dialog and wait until the operations have all been executed. For details on executing operations see the how-to on resizing partitions.
+
+
+
+ Your new hard disk device is now ready for the installation of your new operation system.
+
+
+
diff --git a/doc/introduction.docbook b/doc/introduction.docbook
new file mode 100644
index 0000000..a0361b1
--- /dev/null
+++ b/doc/introduction.docbook
@@ -0,0 +1,31 @@
+
+ Introduction
+
+ &partman; is a utility program to help you manage the disk devices, partitions and file systems on your computer.
+
+
+ It allows you to easily create new partitions, create file systems on new or existing partitions, copy, move or delete partitions and also to modify a partition's size without losing the data on it.
+
+
+
+ To get its job done efficiently &partman; makes use of external tools to support a long list of file systems. See for details about that. You will probably have the required tools for the file systems on your computer installed already.
+
+
+
+ Always back up your data!
+
+ &partman; has been designed and written with high diligence and an emphasis on data integrity. There is however always some danger involved when modifying a device's partition table or its partitions: There might still be a bug in &partman;, an unexpected power failure or a problem with the computer's hardware.
+
+
+ For those reasons you should always have a back up of your important data before making any modifications with a tool like &partman;.
+
+
+ The program's authors take no responsibility whatsoever if you lose any data while using &partman;.
+
+
+
+
+ &partman; uses operations, jobs and commands to logically divide up the work it does. See the glossary for details on this.
+
+
+
diff --git a/doc/mainwindow.png b/doc/mainwindow.png
new file mode 100644
index 0000000..fbf4ce1
Binary files /dev/null and b/doc/mainwindow.png differ
diff --git a/doc/referencemanual.docbook b/doc/referencemanual.docbook
new file mode 100644
index 0000000..20c8bf2
--- /dev/null
+++ b/doc/referencemanual.docbook
@@ -0,0 +1,463 @@
+
+ Command Reference
+
+
+ Overwiew
+ This chapter gives detailed explanations of all commands available in &partman;. It is intended as a reference to accompany the information given in .
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ The Help Menu
+ &help.menu.documentation;
+
+
diff --git a/doc/resize_howto_1.png b/doc/resize_howto_1.png
new file mode 100644
index 0000000..c46319b
Binary files /dev/null and b/doc/resize_howto_1.png differ
diff --git a/doc/resize_howto_2.png b/doc/resize_howto_2.png
new file mode 100644
index 0000000..11bbd32
Binary files /dev/null and b/doc/resize_howto_2.png differ
diff --git a/doc/resize_howto_3.png b/doc/resize_howto_3.png
new file mode 100644
index 0000000..73671f0
Binary files /dev/null and b/doc/resize_howto_3.png differ
diff --git a/doc/resize_howto_4.png b/doc/resize_howto_4.png
new file mode 100644
index 0000000..3f5ec4c
Binary files /dev/null and b/doc/resize_howto_4.png differ
diff --git a/doc/resize_howto_5.png b/doc/resize_howto_5.png
new file mode 100644
index 0000000..ffb6354
Binary files /dev/null and b/doc/resize_howto_5.png differ
diff --git a/doc/resize_howto_6.png b/doc/resize_howto_6.png
new file mode 100644
index 0000000..6de679c
Binary files /dev/null and b/doc/resize_howto_6.png differ
diff --git a/doc/resize_howto_7.png b/doc/resize_howto_7.png
new file mode 100644
index 0000000..9b01bef
Binary files /dev/null and b/doc/resize_howto_7.png differ
diff --git a/doc/resize_howto_8.png b/doc/resize_howto_8.png
new file mode 100644
index 0000000..94b557b
Binary files /dev/null and b/doc/resize_howto_8.png differ
diff --git a/doc/resize_howto_9.png b/doc/resize_howto_9.png
new file mode 100644
index 0000000..394326a
Binary files /dev/null and b/doc/resize_howto_9.png differ
diff --git a/doc/resizehowto.docbook b/doc/resizehowto.docbook
new file mode 100644
index 0000000..6e89726
--- /dev/null
+++ b/doc/resizehowto.docbook
@@ -0,0 +1,172 @@
+
+ How-To: Resizing a Partition
+
+
+ This how-to explains the resizing of a partition that is becoming too full. See the following screenshot for the initial situation before resizing:
+
+
+
+
+
+
+ Main window before resizing partitions
+
+
+
+
+
+ On device /dev/sdb
, partition sdb2
has only little free space left while the other partition, sdb1
, is far from being full. For that reason it seems advisable to make the first partition a little smaller and grow sdb2
so it has more free space available.
+
+
+
+ Note: You cannot modify mounted partitions.
+ In the screenshot above both partitions are not currently mounted. If one or both of them were mounted you would have to unmount them first using .
+
+
+
+ The first step is to make more room for the partition to grow, so start by shrinking sdb1
from its current size of 7.21 GiB to a more fittingly 5.00 GiB. Click on the partition and choose . The following dialog comes up:
+
+
+
+
+
+
+ Resize dialog before resizing /dev/sdb1
+
+
+
+
+
+ The dialog allows you to resize the partition in multiple ways. You can either drag the right handle to the left until the partition has the desired size or simply enter the size in the Size text field. Another possibility would be to adjust the size by clicking on the little arrows next to the text field, but that is a little tedious for larger changes.
+
+
+
+ Whichever way you prefer for setting the new size, the dialog should now look like this:
+
+
+
+
+
+
+ Resize dialog after resizing /dev/sdb1
+
+
+
+
+
+ After you click on OK, a new operation is added to the pending operations list and the graphical view and tree view of the device are updated to reflect the new situation:
+
+
+
+
+
+
+ Main window after resizing /dev/sdb1
+
+
+
+
+
+ Note: Operations are previewed first before applying them.
+ Although the main window reflects the device's state how it will be after applying the new operation, the operation has in fact not been applied yet: While operations are pending you can still undo them (one by one using or to undo all of them) or quit &partman;, and nothing will have been modified at all.
+
+
+
+ Now that there is some free space between the two partitions you can move and grow partition sdb2
. First, click on sdb2
and choose again. The resize dialog comes up once more, this time for the second partition. Drag its left handle to the leftmost end so that the dialog looks like this:
+
+
+
+
+
+
+ Resize dialog after resizing /dev/sdb2
+
+
+
+
+
+ Be careful to make sure that the Free space before text field really does show 0 MiB
because otherwise there will be a little free space left between the partitions that will then be wasted.
+
+
+
+ Now click OK again. In the main window things now look like this:
+
+
+
+
+
+
+ Main window after resizing /dev/sdb2
+
+
+
+
+
+ This already looks like what you wanted, so choose . A dialog box will come up and ask you if you are sure to apply the pending operations. Confirm this dialog box and &partman; will begin executing operations:
+
+
+
+
+
+
+ &partman; is applying operations
+
+
+
+
+
+ While operations are being executed you can click on the plus-sign next to each operation in the list to find out the jobs it is made up of and see which job is currently being run.
+
+
+
+ Resizing a partition in the way you resized /dev/sdb2
above always means it has to be moved to the left first before it can be grown because partitions can never be grown to the left directly. Unfortunately, moving such a large partition will take quite some time. It is not unusual for an operation like this to take several minutes or even more.
+
+
+
+ Finally, all operations will have been successfully completed:
+
+
+
+
+
+
+ Progress dialog after successfully applying operations
+
+
+
+
+
+ By clicking on OK you can now close the progress dialog and return to the main window. &partman; will rescan your devices at this point so that might take a few seconds.
+
+
+
+ If you are interested in some more details about the operations that were just run click on Details. You will see the detailed report that is always generated (and updated on the fly) while &partman; executes operations:
+
+
+
+
+
+
+ Progress dialog details
+
+
+
+
+
+ This report is particularly of interest if an error occurs while executing operations. A report shows each operation, each job and each external command that is being run and is thus very helpful when trying to track down problems.
+
+
+
+ You can save the report as HTML or view it in an external web browser.
+
+
+
+
+ Always save the detailed report as HTML when executing the operations fails with errors or warnings for later reference. You might also want to include it in a bug report you submit to &partman;'s authors.
+
+
+
+
+ To hide the details again click on Details and to finally close the progress dialog click on OK.
+
+
diff --git a/doc/usermanual.docbook b/doc/usermanual.docbook
new file mode 100644
index 0000000..8785619
--- /dev/null
+++ b/doc/usermanual.docbook
@@ -0,0 +1,89 @@
+
+ Using &partman;
+
+
+ The Main Window
+
+
+ Besides the main view showing the currently selected device in a graphical and a tree view, &partman; uses &Qt;'s dock widgets
or panels to display some information and allow selections. See the following screen shot for an overview of &partman;'s main window.
+
+
+
+
+ &partman;'s main window
+
+
+ Main Window
+
+
+
+
+
+
+
+ Menubar: The menu bar presents some custom and some non-standard menus to choose actions to perform. All commands are described in detail in .
+
+
+
+ Toolbar: &partman;'s tool bar is a &kde; 4 standard tool bar. It can be fully customized; for details see .
+
+
+
+
+ Devices Panel: This panel lists all devices found on your computer that &partman; can handle. Select a device in this panel to view or modify it in the graphical device view or in the tree device view.
+
+
+
+
+ Graphical Device View: In this view &partman; shows a graphical representation of the currently selected device. Each of the device's partitions has its own box with device node name (sda1
for the first partition in the screenshot above) and usage information (the dark violet area and 7.61 GiB
in the screenshot).
+
+
+ Extended partitions are visually distinct by their extra border (light green in the screenshot above) around them.
+
+
+ You can select a partition by clicking on it in the graphical device view. A double click opens the partition's properties dialog. A right click shows the partition context menu.
+
+
+
+
+
+ Tree Device View: The tree device view shows extended information about each partition on the selected device. The currently selected partition is highlighted. Double-clicking a partition opens the partition's properties dialog. A right click shows the partition context menu.
+
+
+
+
+ Information Panel: The information panel shows some details about the currently selected device or partition. It is not enabled by default.
+
+
+
+
+ Pending Operations Panel: This panel lists all operations that will be executed once you choose .
+
+
+ In the screenshot above, one operation is pending: If the user applies the operations now, the ext2 file system on /dev/sdb7 (which is 1.99 GiB in size) will be checked for errors and, if required, repaired.
+
+
+
+
+
+ Statusbar: The status bar shows how many operations are currently pending.
+
+
+
+
+ Log Output Panel: This panel shows log information. It is only of secondary importance for non-advanced users and is not enabled by default.
+
+
+
+
+
+
+
+ &partman-resizehowto;
+
+ &partman-copyhowto;
+
+ &partman-installoshowto;
+
+
+