Sun May 30 00:18:47 UTC 2010

dev/null                                                                      |binary
 en-US/.directory                                                              |    4 
 en-US/Account_Configuration-common.xml                                        |   82 
 en-US/Account_Configuration_common-para-6.xml                                 |   15 
 en-US/Account_Configuration_common-title.xml                                  |    5 
 en-US/Adding_Partitions-section-2-indexterm-1.xml                             |   10 
 en-US/Adding_Partitions-section-2-indexterm-2.xml                             |   12 
 en-US/Adding_Partitions-section-2-indexterm-3.xml                             |   10 
 en-US/Adding_Partitions-section-2-indexterm-4.xml                             |   11 
 en-US/Adding_Partitions-section-2-itemizedlist-1-listitem-0.xml               |   18 
 en-US/Adding_Partitions-section-2-itemizedlist-1-listitem-1.xml               |   11 
 en-US/Adding_Partitions-section-2-itemizedlist-1-listitem-2.xml               |   14 
 en-US/Adding_Partitions-section-2-itemizedlist-1-listitem-2a.xml              |    9 
 en-US/Adding_Partitions-section-2-itemizedlist-1-listitem-3.xml               |    9 
 en-US/Adding_Partitions-section-2-itemizedlist-1-listitem-4.xml               |    9 
 en-US/Adding_Partitions-section-2-itemizedlist-1-listitem-5.xml               |    9 
 en-US/Adding_Partitions-section-2-itemizedlist-1-listitem-6.xml               |   12 
 en-US/Adding_Partitions-section-2-itemizedlist-1-listitem-7.xml               |   10 
 en-US/Adding_Partitions-section-2-itemizedlist-1.xml                          |   36 
 en-US/Adding_Partitions-section-2-para-1.xml                                  |    7 
 en-US/Adding_Partitions-x86.xml                                               |   93 
 en-US/Adding_Partitions_common-indexterm-1.xml                                |   12 
 en-US/Adding_Partitions_common-indexterm-2.xml                                |   10 
 en-US/Adding_Partitions_common-indexterm-3.xml                                |   11 
 en-US/Adding_Partitions_common-title-1.xml                                    |    8 
 en-US/Adding_Partitions_x86_ppc-listitem-1.xml                                |   12 
 en-US/Adding_Partitions_x86_ppc-listitem-2.xml                                |    9 
 en-US/Adding_Partitions_x86_ppc-listitem-3.xml                                |   12 
 en-US/Adding_Partitions_x86_ppc-listitem-4.xml                                |   17 
 en-US/Adding_Partitions_x86_ppc-listitem-5.xml                                |   12 
 en-US/Adding_Partitions_x86_ppc-listitem-6.xml                                |   12 
 en-US/Adding_Partitions_x86_ppc-listitem-7.xml                                |   10 
 en-US/Adding_Partitions_x86_ppc-title-2.xml                                   |    8 
 en-US/Advice_on_Partitions.xml                                                |  146 
 en-US/Assign_Storage_Devices-common-figure-1.xml                              |   14 
 en-US/Assign_Storage_Devices-common-para-1.xml                                |    7 
 en-US/Assign_Storage_Devices-common-para-2.xml                                |    7 
 en-US/Assign_Storage_Devices-common-para-3.xml                                |    7 
 en-US/Assign_Storage_Devices-common-para-4.xml                                |    7 
 en-US/Assign_Storage_Devices-common-para-5.xml                                |    7 
 en-US/Assign_Storage_Devices-common-para-6.xml                                |    7 
 en-US/Assign_Storage_Devices-common-title.xml                                 |    7 
 en-US/Assign_Storage_Devices-x86.xml                                          |   36 
 en-US/Author_Group.xml                                                        |    9 
 en-US/Automatic_Partitioning_common-caution-1.xml                             |   14 
 en-US/Automatic_Partitioning_common-indexterm-1.xml                           |   12 
 en-US/Automatic_Partitioning_common-indexterm-2.xml                           |   10 
 en-US/Automatic_Partitioning_common-note-1.xml                                |   15 
 en-US/Automatic_Partitioning_common-para-1.xml                                |   11 
 en-US/Automatic_Partitioning_common-para-2.xml                                |    8 
 en-US/Automatic_Partitioning_common-para-3.xml                                |    8 
 en-US/Automatic_Partitioning_common-para-4.xml                                |   10 
 en-US/Automatic_Partitioning_common-para-5.xml                                |   10 
 en-US/Automatic_Partitioning_common-varlistentry-1.xml                        |   19 
 en-US/Automatic_Partitioning_common-varlistentry-2.xml                        |   12 
 en-US/Automatic_Partitioning_common-varlistentry-3.xml                        |   20 
 en-US/Automatic_Partitioning_x86-variablelist-1.xml                           |   34 
 en-US/Automatic_Partitioning_x86_ppc-tip-para-1.xml                           |   10 
 en-US/Automatic_Partitioning_x86_ppc-tip-para-2.xml                           |   10 
 en-US/Automatic_Partitioning_x86_ppc-tip-para-3.xml                           |   10 
 en-US/Beginning_Installation-x86.xml                                          |   59 
 en-US/Beginning_Installation_Hard_Disk-x86.xml                                |   46 
 en-US/Beginning_Installation_Hard_Disk_common-indexterm-1.xml                 |    7 
 en-US/Beginning_Installation_Hard_Disk_common-indexterm-10.xml                |    8 
 en-US/Beginning_Installation_Hard_Disk_common-indexterm-2.xml                 |    8 
 en-US/Beginning_Installation_Hard_Disk_common-indexterm-3.xml                 |    8 
 en-US/Beginning_Installation_Hard_Disk_common-indexterm-4.xml                 |    8 
 en-US/Beginning_Installation_Hard_Disk_common-indexterm-5.xml                 |    8 
 en-US/Beginning_Installation_Hard_Disk_common-indexterm-6.xml                 |    8 
 en-US/Beginning_Installation_Hard_Disk_common-indexterm-7.xml                 |    8 
 en-US/Beginning_Installation_Hard_Disk_common-indexterm-8.xml                 |    8 
 en-US/Beginning_Installation_Hard_Disk_common-indexterm-9.xml                 |    8 
 en-US/Beginning_Installation_Hard_Disk_common-note-1.xml                      |   10 
 en-US/Beginning_Installation_Hard_Disk_common-note-2.xml                      |   10 
 en-US/Beginning_Installation_Hard_Disk_common-para-1.xml                      |    7 
 en-US/Beginning_Installation_Hard_Disk_common-para-10.xml                     |    7 
 en-US/Beginning_Installation_Hard_Disk_common-para-11.xml                     |    8 
 en-US/Beginning_Installation_Hard_Disk_common-para-3.xml                      |   11 
 en-US/Beginning_Installation_Hard_Disk_common-para-5.xml                      |    8 
 en-US/Beginning_Installation_Hard_Disk_common-para-6.xml                      |    7 
 en-US/Beginning_Installation_Hard_Disk_common-para-8.xml                      |    7 
 en-US/Beginning_Installation_Hard_Disk_common-para-9.xml                      |    7 
 en-US/Beginning_Installation_Hard_Disk_common-screen-1.xml                    |    9 
 en-US/Beginning_Installation_Hard_Disk_common-table-1.xml                     |   30 
 en-US/Beginning_Installation_Hard_Disk_common-title-1.xml                     |   10 
 en-US/Beginning_Installation_Hard_Disk_x86_ppc-figure-1.xml                   |   16 
 en-US/Beginning_Installation_NFS-x86.xml                                      |   40 
 en-US/Beginning_Installation_NFS_common-figure-1.xml                          |   16 
 en-US/Beginning_Installation_NFS_common-indexterm-1.xml                       |   12 
 en-US/Beginning_Installation_NFS_common-indexterm-2.xml                       |   11 
 en-US/Beginning_Installation_NFS_common-indexterm-3.xml                       |   12 
 en-US/Beginning_Installation_NFS_common-indexterm-4.xml                       |   12 
 en-US/Beginning_Installation_NFS_common-para-1.xml                            |   10 
 en-US/Beginning_Installation_NFS_common-para-2.xml                            |   10 
 en-US/Beginning_Installation_NFS_common-para-4.xml                            |    8 
 en-US/Beginning_Installation_NFS_common-para-5.xml                            |    7 
 en-US/Beginning_Installation_NFS_common-para-6.xml                            |    7 
 en-US/Beginning_Installation_NFS_common-title-1.xml                           |    8 
 en-US/Beginning_Installation_Network-x86.xml                                  |   53 
 en-US/Beginning_Installation_Network_x86_ppc-indexterm-1.xml                  |   11 
 en-US/Beginning_Installation_Network_x86_ppc-indexterm-2.xml                  |    7 
 en-US/Beginning_Installation_Network_x86_ppc-indexterm-3.xml                  |    8 
 en-US/Beginning_Installation_Network_x86_ppc-list-1.xml                       |   18 
 en-US/Beginning_Installation_Network_x86_ppc-para-1.xml                       |    7 
 en-US/Beginning_Installation_Network_x86_ppc-para-2.xml                       |    7 
 en-US/Beginning_Installation_Network_x86_ppc-para-3.xml                       |    7 
 en-US/Beginning_Installation_Network_x86_ppc-para-4.xml                       |    7 
 en-US/Beginning_Installation_Network_x86_ppc-para-5.xml                       |    8 
 en-US/Beginning_Installation_Network_x86_ppc-para-6.xml                       |    8 
 en-US/Beginning_Installation_Network_x86_ppc-para-7.xml                       |   13 
 en-US/Beginning_Installation_Network_x86_ppc-para-8.xml                       |   14 
 en-US/Beginning_Installation_Network_x86_ppc-title.xml                        |    7 
 en-US/Beginning_Installation_URL-common-figure-1.xml                          |   13 
 en-US/Beginning_Installation_URL-common-indexterm-1.xml                       |   13 
 en-US/Beginning_Installation_URL-common-indexterm-2.xml                       |   11 
 en-US/Beginning_Installation_URL-common-indexterm-3.xml                       |   11 
 en-US/Beginning_Installation_URL-common-para-1.xml                            |    8 
 en-US/Beginning_Installation_URL-common-para-2-Fedora.xml                     |    8 
 en-US/Beginning_Installation_URL-common-para-3.xml                            |    7 
 en-US/Beginning_Installation_URL-common-title-1.xml                           |    5 
 en-US/Beginning_Installation_URL-x86.xml                                      |   33 
 en-US/Beginning_Installation_x86_ppc-indexterm-1.xml                          |   12 
 en-US/Beginning_Installation_x86_ppc-indexterm-2.xml                          |   11 
 en-US/Beginning_Installation_x86_ppc-indexterm-3.xml                          |   11 
 en-US/Beginning_Installation_x86_ppc-indexterm-4.xml                          |   11 
 en-US/Beginning_Installation_x86_ppc-indexterm-5.xml                          |   11 
 en-US/Beginning_Installation_x86_ppc-indexterm-6.xml                          |   11 
 en-US/Beginning_Installation_x86_ppc-para-1.xml                               |    7 
 en-US/Beginning_Installation_x86_ppc-para-3.xml                               |   11 
 en-US/Beginning_Installation_x86_ppc-title-1.xml                              |    8 
 en-US/Book_Info.xml                                                           |   27 
 en-US/Boot-x86.xml                                                            |  144 
 en-US/Boot_Init_Shutdown.xml                                                  |  770 -
 en-US/Boot_Order-para-1.xml                                                   |    7 
 en-US/Boot_Order-para-2.xml                                                   |    7 
 en-US/Boot_Order-para-3.xml                                                   |    7 
 en-US/Boot_Order-para-4.xml                                                   |    7 
 en-US/Boot_Order-para-5.xml                                                   |    7 
 en-US/Boot_x86_ppc-figure-1.xml                                               |   16 
 en-US/Boot_x86_ppc-indexterm-1.xml                                            |    9 
 en-US/Boot_x86_ppc-indexterm-2.xml                                            |    9 
 en-US/Boot_x86_ppc-para-1.xml                                                 |    8 
 en-US/Boot_x86_ppc-para-2.xml                                                 |    8 
 en-US/Boot_x86_ppc-para-3.xml                                                 |    8 
 en-US/Boot_x86_ppc-para-4.xml                                                 |    8 
 en-US/Boot_x86_ppc-para-5.xml                                                 |    8 
 en-US/Boot_x86_ppc-para-6.xml                                                 |    8 
 en-US/Boot_x86_ppc-para-7.xml                                                 |    8 
 en-US/Boot_x86_ppc-para-8.xml                                                 |    8 
 en-US/Boot_x86_ppc-procedure-1.xml                                            |   23 
 en-US/Boot_x86_ppc-table-1.xml                                                |   29 
 en-US/Boot_x86_ppc-title-1.xml                                                |    6 
 en-US/Boot_x86_ppc-title-2.xml                                                |    6 
 en-US/Boot_x86_ppc-title-3.xml                                                |    9 
 en-US/Boot_x86_ppc-title-4.xml                                                |    8 
 en-US/Boot_x86_ppc-variablelist-1.xml                                         |   56 
 en-US/Complete-x86.xml                                                        |   34 
 en-US/Complete_common-para-1.xml                                              |    7 
 en-US/Complete_common-title-1.xml                                             |    8 
 en-US/Complete_x86-para-2.xml                                                 |   10 
 en-US/Contributors_and_production_methods.xml                                 |  554 -
 en-US/Create_LVM-common-important-1.xml                                       |   10 
 en-US/Create_LVM-common-para-1.xml                                            |    7 
 en-US/Create_LVM-common-para-2.xml                                            |    7 
 en-US/Create_LVM-common-title-1.xml                                           |    8 
 en-US/Create_LVM-common-variablelist-1.xml                                    |   54 
 en-US/Create_LVM-x86.xml                                                      |   45 
 en-US/Create_Software_RAID-common-para-1.xml                                  |    9 
 en-US/Create_Software_RAID-common-para-2.xml                                  |    9 
 en-US/Create_Software_RAID-common-title-1.xml                                 |    8 
 en-US/Create_Software_RAID-common-variablelist-1.xml                          |   99 
 en-US/Create_Software_RAID-x86.xml                                            |   42 
 en-US/Create_Storage-common-figure-1.xml                                      |   14 
 en-US/Create_Storage-common-listitem-1.xml                                    |   13 
 en-US/Create_Storage-common-listitem-2.xml                                    |   10 
 en-US/Create_Storage-common-listitem-3.xml                                    |   10 
 en-US/Create_Storage-common-listitem-4.xml                                    |   10 
 en-US/Create_Storage-common-listitem-5.xml                                    |   10 
 en-US/Create_Storage-common-listitem-6.xml                                    |   10 
 en-US/Create_Storage-common-listitem-7.xml                                    |   10 
 en-US/Create_Storage-common-para-1.xml                                        |    8 
 en-US/Create_Storage-common-para-2.xml                                        |    8 
 en-US/Create_Storage-common-title-1.xml                                       |    8 
 en-US/Create_Storage-common-title-2.xml                                       |    8 
 en-US/Create_Storage-common-title-3.xml                                       |    8 
 en-US/Create_Storage-common-title-4.xml                                       |    8 
 en-US/Create_Storage-x86.xml                                                  |   57 
 en-US/DU-Preparing_a_driver_update_disk_ppc_x86-warning-1.xml                 |   10 
 en-US/DiskEncryptionUserGuide.xml                                             |  336 
 en-US/Disk_Partitioning-x86.xml                                               |  126 
 en-US/Disk_Partitioning_Advanced_Storage-indexterm1.xml                       |   10 
 en-US/Disk_Partitioning_Advanced_Storage-indexterm2.xml                       |   10 
 en-US/Disk_Partitioning_Advanced_Storage-x86.xml                              |   70 
 en-US/Disk_Partitioning_Advanced_Storage_common-figure-1.xml                  |   13 
 en-US/Disk_Partitioning_Advanced_Storage_common-figure-2.xml                  |   13 
 en-US/Disk_Partitioning_Advanced_Storage_common-figure-3.xml                  |   13 
 en-US/Disk_Partitioning_Advanced_Storage_common-para-1.xml                    |    7 
 en-US/Disk_Partitioning_Advanced_Storage_common-para-2.xml                    |    7 
 en-US/Disk_Partitioning_Advanced_Storage_common-para-3.xml                    |   10 
 en-US/Disk_Partitioning_Advanced_Storage_common-para-4.xml                    |    7 
 en-US/Disk_Partitioning_Advanced_Storage_common-para-5.xml                    |    7 
 en-US/Disk_Partitioning_Advanced_Storage_common-para-6.xml                    |    7 
 en-US/Disk_Partitioning_Advanced_Storage_common-title-2.xml                   |    7 
 en-US/Disk_Partitioning_Advanced_Storage_common-title-3.xml                   |    7 
 en-US/Disk_Partitioning_Advanced_Storage_common-title.xml                     |   10 
 en-US/Disk_Partitioning_Graphical_common-para-1.xml                           |   10 
 en-US/Disk_Partitioning_Graphical_common-para-2.xml                           |   11 
 en-US/Disk_Partitioning_Graphical_common-para-3.xml                           |    8 
 en-US/Disk_Partitioning_Graphical_common-para-4.xml                           |    8 
 en-US/Disk_Partitioning_Graphical_common-para-5.xml                           |    8 
 en-US/Disk_Partitioning_Graphical_common-para-6.xml                           |    8 
 en-US/Disk_Partitioning_Graphical_common-variablelist-1.xml                   |   47 
 en-US/Disk_Partitioning_Graphical_x86_ppc-para-1.xml                          |    8 
 en-US/Disk_Partitioning_Scheme-x86.xml                                        |   19 
 en-US/Disk_Partitioning_Scheme_common-indexterm-1.xml                         |   11 
 en-US/Disk_Partitioning_Scheme_common-indexterm-2.xml                         |   12 
 en-US/Disk_Partitioning_Scheme_common-indexterm-3.xml                         |   11 
 en-US/Disk_Partitioning_Scheme_common-indexterm-4.xml                         |   11 
 en-US/Disk_Partitioning_Scheme_common-indexterm-5.xml                         |    8 
 en-US/Disk_Partitioning_Scheme_common-listitem-1.xml                          |   25 
 en-US/Disk_Partitioning_Scheme_common-title.xml                               |    8 
 en-US/Disk_Partitioning_Scheme_x86_s390-para-1.xml                            |   10 
 en-US/Disk_Partitioning_Setup-x86.xml                                         |   72 
 en-US/Disk_Partitioning_Setup_common-figure-1.xml                             |   13 
 en-US/Disk_Partitioning_Setup_common-indexterm-1.xml                          |   10 
 en-US/Disk_Partitioning_Setup_common-indexterm-2.xml                          |    9 
 en-US/Disk_Partitioning_Setup_common-indexterm-6.xml                          |    8 
 en-US/Disk_Partitioning_Setup_common-indexterm-7.xml                          |    8 
 en-US/Disk_Partitioning_Setup_common-indexterm-8.xml                          |    8 
 en-US/Disk_Partitioning_Setup_common-para-1.xml                               |    8 
 en-US/Disk_Partitioning_Setup_common-para-2.xml                               |    8 
 en-US/Disk_Partitioning_Setup_common-title.xml                                |    8 
 en-US/Disk_Partitioning_X86_Partitions.xml                                    |  146 
 en-US/Disk_Partitioning_common-indexterm-1.xml                                |   11 
 en-US/Disk_Partitioning_common-indexterm-2.xml                                |    8 
 en-US/Disk_Partitioning_common-indexterm-3.xml                                |   11 
 en-US/Disk_Partitioning_common-para-1.xml                                     |    7 
 en-US/Disk_Partitioning_common-title-1.xml                                    |    8 
 en-US/Disk_Partitioning_x86_ppc-para-1.xml                                    |    7 
 en-US/Encrypt-x86.xml                                                         |   19 
 en-US/Encrypt_common-figure-1.xml                                             |   19 
 en-US/Encrypt_common-para-1.xml                                               |    7 
 en-US/Encrypt_common-para-2.xml                                               |    7 
 en-US/Encrypt_common-title-1.xml                                              |    7 
 en-US/Graphical_Installation-x86.xml                                          |  310 
 en-US/Graphical_Installation_User_Interface_x86_ppc-note-Fedora.xml           |   20 
 en-US/Graphical_Installation_User_Interface_x86_ppc-note-para-1.xml           |   10 
 en-US/Graphical_Installation_User_Interface_x86_ppc-note-para-2.xml           |   11 
 en-US/Graphical_Installation_common-list-1.xml                                |   38 
 en-US/Graphical_Installation_common-list-item-1.xml                           |   13 
 en-US/Graphical_Installation_common-list-item-2.xml                           |   13 
 en-US/Graphical_Installation_common-list-item-3.xml                           |   12 
 en-US/Graphical_Installation_common-list-item-4.xml                           |   12 
 en-US/Graphical_Installation_common-list-item-5.xml                           |   12 
 en-US/Graphical_Installation_common-list-item-6.xml                           |   13 
 en-US/Graphical_Installation_common-note-1.xml                                |   31 
 en-US/Graphical_Installation_common-note-2.xml                                |   11 
 en-US/Graphical_Installation_common-para-1.xml                                |   10 
 en-US/Graphical_Installation_common-para-2.xml                                |   10 
 en-US/Graphical_Installation_common-section-2.xml                             |   40 
 en-US/Graphical_Installation_screenshots.xml                                  |   16 
 en-US/Graphical_Installation_x86-Installation-methods.xml                     |   93 
 en-US/Graphical_Installation_x86-common-section-1.xml                         |   77 
 en-US/Graphical_Installation_x86-para-5.xml                                   |   12 
 en-US/Graphical_Installation_x86_Starting.xml                                 |  280 
 en-US/Graphical_Installation_x86_ppc-para-1.xml                               |   10 
 en-US/Graphical_Installation_x86_ppc-para-3.xml                               |    9 
 en-US/Graphical_Installation_x86_ppc-para-4.xml                               |   10 
 en-US/Graphical_Installation_x86_ppc-para-6.xml                               |    9 
 en-US/Graphical_Installation_x86_ppc-table-1-title.xml                        |    8 
 en-US/Graphical_and_Text_Interfaces.xml                                       |   49 
 en-US/Grub.xml                                                                | 1111 --
 en-US/Important-Enable_EPEL.xml                                               |   14 
 en-US/Important-Kickstart_and_Firstboot.xml                                   |   10 
 en-US/Important_UEFI.xml                                                      |   14 
 en-US/Initializing_Hard_Disk-x86.xml                                          |   40 
 en-US/Initializing_Hard_Disk_common-indexterm.xml                             |    9 
 en-US/Initializing_Hard_Disk_common-note-1.xml                                |   12 
 en-US/Initializing_Hard_Disk_common-para-1.xml                                |    9 
 en-US/Initializing_Hard_Disk_common-para-2.xml                                |    9 
 en-US/Initializing_Hard_Disk_common-para-3.xml                                |    9 
 en-US/Initializing_Hard_Disk_common-title.xml                                 |    6 
 en-US/Installation_Guide.ent                                                  |    6 
 en-US/Installation_Guide.xml                                                  |  148 
 en-US/Installation_Method-x86.xml                                             |   44 
 en-US/Installation_Method_common-indexterm.xml                                |    9 
 en-US/Installation_Method_common-title.xml                                    |    6 
 en-US/Installing_Packages-x86.xml                                             |   27 
 en-US/Installing_Packages_common-note-1.xml                                   |   13 
 en-US/Installing_Packages_common-para-1.xml                                   |    7 
 en-US/Installing_Packages_common-para-2.xml                                   |   12 
 en-US/Installing_Packages_common-para-2a.xml                                  |   17 
 en-US/Installing_Packages_common-para-3.xml                                   |   10 
 en-US/Installing_Packages_common-title.xml                                    |    8 
 en-US/Key_Board_Configuration-x86.xml                                         |   41 
 en-US/Key_Board_Configuration_x86_ppc-indexterm-1.xml                         |   11 
 en-US/Key_Board_Configuration_x86_ppc-indexterm-2.xml                         |   11 
 en-US/Key_Board_Configuration_x86_ppc-para-1.xml                              |   10 
 en-US/Key_Board_Configuration_x86_ppc-para-2.xml                              |   15 
 en-US/Key_Board_Configuration_x86_ppc-title-1.xml                             |    8 
 en-US/Kickstart-note-1.xml                                                    |    9 
 en-US/Kickstart2.xml                                                          | 3680 ---------
 en-US/Ksconfig.xml                                                            |  828 --
 en-US/Language_Selection-x86.xml                                              |   44 
 en-US/Language_Selection_common-indexterm.xml                                 |    8 
 en-US/Language_Selection_common-para-1.xml                                    |    7 
 en-US/Language_Selection_common-para-2.xml                                    |    7 
 en-US/Language_Selection_common-para-3.xml                                    |    9 
 en-US/Language_Selection_common-title.xml                                     |    5 
 en-US/Making_Fedora_Media.xml                                                 |   77 
 en-US/Making_USB_media.xml                                                    |  282 
 en-US/Netboot_DHCP.xml                                                        |   37 
 en-US/Netboot_TFTP.xml                                                        |   27 
 en-US/Netconfig_common-figure-2.xml                                           |   16 
 en-US/Netconfig_common-para-7.xml                                             |    9 
 en-US/Netconfig_common-para-8.xml                                             |    9 
 en-US/Netconfig_common-para-9.xml                                             |    9 
 en-US/Netconfig_common-title-2.xml                                            |    7 
 en-US/Note-Multiple_NICs_and_PXE.xml                                          |   21 
 en-US/Note_Aborting_Installation.xml                                          |   11 
 en-US/Note_Nondestructive_Method.xml                                          |   11 
 en-US/Other_Disk_Devices-common-note-1.xml                                    |   10 
 en-US/Other_Disk_Devices-common-para-1.xml                                    |    7 
 en-US/Other_Disk_Devices-common-para-2.xml                                    |    8 
 en-US/Other_Disk_Devices-common-para-3.xml                                    |    7 
 en-US/Other_Disk_Devices-common-title-1.xml                                   |    7 
 en-US/Other_Disk_Devices-common-title-2.xml                                   |    7 
 en-US/Other_Disk_Devices-common-title-3.xml                                   |    7 
 en-US/Other_Disk_Devices-common-title-4.xml                                   |    7 
 en-US/Other_Disk_Devices-x86.xml                                              |   57 
 en-US/Package_Selection-x86.xml                                               |   90 
 en-US/Package_Selection_Customizing-x86.xml                                   |  186 
 en-US/Package_Selection_Repositories-x86.xml                                  |  108 
 en-US/Package_Selection_common-imagecap-1.xml                                 |   10 
 en-US/Package_Selection_common-imagecap-2.xml                                 |    7 
 en-US/Package_Selection_common-imagecap-3.xml                                 |    7 
 en-US/Package_Selection_common-indexterm-1.xml                                |   11 
 en-US/Package_Selection_common-indexterm-2.xml                                |   11 
 en-US/Package_Selection_common-indexterm-3.xml                                |   11 
 en-US/Package_Selection_common-indexterm-4.xml                                |   10 
 en-US/Package_Selection_common-indexterm-5.xml                                |   11 
 en-US/Package_Selection_common-indexterm-6.xml                                |   12 
 en-US/Package_Selection_common-list-1.xml                                     |   37 
 en-US/Package_Selection_common-note-1.xml                                     |   15 
 en-US/Package_Selection_common-note-2.xml                                     |   14 
 en-US/Package_Selection_common-para-1.xml                                     |   10 
 en-US/Package_Selection_common-para-2.xml                                     |    7 
 en-US/Package_Selection_common-para-3.xml                                     |   10 
 en-US/Package_Selection_common-para-4.xml                                     |   10 
 en-US/Package_Selection_common-para-7.xml                                     |   11 
 en-US/Package_Selection_common-title-1.xml                                    |    8 
 en-US/Partitions-x86.xml                                                      | 1080 --
 en-US/Partitions_common-caution-1.xml                                         |   15 
 en-US/Partitions_common-imagecap-1.xml                                        |    9 
 en-US/Partitions_common-imagecap-10.xml                                       |   10 
 en-US/Partitions_common-imagecap-2.xml                                        |    9 
 en-US/Partitions_common-imagecap-3.xml                                        |    9 
 en-US/Partitions_common-imagecap-4.xml                                        |    9 
 en-US/Partitions_common-imagecap-5.xml                                        |    9 
 en-US/Partitions_common-imagecap-6.xml                                        |    9 
 en-US/Partitions_common-imagecap-7.xml                                        |    9 
 en-US/Partitions_common-imagecap-8.xml                                        |    9 
 en-US/Partitions_common-imagecap-9.xml                                        |    9 
 en-US/Partitions_common-indexterm-1.xml                                       |   11 
 en-US/Partitions_common-indexterm-10.xml                                      |   11 
 en-US/Partitions_common-indexterm-11.xml                                      |   11 
 en-US/Partitions_common-indexterm-12.xml                                      |   11 
 en-US/Partitions_common-indexterm-13.xml                                      |   10 
 en-US/Partitions_common-indexterm-14.xml                                      |   11 
 en-US/Partitions_common-indexterm-15.xml                                      |   11 
 en-US/Partitions_common-indexterm-16.xml                                      |   11 
 en-US/Partitions_common-indexterm-17.xml                                      |   11 
 en-US/Partitions_common-indexterm-18.xml                                      |   11 
 en-US/Partitions_common-indexterm-19.xml                                      |   11 
 en-US/Partitions_common-indexterm-2.xml                                       |   11 
 en-US/Partitions_common-indexterm-3.xml                                       |   11 
 en-US/Partitions_common-indexterm-4.xml                                       |   11 
 en-US/Partitions_common-indexterm-5.xml                                       |   11 
 en-US/Partitions_common-indexterm-6.xml                                       |   11 
 en-US/Partitions_common-indexterm-7.xml                                       |   11 
 en-US/Partitions_common-indexterm-8.xml                                       |   11 
 en-US/Partitions_common-indexterm-9.xml                                       |   11 
 en-US/Partitions_common-itemizedlist-1.xml                                    |   24 
 en-US/Partitions_common-itemizedlist-2.xml                                    |   26 
 en-US/Partitions_common-itemizedlist-3.xml                                    |   26 
 en-US/Partitions_common-note-1.xml                                            |   14 
 en-US/Partitions_common-note-3.xml                                            |   11 
 en-US/Partitions_common-para-1.xml                                            |   10 
 en-US/Partitions_common-para-10.xml                                           |   10 
 en-US/Partitions_common-para-11.xml                                           |   11 
 en-US/Partitions_common-para-12.xml                                           |   11 
 en-US/Partitions_common-para-13.xml                                           |   10 
 en-US/Partitions_common-para-14.xml                                           |   11 
 en-US/Partitions_common-para-15.xml                                           |   10 
 en-US/Partitions_common-para-16.xml                                           |    8 
 en-US/Partitions_common-para-17.xml                                           |   10 
 en-US/Partitions_common-para-18.xml                                           |   10 
 en-US/Partitions_common-para-19.xml                                           |   10 
 en-US/Partitions_common-para-2.xml                                            |   10 
 en-US/Partitions_common-para-20.xml                                           |   10 
 en-US/Partitions_common-para-21.xml                                           |   11 
 en-US/Partitions_common-para-22.xml                                           |   11 
 en-US/Partitions_common-para-23.xml                                           |   10 
 en-US/Partitions_common-para-24.xml                                           |   11 
 en-US/Partitions_common-para-3.xml                                            |   10 
 en-US/Partitions_common-para-4.xml                                            |   11 
 en-US/Partitions_common-para-5.xml                                            |   10 
 en-US/Partitions_common-para-6.xml                                            |   10 
 en-US/Partitions_common-para-7.xml                                            |   10 
 en-US/Partitions_common-para-8.xml                                            |   10 
 en-US/Partitions_common-para-9.xml                                            |   10 
 en-US/Partitions_common-table-title-1.xml                                     |    8 
 en-US/Partitions_common-term-1.xml                                            |   12 
 en-US/Partitions_common-title-10.xml                                          |    8 
 en-US/Partitions_common-title-2.xml                                           |    8 
 en-US/Partitions_common-title-3.xml                                           |    8 
 en-US/Partitions_common-title-4.xml                                           |    8 
 en-US/Partitions_common-title-5.xml                                           |    8 
 en-US/Partitions_common-title-6.xml                                           |    5 
 en-US/Partitions_common-title-7.xml                                           |    8 
 en-US/Partitions_common-title-8.xml                                           |    8 
 en-US/Partitions_common-title-9.xml                                           |    8 
 en-US/Partitions_common-title.xml                                             |    8 
 en-US/Partitions_complete-note-1.xml                                          |   14 
 en-US/Preface.xml                                                             |   13 
 en-US/Prepare_To_Install-common-Boot_Media.xml                                |    8 
 en-US/Procedure-dd_Image_to_USB.xml                                           |   30 
 en-US/Rescue_Mode.xml                                                         |  400 -
 en-US/Revision_History.xml                                                    |   26 
 en-US/Specialized_Storage_Devices-x86.xml                                     |   52 
 en-US/Specialized_Storage_Devices_common-figure-1.xml                         |   14 
 en-US/Specialized_Storage_Devices_common-figure-2.xml                         |   14 
 en-US/Specialized_Storage_Devices_common-figure-3.xml                         |   14 
 en-US/Specialized_Storage_Devices_common-para-1.xml                           |    7 
 en-US/Specialized_Storage_Devices_common-para-2.xml                           |    7 
 en-US/Specialized_Storage_Devices_common-para-3.xml                           |    7 
 en-US/Specialized_Storage_Devices_common-para-4.xml                           |    7 
 en-US/Specialized_Storage_Devices_common-para-5.xml                           |    7 
 en-US/Specialized_Storage_Devices_common-para-6.xml                           |    7 
 en-US/Specialized_Storage_Devices_common-title.xml                            |    8 
 en-US/Specialized_Storage_Devices_common-variablelist-1.xml                   |   38 
 en-US/Steps-x86.xml                                                           |   29 
 en-US/Steps_Cdrom-x86.xml                                                     |  114 
 en-US/Steps_Cdrom_x86_ppc_preamble.xml                                        |    7 
 en-US/Steps_Diskspace-x86.xml                                                 |   39 
 en-US/Steps_Diskspace_x86_ppc_Itemized_List.xml                               |   23 
 en-US/Steps_Diskspace_x86_ppc_oneline_paragraph.xml                           |    9 
 en-US/Steps_Hardware-x86.xml                                                  |   29 
 en-US/Steps_Hd_Install-x86.xml                                                |   82 
 en-US/Steps_Hd_Install_x86_note_1.xml                                         |   19 
 en-US/Steps_Hd_Install_x86_ppc_note_1.xml                                     |   14 
 en-US/Steps_Hd_Install_x86_ppc_note_para_1.xml                                |    9 
 en-US/Steps_Hd_Install_x86_ppc_para_1.xml                                     |    7 
 en-US/Steps_Hd_Install_x86_ppc_s390_listitem_1.xml                            |    7 
 en-US/Steps_Hd_Install_x86_ppc_s390_listitem_1a.xml                           |    6 
 en-US/Steps_Hd_Install_x86_ppc_s390_listitem_2.xml                            |   10 
 en-US/Steps_Hd_Install_x86_ppc_s390_listitem_2b.xml                           |   10 
 en-US/Steps_Hd_Install_x86_ppc_s390_para_1.xml                                |   12 
 en-US/Steps_Hd_Install_x86_ppc_s390_para_2.xml                                |    7 
 en-US/Steps_Network_Install-x86.xml                                           |   73 
 en-US/Steps_Network_Install_x86_ppc_note.xml                                  |   14 
 en-US/Steps_Network_Install_x86_ppc_note_2.xml                                |   15 
 en-US/Steps_Network_Install_x86_ppc_s390_itemized_list_1.xml                  |   60 
 en-US/Steps_Network_Install_x86_ppc_s390_note_1.xml                           |   11 
 en-US/Steps_Network_Install_x86_ppc_s390_para_1.xml                           |    7 
 en-US/Steps_Network_Install_x86_ppc_s390_para_2.xml                           |   10 
 en-US/Steps_Network_Install_x86_ppc_s390_para_3.xml                           |   10 
 en-US/Steps_Network_Install_x86_ppc_s390_section_1.xml                        |   58 
 en-US/Steps_Network_Install_x86_ppc_s390_section_2.xml                        |   71 
 en-US/Steps_Upgrade-common.xml                                                |   11 
 en-US/Storage_Devices-x86.xml                                                 |   33 
 en-US/Storage_Devices_common-figure-1.xml                                     |   14 
 en-US/Storage_Devices_common-indexterm-1.xml                                  |   12 
 en-US/Storage_Devices_common-indexterm-2.xml                                  |   12 
 en-US/Storage_Devices_common-para-1.xml                                       |    8 
 en-US/Storage_Devices_common-title.xml                                        |    6 
 en-US/Storage_Devices_common-variablelist-1.xml                               |   55 
 en-US/Swap_Partrecommend.xml                                                  |   59 
 en-US/System_Requirements_Table.xml                                           |  148 
 en-US/Systems_with_Intel_BIOS_RAID.xml                                        |   14 
 en-US/Time_Zone-x86.xml                                                       |   53 
 en-US/Time_Zone_common-figure-1.xml                                           |   13 
 en-US/Time_Zone_common-indexterm-1.xml                                        |    8 
 en-US/Time_Zone_common-indexterm-2.xml                                        |   10 
 en-US/Time_Zone_common-indexterm-3.xml                                        |   11 
 en-US/Time_Zone_common-indexterm-4.xml                                        |   11 
 en-US/Time_Zone_common-indexterm-5.xml                                        |   11 
 en-US/Time_Zone_common-indexterm-6.xml                                        |   11 
 en-US/Time_Zone_common-indexterm-7.xml                                        |    8 
 en-US/Time_Zone_common-itemizedlist-1.xml                                     |   20 
 en-US/Time_Zone_common-note-1.xml                                             |   15 
 en-US/Time_Zone_common-para-1.xml                                             |   10 
 en-US/Time_Zone_common-para-2.xml                                             |   10 
 en-US/Time_Zone_common-para-4.xml                                             |   10 
 en-US/Time_Zone_common-para-5.xml                                             |   13 
 en-US/Time_Zone_common-para-6.xml                                             |    8 
 en-US/Time_Zone_common-tip-1.xml                                              |   15 
 en-US/Time_Zone_common-title.xml                                              |    5 
 en-US/Trouble-x86.xml                                                         |  313 
 en-US/Trouble_After_Booting_GUI-indexterm-1.xml                               |   12 
 en-US/Trouble_After_Booting_GUI-indexterm-2.xml                               |   12 
 en-US/Trouble_After_Booting_GUI-indexterm-3.xml                               |   12 
 en-US/Trouble_After_Booting_GUI-para-1.xml                                    |    8 
 en-US/Trouble_After_Booting_GUI-para-10.xml                                   |   10 
 en-US/Trouble_After_Booting_GUI-para-2.xml                                    |   10 
 en-US/Trouble_After_Booting_GUI-para-3.xml                                    |   10 
 en-US/Trouble_After_Booting_GUI-para-4.xml                                    |   11 
 en-US/Trouble_After_Booting_GUI-para-5.xml                                    |   10 
 en-US/Trouble_After_Booting_GUI-para-6.xml                                    |   11 
 en-US/Trouble_After_Booting_GUI-para-7.xml                                    |   11 
 en-US/Trouble_After_Booting_GUI-para-8.xml                                    |   10 
 en-US/Trouble_After_Booting_GUI-para-9.xml                                    |   13 
 en-US/Trouble_After_Booting_GUI-screen-1.xml                                  |   14 
 en-US/Trouble_After_Booting_GUI-screen-2.xml                                  |   10 
 en-US/Trouble_After_Booting_GUI-warning-1.xml                                 |   14 
 en-US/Trouble_After_Booting_GUI_x86_ppc-title-1.xml                           |    8 
 en-US/Trouble_After_Booting_Problems-Apache.xml                               |   24 
 en-US/Trouble_After_Booting_Problems-Printer.xml                              |   22 
 en-US/Trouble_After_Booting_Problems_Login-indexterm-1.xml                    |   12 
 en-US/Trouble_After_Booting_Problems_Login-para-1.xml                         |    7 
 en-US/Trouble_After_Booting_Problems_Login-para-10.xml                        |   11 
 en-US/Trouble_After_Booting_Problems_Login-para-11.xml                        |    7 
 en-US/Trouble_After_Booting_Problems_Login-para-2.xml                         |   10 
 en-US/Trouble_After_Booting_Problems_Login-para-4.xml                         |   11 
 en-US/Trouble_After_Booting_Problems_Login-para-5.xml                         |   10 
 en-US/Trouble_After_Booting_Problems_Login-para-6.xml                         |   10 
 en-US/Trouble_After_Booting_Problems_Login-para-7.xml                         |   10 
 en-US/Trouble_After_Booting_Problems_Login-para-8.xml                         |   10 
 en-US/Trouble_After_Booting_Problems_Login-para-9.xml                         |   12 
 en-US/Trouble_After_Booting_Problems_Login-screen-1.xml                       |   10 
 en-US/Trouble_After_Booting_Problems_Login-screen-2.xml                       |   12 
 en-US/Trouble_After_Booting_Problems_Login-title-1.xml                        |    8 
 en-US/Trouble_After_Booting_X_Server_Non_Root.xml                             |   32 
 en-US/Trouble_After_Booting_X_Windows.xml                                     |   26 
 en-US/Trouble_After_Ram.xml                                                   |   89 
 en-US/Trouble_After_common-indexterm-1.xml                                    |   11 
 en-US/Trouble_After_common-title-1.xml                                        |    8 
 en-US/Trouble_Begin_GUI-indexterm-1.xml                                       |   12 
 en-US/Trouble_Begin_GUI-indexterm-2.xml                                       |   12 
 en-US/Trouble_Begin_GUI-note-1.xml                                            |   14 
 en-US/Trouble_Begin_GUI-para-1.xml                                            |   11 
 en-US/Trouble_Begin_GUI-title.xml                                             |    8 
 en-US/Trouble_Begin_x86_ppc_indexterm-1.xml                                   |   10 
 en-US/Trouble_Begin_x86_ppc_title-1.xml                                       |    8 
 en-US/Trouble_During-x86.xml                                                  |  119 
 en-US/Trouble_During_common-other-partitioning-indexterm-1.xml                |   12 
 en-US/Trouble_During_common-other-partitioning-listitem-1.xml                 |   12 
 en-US/Trouble_During_common-other-partitioning-listitem-3.xml                 |   12 
 en-US/Trouble_During_common-other-partitioning-para-1.xml                     |    7 
 en-US/Trouble_During_common-other-partitioning-para-2.xml                     |   10 
 en-US/Trouble_During_common-other-partitioning-tip-1.xml                      |    9 
 en-US/Trouble_During_common-other-partitioning-title-1.xml                    |    8 
 en-US/Trouble_During_common-partitions-indexterm-1.xml                        |   12 
 en-US/Trouble_During_common-partitions-indexterm-2.xml                        |   13 
 en-US/Trouble_During_common-partitions-para-1.xml                             |    9 
 en-US/Trouble_During_common-partitions-para-2.xml                             |   10 
 en-US/Trouble_During_common-partitions-para-3.xml                             |   10 
 en-US/Trouble_During_common-python-errors.xml                                 |   66 
 en-US/Trouble_During_common-title-1.xml                                       |    6 
 en-US/Trouble_During_x86_ppc-para-1.xml                                       |    8 
 en-US/Trouble_During_x86_ppc-para-3.xml                                       |    7 
 en-US/Trouble_During_x86_ppc-screen-1.xml                                     |    8 
 en-US/Trouble_During_x86_ppc-section-2-figure-1.xml                           |   13 
 en-US/Trouble_During_x86_ppc-section-2-indexterms-2.xml                       |    8 
 en-US/Trouble_During_x86_ppc-section-2-indexterms-3.xml                       |    8 
 en-US/Trouble_During_x86_ppc-section-2-indexterms.xml                         |    9 
 en-US/Trouble_During_x86_ppc-section-2-para-1.xml                             |    8 
 en-US/Trouble_During_x86_ppc-section-2-para-2.xml                             |   60 
 en-US/Trouble_During_x86_ppc-section-2-variablelist-1.xml                     |   48 
 en-US/Trouble_During_x86_ppc-sectiontitle-2.xml                               |    5 
 en-US/Trouble_No_Boot-Sig11-indexterm-1.xml                                   |   12 
 en-US/Trouble_No_Boot-Sig11-para-1.xml                                        |   10 
 en-US/Trouble_No_Boot-Sig11-para-2.xml                                        |    7 
 en-US/Trouble_No_Boot-Sig11-para-3.xml                                        |    7 
 en-US/Trouble_No_Boot-Sig11-para-7.xml                                        |    7 
 en-US/Trouble_No_Boot-Sig11-para-8.xml                                        |   10 
 en-US/Trouble_No_Boot-Sig11-screen-2.xml                                      |   10 
 en-US/Trouble_No_Boot-Sig11-screen-3.xml                                      |   10 
 en-US/Trouble_No_Boot-Sig11-title-1.xml                                       |    8 
 en-US/Trouble_No_Boot-indexterm-1.xml                                         |   11 
 en-US/Trouble_No_Boot-title-1.xml                                             |    5 
 en-US/Trouble_common-indexterm-1.xml                                          |    7 
 en-US/Trouble_common-indexterm-2.xml                                          |    7 
 en-US/Trouble_common-indexterm-3.xml                                          |    7 
 en-US/Trouble_common-indexterm-4.xml                                          |    7 
 en-US/Trouble_common-indexterm-5.xml                                          |    7 
 en-US/Trouble_common-indexterm-6.xml                                          |    7 
 en-US/Trouble_common-indexterm-7.xml                                          |    7 
 en-US/Trouble_common-indexterm-8.xml                                          |    7 
 en-US/Trouble_common-para-1.xml                                               |    8 
 en-US/Trouble_common-para-2.xml                                               |    8 
 en-US/Trouble_common-para-3.xml                                               |    7 
 en-US/Trouble_common-variablelist-1.xml                                       |   46 
 en-US/Understanding_LVM.xml                                                   |   77 
 en-US/Upgrade-x86.xml                                                         |   50 
 en-US/Upgrade_common-para-1.xml                                               |    7 
 en-US/Upgrade_common-section-1.xml                                            |  100 
 en-US/Upgrade_common-section-2-note-1.xml                                     |   20 
 en-US/Upgrade_common-section-2-para-1.xml                                     |   10 
 en-US/Upgrade_common-section-2-para-2.xml                                     |    8 
 en-US/Upgrade_common-section-2-title.xml                                      |    8 
 en-US/Upgrade_common-title-1.xml                                              |    8 
 en-US/Upgrading-common-figure-1.xml                                           |   14 
 en-US/Upgrading-common-figure-2.xml                                           |   14 
 en-US/Upgrading-common-indexterm-1.xml                                        |   11 
 en-US/Upgrading-common-note-1.xml                                             |   11 
 en-US/Upgrading-common-note-2.xml                                             |   12 
 en-US/Upgrading-common-para-1.xml                                             |    9 
 en-US/Upgrading-common-para-2.xml                                             |    8 
 en-US/Upgrading-common-para-3.xml                                             |    9 
 en-US/Upgrading-common-para-4.xml                                             |    9 
 en-US/Upgrading-common-para-5.xml                                             |    9 
 en-US/Upgrading-common-para-6.xml                                             |    9 
 en-US/Upgrading-common-para-7.xml                                             |    9 
 en-US/Upgrading-common-para-8.xml                                             |   10 
 en-US/Upgrading-common-para-9.xml                                             |   11 
 en-US/Upgrading-common-screen-1.xml                                           |    8 
 en-US/Upgrading-common-screen-2.xml                                           |    8 
 en-US/Upgrading-common-title-1.xml                                            |    8 
 en-US/Upgrading-common-title-2.xml                                            |    8 
 en-US/Upgrading-common-title-3.xml                                            |    8 
 en-US/Upgrading-common-title-4.xml                                            |    8 
 en-US/Upgrading-common-warning-1.xml                                          |   13 
 en-US/Verifying_Media.xml                                                     |   15 
 en-US/Welcome-x86.xml                                                         |   22 
 en-US/Write_changes_to_disk.xml                                               |   34 
 en-US/X86_Bios_Tip.xml                                                        |   19 
 en-US/X86_Bootloader.xml                                                      |  510 -
 en-US/X86_Trouble_After_Grub.xml                                              |   39 
 en-US/X86_Uninstall-Linux-bootloader.xml                                      |   62 
 en-US/X86_Uninstall-Linux-expand-lvm.xml                                      |  115 
 en-US/X86_Uninstall-Linux-expand-nolvm.xml                                    |   55 
 en-US/X86_Uninstall-Linux-expand.xml                                          |   24 
 en-US/X86_Uninstall-Linux-partitions.xml                                      |   27 
 en-US/X86_Uninstall-Linux.xml                                                 |   18 
 en-US/X86_Uninstall-Mac.xml                                                   |   62 
 en-US/X86_Uninstall-Windows-2000XP2003.xml                                    |  129 
 en-US/X86_Uninstall-Windows-Vista2008.xml                                     |  109 
 en-US/X86_Uninstall-Windows-add-title-1.xml                                   |    5 
 en-US/X86_Uninstall-Windows-bootloader-para-1.xml                             |    7 
 en-US/X86_Uninstall-Windows-bootloader-para-2.xml                             |    7 
 en-US/X86_Uninstall-Windows-bootloader-para-3.xml                             |    7 
 en-US/X86_Uninstall-Windows-bootloader-para-4.xml                             |    7 
 en-US/X86_Uninstall-Windows-extend-note-1.xml                                 |    9 
 en-US/X86_Uninstall-Windows-extend-para-1.xml                                 |    7 
 en-US/X86_Uninstall-Windows-extend-para-2.xml                                 |    7 
 en-US/X86_Uninstall-Windows-extend-title-1.xml                                |    5 
 en-US/X86_Uninstall-Windows-remove-para-1.xml                                 |    7 
 en-US/X86_Uninstall-Windows-remove-para-2.xml                                 |    7 
 en-US/X86_Uninstall-Windows-remove-para-3.xml                                 |    7 
 en-US/X86_Uninstall-Windows-remove-para-4.xml                                 |    7 
 en-US/X86_Uninstall-Windows-warning-para-1.xml                                |    7 
 en-US/X86_Uninstall-msdos.xml                                                 |   75 
 en-US/X86_Uninstall-single.xml                                                |   47 
 en-US/X86_Uninstall.xml                                                       |   75 
 en-US/adminoptions.xml                                                        |  905 --
 en-US/expert-quickstart.xml                                                   |  137 
 en-US/ext4-and-btrfs.xml                                                      |   11 
 en-US/firstboot.xml                                                           |  198 
 en-US/iSCSI.xml                                                               |   60 
 en-US/images/boot/.svn/all-wcprops                                            |   11 
 en-US/images/boot/.svn/entries                                                |   62 
 en-US/images/boot/.svn/prop-base/boot_screen.png.svn-base                     |    5 
 en-US/images/encrypt/.svn/all-wcprops                                         |   11 
 en-US/images/encrypt/.svn/entries                                             |   62 
 en-US/images/encrypt/.svn/prop-base/passphrase.png.svn-base                   |    5 
 en-US/images/icon.svg                                                         | 3936 ----------
 en-US/images/installationmethod/.svn/all-wcprops                              |   11 
 en-US/images/installationmethod/.svn/entries                                  |   62 
 en-US/images/installationmethod/.svn/prop-base/method.png.svn-base            |    5 
 en-US/images/storagedevices/.svn/all-wcprops                                  |   35 
 en-US/images/storagedevices/.svn/entries                                      |  198 
 en-US/images/storagedevices/.svn/prop-base/assignstoragedevices.png.svn-base  |    5 
 en-US/images/storagedevices/.svn/prop-base/searchstoragedevices.png.svn-base  |    5 
 en-US/images/storagedevices/.svn/prop-base/selectstoragedevices.png.svn-base  |    5 
 en-US/images/storagedevices/.svn/prop-base/storagedevices.png.svn-base        |    5 
 en-US/images/storagedevices/.svn/prop-base/storagedevicescolumns.png.svn-base |    5 
 en-US/intro.xml                                                               |   69 
 en-US/medialess.xml                                                           |  136 
 en-US/networkconfig-fedora.xml                                                |  158 
 en-US/new-users.xml                                                           |  315 
 en-US/nextsteps.xml                                                           |  591 -
 en-US/pxe-server-manual.xml                                                   |  427 -
 en-US/pxe-server-para-1.xml                                                   |    7 
 en-US/pxe-server-para-2.xml                                                   |    7 
 en-US/pxe-server.xml                                                          |  223 
 en-US/techref.xml                                                             |  240 
 en-US/upgrading-fedora.xml                                                    |  114 
 en-US/vnc_Installation_Chapter.xml                                            |  239 
 en-US/vnc_Modes_Chapter.xml                                                   |  134 
 en-US/vnc_References_Chapter.xml                                              |   39 
 en-US/vnc_VNC_Whitepaper.xml                                                  |   75 
 en-US/vnc_Viewer_Chapter.xml                                                  |   69 
 publican.cfg                                                                  |    7 
 694 files changed, 30221 deletions(-)

New commits:
commit ab19f170bf32e0ba4837b79d2d6b211a9493aefa
Author: Ruediger Landmann <r.landmann at redhat.com>
Date:   Sun May 30 10:17:59 2010 +1000

    clean out later content

diff --git a/en-US/.directory b/en-US/.directory
deleted file mode 100644
index c57e9e6..0000000
--- a/en-US/.directory
+++ /dev/null
@@ -1,4 +0,0 @@
-[Dolphin]
-AdditionalInfo=3
-Timestamp=2009,9,30,1,24,1
-ViewMode=1
diff --git a/en-US/Account_Configuration-common.xml b/en-US/Account_Configuration-common.xml
deleted file mode 100644
index 1a6fc4f..0000000
--- a/en-US/Account_Configuration-common.xml
+++ /dev/null
@@ -1,82 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<section id="sn-account_configuration">
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Account_Configuration_common-title.xml"/>
-	<!-- Account Configuration -->
-	<indexterm significance="normal">
-		<primary>root password</primary>
-	</indexterm>
-	<indexterm significance="normal">
-		<primary>password</primary>
-		<secondary>setting root</secondary>
-	</indexterm>
-	<para>
-		Setting up a root account and password is one of the most important steps during your installation. Your root account is similar to the administrator account used on Microsoft Windows machines. The root account is used to install packages, upgrade RPMs, and perform most system maintenance. Logging in as root gives you complete control over your system.
-	</para>
-	 
-	<note>
-		<title>Note</title>
-
-		<para>
-			The root user (also known as the superuser) has complete access to the entire system; for this reason, logging in as the root user is best done <emphasis>only</emphasis> to perform system maintenance or administration.
-		</para>
-	</note>
-	<figure float="0"><title>Root Password</title>
-		<mediaobject>
-			<imageobject><imagedata fileref="images/accountconfig/rootpassword.png" format="PNG"/></imageobject>
-			<textobject><para>
-					Setting your root password.
-				</para>
-			</textobject>
-		</mediaobject>
-	</figure>
-	<para>
-		Use the root account only for system administration. Create a non-root account for your general use and <command>su -</command> to root when you need to fix something quickly. These basic rules minimize the chances of a typo or an
-		incorrect command doing damage to your system.
-	</para>
-	<note><title>Note</title>
-		<para>
-			To become root, type <command>su -</command> at the shell prompt in a terminal window and then press <keycap >Enter</keycap>. Then, enter the root password and press <keycap >Enter</keycap>.
-		</para>
-	</note>
-	<para>
-		The installation program prompts you to set a root password<footnote>
-		<para>
-			A root password is the administrative password for your Fedora system. You should only log in as root when needed for system maintenance. The root account does not operate within the restrictions placed on normal user accounts, so
-			changes made as root can have implications for your entire system.
-		</para>
-		</footnote> for your system. <emphasis>You cannot proceed to the next stage of the installation process without entering a root password.</emphasis>
-	</para>
-	 
-	<para>
-		The root password must be at least six characters long; the password you type is not echoed to the screen. You must enter the password twice; if the two passwords do not match, the installation program asks you to enter them again.
-	</para>
-	 
-	<para>
-		You should make the root password something you can remember, but not something that is easy for someone else to guess. Your name, your phone number, <firstterm>qwerty</firstterm>, <firstterm>password, root</firstterm>, <firstterm>123456</firstterm>, and
-		<firstterm>anteater</firstterm> are all examples of bad passwords. Good passwords mix numerals with upper and lower case letters and do not contain dictionary words: <firstterm>Aard387vark</firstterm> or <firstterm>420BMttNT</firstterm>, for example.
-		Remember that the password is case-sensitive. If you write down your password, keep it in a secure place. However, it is recommended that you do not write down this or any password you create.
-	</para>
-	 
-	<note>
-		<title>Note</title>
-
-		<para>
-			Do not use one of the example passwords offered in this manual. Using one of these passwords could be considered a security risk.
-		</para>
-	</note>
-	<note><title>Note</title>
-		<para>
-			To change your root password after you have completed the installation, use the <application>Root Password Tool</application>.
-		</para>
-		<para>
-			Type the <command >system-config-rootpassword</command> command in a shell prompt to launch the <application>Root Password Tool</application>. If you are not root, it prompts you for the root password to continue.
-		</para>
-	</note>
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Account_Configuration_common-para-6.xml"/>
-	<!-- Enter the root password into the Root Password field.... -->
-	
-</section>
diff --git a/en-US/Account_Configuration_common-para-6.xml b/en-US/Account_Configuration_common-para-6.xml
deleted file mode 100644
index 62917bb..0000000
--- a/en-US/Account_Configuration_common-para-6.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
- "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
-]>
-
-<!-- $Id: -->
-
-  <para>
-    Enter the <systemitem class="username">root</systemitem> password
-    into the <guilabel>Root Password</guilabel> field.  Fedora displays
-    the characters as asterisks for security.  Type the same password
-    into the <guilabel>Confirm</guilabel> field to ensure it is set
-    correctly. After you set the root password, select
-    <guibutton>Next</guibutton> to proceed.
-  </para>
diff --git a/en-US/Account_Configuration_common-title.xml b/en-US/Account_Configuration_common-title.xml
deleted file mode 100644
index 29c6c9d..0000000
--- a/en-US/Account_Configuration_common-title.xml
+++ /dev/null
@@ -1,5 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE title PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<title>Set the Root Password</title>
\ No newline at end of file
diff --git a/en-US/Adding_Partitions-section-2-indexterm-1.xml b/en-US/Adding_Partitions-section-2-indexterm-1.xml
deleted file mode 100644
index 2bf145f..0000000
--- a/en-US/Adding_Partitions-section-2-indexterm-1.xml
+++ /dev/null
@@ -1,10 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE indexterm PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<indexterm significance="normal">
-	<primary>file system types</primary>
-</indexterm>
\ No newline at end of file
diff --git a/en-US/Adding_Partitions-section-2-indexterm-2.xml b/en-US/Adding_Partitions-section-2-indexterm-2.xml
deleted file mode 100644
index 520afac..0000000
--- a/en-US/Adding_Partitions-section-2-indexterm-2.xml
+++ /dev/null
@@ -1,12 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE indexterm PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<indexterm significance="normal">
-	<primary>partitioning</primary>
-	<secondary>creating new</secondary>
-	<tertiary>file system type</tertiary>
-</indexterm>
\ No newline at end of file
diff --git a/en-US/Adding_Partitions-section-2-indexterm-3.xml b/en-US/Adding_Partitions-section-2-indexterm-3.xml
deleted file mode 100644
index 773ec45..0000000
--- a/en-US/Adding_Partitions-section-2-indexterm-3.xml
+++ /dev/null
@@ -1,10 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE indexterm PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<indexterm significance="normal">
-	<primary><application>Partitioning</application>
-	</primary>
-	<secondary>adding partitions</secondary>
-	<tertiary>file system type</tertiary>
-</indexterm>
\ No newline at end of file
diff --git a/en-US/Adding_Partitions-section-2-indexterm-4.xml b/en-US/Adding_Partitions-section-2-indexterm-4.xml
deleted file mode 100644
index 66bfb67..0000000
--- a/en-US/Adding_Partitions-section-2-indexterm-4.xml
+++ /dev/null
@@ -1,11 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE indexterm PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<indexterm significance="normal">
-	<primary>adding partitions</primary>
-	<secondary>file system type</secondary>
-</indexterm>
\ No newline at end of file
diff --git a/en-US/Adding_Partitions-section-2-itemizedlist-1-listitem-0.xml b/en-US/Adding_Partitions-section-2-itemizedlist-1-listitem-0.xml
deleted file mode 100644
index 384f9f2..0000000
--- a/en-US/Adding_Partitions-section-2-itemizedlist-1-listitem-0.xml
+++ /dev/null
@@ -1,18 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE listitem PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<listitem>
-	<para>
-		<guilabel>Btrfs</guilabel> &mdash; Btrfs is under development as a file system capable of addressing and managing more files, larger files, and larger volumes than the ext2, ext3, and ext4 file systems. Btrfs is designed to make the file system tolerant of errors, and to facilitate the detection and repair of errors when they occur. It uses checksums to ensure the validity of data and metadata, and maintains snapshots of the file system that can be used for backup or repair. 
-	</para>
-	<para>
-		Because Btrfs is still experimental and under development, the installation program does not offer it by default. If you want to create a Btrfs partition on a drive, you must commence the installation process with the boot option <command>btrfs</command>. Refer to <xref linkend="ap-admin-options"/> for instructions. 
-	</para>
-	<warning>
-	<title>Btrfs is still experimental</title>
-	<para>
-		Fedora &PRODVER; includes Btrfs as a technology preview to allow you to experiment with this file system. You should not choose Btrfs for partitions that will contain valuable data or that are essential for the operation of important systems. 
-	</para>
-	</warning>
-</listitem>
diff --git a/en-US/Adding_Partitions-section-2-itemizedlist-1-listitem-1.xml b/en-US/Adding_Partitions-section-2-itemizedlist-1-listitem-1.xml
deleted file mode 100644
index 9f24b16..0000000
--- a/en-US/Adding_Partitions-section-2-itemizedlist-1-listitem-1.xml
+++ /dev/null
@@ -1,11 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE listitem PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-<listitem>
-	<para>
-		<guilabel>ext2</guilabel> &mdash; An ext2 file system supports standard Unix file types (regular files, directories, symbolic links, etc). It provides the ability to assign long file names, up to 255 characters.
-	</para>
-</listitem>
diff --git a/en-US/Adding_Partitions-section-2-itemizedlist-1-listitem-2.xml b/en-US/Adding_Partitions-section-2-itemizedlist-1-listitem-2.xml
deleted file mode 100644
index 39aa956..0000000
--- a/en-US/Adding_Partitions-section-2-itemizedlist-1-listitem-2.xml
+++ /dev/null
@@ -1,14 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE listitem PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<listitem>
-	<para>
-		<guilabel>ext3</guilabel> &mdash; The ext3 file system is based on the ext2 file system and has one main advantage &mdash; journaling. Using a journaling file system reduces time spent recovering a file system after a crash as there is no need to <command>fsck</command>
-		<footnote>
-			<para>
-				The <command>fsck</command> application is used to check the file system for metadata consistency and optionally repair one or more Linux file systems.
-			</para>
-		</footnote> the file system. 
-	</para>
-</listitem>
diff --git a/en-US/Adding_Partitions-section-2-itemizedlist-1-listitem-2a.xml b/en-US/Adding_Partitions-section-2-itemizedlist-1-listitem-2a.xml
deleted file mode 100644
index 61935f0..0000000
--- a/en-US/Adding_Partitions-section-2-itemizedlist-1-listitem-2a.xml
+++ /dev/null
@@ -1,9 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE listitem PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<listitem>
-	<para>
-		<guilabel>ext4</guilabel> &mdash; The ext4 file system is based on the ext3 file system and features a number of improvements. These include support for larger file systems and larger files, faster and more efficient allocation of disk space, no limit on the number of subdirectories within a directory, faster file system checking, and more robust journalling. The ext4 file system is selected by default and is highly recommended. 
-	</para>
-</listitem>
diff --git a/en-US/Adding_Partitions-section-2-itemizedlist-1-listitem-3.xml b/en-US/Adding_Partitions-section-2-itemizedlist-1-listitem-3.xml
deleted file mode 100644
index 11d03a1..0000000
--- a/en-US/Adding_Partitions-section-2-itemizedlist-1-listitem-3.xml
+++ /dev/null
@@ -1,9 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE listitem PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<listitem>
-	<para>
-		<guilabel>physical volume (LVM)</guilabel> &mdash; Creating one or more physical volume (LVM) partitions allows you to create an LVM logical volume. LVM can improve performance when using physical disks. <!-- Reference to RHEL Deployment Guide: For more information regarding LVM, refer to the <citetitle>Red Hat Enterprise Linux Deployment Guide</citetitle>. -->
-	</para>
-</listitem>
\ No newline at end of file
diff --git a/en-US/Adding_Partitions-section-2-itemizedlist-1-listitem-4.xml b/en-US/Adding_Partitions-section-2-itemizedlist-1-listitem-4.xml
deleted file mode 100644
index 1cba297..0000000
--- a/en-US/Adding_Partitions-section-2-itemizedlist-1-listitem-4.xml
+++ /dev/null
@@ -1,9 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE listitem PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<listitem>
-	<para>
-		<guilabel>software RAID</guilabel> &mdash; Creating two or more software RAID partitions allows you to create a RAID device. <!-- Reference to RHEL Deployment Guide: For more information regarding RAID, refer to the chapter <citetitle>RAID (Redundant Array of Independent Disks)</citetitle> in the <citetitle>Red Hat Enterprise Linux Deployment Guide</citetitle>. -->
-	</para>
-</listitem>
\ No newline at end of file
diff --git a/en-US/Adding_Partitions-section-2-itemizedlist-1-listitem-5.xml b/en-US/Adding_Partitions-section-2-itemizedlist-1-listitem-5.xml
deleted file mode 100644
index 4b5adae..0000000
--- a/en-US/Adding_Partitions-section-2-itemizedlist-1-listitem-5.xml
+++ /dev/null
@@ -1,9 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE listitem PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<listitem>
-	<para>
-		<guilabel>swap</guilabel> &mdash; Swap partitions are used to support virtual memory. In other words, data is written to a swap partition when there is not enough RAM to store the data your system is processing. <!-- Reference to RHEL Deployment Guide: Refer to the <citetitle>Red Hat Enterprise Linux Deployment Guide</citetitle> for additional information. -->
-	</para>
-</listitem>
\ No newline at end of file
diff --git a/en-US/Adding_Partitions-section-2-itemizedlist-1-listitem-6.xml b/en-US/Adding_Partitions-section-2-itemizedlist-1-listitem-6.xml
deleted file mode 100644
index b8e95be..0000000
--- a/en-US/Adding_Partitions-section-2-itemizedlist-1-listitem-6.xml
+++ /dev/null
@@ -1,12 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE listitem PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<listitem>
-	<para>
-		<guilabel>vfat</guilabel> &mdash; The VFAT file system is a Linux file system that is compatible with Microsoft Windows long filenames on the FAT file system. This file system must be used for the <filename >/boot/efi/</filename> partition on Itanium systems.
-	</para>
-</listitem>
\ No newline at end of file
diff --git a/en-US/Adding_Partitions-section-2-itemizedlist-1-listitem-7.xml b/en-US/Adding_Partitions-section-2-itemizedlist-1-listitem-7.xml
deleted file mode 100644
index 1e538a5..0000000
--- a/en-US/Adding_Partitions-section-2-itemizedlist-1-listitem-7.xml
+++ /dev/null
@@ -1,10 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE listitem PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<listitem>
-	<para>
-		<guilabel>xfs</guilabel> &mdash; XFS is a highly scalable, high-performance file system that supports filesystems up to 16 exabytes (approximately 16 million terabytes), files up to 8 exabytes (approximately 8 million terabytes) and directory structures containing tens of millions of entries. XFS supports metadata journaling, which facilitates quicker crash recovery. The XFS file system can also be defragmented and resized while mounted and active. 
-	</para>
-</listitem>
-
diff --git a/en-US/Adding_Partitions-section-2-itemizedlist-1.xml b/en-US/Adding_Partitions-section-2-itemizedlist-1.xml
deleted file mode 100644
index faa90ac..0000000
--- a/en-US/Adding_Partitions-section-2-itemizedlist-1.xml
+++ /dev/null
@@ -1,36 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE itemizedlist PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<!-- Nota Bene that this file is now only used from the x86 version. The list is now included in Adding_Partitions-ppc.xml as items, as vfat does appear in the PPC list -->
-
-<itemizedlist>
-
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Adding_Partitions-section-2-itemizedlist-1-listitem-0.xml"/>
-	<!-- btrfs -->
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Adding_Partitions-section-2-itemizedlist-1-listitem-1.xml"/>
-	<!-- ext2 -->
-
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Adding_Partitions-section-2-itemizedlist-1-listitem-2.xml"/>
-	<!-- ext3 -->
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Adding_Partitions-section-2-itemizedlist-1-listitem-2a.xml"/>
-	<!-- ext4 -->
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Adding_Partitions-section-2-itemizedlist-1-listitem-3.xml"/>
-	<!-- LVM -->
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Adding_Partitions-section-2-itemizedlist-1-listitem-4.xml"/>
-	<!-- Sofware RAID -->
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Adding_Partitions-section-2-itemizedlist-1-listitem-5.xml"/>
-	<!-- swap -->
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Adding_Partitions-section-2-itemizedlist-1-listitem-6.xml"/>
-	<!-- vfat -->
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Adding_Partitions-section-2-itemizedlist-1-listitem-7.xml"/>
-	<!-- xfs -->
-	
-</itemizedlist>
\ No newline at end of file
diff --git a/en-US/Adding_Partitions-section-2-para-1.xml b/en-US/Adding_Partitions-section-2-para-1.xml
deleted file mode 100644
index e6b5820..0000000
--- a/en-US/Adding_Partitions-section-2-para-1.xml
+++ /dev/null
@@ -1,7 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<para>
-	Fedora allows you to create different partition types, based on the file system they will use. The following is a brief description of the different file systems available, and how they can be utilized.
-</para>
\ No newline at end of file
diff --git a/en-US/Adding_Partitions-x86.xml b/en-US/Adding_Partitions-x86.xml
deleted file mode 100644
index 136d19c..0000000
--- a/en-US/Adding_Partitions-x86.xml
+++ /dev/null
@@ -1,93 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<section id="Adding_Partitions-x86">
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Adding_Partitions_common-title-1.xml"/>
-	<!-- Adding Partitions -->
-	
-	<!-- Begin Index terms -->
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Adding_Partitions_common-indexterm-1.xml"/>
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Adding_Partitions_common-indexterm-2.xml"/>
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Adding_Partitions_common-indexterm-3.xml"/>
-	<!-- End Index terms -->
-	
-	<para>
-		To add a new partition, select the <guibutton>Create</guibutton> button. A dialog box appears (refer to <xref linkend="fig-diskpartitioning-part-add-x86"/>).
-	</para>
-	
-	<note>
-		<title>Note</title>
-		
-		<para>
-			You must dedicate at least one partition for this installation, and optionally more. For more information, refer to <xref linkend="ch-partitions-x86"/>.
-		</para>
-	</note>
-	
-	<figure float="0" id="fig-diskpartitioning-part-add-x86"><title>Creating a New Partition</title>
-		<mediaobject>
-			<imageobject><imagedata fileref="images/diskpartitioning/part-add.png" format="PNG"/></imageobject>
-			<textobject><para>
-					Creating a new partition.
-				</para>
-			</textobject>
-		</mediaobject>
-	</figure>
-	
-	<itemizedlist>
-		<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Adding_Partitions_x86_ppc-listitem-1.xml"/>
-		<!-- Mount Point: Enter the partition's mount point. -->
-		
-		<listitem>
-			<para>
-				<guilabel>File System Type</guilabel>: Using the pull-down menu, select the appropriate file system type for this partition. For more information on file system types, refer to <xref linkend="s3-diskpartitioning-file-x86"/>.
-			</para>
-		</listitem>
-		
-		<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Adding_Partitions_x86_ppc-listitem-2.xml"/>
-		<!-- Allowable Drives: This field contains a list of the hard disks installed on your system. -->
-			
-		<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Adding_Partitions_x86_ppc-listitem-3.xml"/>
-		<!-- Size (MB): Enter the size (in megabytes) of the partition. -->
-		
-		<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Adding_Partitions_x86_ppc-listitem-4.xml"/>
-		<!-- Additional Size Options: Choose whether to keep this partition at a fixed size, -->
-		
-		<listitem>
-			<para>
-				<guilabel>Force to be a primary partition</guilabel>: Select whether the partition you are creating should be one of the first four partitions on the hard drive. If unselected, the partition is created as a logical partition. Refer to <xref linkend="s2-partitions-overview-extended-x86"/>, for more information.
-			</para>
-		</listitem>
-		
-		<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Adding_Partitions_x86_ppc-listitem-7.xml"/>
-		<!-- Encrypt: Choose whether to encrypt the partition so that the data stored on it cannot be accessed without a passphrase -->
-		
-		<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Adding_Partitions_x86_ppc-listitem-5.xml"/>
-		<!-- OK: Select OK once you are satisfied with the settings -->
-		
-		<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Adding_Partitions_x86_ppc-listitem-6.xml"/>
-		<!-- Cancel: Select Cancel if you do not want -->
-		
-	</itemizedlist>
-		
-	<section id="s3-diskpartitioning-file-x86">
-		
-		<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Adding_Partitions_x86_ppc-title-2.xml"/>
-		<!-- File System Types -->
-		
-		<!-- Begin Index terms -->
-		<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Adding_Partitions-section-2-indexterm-1.xml"/>
-		<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Adding_Partitions-section-2-indexterm-2.xml"/>
-		<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Adding_Partitions-section-2-indexterm-3.xml"/>
-		<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Adding_Partitions-section-2-indexterm-4.xml"/>
-		<!-- End Index terms -->
-		
-		<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Adding_Partitions-section-2-para-1.xml"/>
-		<!-- Red Hat Enterprise Linux allows you to create different partition types -->
-		
-		<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Adding_Partitions-section-2-itemizedlist-1.xml"/>
-		<!-- ext2, ext3, physical volume (LVM) etc... -->
-		
-	</section>	
-</section>
-		
\ No newline at end of file
diff --git a/en-US/Adding_Partitions_common-indexterm-1.xml b/en-US/Adding_Partitions_common-indexterm-1.xml
deleted file mode 100644
index 78e63d6..0000000
--- a/en-US/Adding_Partitions_common-indexterm-1.xml
+++ /dev/null
@@ -1,12 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE indexterm PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<indexterm significance="normal">
-	<primary><application>Disk Partitioner</application>
-	</primary>
-	<secondary>adding partitions</secondary>
-</indexterm>
\ No newline at end of file
diff --git a/en-US/Adding_Partitions_common-indexterm-2.xml b/en-US/Adding_Partitions_common-indexterm-2.xml
deleted file mode 100644
index ebd741c..0000000
--- a/en-US/Adding_Partitions_common-indexterm-2.xml
+++ /dev/null
@@ -1,10 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE indexterm PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<indexterm significance="normal">
-		<primary>adding partitions</primary>
-	</indexterm>
\ No newline at end of file
diff --git a/en-US/Adding_Partitions_common-indexterm-3.xml b/en-US/Adding_Partitions_common-indexterm-3.xml
deleted file mode 100644
index a06522c..0000000
--- a/en-US/Adding_Partitions_common-indexterm-3.xml
+++ /dev/null
@@ -1,11 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE indexterm PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<indexterm significance="normal">
-		<primary>partitioning</primary>
-		<secondary>creating new</secondary>
-	</indexterm>
\ No newline at end of file
diff --git a/en-US/Adding_Partitions_common-title-1.xml b/en-US/Adding_Partitions_common-title-1.xml
deleted file mode 100644
index 38f0a61..0000000
--- a/en-US/Adding_Partitions_common-title-1.xml
+++ /dev/null
@@ -1,8 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE title PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<title>Adding Partitions</title>
\ No newline at end of file
diff --git a/en-US/Adding_Partitions_x86_ppc-listitem-1.xml b/en-US/Adding_Partitions_x86_ppc-listitem-1.xml
deleted file mode 100644
index 9e4b062..0000000
--- a/en-US/Adding_Partitions_x86_ppc-listitem-1.xml
+++ /dev/null
@@ -1,12 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE listitem PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<listitem>
-	<para>
-		<guilabel>Mount Point</guilabel>: Enter the partition's mount point. For example, if this partition should be the root partition, enter <userinput>/</userinput>; enter <userinput>/boot</userinput> for the <filename>/boot</filename> partition, and so on. You can also use the pull-down menu to choose the correct mount point for your partition. For a swap partition the mount point should not be set - setting the filesystem type to swap is sufficient.
-	</para>
-</listitem>
\ No newline at end of file
diff --git a/en-US/Adding_Partitions_x86_ppc-listitem-2.xml b/en-US/Adding_Partitions_x86_ppc-listitem-2.xml
deleted file mode 100644
index f12ca6f..0000000
--- a/en-US/Adding_Partitions_x86_ppc-listitem-2.xml
+++ /dev/null
@@ -1,9 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE listitem PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<listitem>
-	<para>
-		<guilabel>Allowable Drives</guilabel>: This field contains a list of the hard disks installed on your system. If a hard disk's box is highlighted, then a desired partition can be created on that hard disk. If the box is <emphasis>not</emphasis> checked, then the partition will <emphasis>never</emphasis> be created on that hard disk. By using different checkbox settings, you can have <application>anaconda</application> place partitions where you need them, or let <application>anaconda</application> decide where partitions should go.
-	</para>
-</listitem>
\ No newline at end of file
diff --git a/en-US/Adding_Partitions_x86_ppc-listitem-3.xml b/en-US/Adding_Partitions_x86_ppc-listitem-3.xml
deleted file mode 100644
index 3e08fed..0000000
--- a/en-US/Adding_Partitions_x86_ppc-listitem-3.xml
+++ /dev/null
@@ -1,12 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE listitem PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<listitem>
-	<para>
-		<guilabel>Size (MB)</guilabel>: Enter the size (in megabytes) of the partition. Note, this field starts with 200 MB; unless changed, only a 200 MB partition will be created.
-	</para>
-</listitem>
\ No newline at end of file
diff --git a/en-US/Adding_Partitions_x86_ppc-listitem-4.xml b/en-US/Adding_Partitions_x86_ppc-listitem-4.xml
deleted file mode 100644
index 1d7ee30..0000000
--- a/en-US/Adding_Partitions_x86_ppc-listitem-4.xml
+++ /dev/null
@@ -1,17 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE listitem PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<listitem>
-	<para>
-		<guilabel>Additional Size Options</guilabel>: Choose whether to keep this partition at a fixed size, to allow it to "grow" (fill up the available hard drive space) to a certain point, or to allow it to grow to fill any remaining hard
-		drive space available.
-	</para>
-
-	<para>
-		If you choose <guilabel>Fill all space up to (MB)</guilabel>, you must give size constraints in the field to the right of this option. This allows you to keep a certain amount of space free on your hard drive for future use.
-	</para>
-</listitem>
\ No newline at end of file
diff --git a/en-US/Adding_Partitions_x86_ppc-listitem-5.xml b/en-US/Adding_Partitions_x86_ppc-listitem-5.xml
deleted file mode 100644
index 60975ab..0000000
--- a/en-US/Adding_Partitions_x86_ppc-listitem-5.xml
+++ /dev/null
@@ -1,12 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE listitem PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<listitem>
-	<para>
-		<guibutton>OK</guibutton>: Select <guibutton>OK</guibutton> once you are satisfied with the settings and wish to create the partition.
-	</para>
-</listitem>
\ No newline at end of file
diff --git a/en-US/Adding_Partitions_x86_ppc-listitem-6.xml b/en-US/Adding_Partitions_x86_ppc-listitem-6.xml
deleted file mode 100644
index 09de374..0000000
--- a/en-US/Adding_Partitions_x86_ppc-listitem-6.xml
+++ /dev/null
@@ -1,12 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE listitem PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<listitem>
-	<para>
-		<guibutton>Cancel</guibutton>: Select <guibutton>Cancel</guibutton> if you do not want to create the partition.
-	</para>
-</listitem>
\ No newline at end of file
diff --git a/en-US/Adding_Partitions_x86_ppc-listitem-7.xml b/en-US/Adding_Partitions_x86_ppc-listitem-7.xml
deleted file mode 100644
index 2fe5be8..0000000
--- a/en-US/Adding_Partitions_x86_ppc-listitem-7.xml
+++ /dev/null
@@ -1,10 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE listitem PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<listitem>
-	<para>
-		<guilabel>Encrypt</guilabel>: Choose whether to encrypt the partition so that the data stored on it cannot be accessed without a passphrase, even if the storage device is connected to another system. Refer to <xref linkend="Disk_Encryption_Guide"/> for information on encryption of storage devices. If you select this option, the installer prompts you to provide a passphrase before it writes the partition to the disk.
-	</para>
-</listitem>
-
diff --git a/en-US/Adding_Partitions_x86_ppc-title-2.xml b/en-US/Adding_Partitions_x86_ppc-title-2.xml
deleted file mode 100644
index 5299ff8..0000000
--- a/en-US/Adding_Partitions_x86_ppc-title-2.xml
+++ /dev/null
@@ -1,8 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE title PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<title>File System Types</title>
\ No newline at end of file
diff --git a/en-US/Advice_on_Partitions.xml b/en-US/Advice_on_Partitions.xml
deleted file mode 100644
index 72c077d..0000000
--- a/en-US/Advice_on_Partitions.xml
+++ /dev/null
@@ -1,146 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-
-<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
- "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd">
-
-  <section id="sn-partitioning-advice">
-    <title>Advice on Partitions</title>
-    <para>Optimal partition setup depends on the usage for the Linux
-      system in question.  The following tips may help you decide how to
-      allocate your disk space.</para>
-
-    <itemizedlist>
-      <listitem>
-	<para>
-	  If you expect that you or other users will store data on the
-	  system, create a separate partition for the
-	  <filename>/home</filename> directory within a volume group.
-	  With a separate <filename>/home</filename> partition, you may
-	  upgrade or reinstall Fedora without erasing user data files.
-	</para>
-      </listitem>
-      <listitem>
-	<para>Each kernel installed on your system requires
-	  approximately 10 MB on the <filename
-	    class="partition">/boot</filename> partition.  Unless you
-	  plan to install a great many kernels, the default partition
-	  size of 250 MB for <filename
-	    class="partition">/boot</filename> should suffice.</para>
-	    <xi:include href="ext4-and-btrfs.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
-      </listitem>
-      <listitem>
-	<para>The <filename class="directory">/var</filename> directory
-	  holds content for a number of applications, including the
-	  <application>Apache</application> web server.  It also is used
-	  to store downloaded update packages on a temporary basis.
-	  Ensure that the partition containing the <filename
-	    class="directory">/var</filename> directory has enough space
-	  to download pending updates and hold your other
-	  content.</para>
-	<important>
-	  <title>Pending Updates</title>
-	  <para>Because Fedora is a rapidly progressing collection of
-	    software, many updates may be available late in a release
-	    cycle.  You can add an update repository to the sources for
-	    installation later to minimize this issue. Refer to <xref
-	      linkend="sn-additional-repos"/> for more information.
-	  </para>
-	</important>
-      </listitem>
-      <listitem>
-	<para>The <filename class="directory">/usr</filename> directory
-	  holds the majority of software content on a Fedora system.
-	  For an installation of the default set of software, allocate
-	  at least 4 GB of space.  If you are a software developer or
-	  plan to use your Fedora system to learn software development
-	  skills, you may want to at least double this
-	  allocation.</para>
-	  <important>
-	  <title>Do not place <filename class="directory">/usr</filename> on a separate partition</title>
-	  <para>If <filename class="directory">/usr</filename> is on a separate partition from <filename class="directory">/</filename>, the boot process becomes much more complex, and in some situations (like installations on iSCSI drives), might not work at all. </para>
-	  </important>
-      </listitem>
-      <listitem>
-	<para>Consider leaving a portion of the space in an LVM volume
-	  group unallocated.  This unallocated space gives you
-	  flexibility if your space requirements change but you do not
-	  wish to remove data from other partitions to reallocate
-	  storage.</para>
-      </listitem>
-      <listitem>
-	<para>If you separate subdirectories into partitions, you can
-	  retain content in those subdirectories if you decide to
-	  install a new version of Fedora over your current system.
-	  For instance, if you intend to run a
-	  <application>MySQL</application> database in <filename
-	    class="directory">/var/lib/mysql</filename>, make a separate
-	  partition for that directory in case you need to reinstall
-	  later.</para>
-      </listitem>
-    </itemizedlist>
-    <para>The following table is a possible partition setup for a system
-      with a single, new 80 GB hard disk and 1 GB of RAM.  Note that
-      approximately 10 GB of the volume group is unallocated to allow
-      for future growth.</para>
-    <note>
-      <title>Example Usage</title>
-      <para>This setup is not optimal for all use cases.</para>
-    </note>
-    <example id="ex-partitioning-80g">
-    <title>Example partition setup</title>
-      <para>
-	  <table frame='all'><title>Example partition setup</title>
-	    <tgroup cols='2' align='left' colsep='1' rowsep='1'>
-	      <thead>
-		  <row>
-		    <entry>Partition</entry>
-		    <entry>Size and type</entry>
-		  </row>
-	      </thead>
-	      <tbody>
-		  <row>
-		    <entry><filename class="partition">/boot</filename></entry>
-		    <entry>250 MB <systemitem class="filesystem">ext4</systemitem>
-		      partition</entry>
-		  </row>
-		  <row>
-		    <entry><filename class="partition">swap</filename></entry>
-		    <entry>2 GB swap</entry>
-		  </row>
-		  <row>
-		    <entry>LVM physical volume</entry>
-		    <entry>Remaining space, as one LVM volume group</entry>
-		  </row>
-		</tbody>
-	      </tgroup>
-	  </table>
-      </para>
-      <para>The physical volume is assigned to the default volume group and divided into the following logical volumes:</para>
-      <para>
-	  <table frame='all'><title>Example partition setup: LVM physical volume</title>
-	    <tgroup cols='2' align='left' colsep='1' rowsep='1'>
-	      <thead>
-		  <row>
-		    <entry>Partition</entry>
-		    <entry>Size and type</entry>
-		  </row>
-	      </thead>
-	      <tbody>
-		  <row>
-		    <entry><filename class="partition">/</filename></entry>
-		    <entry>13 GB ext4</entry>
-		  </row>
-		  <row>
-		    <entry><filename class="partition">/var</filename></entry>
-		    <entry>4 GB ext4</entry>
-		  </row>
-		  <row>
-		    <entry><filename class="partition">/home</filename></entry>
-		    <entry>50 GB ext4</entry>
-		  </row>
-		</tbody>
-	      </tgroup>
-	  </table>
-	</para>
-    </example>
-  </section>
diff --git a/en-US/Assign_Storage_Devices-common-figure-1.xml b/en-US/Assign_Storage_Devices-common-figure-1.xml
deleted file mode 100644
index ab00669..0000000
--- a/en-US/Assign_Storage_Devices-common-figure-1.xml
+++ /dev/null
@@ -1,14 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE figure PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-
-<figure float="0"><title>Assign storage devices</title>
-	<mediaobject>
-		<imageobject><imagedata fileref="images/storagedevices/assignstoragedevices.png" format="PNG"/></imageobject>
-		<textobject><para>
-				Screen to select storage devices for installation or for data storage only
-			</para>
-		</textobject>
-	</mediaobject>
-</figure>
diff --git a/en-US/Assign_Storage_Devices-common-para-1.xml b/en-US/Assign_Storage_Devices-common-para-1.xml
deleted file mode 100644
index b3b91c8..0000000
--- a/en-US/Assign_Storage_Devices-common-para-1.xml
+++ /dev/null
@@ -1,7 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE title PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<para>
-	During installation, the devices that you identify here as being for data storage only are mounted as part of the file system, but are not partitioned or formatted. 
-</para>
diff --git a/en-US/Assign_Storage_Devices-common-para-2.xml b/en-US/Assign_Storage_Devices-common-para-2.xml
deleted file mode 100644
index bf4b1c4..0000000
--- a/en-US/Assign_Storage_Devices-common-para-2.xml
+++ /dev/null
@@ -1,7 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE title PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<para>
-	The screen is split into two panes. The left pane contains a list of devices to be used for data storage only. The right pane contains a list of devices that are to be available for installation of the operating system.
-</para>
diff --git a/en-US/Assign_Storage_Devices-common-para-3.xml b/en-US/Assign_Storage_Devices-common-para-3.xml
deleted file mode 100644
index c6c998a..0000000
--- a/en-US/Assign_Storage_Devices-common-para-3.xml
+++ /dev/null
@@ -1,7 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<para>
-	Each list contains information about the devices to help you to identify them. A small drop-down menu marked with an icon is located to the right of the column headings. This menu allows you to select the types of data presented on each device. Reducing or expanding the amount of information presented might help you to identify particular devices.
-</para>
diff --git a/en-US/Assign_Storage_Devices-common-para-4.xml b/en-US/Assign_Storage_Devices-common-para-4.xml
deleted file mode 100644
index 077d98c..0000000
--- a/en-US/Assign_Storage_Devices-common-para-4.xml
+++ /dev/null
@@ -1,7 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<para>
-	Move a device from one list to the other by clicking on the device, then clicking either the button labeled with a left-pointing arrow to move it to the list of data storage devices or the button labeled with a right-pointing arrow to move it to the list of devices available for installation of the operating system.
-</para>
diff --git a/en-US/Assign_Storage_Devices-common-para-5.xml b/en-US/Assign_Storage_Devices-common-para-5.xml
deleted file mode 100644
index 98aec91..0000000
--- a/en-US/Assign_Storage_Devices-common-para-5.xml
+++ /dev/null
@@ -1,7 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<para>
-	The list of devices available as installation targets also includes a radio button beside each device. Use this radio button to specify the device that you want to use as the boot device for the system.
-</para>
diff --git a/en-US/Assign_Storage_Devices-common-para-6.xml b/en-US/Assign_Storage_Devices-common-para-6.xml
deleted file mode 100644
index 0787d78..0000000
--- a/en-US/Assign_Storage_Devices-common-para-6.xml
+++ /dev/null
@@ -1,7 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<para>
-	When you have finished identifying devices to be used for installation, click <guibutton>Next</guibutton> to continue.
-</para>
diff --git a/en-US/Assign_Storage_Devices-common-title.xml b/en-US/Assign_Storage_Devices-common-title.xml
deleted file mode 100644
index 8fa40c9..0000000
--- a/en-US/Assign_Storage_Devices-common-title.xml
+++ /dev/null
@@ -1,7 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE title PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<title>
-	Assign Storage Devices
-</title>
diff --git a/en-US/Assign_Storage_Devices-x86.xml b/en-US/Assign_Storage_Devices-x86.xml
deleted file mode 100644
index 609c4cd..0000000
--- a/en-US/Assign_Storage_Devices-x86.xml
+++ /dev/null
@@ -1,36 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<section id="Assign_Storage_Devices-x86">
-
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Assign_Storage_Devices-common-title.xml"/>
-	<!-- Storage Devices -->
-	
-	<para>
-		If you selected more than one storage device on the storage devices selection screen (refer to <xref linkend="Storage_Devices-x86"/>) system, <application>anaconda</application> asks you to select which of these devices should be available for installation of the operating system, and which should only be attached to the file system for data storage. 
-	</para>
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Assign_Storage_Devices-common-para-1.xml"/>
-	<!-- During installation, the devices that you identify here -->
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Assign_Storage_Devices-common-figure-1.xml"/>
-	<!-- Assign Storage Devices -->
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Assign_Storage_Devices-common-para-2.xml"/>
-	<!-- The screen is split into two panes. -->
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Assign_Storage_Devices-common-para-3.xml"/>
-	<!-- Each list contains information about the devices to help you to identify them. -->
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Assign_Storage_Devices-common-para-4.xml"/>
-	<!-- Move a device from one list to the other by clicking on the device, -->
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Assign_Storage_Devices-common-para-5.xml"/>
-	<!-- The list of devices available as installation targets includes -->
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Assign_Storage_Devices-common-para-6.xml"/>
-	<!-- When you have finished identifying devices to be used for installation -->
-
-</section>
-
diff --git a/en-US/Author_Group.xml b/en-US/Author_Group.xml
deleted file mode 100644
index 08c0b5e..0000000
--- a/en-US/Author_Group.xml
+++ /dev/null
@@ -1,9 +0,0 @@
-<?xml version='1.0'?>
-<!DOCTYPE authorgroup PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd">
-
-<authorgroup>
-	<author>
-		<firstname>Fedora</firstname>
-		<surname>Documentation Project</surname>
-	</author>
-</authorgroup>
diff --git a/en-US/Automatic_Partitioning_common-caution-1.xml b/en-US/Automatic_Partitioning_common-caution-1.xml
deleted file mode 100644
index 04e6dd5..0000000
--- a/en-US/Automatic_Partitioning_common-caution-1.xml
+++ /dev/null
@@ -1,14 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE caution PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<warning>
-	<title>Warning</title>
-
-	<para>
-		It is always a good idea to back up any data that you have on your systems. For example, if you are upgrading or creating a dual-boot system, you should back up any data you wish to keep on your drive(s). Mistakes do happen and can result in the loss of all your data.
-	</para>
-</warning>
\ No newline at end of file
diff --git a/en-US/Automatic_Partitioning_common-indexterm-1.xml b/en-US/Automatic_Partitioning_common-indexterm-1.xml
deleted file mode 100644
index edee67e..0000000
--- a/en-US/Automatic_Partitioning_common-indexterm-1.xml
+++ /dev/null
@@ -1,12 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE indexterm PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-
-<indexterm significance="normal">
-	<primary>partitioning</primary>
-	<secondary>automatic</secondary>
-</indexterm>
\ No newline at end of file
diff --git a/en-US/Automatic_Partitioning_common-indexterm-2.xml b/en-US/Automatic_Partitioning_common-indexterm-2.xml
deleted file mode 100644
index 50f377c..0000000
--- a/en-US/Automatic_Partitioning_common-indexterm-2.xml
+++ /dev/null
@@ -1,10 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE indexterm PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<indexterm significance="normal">
-	<primary>automatic partitioning</primary>
-</indexterm>
\ No newline at end of file
diff --git a/en-US/Automatic_Partitioning_common-note-1.xml b/en-US/Automatic_Partitioning_common-note-1.xml
deleted file mode 100644
index 8b34f18..0000000
--- a/en-US/Automatic_Partitioning_common-note-1.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE caution PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-  <important>
-    <title>Installing in text mode</title>
-
-	<para>
-		If you install Fedora in text mode, you can only use the default partitioning schemes described in this section. Therefore, although you can choose to use a whole drive, to remove existing Linux partitions, or to use the free space on the drive, you cannot customize the partition layout. That is, you cannot add or remove partitions or file systems beyond those that the installer automatically adds or removes. If you require a customized layout at installation time, you should perform a graphical installation over a VNC connection or a kickstart installation.
-	</para>
-
-	<para>
-		Furthermore, advanced options such as LVM, encrypted filesystems, and resizable filesystems are available only in graphical mode and kickstart. 
-	</para>
-  </important>
\ No newline at end of file
diff --git a/en-US/Automatic_Partitioning_common-para-1.xml b/en-US/Automatic_Partitioning_common-para-1.xml
deleted file mode 100644
index 75368cd..0000000
--- a/en-US/Automatic_Partitioning_common-para-1.xml
+++ /dev/null
@@ -1,11 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<para>
-	Your options are:
-</para>
-
diff --git a/en-US/Automatic_Partitioning_common-para-2.xml b/en-US/Automatic_Partitioning_common-para-2.xml
deleted file mode 100644
index 9eda6af..0000000
--- a/en-US/Automatic_Partitioning_common-para-2.xml
+++ /dev/null
@@ -1,8 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<para>
-	Choose your preferred partitioning method by clicking the radio button to the left of its description in the dialog box.
-</para>
-
diff --git a/en-US/Automatic_Partitioning_common-para-3.xml b/en-US/Automatic_Partitioning_common-para-3.xml
deleted file mode 100644
index 629ad8e..0000000
--- a/en-US/Automatic_Partitioning_common-para-3.xml
+++ /dev/null
@@ -1,8 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<para>
-	To review and make any necessary changes to the partitions created by automatic partitioning, select the <guilabel>Review</guilabel> option. After selecting <guilabel>Review</guilabel> and clicking <guibutton>Next</guibutton> to move forward, the partitions created for you by <application>anaconda</application> appear. You can make modifications to these partitions if they do not meet your needs.
-</para>
-	
\ No newline at end of file
diff --git a/en-US/Automatic_Partitioning_common-para-4.xml b/en-US/Automatic_Partitioning_common-para-4.xml
deleted file mode 100644
index 5ed0b92..0000000
--- a/en-US/Automatic_Partitioning_common-para-4.xml
+++ /dev/null
@@ -1,10 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<para>
-	Click <guibutton>Next</guibutton> once you have made your selections to proceed.
-</para>
\ No newline at end of file
diff --git a/en-US/Automatic_Partitioning_common-para-5.xml b/en-US/Automatic_Partitioning_common-para-5.xml
deleted file mode 100644
index 2b7e439..0000000
--- a/en-US/Automatic_Partitioning_common-para-5.xml
+++ /dev/null
@@ -1,10 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-
-<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
- "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd">
-
-<para>
-	Select <guilabel>Encrypt system</guilabel> to encrypt all partitions except the <filename class="partition">/boot</filename> partition. Refer to <xref linkend="Disk_Encryption_Guide"/> for information on encryption. 
-</para>
-    
-
diff --git a/en-US/Automatic_Partitioning_common-varlistentry-1.xml b/en-US/Automatic_Partitioning_common-varlistentry-1.xml
deleted file mode 100644
index 7e88634..0000000
--- a/en-US/Automatic_Partitioning_common-varlistentry-1.xml
+++ /dev/null
@@ -1,19 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE varlistentry PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<varlistentry>
-	<term>Use All Space</term>
-	<listitem>
-		<para>
-			Select this option to remove all partitions on your hard drives (this includes partitions created by other operating systems such as Windows VFAT or NTFS partitions).
-		</para>
-		<warning>
-			<title>Warning</title>
-			<para>
-				If you select this option, all data on the selected hard drive(s) is removed by the installation program. Do not select this option if you have information that you want to keep on the hard drive(s) where you are installing Fedora.
-			</para>
-		</warning>
-	</listitem>
-</varlistentry>
-
diff --git a/en-US/Automatic_Partitioning_common-varlistentry-2.xml b/en-US/Automatic_Partitioning_common-varlistentry-2.xml
deleted file mode 100644
index fee118e..0000000
--- a/en-US/Automatic_Partitioning_common-varlistentry-2.xml
+++ /dev/null
@@ -1,12 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE varlistentry PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<varlistentry>
-	<term>Replace Existing Linux System(s)</term>
-	<listitem>
-		<para>
-			Select this option to remove only partitions created by a previous Linux installation. This does not remove other partitions you may have on your hard drives (such as VFAT or FAT32 partitions).
-		</para>
-	</listitem>
-</varlistentry>
diff --git a/en-US/Automatic_Partitioning_common-varlistentry-3.xml b/en-US/Automatic_Partitioning_common-varlistentry-3.xml
deleted file mode 100644
index 573070e..0000000
--- a/en-US/Automatic_Partitioning_common-varlistentry-3.xml
+++ /dev/null
@@ -1,20 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE varlistentry PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<varlistentry>
-	<term>Shrink Current System</term>
-	<listitem>
-		<para>
-			Select this option to resize your current data and partitions manually and install a default Red Hat Enterprise Linux layout in the space that is freed.
-		</para>
-		<warning>
-			<title>Warning</title>
-			<para>
-				If you shrink partitions on which other operating systems are installed, you might not be able to use those operating systems. Although this partitioning option does not destroy data, operating systems typically require some free space in their partitions. Before you resize a partition that holds an operating system that you might want to use again, find out how much space you need to leave free.
-			</para>
-		</warning>
-	</listitem>
-</varlistentry>
-	
-	
\ No newline at end of file
diff --git a/en-US/Automatic_Partitioning_x86-variablelist-1.xml b/en-US/Automatic_Partitioning_x86-variablelist-1.xml
deleted file mode 100644
index e47d35c..0000000
--- a/en-US/Automatic_Partitioning_x86-variablelist-1.xml
+++ /dev/null
@@ -1,34 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE variablelist PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<variablelist>
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Automatic_Partitioning_common-varlistentry-1.xml"/>
-	<!-- Use All Space -->
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Automatic_Partitioning_common-varlistentry-2.xml"/>
-	<!-- Replace Existing Linux System(s) -->
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Automatic_Partitioning_common-varlistentry-3.xml"/>
-	<!-- Shrink Current System -->
-	
-	<varlistentry>
-		<term>Use Free Space</term>
-		<listitem>
-			<para>
-				Select this option to retain your current data and partitions and install Fedora in the unused space available on the storage drives. Ensure that there is sufficient space available on the storage drives before you select this option â€” refer to <xref linkend="Disk_Space-x86"/>.
-			</para>
-		</listitem>
-	</varlistentry>
-	
-	<varlistentry>
-		<term>Create Custom Layout</term>
-		<listitem>
-			<para>
-				Select this option to partition storage devices manually and create customized layouts. Refer to <xref linkend="s1-diskpartitioning-x86"/>
-			</para>
-		</listitem>
-	</varlistentry>
-	
-</variablelist>
-
diff --git a/en-US/Automatic_Partitioning_x86_ppc-tip-para-1.xml b/en-US/Automatic_Partitioning_x86_ppc-tip-para-1.xml
deleted file mode 100644
index 6c16c4e..0000000
--- a/en-US/Automatic_Partitioning_x86_ppc-tip-para-1.xml
+++ /dev/null
@@ -1,10 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<para>
-	If you have a RAID card, be aware that some BIOSes do not support booting from the RAID card. In cases such as these, the <filename>/boot/</filename> partition must be created on a partition outside of the RAID array, such as on a separate hard drive. An internal hard drive is necessary to use for partition creation with problematic RAID cards.
-</para>
\ No newline at end of file
diff --git a/en-US/Automatic_Partitioning_x86_ppc-tip-para-2.xml b/en-US/Automatic_Partitioning_x86_ppc-tip-para-2.xml
deleted file mode 100644
index 2150171..0000000
--- a/en-US/Automatic_Partitioning_x86_ppc-tip-para-2.xml
+++ /dev/null
@@ -1,10 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<para>
-	A <filename>/boot/</filename> partition is also necessary for software RAID setups.
-</para>
\ No newline at end of file
diff --git a/en-US/Automatic_Partitioning_x86_ppc-tip-para-3.xml b/en-US/Automatic_Partitioning_x86_ppc-tip-para-3.xml
deleted file mode 100644
index fe49710..0000000
--- a/en-US/Automatic_Partitioning_x86_ppc-tip-para-3.xml
+++ /dev/null
@@ -1,10 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<para>
-	If you have chosen to automatically partition your system, you should select <guilabel>Review</guilabel> and manually edit your <filename>/boot/</filename> partition.
-</para>
\ No newline at end of file
diff --git a/en-US/Beginning_Installation-x86.xml b/en-US/Beginning_Installation-x86.xml
deleted file mode 100644
index 863590a..0000000
--- a/en-US/Beginning_Installation-x86.xml
+++ /dev/null
@@ -1,59 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<section id="s1-begininstall-cd-inst-x86">	
-		
-	<!-- Installing from CD-ROM -->
-	
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Beginning_Installation_x86_ppc-title-1.xml"/>
-	<!-- Title: Installing from CD-ROM or DVD -->
-	
-	<!-- Index terms -->
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Beginning_Installation_x86_ppc-indexterm-1.xml"/>
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Beginning_Installation_x86_ppc-indexterm-2.xml"/>
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Beginning_Installation_x86_ppc-indexterm-3.xml"/>
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Beginning_Installation_x86_ppc-indexterm-4.xml"/>
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Beginning_Installation_x86_ppc-indexterm-5.xml"/>
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Beginning_Installation_x86_ppc-indexterm-6.xml"/>
-	<!-- End of Index terms -->
-
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Beginning_Installation_x86_ppc-para-1.xml"/>
-	<!-- To install Fedora from a CD-ROM, -->
-
-	<!-- <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Beginning_Installation_x86_ppc-note-1.xml"/> -->
-	<!-- The first CD-ROM is required when booting the installation program, -->
-	
-	<para>
-		The installation program then probes your system and attempts to identify your CD-ROM drive. It starts by looking for an IDE (also known as an ATAPI) CD-ROM drive.
-	</para>
-
-	<note>
-		<title>Note</title>
-		<indexterm significance="normal">
-			<primary>installation</primary>
-			<secondary>aborting</secondary>
-		</indexterm>
-		<indexterm significance="normal">
-			<primary>canceling the installation</primary>
-		</indexterm>
-		<para>
-			To abort the installation process at this time, reboot your machine and then eject the boot media. You can safely cancel the installation at any point before the <guilabel>About to Install</guilabel> screen. Refer to
-			<xref linkend="s1-installpkgs-x86"/> for more information.
-		</para>
-	</note>
-
-	<indexterm significance="normal">
-		<primary>CD-ROM</primary>
-		<secondary>SCSI</secondary>
-	</indexterm>
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Beginning_Installation_x86_ppc-para-3.xml"/>
-	<!-- If your CD-ROM drive is not detected... -->
-	
-	<para>
-		If the DVD/CD-ROM drive is found and the driver loaded, the installer will present you with the option to perform a media check on the DVD/CD-ROM. This will take some time, and you may opt to skip over this step. However, if you later encounter problems with the installer, you should reboot and perform the media check before calling for support. From the media check dialog, continue to the next stage of the installation process (refer to <xref linkend="sn-welcome-x86"/>).
-	</para>
-
-</section>
\ No newline at end of file
diff --git a/en-US/Beginning_Installation_Hard_Disk-x86.xml b/en-US/Beginning_Installation_Hard_Disk-x86.xml
deleted file mode 100644
index 9034375..0000000
--- a/en-US/Beginning_Installation_Hard_Disk-x86.xml
+++ /dev/null
@@ -1,46 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<section id="s1-begininstall-hd-x86">
-		
-		<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Beginning_Installation_Hard_Disk_common-title-1.xml"/>
-		<!-- Installing from a Hard Drive -->
-		
-		<!-- Index terms -->
-		<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Beginning_Installation_Hard_Disk_common-indexterm-1.xml"/>
-		<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Beginning_Installation_Hard_Disk_common-indexterm-2.xml"/>
-		<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Beginning_Installation_Hard_Disk_common-indexterm-3.xml"/>
-		<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Beginning_Installation_Hard_Disk_common-indexterm-4.xml"/>
-		<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Beginning_Installation_Hard_Disk_common-indexterm-5.xml"/>
-		<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Beginning_Installation_Hard_Disk_common-indexterm-6.xml"/>
-		<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Beginning_Installation_Hard_Disk_common-indexterm-7.xml"/>
-		<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Beginning_Installation_Hard_Disk_common-indexterm-8.xml"/>
-		<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Beginning_Installation_Hard_Disk_common-indexterm-9.xml"/>
-		<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Beginning_Installation_Hard_Disk_common-indexterm-10.xml"/>
-		<!-- End index terms -->
-		
-		<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Beginning_Installation_Hard_Disk_common-para-1.xml"/>
-		<!-- The Select Partition screen applies only if... -->
-		
-		<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Beginning_Installation_Hard_Disk_x86_ppc-figure-1.xml"/>
-		<!-- Selecting Partition Dialog -->
-		
-		<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Beginning_Installation_Hard_Disk_common-para-9.xml"/>
-		<!-- Select the partition containing the ISO files from the... -->
-		
-		<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Beginning_Installation_Hard_Disk_common-para-10.xml"/>
-		<!-- Also specify the Directory holding images. Enter the full... -->
-		
-		<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Beginning_Installation_Hard_Disk_common-table-1.xml"/>
-		<!-- Location of ISO images for different partition types -->
-		
-		<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Beginning_Installation_Hard_Disk_common-para-3.xml"/>
-		<!-- If the ISO images are in the root (top-level) directory -->
-		
-		<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Beginning_Installation_Hard_Disk_common-note-2.xml"/>
-		<!-- An entry without a leading slash may call the installation to fail. -->
-		
-		<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Beginning_Installation_Hard_Disk_common-para-11.xml"/>
-		<!-- Select OK to continue. Proceed with... -->
-	</section>	
\ No newline at end of file
diff --git a/en-US/Beginning_Installation_Hard_Disk_common-indexterm-1.xml b/en-US/Beginning_Installation_Hard_Disk_common-indexterm-1.xml
deleted file mode 100644
index 1f4382d..0000000
--- a/en-US/Beginning_Installation_Hard_Disk_common-indexterm-1.xml
+++ /dev/null
@@ -1,7 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE indexterm PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<indexterm significance="normal">
-		<primary>hard drive installation</primary>
-	</indexterm>
\ No newline at end of file
diff --git a/en-US/Beginning_Installation_Hard_Disk_common-indexterm-10.xml b/en-US/Beginning_Installation_Hard_Disk_common-indexterm-10.xml
deleted file mode 100644
index c89c149..0000000
--- a/en-US/Beginning_Installation_Hard_Disk_common-indexterm-10.xml
+++ /dev/null
@@ -1,8 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE indexterm PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<indexterm significance="normal">
-    <primary>file systems</primary>
-    <secondary>ext4</secondary>
-</indexterm> 
diff --git a/en-US/Beginning_Installation_Hard_Disk_common-indexterm-2.xml b/en-US/Beginning_Installation_Hard_Disk_common-indexterm-2.xml
deleted file mode 100644
index 6594b22..0000000
--- a/en-US/Beginning_Installation_Hard_Disk_common-indexterm-2.xml
+++ /dev/null
@@ -1,8 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE indexterm PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<indexterm significance="normal">
-		<primary>installation</primary>
-		<secondary>hard drive</secondary>
-	</indexterm>
\ No newline at end of file
diff --git a/en-US/Beginning_Installation_Hard_Disk_common-indexterm-3.xml b/en-US/Beginning_Installation_Hard_Disk_common-indexterm-3.xml
deleted file mode 100644
index 700f48b..0000000
--- a/en-US/Beginning_Installation_Hard_Disk_common-indexterm-3.xml
+++ /dev/null
@@ -1,8 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE indexterm PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<indexterm significance="normal">
-    <primary>ext2</primary>
-    <see>file systems</see>
-</indexterm>
diff --git a/en-US/Beginning_Installation_Hard_Disk_common-indexterm-4.xml b/en-US/Beginning_Installation_Hard_Disk_common-indexterm-4.xml
deleted file mode 100644
index 18aafa3..0000000
--- a/en-US/Beginning_Installation_Hard_Disk_common-indexterm-4.xml
+++ /dev/null
@@ -1,8 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE indexterm PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<indexterm significance="normal">
-    <primary>file systems</primary>
-    <secondary>ext2</secondary>
-</indexterm>
\ No newline at end of file
diff --git a/en-US/Beginning_Installation_Hard_Disk_common-indexterm-5.xml b/en-US/Beginning_Installation_Hard_Disk_common-indexterm-5.xml
deleted file mode 100644
index 02181fe..0000000
--- a/en-US/Beginning_Installation_Hard_Disk_common-indexterm-5.xml
+++ /dev/null
@@ -1,8 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE indexterm PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<indexterm significance="normal">
-    <primary>ext3</primary>
-    <see>file systems</see>
-</indexterm>
diff --git a/en-US/Beginning_Installation_Hard_Disk_common-indexterm-6.xml b/en-US/Beginning_Installation_Hard_Disk_common-indexterm-6.xml
deleted file mode 100644
index a8b0aae..0000000
--- a/en-US/Beginning_Installation_Hard_Disk_common-indexterm-6.xml
+++ /dev/null
@@ -1,8 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE indexterm PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<indexterm significance="normal">
-    <primary>file systems</primary>
-    <secondary>ext3</secondary>
-</indexterm> 
diff --git a/en-US/Beginning_Installation_Hard_Disk_common-indexterm-7.xml b/en-US/Beginning_Installation_Hard_Disk_common-indexterm-7.xml
deleted file mode 100644
index 6f640c5..0000000
--- a/en-US/Beginning_Installation_Hard_Disk_common-indexterm-7.xml
+++ /dev/null
@@ -1,8 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE indexterm PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<indexterm significance="normal">
-    <primary>vfat</primary>
-    <see>file systems</see>
-</indexterm>
\ No newline at end of file
diff --git a/en-US/Beginning_Installation_Hard_Disk_common-indexterm-8.xml b/en-US/Beginning_Installation_Hard_Disk_common-indexterm-8.xml
deleted file mode 100644
index 69858e8..0000000
--- a/en-US/Beginning_Installation_Hard_Disk_common-indexterm-8.xml
+++ /dev/null
@@ -1,8 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE indexterm PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<indexterm significance="normal">
-    <primary>file systems</primary>
-    <secondary>vfat</secondary>
-</indexterm> 
diff --git a/en-US/Beginning_Installation_Hard_Disk_common-indexterm-9.xml b/en-US/Beginning_Installation_Hard_Disk_common-indexterm-9.xml
deleted file mode 100644
index 4815239..0000000
--- a/en-US/Beginning_Installation_Hard_Disk_common-indexterm-9.xml
+++ /dev/null
@@ -1,8 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE indexterm PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<indexterm significance="normal">
-    <primary>ext4</primary>
-    <see>file systems</see>
-</indexterm>
\ No newline at end of file
diff --git a/en-US/Beginning_Installation_Hard_Disk_common-note-1.xml b/en-US/Beginning_Installation_Hard_Disk_common-note-1.xml
deleted file mode 100644
index 2606265..0000000
--- a/en-US/Beginning_Installation_Hard_Disk_common-note-1.xml
+++ /dev/null
@@ -1,10 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE indexterm PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<important>
-  <title>Cannot Install from LVM Partitions</title>
-  <para>
-    You cannot use ISO files on partitions controlled by LVM (Logical Volume Management).
-  </para>
-</important>
diff --git a/en-US/Beginning_Installation_Hard_Disk_common-note-2.xml b/en-US/Beginning_Installation_Hard_Disk_common-note-2.xml
deleted file mode 100644
index dc2bf33..0000000
--- a/en-US/Beginning_Installation_Hard_Disk_common-note-2.xml
+++ /dev/null
@@ -1,10 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE indexterm PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<important>
-  <title>Use a leading slash</title>
-  <para>
-    An entry without a leading slash may cause the installation to fail.
-  </para>
-</important>
diff --git a/en-US/Beginning_Installation_Hard_Disk_common-para-1.xml b/en-US/Beginning_Installation_Hard_Disk_common-para-1.xml
deleted file mode 100644
index 34f0b4a..0000000
--- a/en-US/Beginning_Installation_Hard_Disk_common-para-1.xml
+++ /dev/null
@@ -1,7 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<para>
-	The <guilabel>Select Partition</guilabel> screen applies only if you are installing from a disk partition (that is, if you used the <literal>askmethod</literal> boot options and selected <guimenuitem>Hard Drive</guimenuitem> in the <guilabel>Installation Method</guilabel> dialog). This dialog allows you to name the disk partition and directory from which you are installing Fedora. If you used the <literal>repo=hd</literal> boot option, you already specified a partition.
-</para>
diff --git a/en-US/Beginning_Installation_Hard_Disk_common-para-10.xml b/en-US/Beginning_Installation_Hard_Disk_common-para-10.xml
deleted file mode 100644
index a7cddcb..0000000
--- a/en-US/Beginning_Installation_Hard_Disk_common-para-10.xml
+++ /dev/null
@@ -1,7 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE indexterm PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<para>
-  Also specify the <guilabel>Directory holding images</guilabel>. Enter the full directory path from the drive that contains the ISO image files.  The following table shows some examples of how to enter this information:
-</para>
diff --git a/en-US/Beginning_Installation_Hard_Disk_common-para-11.xml b/en-US/Beginning_Installation_Hard_Disk_common-para-11.xml
deleted file mode 100644
index 4c9a012..0000000
--- a/en-US/Beginning_Installation_Hard_Disk_common-para-11.xml
+++ /dev/null
@@ -1,8 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE indexterm PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<para>
-  Select <guibutton>OK</guibutton> to continue.  Proceed with <xref
-    linkend="sn-welcome-x86"/>.
-</para>
diff --git a/en-US/Beginning_Installation_Hard_Disk_common-para-3.xml b/en-US/Beginning_Installation_Hard_Disk_common-para-3.xml
deleted file mode 100644
index e969f52..0000000
--- a/en-US/Beginning_Installation_Hard_Disk_common-para-3.xml
+++ /dev/null
@@ -1,11 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-	  
-	  
-	  
-]>
-
-<para>
-		If the ISO images are in the root (top-level) directory of a partition, enter a <filename>/</filename>. If the ISO images are located in a subdirectory of a mounted partition, enter the name of the directory holding the ISO images within that partition. For example, if the partition on which the ISO images is normally mounted as <filename>/home/</filename>, and the images are in <filename>/home/new/</filename>, you would enter
-		<filename>/new/</filename>.
-	</para>
\ No newline at end of file
diff --git a/en-US/Beginning_Installation_Hard_Disk_common-para-5.xml b/en-US/Beginning_Installation_Hard_Disk_common-para-5.xml
deleted file mode 100644
index e8aed77..0000000
--- a/en-US/Beginning_Installation_Hard_Disk_common-para-5.xml
+++ /dev/null
@@ -1,8 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE indexterm PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<para>
-  The ISO files must be located on a hard drive that is either internal to the computer, or attached to the machine by USB. In addition the <filename>install.img</filename> file from within the ISO files must be copied to a directory named <filename class="directory">images</filename> Use this option to install Fedora on computers that are without a network connection or CD/DVD drives.
-</para>
-
diff --git a/en-US/Beginning_Installation_Hard_Disk_common-para-6.xml b/en-US/Beginning_Installation_Hard_Disk_common-para-6.xml
deleted file mode 100644
index ec364c1..0000000
--- a/en-US/Beginning_Installation_Hard_Disk_common-para-6.xml
+++ /dev/null
@@ -1,7 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE indexterm PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<para>
-  To extract the <filename>install.img</filename> from the ISO follow the procedure:
-</para>
diff --git a/en-US/Beginning_Installation_Hard_Disk_common-para-8.xml b/en-US/Beginning_Installation_Hard_Disk_common-para-8.xml
deleted file mode 100644
index a01925b..0000000
--- a/en-US/Beginning_Installation_Hard_Disk_common-para-8.xml
+++ /dev/null
@@ -1,7 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE indexterm PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<para>
-  Before you begin installation from a hard drive, check the partition type to ensure that Fedora can read it. To check a partition's file system under Windows, use the <application>Disk Management</application> tool. To check a partition's file system under Linux, use the <command>fdisk</command> utility.
-</para>
\ No newline at end of file
diff --git a/en-US/Beginning_Installation_Hard_Disk_common-para-9.xml b/en-US/Beginning_Installation_Hard_Disk_common-para-9.xml
deleted file mode 100644
index 1de7004..0000000
--- a/en-US/Beginning_Installation_Hard_Disk_common-para-9.xml
+++ /dev/null
@@ -1,7 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE indexterm PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<para>
-  Select the partition containing the ISO files from the list of available partitions. Internal IDE, SATA, SCSI, and USB drive device names begin with <filename>/dev/sd</filename>. Each individual drive has its own letter, for example <filename>/dev/sda</filename>. Each partition on a drive is numbered, for example <filename>/dev/sda1</filename>.
-</para>
diff --git a/en-US/Beginning_Installation_Hard_Disk_common-screen-1.xml b/en-US/Beginning_Installation_Hard_Disk_common-screen-1.xml
deleted file mode 100644
index 085e8cd..0000000
--- a/en-US/Beginning_Installation_Hard_Disk_common-screen-1.xml
+++ /dev/null
@@ -1,9 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE indexterm PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<screen>
-  <command>mount -t iso9660 /path/to/Fedora&PRODVER;.iso /mnt/point -o loop,ro</command>
-  <command>cp -pr /mnt/point/images /path/images/</command>
-  <command>umount /mnt/point</command>
-</screen>
diff --git a/en-US/Beginning_Installation_Hard_Disk_common-table-1.xml b/en-US/Beginning_Installation_Hard_Disk_common-table-1.xml
deleted file mode 100644
index 228629f..0000000
--- a/en-US/Beginning_Installation_Hard_Disk_common-table-1.xml
+++ /dev/null
@@ -1,30 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE indexterm PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<table id="table-Location_of_ISO_images" frame='all'><title>Location of ISO images for different partition types</title>
-    <tgroup cols='4' align='left' colsep='1' rowsep='1'>
-      <thead>
-	  <row>
-	    <entry>Partition type</entry>
-	    <entry>Volume</entry>
-	    <entry>Original path to files</entry>
-	    <entry>Directory to use</entry>
-	  </row>
-      </thead>
-      <tbody>  
-	  <row>
-	    <entry>VFAT</entry>
-	    <entry>D:\</entry>
-	    <entry>D:\Downloads\F&PRODVER;</entry>
-	    <entry>/Downloads/F&PRODVER;</entry>
-	  </row>
-	  <row>
-	    <entry>ext2, ext3, ext4</entry>
-	    <entry>/home</entry>
-	    <entry>/home/user1/F&PRODVER;</entry>
-	    <entry>/user1/F&PRODVER;</entry>
-	  </row>
-      </tbody>
-    </tgroup>
-</table>
diff --git a/en-US/Beginning_Installation_Hard_Disk_common-title-1.xml b/en-US/Beginning_Installation_Hard_Disk_common-title-1.xml
deleted file mode 100644
index f58d61f..0000000
--- a/en-US/Beginning_Installation_Hard_Disk_common-title-1.xml
+++ /dev/null
@@ -1,10 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE title PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-	  
-	  
-	  
-]>
-
-<title>Installing from a Hard Drive</title>
-
-<!-- Beginning_Installation_Hard_Disk_common-title-1.xml -->
\ No newline at end of file
diff --git a/en-US/Beginning_Installation_Hard_Disk_x86_ppc-figure-1.xml b/en-US/Beginning_Installation_Hard_Disk_x86_ppc-figure-1.xml
deleted file mode 100644
index 72ab6b8..0000000
--- a/en-US/Beginning_Installation_Hard_Disk_x86_ppc-figure-1.xml
+++ /dev/null
@@ -1,16 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE figure PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-	  
-	  
-	  
-]>
-
-<figure float="0"><title>Selecting Partition Dialog for Hard Drive Installation</title>
-		<mediaobject>
-			<imageobject><imagedata fileref="images/begininstall/hd.png" format="PNG"/></imageobject>
-			<textobject><para>
-					Selecting partition dialog for a hard drive installation.
-				</para>
-			</textobject>
-		</mediaobject>
-	</figure>
\ No newline at end of file
diff --git a/en-US/Beginning_Installation_NFS-x86.xml b/en-US/Beginning_Installation_NFS-x86.xml
deleted file mode 100644
index d9b03b4..0000000
--- a/en-US/Beginning_Installation_NFS-x86.xml
+++ /dev/null
@@ -1,40 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<section  id="s1-begininstall-nfs-x86">
-		
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Beginning_Installation_NFS_common-title-1.xml"/>
-	<!-- Title: Installing via NFS -->
-	
-	<!-- Index terms -->
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Beginning_Installation_NFS_common-indexterm-1.xml"/>
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Beginning_Installation_NFS_common-indexterm-2.xml"/>
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Beginning_Installation_NFS_common-indexterm-3.xml"/>
-	<!-- End Index terms -->
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Beginning_Installation_NFS_common-para-1.xml"/>
-	<!-- The NFS dialog applies only if... -->
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Beginning_Installation_NFS_common-para-2.xml"/>
-	<!-- Enter the domain name or IP address of your NFS server ... -->
-	
-	<para>
-		Next, enter the name of the exported directory. If you followed the setup described in <xref linkend="s1-steps-network-installs-x86"/>, you would enter the directory <filename><replaceable>/export/directory/</replaceable></filename>.
-	</para>
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Beginning_Installation_NFS_common-para-4.xml"/>
-	<!-- If the NFS Server is exporting a mirror... -->
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Beginning_Installation_NFS_common-figure-1.xml"/>
-	<!-- NFS Setup Dialog -->
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Beginning_Installation_NFS_common-indexterm-4.xml"/>
-	<!-- Index term -->
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Beginning_Installation_NFS_common-para-5.xml"/>
-	<!-- If the NFS server is exporting ... -->
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Beginning_Installation_NFS_common-para-6.xml"/>
-	<!-- Next, the Welcome dialog appears -->
-</section>
\ No newline at end of file
diff --git a/en-US/Beginning_Installation_NFS_common-figure-1.xml b/en-US/Beginning_Installation_NFS_common-figure-1.xml
deleted file mode 100644
index be0bc84..0000000
--- a/en-US/Beginning_Installation_NFS_common-figure-1.xml
+++ /dev/null
@@ -1,16 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE figure PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-	  
-	  
-	  
-]>
-
-<figure float="0"><title>NFS Setup Dialog</title>
-	<mediaobject>
-		<imageobject><imagedata fileref="images/begininstall/nfs.png" format="PNG"/></imageobject>
-		<textobject><para>
-				NFS setup dialog.
-			</para>
-		</textobject>
-	</mediaobject>
-</figure>
\ No newline at end of file
diff --git a/en-US/Beginning_Installation_NFS_common-indexterm-1.xml b/en-US/Beginning_Installation_NFS_common-indexterm-1.xml
deleted file mode 100644
index c074258..0000000
--- a/en-US/Beginning_Installation_NFS_common-indexterm-1.xml
+++ /dev/null
@@ -1,12 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE indexterm PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-	  
-	  
-	  
-]>
-
-
-<indexterm significance="normal">
-		<primary>NFS</primary>
-		<secondary>installation</secondary>
-	</indexterm>
\ No newline at end of file
diff --git a/en-US/Beginning_Installation_NFS_common-indexterm-2.xml b/en-US/Beginning_Installation_NFS_common-indexterm-2.xml
deleted file mode 100644
index f2deaac..0000000
--- a/en-US/Beginning_Installation_NFS_common-indexterm-2.xml
+++ /dev/null
@@ -1,11 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE indexterm PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-	  
-	  
-	  
-]>
-
-<indexterm significance="normal">
-		<primary>installation</primary>
-		<secondary>NFS</secondary>
-	</indexterm>
\ No newline at end of file
diff --git a/en-US/Beginning_Installation_NFS_common-indexterm-3.xml b/en-US/Beginning_Installation_NFS_common-indexterm-3.xml
deleted file mode 100644
index cb28f91..0000000
--- a/en-US/Beginning_Installation_NFS_common-indexterm-3.xml
+++ /dev/null
@@ -1,12 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE indexterm PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-	  
-	  
-	  
-]>
-
-<indexterm significance="normal">
-		<primary>network</primary>
-		<secondary>installations</secondary>
-		<tertiary>NFS</tertiary>
-	</indexterm>
\ No newline at end of file
diff --git a/en-US/Beginning_Installation_NFS_common-indexterm-4.xml b/en-US/Beginning_Installation_NFS_common-indexterm-4.xml
deleted file mode 100644
index 6ccc09f..0000000
--- a/en-US/Beginning_Installation_NFS_common-indexterm-4.xml
+++ /dev/null
@@ -1,12 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE indexterm PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-	  
-	  
-	  
-]>
-
-<indexterm significance="normal">
-		<primary>installation</primary>
-		<secondary>NFS</secondary>
-		<tertiary>server information</tertiary>
-	</indexterm>
\ No newline at end of file
diff --git a/en-US/Beginning_Installation_NFS_common-para-1.xml b/en-US/Beginning_Installation_NFS_common-para-1.xml
deleted file mode 100644
index d9a15b5..0000000
--- a/en-US/Beginning_Installation_NFS_common-para-1.xml
+++ /dev/null
@@ -1,10 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-	  
-	  
-	  
-]>
-
-<para>
-	The NFS dialog applies only if you booted with the <literal>askmethod</literal> boot option and selected <guimenuitem>NFS Image</guimenuitem> in the <guilabel>Installation Method</guilabel> dialog. If you used the <literal>repo=nfs</literal>boot option, you already specified a server and path.
-</para>
\ No newline at end of file
diff --git a/en-US/Beginning_Installation_NFS_common-para-2.xml b/en-US/Beginning_Installation_NFS_common-para-2.xml
deleted file mode 100644
index 946a767..0000000
--- a/en-US/Beginning_Installation_NFS_common-para-2.xml
+++ /dev/null
@@ -1,10 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-	  
-	  
-	  
-]>
-
-<para>
-	Enter the domain name or IP address of your NFS server. For example, if you are installing from a host named <filename>eastcoast</filename> in the domain <filename>example.com</filename>, enter <filename>eastcoast.example.com</filename> in the <guilabel>NFS Server</guilabel> field.
-</para>
\ No newline at end of file
diff --git a/en-US/Beginning_Installation_NFS_common-para-4.xml b/en-US/Beginning_Installation_NFS_common-para-4.xml
deleted file mode 100644
index eb1ad23..0000000
--- a/en-US/Beginning_Installation_NFS_common-para-4.xml
+++ /dev/null
@@ -1,8 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-
-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<para>
-	If the NFS server is exporting a mirror of the Fedora installation tree, enter the directory which contains the root of the installation tree. If everything was specified properly, a message appears indicating that the installation program for Fedora is running.
-</para>
\ No newline at end of file
diff --git a/en-US/Beginning_Installation_NFS_common-para-5.xml b/en-US/Beginning_Installation_NFS_common-para-5.xml
deleted file mode 100644
index 84e1543..0000000
--- a/en-US/Beginning_Installation_NFS_common-para-5.xml
+++ /dev/null
@@ -1,7 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<para>
-	If the NFS server is exporting the ISO images of the Fedora CD-ROMs, enter the directory which contains the ISO images.
-</para>
\ No newline at end of file
diff --git a/en-US/Beginning_Installation_NFS_common-para-6.xml b/en-US/Beginning_Installation_NFS_common-para-6.xml
deleted file mode 100644
index 6be8e7b..0000000
--- a/en-US/Beginning_Installation_NFS_common-para-6.xml
+++ /dev/null
@@ -1,7 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<para>
-	Next, the <guilabel>Welcome</guilabel> dialog appears.
-</para>
\ No newline at end of file
diff --git a/en-US/Beginning_Installation_NFS_common-title-1.xml b/en-US/Beginning_Installation_NFS_common-title-1.xml
deleted file mode 100644
index 85c6494..0000000
--- a/en-US/Beginning_Installation_NFS_common-title-1.xml
+++ /dev/null
@@ -1,8 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE title PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-	  
-	  
-	  
-]>
-
-<title>Installing via NFS</title>
\ No newline at end of file
diff --git a/en-US/Beginning_Installation_Network-x86.xml b/en-US/Beginning_Installation_Network-x86.xml
deleted file mode 100644
index 7746cd6..0000000
--- a/en-US/Beginning_Installation_Network-x86.xml
+++ /dev/null
@@ -1,53 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<section id="s1-begininstall-perform-nfs-x86">
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Beginning_Installation_Network_x86_ppc-title.xml"/>
-	<!-- Performing a Network Installation -->
-	
-	<!-- Index terms -->
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Beginning_Installation_Network_x86_ppc-indexterm-1.xml"/>
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Beginning_Installation_Network_x86_ppc-indexterm-2.xml"/>
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Beginning_Installation_Network_x86_ppc-indexterm-3.xml"/>
-	<!-- End Index terms -->
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Beginning_Installation_Network_x86_ppc-para-3.xml"/>
-	<!-- The installation program is network-aware,  -->
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Beginning_Installation_Network_x86_ppc-para-1.xml"/>
-	<!-- If you are performing a network installation,  -->
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Beginning_Installation_Network_x86_ppc-para-4.xml"/>
-	<!-- By default, the installation program uses DHCP...  -->
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Beginning_Installation_Network_x86_ppc-para-2.xml"/>
-	<!-- Enter the IP address you are using during installation...  -->
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Beginning_Installation_Network_x86_ppc-para-5.xml"/>
-	<!-- The installation program supports only the IPv4 protocol.  -->
-	
-	<figure float="0" id="fig-x86-configuretcpip"><title>TCP/IP Configuration</title>
-		<mediaobject>
-			<imageobject><imagedata fileref="images/begininstall/configure_tcp.png" format="PNG"/></imageobject>
-			<textobject><para>
-					Configure the network device address(es) for installation.
-				</para>
-			</textobject>
-		</mediaobject>
-	</figure>
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Beginning_Installation_Network_x86_ppc-para-6.xml"/>
-	<!-- These settings apply only during the installation process.  -->
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Beginning_Installation_Network_x86_ppc-para-7.xml"/>
-	<!-- You can install from a Web, FTP, or NFS server either on...  -->
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Beginning_Installation_Network_x86_ppc-para-8.xml"/>
-	<!-- The Fedora Project maintains a list of Web and FTP public...  -->
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Beginning_Installation_Network_x86_ppc-list-1.xml"/>
-	<!-- If you are installing via NFS, proceed to...  -->
-	
-</section>
\ No newline at end of file
diff --git a/en-US/Beginning_Installation_Network_x86_ppc-indexterm-1.xml b/en-US/Beginning_Installation_Network_x86_ppc-indexterm-1.xml
deleted file mode 100644
index c90c6d5..0000000
--- a/en-US/Beginning_Installation_Network_x86_ppc-indexterm-1.xml
+++ /dev/null
@@ -1,11 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE indexterm PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-	  
-	  
-	  
-]>
-
-<indexterm significance="normal">
-		<primary>network installation</primary>
-		<secondary>performing</secondary>
-</indexterm>
\ No newline at end of file
diff --git a/en-US/Beginning_Installation_Network_x86_ppc-indexterm-2.xml b/en-US/Beginning_Installation_Network_x86_ppc-indexterm-2.xml
deleted file mode 100644
index dec1349..0000000
--- a/en-US/Beginning_Installation_Network_x86_ppc-indexterm-2.xml
+++ /dev/null
@@ -1,7 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE indexterm PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<indexterm significance="normal">
-		<primary>TCP/IP configuration</primary>
-	</indexterm>
\ No newline at end of file
diff --git a/en-US/Beginning_Installation_Network_x86_ppc-indexterm-3.xml b/en-US/Beginning_Installation_Network_x86_ppc-indexterm-3.xml
deleted file mode 100644
index 4d18dd6..0000000
--- a/en-US/Beginning_Installation_Network_x86_ppc-indexterm-3.xml
+++ /dev/null
@@ -1,8 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE indexterm PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<indexterm significance="normal">
-    <primary>NFS (Network File System)</primary>
-    <secondary>install from</secondary>
-  </indexterm>
\ No newline at end of file
diff --git a/en-US/Beginning_Installation_Network_x86_ppc-list-1.xml b/en-US/Beginning_Installation_Network_x86_ppc-list-1.xml
deleted file mode 100644
index 431907b..0000000
--- a/en-US/Beginning_Installation_Network_x86_ppc-list-1.xml
+++ /dev/null
@@ -1,18 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-    <itemizedlist>
-      <listitem>
-	<para>
-	  If you are installing via NFS, proceed to <xref
-	    linkend="s1-begininstall-nfs-x86"/>.
-	</para>
-      </listitem>
-      <listitem>
-	<para>
-	  If you are installing via Web or FTP, proceed to <xref
-	    linkend="s1-begininstall-url-x86"/>.
-	</para>
-      </listitem>
-    </itemizedlist>
diff --git a/en-US/Beginning_Installation_Network_x86_ppc-para-1.xml b/en-US/Beginning_Installation_Network_x86_ppc-para-1.xml
deleted file mode 100644
index 73bd3a9..0000000
--- a/en-US/Beginning_Installation_Network_x86_ppc-para-1.xml
+++ /dev/null
@@ -1,7 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<para>
-	If you are performing a network installation, the <guilabel>Configure TCP/IP</guilabel> dialog appears. This dialog asks for your IP and other network addresses. You can choose to configure the IP address and Netmask of the device via DHCP or manually. 
-</para>
\ No newline at end of file
diff --git a/en-US/Beginning_Installation_Network_x86_ppc-para-2.xml b/en-US/Beginning_Installation_Network_x86_ppc-para-2.xml
deleted file mode 100644
index f296f02..0000000
--- a/en-US/Beginning_Installation_Network_x86_ppc-para-2.xml
+++ /dev/null
@@ -1,7 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<para>
-	Enter the IP address you are using during installation and press <keycap>Enter</keycap>. 
-</para>
\ No newline at end of file
diff --git a/en-US/Beginning_Installation_Network_x86_ppc-para-3.xml b/en-US/Beginning_Installation_Network_x86_ppc-para-3.xml
deleted file mode 100644
index 795546f..0000000
--- a/en-US/Beginning_Installation_Network_x86_ppc-para-3.xml
+++ /dev/null
@@ -1,7 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<para>
-  The installation program is network-aware and can use network settings for a number of functions.  For instance, if you boot the installer with the <literal>askmethod</literal> or <literal>repo=</literal> options, you can install Fedora from a network server using FTP, HTTP, or NFS protocols.  You can also instruct the installation program to consult additional software repositories later in the process.
-</para>
\ No newline at end of file
diff --git a/en-US/Beginning_Installation_Network_x86_ppc-para-4.xml b/en-US/Beginning_Installation_Network_x86_ppc-para-4.xml
deleted file mode 100644
index 393ead5..0000000
--- a/en-US/Beginning_Installation_Network_x86_ppc-para-4.xml
+++ /dev/null
@@ -1,7 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<para>
-  By default, the installation program uses DHCP to automatically provide network settings. If you use a cable or DSL modem, router, firewall, or other network hardware to communicate with the Internet, DHCP is a suitable option. If your network has no DHCP server, clear the check box labeled <guilabel>Use dynamic IP configuration (DHCP)</guilabel>.
-</para>
\ No newline at end of file
diff --git a/en-US/Beginning_Installation_Network_x86_ppc-para-5.xml b/en-US/Beginning_Installation_Network_x86_ppc-para-5.xml
deleted file mode 100644
index c7e6106..0000000
--- a/en-US/Beginning_Installation_Network_x86_ppc-para-5.xml
+++ /dev/null
@@ -1,8 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<para>
-  The installation program supports the IPv4 and IPv6 protocols.
-</para>
-
diff --git a/en-US/Beginning_Installation_Network_x86_ppc-para-6.xml b/en-US/Beginning_Installation_Network_x86_ppc-para-6.xml
deleted file mode 100644
index 5210dcf..0000000
--- a/en-US/Beginning_Installation_Network_x86_ppc-para-6.xml
+++ /dev/null
@@ -1,8 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-    <para>
-      When the installation process completes, it will transfer these settings to your system. 
-    </para>
-
diff --git a/en-US/Beginning_Installation_Network_x86_ppc-para-7.xml b/en-US/Beginning_Installation_Network_x86_ppc-para-7.xml
deleted file mode 100644
index 4e121d9..0000000
--- a/en-US/Beginning_Installation_Network_x86_ppc-para-7.xml
+++ /dev/null
@@ -1,13 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-    <para>
-      You can install from a Web, FTP, or NFS server either on your
-      local network or, if you are connected, on the Internet. You may
-      install Fedora from your own private mirror, or use one of the
-      public mirrors maintained by members of the community. To ensure
-      that the connection is as fast and reliable as possible, use a
-      server that is close to your own geographical location.
-    </para>
-
diff --git a/en-US/Beginning_Installation_Network_x86_ppc-para-8.xml b/en-US/Beginning_Installation_Network_x86_ppc-para-8.xml
deleted file mode 100644
index c51a865..0000000
--- a/en-US/Beginning_Installation_Network_x86_ppc-para-8.xml
+++ /dev/null
@@ -1,14 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-    <para>
-      The Fedora Project maintains a list of Web and FTP public mirrors, sorted
-      by region, at <ulink
-	url="http://fedoraproject.org/wiki/Mirrors"/>. To determine the
-      complete directory path for the installation files, add
-      <filename>/&PRODVER;/Fedora/<replaceable>architecture</replaceable>/os/</filename> 
-      to the path shown on the web page.  A correct mirror location for
-      an <systemitem>i386</systemitem> system resembles the URL
-      <literal>http://mirror.example.com/pub/fedora/linux/releases/&PRODVER;/Fedora/i386/os</literal>.
-    </para>
diff --git a/en-US/Beginning_Installation_Network_x86_ppc-title.xml b/en-US/Beginning_Installation_Network_x86_ppc-title.xml
deleted file mode 100644
index 5d6ebc0..0000000
--- a/en-US/Beginning_Installation_Network_x86_ppc-title.xml
+++ /dev/null
@@ -1,7 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE title PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-	  
-	  
-	  
-]>
-<title>Performing a Network Installation</title>
\ No newline at end of file
diff --git a/en-US/Beginning_Installation_URL-common-figure-1.xml b/en-US/Beginning_Installation_URL-common-figure-1.xml
deleted file mode 100644
index 4e878e3..0000000
--- a/en-US/Beginning_Installation_URL-common-figure-1.xml
+++ /dev/null
@@ -1,13 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE figure PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<figure float="0"><title>URL Setup Dialog</title>
-	<mediaobject>
-		<imageobject><imagedata fileref="images/begininstall/url.png" format="PNG"/></imageobject>
-		<textobject><para>
-				URL setup dialog.
-			</para>
-		</textobject>
-	</mediaobject>
-</figure>
\ No newline at end of file
diff --git a/en-US/Beginning_Installation_URL-common-indexterm-1.xml b/en-US/Beginning_Installation_URL-common-indexterm-1.xml
deleted file mode 100644
index 4b954a7..0000000
--- a/en-US/Beginning_Installation_URL-common-indexterm-1.xml
+++ /dev/null
@@ -1,13 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE indexterm PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-	  
-	  
-	  
-]>
-
-<indexterm significance="normal">
-	<primary>network</primary>
-	<secondary>installations</secondary>
-	<tertiary>HTTP</tertiary>
-</indexterm>
-
diff --git a/en-US/Beginning_Installation_URL-common-indexterm-2.xml b/en-US/Beginning_Installation_URL-common-indexterm-2.xml
deleted file mode 100644
index 5df39fc..0000000
--- a/en-US/Beginning_Installation_URL-common-indexterm-2.xml
+++ /dev/null
@@ -1,11 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE indexterm PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-	  
-	  
-	  
-]>
-
-<indexterm significance="normal">
-	<primary>HTTP</primary>
-	<secondary>installation</secondary>
-</indexterm>
\ No newline at end of file
diff --git a/en-US/Beginning_Installation_URL-common-indexterm-3.xml b/en-US/Beginning_Installation_URL-common-indexterm-3.xml
deleted file mode 100644
index b7ffa50..0000000
--- a/en-US/Beginning_Installation_URL-common-indexterm-3.xml
+++ /dev/null
@@ -1,11 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE indexterm PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-	  
-	  
-	  
-]>
-
-<indexterm significance="normal">
-	<primary>installation</primary>
-	<secondary>HTTP</secondary>
-</indexterm>
\ No newline at end of file
diff --git a/en-US/Beginning_Installation_URL-common-para-1.xml b/en-US/Beginning_Installation_URL-common-para-1.xml
deleted file mode 100644
index ac0fd76..0000000
--- a/en-US/Beginning_Installation_URL-common-para-1.xml
+++ /dev/null
@@ -1,8 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<para>
-	The URL dialog applies only if you are installing from a FTP or HTTP server (if you selected <guimenuitem>URL</guimenuitem> in the <guilabel>Installation Method</guilabel> dialog). This dialog prompts you for information about
-	the FTP or HTTP server from which you are installing Fedora.
-</para>
\ No newline at end of file
diff --git a/en-US/Beginning_Installation_URL-common-para-2-Fedora.xml b/en-US/Beginning_Installation_URL-common-para-2-Fedora.xml
deleted file mode 100644
index a3dd700..0000000
--- a/en-US/Beginning_Installation_URL-common-para-2-Fedora.xml
+++ /dev/null
@@ -1,8 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-
-<para>
-	Enter the URL for the directory that contains the installation image file (<filename>install.img</filename>) on your chosen FTP or HTTP site and press <keycap>Enter</keycap>. By default, this directory will be named <filename>/pub/fedora/linux/releases/&PRODVER;/Fedora/<replaceable>arch</replaceable>/os/images/</filename>, where <replaceable>arch</replaceable> is replaced with the architecture type of your system, such as i386. The complete URL will therefore resemble this example:<filename>http://download.fedoraproject.org/pub/fedora/linux/releases/&PRODVER;/Fedora/i386/os/images</filename>. Specify the address of a proxy server, and if necessary, provide a port number, username, and password. If the system can reach the URL that you provided, and can find a file named <filename>install.img</filename> at that location, a message box appears indicating that files are being retrieved from the server.
-</para>
diff --git a/en-US/Beginning_Installation_URL-common-para-3.xml b/en-US/Beginning_Installation_URL-common-para-3.xml
deleted file mode 100644
index 6be8e7b..0000000
--- a/en-US/Beginning_Installation_URL-common-para-3.xml
+++ /dev/null
@@ -1,7 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<para>
-	Next, the <guilabel>Welcome</guilabel> dialog appears.
-</para>
\ No newline at end of file
diff --git a/en-US/Beginning_Installation_URL-common-title-1.xml b/en-US/Beginning_Installation_URL-common-title-1.xml
deleted file mode 100644
index bf7e57a..0000000
--- a/en-US/Beginning_Installation_URL-common-title-1.xml
+++ /dev/null
@@ -1,5 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE title PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<title>Installing via FTP or HTTP</title>
\ No newline at end of file
diff --git a/en-US/Beginning_Installation_URL-x86.xml b/en-US/Beginning_Installation_URL-x86.xml
deleted file mode 100644
index 2598a25..0000000
--- a/en-US/Beginning_Installation_URL-x86.xml
+++ /dev/null
@@ -1,33 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<section id="s1-begininstall-url-x86">
-		
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Beginning_Installation_URL-common-title-1.xml"/>
-	<!-- Installing via HTTP -->
-	
-	<!-- Index terms -->
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Beginning_Installation_URL-common-indexterm-1.xml"/>
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Beginning_Installation_URL-common-indexterm-2.xml"/>
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Beginning_Installation_URL-common-indexterm-3.xml"/>
-	<!-- End Index terms -->
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Beginning_Installation_URL-common-para-1.xml"/>
-	<!-- The HTTP dialog applies only if you are installing... -->
-	
-	<!-- <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Beginning_Installation_URL-common-para-2.xml"/> -->
-	<!-- RHEL version of paragraph -->
-	<!-- Enter the name or IP address of the HTTP site... -->
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Beginning_Installation_URL-common-para-2-Fedora.xml"/>
-	<!-- Enter the name or IP address of the HTTP site... -->
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Beginning_Installation_URL-common-figure-1.xml"/>
-	<!-- HTTP Setup Dialog -->
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Beginning_Installation_URL-common-para-3.xml"/>
-	<!-- Next, the Welcome dialog appears -->
-	
-</section>
\ No newline at end of file
diff --git a/en-US/Beginning_Installation_x86_ppc-indexterm-1.xml b/en-US/Beginning_Installation_x86_ppc-indexterm-1.xml
deleted file mode 100644
index 4150c19..0000000
--- a/en-US/Beginning_Installation_x86_ppc-indexterm-1.xml
+++ /dev/null
@@ -1,12 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE indexterm PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-
-<indexterm significance="normal"> 
-	<primary>installation</primary>
-	<secondary>starting</secondary>
-</indexterm>
\ No newline at end of file
diff --git a/en-US/Beginning_Installation_x86_ppc-indexterm-2.xml b/en-US/Beginning_Installation_x86_ppc-indexterm-2.xml
deleted file mode 100644
index d4dc669..0000000
--- a/en-US/Beginning_Installation_x86_ppc-indexterm-2.xml
+++ /dev/null
@@ -1,11 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE indexterm PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<indexterm significance="normal">
-	<primary>starting</primary>
-	<secondary>installation</secondary>
-</indexterm>
\ No newline at end of file
diff --git a/en-US/Beginning_Installation_x86_ppc-indexterm-3.xml b/en-US/Beginning_Installation_x86_ppc-indexterm-3.xml
deleted file mode 100644
index 0cc18ac..0000000
--- a/en-US/Beginning_Installation_x86_ppc-indexterm-3.xml
+++ /dev/null
@@ -1,11 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE indexterm PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<indexterm significance="normal">
-	<primary>CD-ROM</primary>
-	<secondary>IDE</secondary>
-</indexterm>
\ No newline at end of file
diff --git a/en-US/Beginning_Installation_x86_ppc-indexterm-4.xml b/en-US/Beginning_Installation_x86_ppc-indexterm-4.xml
deleted file mode 100644
index 633773f..0000000
--- a/en-US/Beginning_Installation_x86_ppc-indexterm-4.xml
+++ /dev/null
@@ -1,11 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE indexterm PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<indexterm significance="normal">
-	<primary>CD-ROM</primary>
-	<secondary>ATAPI</secondary>
-</indexterm>
\ No newline at end of file
diff --git a/en-US/Beginning_Installation_x86_ppc-indexterm-5.xml b/en-US/Beginning_Installation_x86_ppc-indexterm-5.xml
deleted file mode 100644
index f355e29..0000000
--- a/en-US/Beginning_Installation_x86_ppc-indexterm-5.xml
+++ /dev/null
@@ -1,11 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE indexterm PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<indexterm significance="normal">
-	<primary>installation</primary>
-	<secondary>CD-ROM</secondary>
-</indexterm>
\ No newline at end of file
diff --git a/en-US/Beginning_Installation_x86_ppc-indexterm-6.xml b/en-US/Beginning_Installation_x86_ppc-indexterm-6.xml
deleted file mode 100644
index fb3deac..0000000
--- a/en-US/Beginning_Installation_x86_ppc-indexterm-6.xml
+++ /dev/null
@@ -1,11 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE indexterm PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<indexterm significance="normal">
-	<primary>CD-ROM</primary>
-	<secondary>installation from</secondary>
-</indexterm>
\ No newline at end of file
diff --git a/en-US/Beginning_Installation_x86_ppc-para-1.xml b/en-US/Beginning_Installation_x86_ppc-para-1.xml
deleted file mode 100644
index 44a483c..0000000
--- a/en-US/Beginning_Installation_x86_ppc-para-1.xml
+++ /dev/null
@@ -1,7 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<para>
-	To install Fedora from a DVD/CD-ROM, place the DVD or CD #1 in your DVD/CD-ROM drive and boot your system from the DVD/CD-ROM.<!--choose the <guilabel>Local CD-ROM</guilabel> option if you booted using the <command>linux askmethod</command>  and select <guibutton>OK</guibutton>. When prompted, insert the Fedora CD or DVD into your CD/DVD-ROM drive (if you did not boot from the CD). Once the disk is in the CD/DVD-ROM drive, select <guibutton>OK</guibutton>, and press <keycap>Enter</keycap>.--> Even if you booted from alternative media, you can still install Fedora from CD or DVD media.
-</para>
diff --git a/en-US/Beginning_Installation_x86_ppc-para-3.xml b/en-US/Beginning_Installation_x86_ppc-para-3.xml
deleted file mode 100644
index fab5b53..0000000
--- a/en-US/Beginning_Installation_x86_ppc-para-3.xml
+++ /dev/null
@@ -1,11 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<para>
-	If your CD-ROM drive is not detected, and it is a SCSI CD-ROM, the installation program prompts you to choose a SCSI driver. Choose the driver that most closely resembles your adapter. You may specify options for the driver if necessary; however, most
-	drivers detect your SCSI adapter automatically.
-</para>
\ No newline at end of file
diff --git a/en-US/Beginning_Installation_x86_ppc-title-1.xml b/en-US/Beginning_Installation_x86_ppc-title-1.xml
deleted file mode 100644
index 40cfa16..0000000
--- a/en-US/Beginning_Installation_x86_ppc-title-1.xml
+++ /dev/null
@@ -1,8 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE title PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<title>Installing from DVD/CD-ROM</title>
\ No newline at end of file
diff --git a/en-US/Book_Info.xml b/en-US/Book_Info.xml
deleted file mode 100644
index 0780836..0000000
--- a/en-US/Book_Info.xml
+++ /dev/null
@@ -1,27 +0,0 @@
-<?xml version='1.0'?>
-<!DOCTYPE bookinfo PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd">
-
-<bookinfo id="Installation_Guide">
-	<title>Installation Guide</title>
-	<subtitle>Installing Fedora 13 on x86, AMD64, and Intel 64 architectures</subtitle>
-	<productname>Fedora</productname>
-	<productnumber>13</productnumber>
-	<edition>1.0</edition>
-	<pubsnumber>1</pubsnumber>
-	<abstract>
-		<para>Provides documentation for the installation process.</para>
-	</abstract>
-	<corpauthor>
-		<inlinemediaobject>
-			<imageobject>
-				<imagedata format='SVG' fileref="Common_Content/images/title_logo.svg" />
-			</imageobject>
-			<textobject><phrase>Fedora Documentation Team</phrase></textobject>
-		</inlinemediaobject>
-	</corpauthor>
-	<xi:include href="Common_Content/Legal_Notice.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
-	<xi:include href="Author_Group.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
-</bookinfo>
-
-
-
diff --git a/en-US/Boot-x86.xml b/en-US/Boot-x86.xml
deleted file mode 100644
index 69f313c..0000000
--- a/en-US/Boot-x86.xml
+++ /dev/null
@@ -1,144 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
- "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd">
-
-<chapter id="ch-Boot-x86">
-	<xi:include href="Boot_x86_ppc-title-1.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
-	<!-- Booting the Installer -->
-
-<!-- start indexterms -->
-	<indexterm>
-		<primary>BIOS (Basic Input/Output System)</primary>
-	</indexterm>
-	<xi:include href="Boot_x86_ppc-indexterm-1.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
-	<!-- CD/DVD media - booting -->
-	<xi:include href="Boot_x86_ppc-indexterm-2.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
-	<!-- USB flash media - booting -->
-<!-- end indexterms -->
-
-	<xi:include href="Important_UEFI.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
-	<!-- The CD and DVD media include boot catalog entries for both BIOS and UEFI firmware interfaces -->
-
-	<xi:include href="Boot_x86_ppc-para-1.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
-	<!-- To start the installation program from a Fedrora CD, DVD, or minimal boot media, -->
-	
-	<procedure>
-		<step>
-			<para>
-				Disconnect any external FireWire or USB disks that you do not need for installation.  Refer to <xref linkend="sn-partitioning-fw-usb-x86"/> for more information.
-			</para>
-		</step>
-		<step>
-			<para>
-				Power on your computer system.
-			</para>
-		</step>
-		<step>
-			<para>
-				Insert the media in your computer.
-			</para>
-		</step>
-		<step>
-			<para>
-				Power off your computer with the boot media still inside.
-			</para>
-		</step>
-		<step>
-			<para>
-				Power on your computer system.
-			</para>
-		</step>
-	</procedure>
-
-<!-- the following paras describe BIOS settings and are therefore relevant only to x86 -->
-	<xi:include href="Boot_Order-para-1.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
-	<xi:include href="Boot_Order-para-2.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
-	<xi:include href="Boot_Order-para-3.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
-	<xi:include href="Boot_Order-para-4.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
-	<xi:include href="Boot_Order-para-5.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
-<!-- end x86-specific material -->
-
-	<xi:include href="Note_Aborting_Installation.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
-	<!-- The CD and DVD media include boot catalog entries for both BIOS and UEFI firmware interfaces -->
-
-
-	<section id="sn-boot-menu-x86">
-		<xi:include href="Boot_x86_ppc-title-2.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
-		<!-- The Boot Menu -->
-		
-		<xi:include href="Boot_x86_ppc-para-2.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
-		<!-- The boot media displays a graphical boot menu with several options. -->
-		
-		<para>
-			When using Fedora Live media, press any key during the initial boot countdown to bring up the <guilabel>Boot Options</guilabel> menu.
-		</para>
-      
-		<xi:include href="Boot_x86_ppc-figure-1.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
-		<!-- The boot screen. -->
-		
-		<xi:include href="Boot_x86_ppc-para-3.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
-		<!-- For a listing and explanation of common boot options, refer  -->
-		
-		<xi:include href="Boot_x86_ppc-para-4.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
-		<!-- If you boot the DVD, rescue CD, or minimal boot media, the boot menu options include:  -->
-		
-		<xi:include href="Boot_x86_ppc-variablelist-1.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
-		<!-- Install or upgrade an existing system  -->
-		
-	</section>
-	
-	<section id="sn-install-diff-source-x86">
-		<xi:include href="Boot_x86_ppc-title-3.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
-		<!-- Installing from a Different Source -->
-		
-		<xi:include href="Boot_x86_ppc-para-5.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
-		<!-- You can install Red Hat Enterprise Linux from the ISO images stored  -->
-		
-		<xi:include href="Boot_x86_ppc-para-6.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
-		<!-- The following table summarizes the different boot methods  -->
-		
-		<xi:include href="Boot_x86_ppc-table-1.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
-		<!-- Boot methods and installation methods  -->
-		
-		<para>
-			Refer to <xref linkend="s1-installmethod-x86"/> for information about installing from locations other than the media with which you booted the system.
-		</para>
-	</section>
-	<section id="sn-booting-from-pxe-x86">
-		<xi:include href="Boot_x86_ppc-title-4.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
-		<!-- Booting from the Network using PXE -->
-		
-		<xi:include href="Boot_x86_ppc-para-7.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
-		<!-- To boot with PXE, you need a properly configured server  -->
-		
-		<para>
-			Configure the computer to boot from the network interface.  This option is in the BIOS, and may be labeled <option>Network Boot</option> or <option>Boot Services</option>.  Once you properly configure PXE booting, the computer can boot the Fedora installation system without any other media.
-		</para>
-		
-		<xi:include href="Boot_x86_ppc-para-8.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
-		<!-- To boot a computer from a PXE server:  -->
-		
-		<xi:include href="Boot_x86_ppc-procedure-1.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
-		<!-- Ensure that the network cable is attached  -->
-		
-		<para>
-			If your PC does not boot from the netboot server, ensure that the BIOS is configured to boot first from the correct network interface.  Some BIOS systems specify the network interface as a possible boot device, but do not support the PXE standard. Refer to your hardware documentation for more information.
-		</para>
-		
-		<xi:include href="Note-Multiple_NICs_and_PXE.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
-		<!-- Some servers with multiple network interfaces might not assign  -->
-		
-	</section>
-	
-</chapter>
-
-
-<!--
-Local variables:
-mode: xml
-fill-column: 72
-End:
--->
-<!-- 
-vim: softtabstop=2:shiftwidth=2:expandtab:textwidth=72 
--->
diff --git a/en-US/Boot_Init_Shutdown.xml b/en-US/Boot_Init_Shutdown.xml
deleted file mode 100644
index d4da316..0000000
--- a/en-US/Boot_Init_Shutdown.xml
+++ /dev/null
@@ -1,770 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<appendix id="ch-boot-init-shutdown"><title>Boot Process, Init, and Shutdown</title>
-	<indexterm significance="normal">
-		<primary>boot process</primary>
-	</indexterm>
-
-	<para>
-		An important and powerful aspect of Fedora is the open, user-configurable method it uses for starting the operating system. Users are free to configure many aspects of the boot process, including specifying the programs launched at boot-time. Similarly, system shutdown gracefully terminates processes in an organized and configurable way, although customization of this process is rarely required.
-	</para>
-	<para>
-		Understanding how the boot and shutdown processes work not only allows customization, but also makes it easier to troubleshoot problems related to starting or shutting down the system.
-	</para>
-	<section id="s1-boot-process-basics">
-		<title>The Boot Process</title>
-		<indexterm significance="normal">
-			<primary>boot process</primary>
-			<secondary>stages of</secondary>
-		</indexterm>
-		<para>
-			Below are the basic stages of the boot process for an x86 system:
-		</para>
-		 
-		<orderedlist inheritnum="ignore" continuation="restarts">
-			<listitem>
-				<para>
-					The system BIOS checks the system and launches the first stage boot loader on the MBR of the primary hard disk.
-				</para>
-			</listitem>
-
-			<listitem>
-				<para>
-					The first stage boot loader loads itself into memory and launches the second stage boot loader from the <filename>/boot/</filename> partition.
-				</para>
-			</listitem>
-
-			<listitem>
-				<para>
-					The second stage boot loader loads the kernel into memory, which in turn loads any necessary modules and mounts the root partition read-only.
-				</para>
-			</listitem>
-
-			<listitem>
-				<para>
-					The kernel transfers control of the boot process to the <command>/sbin/init</command> program.
-				</para>
-			</listitem>
-
-			<listitem>
-				<para>
-					The <command>/sbin/init</command> program loads all services and user-space tools, and mounts all partitions listed in <filename>/etc/fstab</filename>.
-				</para>
-			</listitem>
-
-			<listitem>
-				<para>
-					The user is presented with a login screen for the freshly booted Linux system.
-				</para>
-			</listitem>
-		</orderedlist>
-		 
-		<para>
-			Because configuration of the boot process is more common than the customization of the shutdown process, the remainder of this chapter discusses in detail how the boot process works and how it can be customized to suite specific needs.
-		</para>
-	</section>
-	<section id="s1-boot-init-shutdown-process">
-		<title>A Detailed Look at the Boot Process</title>
-		<indexterm significance="normal">
-			<primary>boot process</primary>
-			<secondary>for x86</secondary>
-		</indexterm>
-		<indexterm significance="normal">
-			<primary>boot process</primary>
-			<seealso>boot loaders</seealso>
-		</indexterm>
-		<indexterm significance="normal">
-			<primary>boot process</primary>
-			<secondary>stages of</secondary>
-		</indexterm>
-		<indexterm significance="normal">
-			<primary>Master Boot Record</primary>
-			<see>MBR</see>
-		</indexterm>
-		<indexterm significance="normal">
-			<primary>MBR</primary>
-			<secondary>definition of</secondary>
-			<seealso>boot process</seealso>
-		</indexterm>
-		<para>
-			The beginning of the boot process varies depending on the hardware platform being used. However, once the kernel is found and loaded by the boot loader, the default boot process is identical across all architectures. This chapter focuses primarily on the x86 architecture.
-		</para>
-		 
-		<section id="s2-boot-init-shutdown-bios">
-			<title>The BIOS</title>
-			<indexterm significance="normal">
-				<primary>Extensible Firmware Interface shell</primary>
-				<see>EFI shell</see>
-			</indexterm>
-			<indexterm significance="normal">
-				<primary>EFI shell</primary>
-				<secondary>definition of</secondary>
-				<seealso>boot process</seealso>
-			</indexterm>
-			<indexterm significance="normal">
-				<primary>boot process</primary>
-				<secondary>stages of</secondary>
-				<tertiary>BIOS</tertiary>
-			</indexterm>
-			<indexterm significance="normal">
-				<primary>boot process</primary>
-				<secondary>stages of</secondary>
-				<tertiary>EFI shell</tertiary>
-			</indexterm>
-			<indexterm significance="normal">
-				<primary>Basic Input/Output System</primary>
-				<see>BIOS</see>
-			</indexterm>
-			<indexterm significance="normal">
-				<primary>BIOS</primary>
-				<secondary>definition of</secondary>
-				<seealso>boot process</seealso>
-			</indexterm>
-			<indexterm significance="normal">
-				<primary>Master Boot Record</primary>
-				<see>MBR</see>
-			</indexterm>
-			<indexterm significance="normal">
-				<primary>MBR</primary>
-				<secondary>definition of</secondary>
-				<seealso>boot loaders</seealso>
-			</indexterm>
-			<para>
-				When an x86 computer is booted, the processor looks at the end of system memory for the <firstterm>Basic Input/Output System</firstterm> or <firstterm>BIOS</firstterm> program and runs it. The BIOS controls not only the first step of the boot process, but also provides the lowest level interface to peripheral devices. For this reason it is written into read-only, permanent memory and is always available for use.
-			</para>
-			 
-			<para>
-				Other platforms use different programs to perform low-level tasks roughly equivalent to those of the BIOS on an x86 system. For instance, Itanium-based computers use the <firstterm>Extensible Firmware Interface</firstterm> (<firstterm>EFI</firstterm>) <firstterm>Shell</firstterm>.
-			</para>
-			 
-			<para>
-				Once loaded, the BIOS tests the system, looks for and checks peripherals, and then locates a valid device with which to boot the system. Usually, it checks any diskette drives and CD-ROM drives present for bootable media, then, failing that, looks to the system's hard drives. In most cases, the order of the drives searched while booting is controlled with a setting in the BIOS, and it looks on the master IDE device on the primary IDE bus. The BIOS then loads into memory whatever program is residing in the first sector of this device, called the <firstterm>Master Boot Record</firstterm> or <firstterm>MBR</firstterm>. The MBR is only 512 bytes in size and contains machine code instructions for booting the machine, called a boot loader, along with the partition table. Once the BIOS finds and loads the boot loader program into memory, it yields control of the boot process to it.
-			</para>
-		</section>
-		 
-		<section id="s2-boot-init-shutdown-loader">
-			<title>The Boot Loader</title>
-			<indexterm significance="normal">
-				<primary>boot process</primary>
-				<secondary>stages of</secondary>
-				<tertiary>boot loader</tertiary>
-			</indexterm>
-			<indexterm significance="normal">
-				<primary>GRUB</primary>
-				<secondary>role in boot process</secondary>
-			</indexterm>
-			<indexterm significance="normal">
-				<primary>GRUB</primary>
-				<seealso>boot loaders</seealso>
-			</indexterm>
-			<indexterm significance="normal">
-				<primary>LILO</primary>
-				<seealso>boot loaders</seealso>
-			</indexterm>
-			<indexterm significance="normal">
-				<primary>LILO</primary>
-				<secondary>role in boot process</secondary>
-			</indexterm>
-			<para>
-				This section looks at the default boot loader for the x86 platform, GRUB. <!-- (RHEL) Depending on the system's architecture, the boot process may differ slightly. Refer to <xref linkend="s3-boot-init-shutdown-other-architectures"/> for a brief overview of non-x86 boot loaders.--> For more information about configuring and using GRUB, see <xref linkend="ch-grub"/>.
-			</para>
-			 
-			<para>
-				A boot loader for the x86 platform is broken into at least two stages. The first stage is a small machine code binary on the MBR. Its sole job is to locate the second stage boot loader and load the first part of it into memory.
-			</para>
-			 
-			<para>
-				GRUB has the advantage of being able to read ext2 and ext3 <footnote>
-				<para>
-					GRUB reads ext3 file systems as ext2, disregarding the journal file. Refer to the chapter titled <citetitle>The ext3 File System</citetitle> in the <citetitle>Red Hat Enterprise Linux Deployment Guide</citetitle> for more information on the ext3 file system.
-				</para>
-				</footnote> partitions and load its configuration file &mdash; <filename>/boot/grub/grub.conf</filename> &mdash; at boot time. Refer to <xref linkend="s1-grub-configfile"/> for information on how to edit this file.
-			</para>
-			<important>
-			  <title>Btrfs</title>
-			  <para>
-			    The <application>GRUB</application> bootloader does not support the Btrfs file system.
-			  </para>
-			</important>
-			<note><title>Note</title>
-				<para>
-					If upgrading the kernel using the <application>Red Hat Update Agent</application>, the boot loader configuration file is updated automatically. More information on Red Hat Network can be found online at the following URL: <ulink url="https://rhn.redhat.com/">https://rhn.redhat.com/</ulink>.
-				</para>
-			</note>
-			<para>
-				Once the second stage boot loader is in memory, it presents the user with a graphical screen showing the different operating systems or kernels it has been configured to boot. On this screen a user can use the arrow keys to choose which operating system or kernel they wish to boot and press <keycap>Enter</keycap>. If no key is pressed, the boot loader loads the default selection after a configurable period of time has passed.
-			</para>
-			 
-			<!-- <note>
-				<title>Note</title>
-
-				<para>
-					If Symmetric Multi-Processor (SMP) kernel support is installed, more than one option is presented the first time the system is booted. In this situation GRUB displays <computeroutput>Fedora (<replaceable>&lt;kernel-version&gt;</replaceable>-smp)</computeroutput>, which is the SMP kernel, and <computeroutput>Fedora (<replaceable>&lt;kernel-version&gt;</replaceable>)</computeroutput>, which is for single processors.
-				</para>
-
-				<para>
-					If any problems occur using the SMP kernel, try selecting the a non-SMP kernel upon rebooting.
-				</para>
-			</note> -->
-			 
-			<para>
-				Once the second stage boot loader has determined which kernel to boot, it locates the corresponding kernel binary in the <filename>/boot/</filename> directory. The kernel binary is named using the following format &mdash; <filename>/boot/vmlinuz-<replaceable>&lt;kernel-version&gt;</replaceable></filename> file (where <filename><replaceable>&lt;kernel-version&gt;</replaceable></filename> corresponds to the kernel version specified in the boot loader's settings).
-			</para>
-			 
-			<para>
-				For instructions on using the boot loader to supply command line arguments to the kernel, refer to <xref linkend="ch-grub"/>. For information on changing the runlevel at the boot loader prompt, refer <xref linkend="s1-grub-runlevels"/>.
-			</para>
-			 
-			<para>
-				The boot loader then places one or more appropriate <firstterm>initramfs</firstterm> images into memory. Next, the kernel decompresses these images from memory to <filename>/sysroot/</filename>, a RAM-based virtual file system, via <command>cpio</command>. The <filename>initramfs</filename> is used by the kernel to load drivers and modules necessary to boot the system. This is particularly important if SCSI hard drives are present or if the systems use the ext3 or ext4 file system.
-			</para>
-			 
-			<para>
-				Once the kernel and the <filename>initramfs</filename> image(s) are loaded into memory, the boot loader hands control of the boot process to the kernel.
-			</para>
-			 
-			<para>
-				For a more detailed overview of the GRUB boot loader, refer to <xref linkend="ch-grub"/>.
-			</para>
-			 
-			<!-- (RHEL) <section id="s3-boot-init-shutdown-other-architectures">
-				<title>Boot Loaders for Other Architectures</title>
-				<indexterm significance="normal">
-					<primary><command>aboot</command>
-					</primary>
-				</indexterm>
-				<indexterm significance="normal">
-					<primary>ELILO</primary>
-				</indexterm>
-				<para>
-					Once the kernel loads and hands off the boot process to the <command>init</command> command, the same sequence of events occurs on every architecture. So the main difference between each architecture's boot process is in the application used to find and load the kernel.
-				</para>
-				 
-				<para>
-					For example, the Itanium architecture uses the ELILO boot loader, the IBM eServer pSeries architecture uses yaboot, and the IBM System z systems use the z/IPL boot loader.
-				</para> -->
-				 
-				<!-- <para>
-					Consult the <citetitle>Red Hat Enterprise Linux Installation Guide</citetitle> specific to these platforms for information on configuring their boot loaders.
-				</para> -->
-			<!-- (RHEL) </section> -->
-		</section>
-		 
-		<section id="s2-boot-init-shutdown-kernel">
-			<title>The Kernel</title>
-			<indexterm significance="normal">
-				<primary>boot process</primary>
-				<secondary>stages of</secondary>
-				<tertiary>kernel</tertiary>
-			</indexterm>
-			<indexterm significance="normal">
-				<primary>kernel</primary>
-				<secondary>role in boot process</secondary>
-			</indexterm>
-			<para>
-				When the kernel is loaded, it immediately initializes and configures the computer's memory and configures the various hardware attached to the system, including all processors, I/O subsystems, and storage devices. It then looks for the compressed <filename>initramfs</filename> image(s) in a predetermined location in memory, decompresses it directly to <filename>/sysroot/</filename>, and loads all necessary drivers. Next, it initializes virtual devices related to the file system, such as LVM or software RAID, before completing the <filename>initramfs</filename> processes and freeing up all the memory the disk image once occupied.
-			</para>
-			 
-			<para>
-				The kernel then creates a root device, mounts the root partition read-only, and frees any unused memory.
-			</para>
-			 
-			<para>
-				At this point, the kernel is loaded into memory and operational. However, since there are no user applications that allow meaningful input to the system, not much can be done with the system.
-			</para>
-			 
-			<para>
-				To set up the user environment, the kernel executes the <command>/sbin/init</command> program.
-			</para>
-		</section>
-		 
-		<section id="s2-boot-init-shutdown-init">
-			<title>The <command>/sbin/init</command> Program</title>
-			<indexterm significance="normal">
-				<primary><command>init</command> command</primary>
-				<secondary>role in boot process</secondary>
-				<seealso>boot process</seealso>
-			</indexterm>
-			<indexterm significance="normal">
-				<primary><command>init</command> command</primary>
-				<seealso>boot process</seealso>
-			</indexterm>
-			<indexterm significance="normal">
-				<primary>boot process</primary>
-				<secondary>stages of</secondary>
-				<tertiary><command>/sbin/init</command> command</tertiary>
-			</indexterm>
-			<para>
-				The <command>/sbin/init</command> program (also called <command>init</command>) coordinates the rest of the boot process and configures the environment for the user.
-			</para>
-			 
-			<para>
-				When the <command>init</command> command starts, it becomes the parent or grandparent of all of the processes that start up automatically on the system. First, it runs the <filename>/etc/rc.d/rc.sysinit</filename> script, which sets the environment path, starts swap, checks the file systems, and executes all other steps required for system initialization. For example, most systems use a clock, so <filename>rc.sysinit</filename> reads the <filename>/etc/sysconfig/clock</filename> configuration file to initialize the hardware clock. Another example is if there are special serial port processes which must be initialized, <filename>rc.sysinit</filename>
-				executes the <filename>/etc/rc.serial</filename> file.
-			</para>
-			 
-			<para>
-				The <command>init</command> command then processes the jobs in the <filename>/etc/event.d</filename> directory, which describe how the system should be set up in each <firstterm>SysV init runlevel</firstterm>. Runlevels are a state, or <firstterm>mode</firstterm>, defined by the services listed in the SysV <filename>/etc/rc.d/rc<replaceable>&lt;x&gt;</replaceable>.d/</filename> directory, where <replaceable>&lt;x&gt;</replaceable> is the number of the runlevel. For more information on SysV init runlevels, refer to <xref linkend="s1-boot-init-shutdown-sysv"/>.
-			</para>
-			 
-			<para>
-				Next, the <command>init</command> command sets the source function library, <filename>/etc/rc.d/init.d/functions</filename>, for the system, which configures how to start, kill, and determine the PID of a program.
-			</para>
-			 
-			<para>
-				The <command>init</command> program starts all of the background processes by looking in the appropriate <filename>rc</filename> directory for the runlevel specified as the default in
-				<filename>/etc/inittab</filename>. The <filename>rc</filename> directories are numbered to correspond to the runlevel they represent. For instance, <filename>/etc/rc.d/rc5.d/</filename> is the directory
-				for runlevel 5.
-			</para>
-			 
-			<para>
-				When booting to runlevel 5, the <command>init</command> program looks in the <filename>/etc/rc.d/rc5.d/</filename> directory to determine which processes to start and stop.
-			</para>
-			 
-			<para>
-				Below is an example listing of the <filename>/etc/rc.d/rc5.d/</filename> directory:
-			</para>
-<screen>
-K05innd -&gt; ../init.d/innd 
-K05saslauthd -&gt; ../init.d/saslauthd 
-K10dc_server -&gt; ../init.d/dc_server 
-K10psacct -&gt; ../init.d/psacct 
-K10radiusd -&gt; ../init.d/radiusd 
-K12dc_client -&gt; ../init.d/dc_client 
-K12FreeWnn -&gt; ../init.d/FreeWnn 
-K12mailman -&gt; ../init.d/mailman 
-K12mysqld -&gt; ../init.d/mysqld 
-K15httpd -&gt; ../init.d/httpd 
-K20netdump-server -&gt; ../init.d/netdump-server 
-K20rstatd -&gt; ../init.d/rstatd 
-K20rusersd -&gt; ../init.d/rusersd 
-K20rwhod -&gt; ../init.d/rwhod 
-K24irda -&gt; ../init.d/irda 
-K25squid -&gt; ../init.d/squid 
-K28amd -&gt; ../init.d/amd 
-K30spamassassin -&gt; ../init.d/spamassassin 
-K34dhcrelay -&gt; ../init.d/dhcrelay 
-K34yppasswdd -&gt; ../init.d/yppasswdd 
-K35dhcpd -&gt; ../init.d/dhcpd 
-K35smb -&gt; ../init.d/smb 
-K35vncserver -&gt; ../init.d/vncserver 
-K36lisa -&gt; ../init.d/lisa 
-K45arpwatch -&gt; ../init.d/arpwatch 
-K45named -&gt; ../init.d/named 
-K46radvd -&gt; ../init.d/radvd 
-K50netdump -&gt; ../init.d/netdump 
-K50snmpd -&gt; ../init.d/snmpd 
-K50snmptrapd -&gt; ../init.d/snmptrapd 
-K50tux -&gt; ../init.d/tux 
-K50vsftpd -&gt; ../init.d/vsftpd 
-K54dovecot -&gt; ../init.d/dovecot 
-K61ldap -&gt; ../init.d/ldap 
-K65kadmin -&gt; ../init.d/kadmin 
-K65kprop -&gt; ../init.d/kprop 
-K65krb524 -&gt; ../init.d/krb524 
-K65krb5kdc -&gt; ../init.d/krb5kdc 
-K70aep1000 -&gt; ../init.d/aep1000 
-K70bcm5820 -&gt; ../init.d/bcm5820 
-K74ypserv -&gt; ../init.d/ypserv 
-K74ypxfrd -&gt; ../init.d/ypxfrd 
-K85mdmpd -&gt; ../init.d/mdmpd 
-K89netplugd -&gt; ../init.d/netplugd 
-K99microcode_ctl -&gt; ../init.d/microcode_ctl 
-S04readahead_early -&gt; ../init.d/readahead_early 
-S05kudzu -&gt; ../init.d/kudzu 
-S06cpuspeed -&gt; ../init.d/cpuspeed 
-S08ip6tables -&gt; ../init.d/ip6tables 
-S08iptables -&gt; ../init.d/iptables 
-S09isdn -&gt; ../init.d/isdn 
-S10network -&gt; ../init.d/network 
-S12syslog -&gt; ../init.d/syslog 
-S13irqbalance -&gt; ../init.d/irqbalance 
-S13portmap -&gt; ../init.d/portmap 
-S15mdmonitor -&gt; ../init.d/mdmonitor 
-S15zebra -&gt; ../init.d/zebra 
-S16bgpd -&gt; ../init.d/bgpd 
-S16ospf6d -&gt; ../init.d/ospf6d 
-S16ospfd -&gt; ../init.d/ospfd 
-S16ripd -&gt; ../init.d/ripd 
-S16ripngd -&gt; ../init.d/ripngd 
-S20random -&gt; ../init.d/random 
-S24pcmcia -&gt; ../init.d/pcmcia 
-S25netfs -&gt; ../init.d/netfs 
-S26apmd -&gt; ../init.d/apmd 
-S27ypbind -&gt; ../init.d/ypbind 
-S28autofs -&gt; ../init.d/autofs 
-S40smartd -&gt; ../init.d/smartd 
-S44acpid -&gt; ../init.d/acpid 
-S54hpoj -&gt; ../init.d/hpoj 
-S55cups -&gt; ../init.d/cups 
-S55sshd -&gt; ../init.d/sshd 
-S56rawdevices -&gt; ../init.d/rawdevices 
-S56xinetd -&gt; ../init.d/xinetd 
-S58ntpd -&gt; ../init.d/ntpd 
-S75postgresql -&gt; ../init.d/postgresql 
-S80sendmail -&gt; ../init.d/sendmail 
-S85gpm -&gt; ../init.d/gpm 
-S87iiim -&gt; ../init.d/iiim 
-S90canna -&gt; ../init.d/canna 
-S90crond -&gt; ../init.d/crond 
-S90xfs -&gt; ../init.d/xfs 
-S95atd -&gt; ../init.d/atd 
-S96readahead -&gt; ../init.d/readahead 
-S97messagebus -&gt; ../init.d/messagebus 
-S97rhnsd -&gt; ../init.d/rhnsd 
-S99local -&gt; ../rc.local
-</screen>
-			<para>
-				As illustrated in this listing, none of the scripts that actually start and stop the services are located in the <filename>/etc/rc.d/rc5.d/</filename> directory. Rather, all of the files in <filename>/etc/rc.d/rc5.d/</filename> are <firstterm>symbolic links</firstterm> pointing to scripts located in the <filename>/etc/rc.d/init.d/</filename> directory. Symbolic links are used in each of the <filename>rc</filename> directories so that the runlevels can be reconfigured by creating, modifying, and deleting the symbolic links without affecting the actual scripts they reference.
-			</para>
-			 
-			<para>
-				The name of each symbolic link begins with either a <computeroutput>K</computeroutput> or an <computeroutput>S</computeroutput>. The <computeroutput>K</computeroutput> links are processes that are killed on that runlevel, while those beginning with an <computeroutput>S</computeroutput> are started.
-			</para>
-			 
-			<para>
-				The <command>init</command> command first stops all of the <computeroutput>K</computeroutput> symbolic links in the directory by issuing the <command>/etc/rc.d/init.d/<replaceable>&lt;command&gt;</replaceable> stop</command> command, where <replaceable>&lt;command&gt;</replaceable> is the process to be killed. It then starts all of the <computeroutput>S</computeroutput> symbolic links by issuing <command>/etc/rc.d/init.d/<replaceable>&lt;command&gt;</replaceable> start</command>.
-			</para>
-			<note><title>Note</title>
-				<para>
-					After the system is finished booting, it is possible to log in as root and execute these same scripts to start and stop services. For instance, the command <command>/etc/rc.d/init.d/httpd stop</command> stops the Apache HTTP Server.
-				</para>
-			</note>
-			<para>
-				Each of the symbolic links are numbered to dictate start order. The order in which the services are started or stopped can be altered by changing this number. The lower the number, the earlier it is started. Symbolic links with the same number are started alphabetically.
-			</para>
-			 
-			<note>
-				<title>Note</title>
-
-				<para>
-					One of the last things the <command>init</command> program executes is the <filename>/etc/rc.d/rc.local</filename> file. This file is useful for system customization. Refer to <xref linkend="s1-boot-init-shutdown-run-boot"/> for more information about using the <filename>rc.local</filename> file.
-				</para>
-			</note>
-			 
-			<para>
-				After the <command>init</command> command has progressed through the appropriate <filename>rc</filename> directory for the runlevel, <application>Upstart</application> forks an <command>/sbin/mingetty</command> process for each virtual console (login prompt) allocated to the runlevel by the job definition in the <filename>/etc/event.d</filename> directory. Runlevels 2 through 5 have all six virtual consoles, while runlevel 1 (single user mode) has one, and runlevels 0 and 6 have none. The <command>/sbin/mingetty</command> process opens communication pathways to <firstterm>tty</firstterm> devices<footnote>
-				<para>
-					Refer to the Red Hat Enterprise Linux Deployment Guide for more information about <filename>tty</filename> devices.
-				</para>
-				</footnote>, sets their modes, prints the login prompt, accepts the user's username and password, and initiates the login process.
-			</para>
-			 
-			<para>
-				In runlevel 5, <application>Upstart</application> runs a script called <filename>/etc/X11/prefdm</filename>. The <filename>prefdm</filename> script executes the preferred X display manager<footnote>
-				<para>
-					Refer to the Red Hat Enterprise Linux Deployment Guide for more information about display managers.
-				</para>
-				</footnote> &mdash; <command>gdm</command>, <command>kdm</command>, or <command>xdm</command>, depending on the contents of the <filename>/etc/sysconfig/desktop</filename> file.
-			</para>
-			 
-			<para>
-				Once finished, the system operates on runlevel 5 and displays a login screen.
-			</para>
-		</section>
-		<section id="s2-boot-init-shutdown-jobs">
-		<title>Job definitions</title>
-		<para>
-			Previously, the <package>sysvinit</package> package provided the <application>init</application> daemon for the default configuration. When the system started, this <application>init</application> daemon ran the <filename>/etc/inittab</filename> script to start system processes defined for each runlevel. The default configuration now uses an event-driven <application>init</application> daemon provided by the <package>Upstart</package> package. Whenever particular <firstterm>events</firstterm> occur, the <application>init</application> daemon processes <firstterm>jobs</firstterm> stored in the <filename>/etc/event.d</filename> directory. The <application>init</application> daemon recognises the start of the system as such an event. 
-		</para>
-		<para>
-			Each job typically specifies a program, and the events that trigger <application>init</application> to run or to stop the program. Some jobs are constructed as <firstterm>tasks</firstterm>, which perform actions and then terminate until another event triggers the job again. Other jobs are constructed as <firstterm>services</firstterm>, which <application>init</application> keeps running until another event (or the user) stops it.
-		</para>
-		<para>
-			For example, the <filename>/etc/events.d/tty2</filename> job is a service to maintain a virtual terminal on <application>tty2</application> from the time that the system starts until the system shuts down, or another event (such as a change in runlevel) stops the job. The job is constructed so that <application>init</application> will restart the virtual terminal if it stops unexpecedly during that time:
-		</para>
-<screen># tty2 - getty
-#
-# This service maintains a getty on tty2 from the point the system is
-# started until it is shut down again.
-
-start on stopped rc2
-start on stopped rc3
-start on stopped rc4
-start on started prefdm
-
-stop on runlevel 0
-stop on runlevel 1
-stop on runlevel 6
-
-respawn
-exec /sbin/mingetty tty2
-</screen>
-		</section>
-	</section>
-	<section id="s1-boot-init-shutdown-run-boot">
-		<title>Running Additional Programs at Boot Time</title>
-		<indexterm significance="normal">
-			<primary>programs</primary>
-			<secondary>running at boot time</secondary>
-		</indexterm>
-		<indexterm significance="normal">
-			<primary><filename>rc.local</filename>
-			</primary>
-			<secondary>modifying</secondary>
-		</indexterm>
-		<indexterm significance="normal">
-			<primary><command>setserial</command> command</primary>
-			<secondary>configuring</secondary>
-		</indexterm>
-		<indexterm significance="normal">
-			<primary><filename>rc.serial</filename>
-			</primary>
-			<seealso><command>setserial</command> command</seealso>
-		</indexterm>
-		<indexterm significance="normal">
-			<primary>serial ports</primary>
-			<see><command>setserial</command> command</see>
-		</indexterm>
-		<para>
-			The <filename>/etc/rc.d/rc.local</filename> script is executed by the <command>init</command> command at boot time or when changing runlevels. Adding commands to the bottom of this script is an easy way to perform necessary tasks like starting special services or initialize devices without writing complex initialization scripts in the <filename>/etc/rc.d/init.d/</filename> directory and creating symbolic links.
-		</para>
-		 
-		<para>
-			The <filename>/etc/rc.serial</filename> script is used if serial ports must be setup at boot time. This script runs <command>setserial</command> commands to configure the system's serial ports. Refer to the <command>setserial</command> man page for more information.
-		</para>
-	</section>
-	<section id="s1-boot-init-shutdown-sysv">
-		<title>SysV Init Runlevels</title>
-		<indexterm significance="normal">
-			<primary>SysV init</primary>
-			<see><command>init</command> command</see>
-		</indexterm>
-		<indexterm significance="normal">
-			<primary><command>init</command> command</primary>
-			<secondary>runlevels</secondary>
-			<tertiary>directories for</tertiary>
-		</indexterm>
-		<indexterm significance="normal">
-			<primary><command>init</command> command</primary>
-			<secondary>SysV init</secondary>
-			<tertiary>definition of</tertiary>
-		</indexterm>
-		<indexterm significance="normal">
-			<primary><command>init</command> command</primary>
-			<secondary>configuration files</secondary>
-			<tertiary><filename>/etc/inittab</filename>
-			</tertiary>
-		</indexterm>
-		<para>
-			The SysV init runlevel system provides a standard process for controlling which programs <command>init</command> launches or halts when initializing a runlevel. SysV init was chosen because it is easier to use and more flexible than the traditional BSD-style init process.
-		</para>
-		 
-		<para>
-			The configuration files for SysV init are located in the <filename>/etc/rc.d/</filename> directory. Within this directory, are the <filename>rc</filename>, <filename>rc.local</filename>, <filename>rc.sysinit</filename>, and, optionally, the <filename>rc.serial</filename> scripts as well as the following directories:
-		</para>
-<screen>
-<computeroutput>init.d/ rc0.d/ rc1.d/ rc2.d/ rc3.d/ rc4.d/ rc5.d/ rc6.d/</computeroutput>
-</screen>
-		<para>
-			The <filename>init.d/</filename> directory contains the scripts used by the <command>/sbin/init</command> command when controlling services. Each of the numbered directories represent the six runlevels configured by default under Fedora.
-		</para>
-		 
-		<section id="s2-init-boot-shutdown-rl">
-			<title>Runlevels</title>
-			<indexterm significance="normal">
-				<primary>runlevels</primary>
-				<see><command>init</command> command</see>
-			</indexterm>
-			<indexterm significance="normal">
-				<primary><command>init</command> command</primary>
-				<secondary>runlevels accessed by</secondary>
-			</indexterm>
-			<para>
-				The idea behind SysV init runlevels revolves around the idea that different systems can be used in different ways. For example, a server runs more efficiently without the drag on system resources created by the X Window System. Or there may be times when a system administrator may need to operate the system at a lower runlevel to perform diagnostic tasks, like fixing disk corruption in runlevel 1.
-			</para>
-			 
-			<para>
-				The characteristics of a given runlevel determine which services are halted and started by <command>init</command>. For instance, runlevel 1 (single user mode) halts any network services, while runlevel 3 starts these services. By assigning specific services to be halted or started on a given runlevel, <command>init</command> can quickly change the mode of the machine without the user manually stopping and starting services.
-			</para>
-			 
-			<para>
-				The following runlevels are defined by default under Fedora:
-			</para>
-			<blockquote><itemizedlist>
-					<listitem>
-						<para>
-							<command>0</command> &mdash; Halt
-						</para>
-					</listitem>
-
-					<listitem>
-						<para>
-							<command>1</command> &mdash; Single-user text mode
-						</para>
-					</listitem>
-
-					<listitem>
-						<para>
-							<command>2</command> &mdash; Not used (user-definable)
-						</para>
-					</listitem>
-
-					<listitem>
-						<para>
-							<command>3</command> &mdash; Full multi-user text mode
-						</para>
-					</listitem>
-
-					<listitem>
-						<para>
-							<command>4</command> &mdash; Not used (user-definable)
-						</para>
-					</listitem>
-
-					<listitem>
-						<para>
-							<command>5</command> &mdash; Full multi-user graphical mode (with an X-based login screen)
-						</para>
-					</listitem>
-
-					<listitem>
-						<para>
-							<command>6</command> &mdash; Reboot
-						</para>
-					</listitem>
-				</itemizedlist>
-			</blockquote>
-			<para>
-				In general, users operate Fedora at runlevel 3 or runlevel 5 &mdash; both full multi-user modes. Users sometimes customize runlevels 2 and 4 to meet specific needs, since they are not used.
-			</para>
-			 
-			<para>
-				The default runlevel for the system is listed in <filename>/etc/inittab</filename>. To find out the default runlevel for a system, look for the line similar to the following near the bottom of
-				<filename>/etc/inittab</filename>:
-			</para>
-<screen>
-<computeroutput>id:5:initdefault:</computeroutput>
-</screen>
-			<para>
-				The default runlevel listed in this example is five, as the number after the first colon indicates. To change it, edit <filename>/etc/inittab</filename> as root.
-			</para>
-			 
-			<warning>
-				<title>Warning</title>
-
-				<para>
-					Be very careful when editing <filename>/etc/inittab</filename>. Simple typos can cause the system to become unbootable. If this happens, either use a boot diskette, enter single-user mode, or enter rescue mode to boot the computer and repair the file.
-				</para>
-
-				<para>
-					For more information on single-user and rescue mode, refer to the chapter titled <citetitle>Basic System Recovery</citetitle> in the <citetitle>Red Hat Enterprise Linux Deployment Guide</citetitle>.
-				</para>
-			</warning>
-			 
-			<para>
-				It is possible to change the default runlevel at boot time by modifying the arguments passed by the boot loader to the kernel. For information on changing the runlevel at boot time, refer to <xref linkend="s1-grub-runlevels"/>.
-			</para>
-		</section>
-		 
-		<section id="s2-boot-init-shutdown-sysv-util">
-			<title>Runlevel Utilities</title>
-			<indexterm significance="normal">
-				<primary>runlevels</primary>
-				<secondary>configuration of</secondary>
-				<seealso>services</seealso>
-			</indexterm>
-			<indexterm significance="normal">
-				<primary><application>Services Configuration Tool</application>
-				</primary>
-				<seealso>services</seealso>
-			</indexterm>
-			<indexterm significance="normal">
-				<primary>services</primary>
-				<secondary>configuring with <application>Services Configuration Tool</application>
-				</secondary>
-			</indexterm>
-			<indexterm significance="normal">
-				<primary><application>ntsysv</application>
-				</primary>
-				<seealso>services</seealso>
-			</indexterm>
-			<indexterm significance="normal">
-				<primary>services</primary>
-				<secondary>configuring with <application>ntsysv</application>
-				</secondary>
-			</indexterm>
-			<indexterm significance="normal">
-				<primary>services</primary>
-				<secondary>configuring with <command>chkconfig</command>
-				</secondary>
-			</indexterm>
-			<indexterm significance="normal">
-				<primary><command>chkconfig</command>
-				</primary>
-				<seealso>services</seealso>
-			</indexterm>
-			<para>
-				One of the best ways to configure runlevels is to use an <firstterm>initscript utility</firstterm>. These tools are designed to simplify the task of maintaining files in the SysV init directory hierarchy and relieves system administrators from having to directly manipulate the numerous symbolic links in the subdirectories of <filename>/etc/rc.d/</filename>.
-			</para>
-			 
-			<para>
-				Fedora provides three such utilities:
-			</para>
-			 
-			<itemizedlist>
-				<listitem>
-					<para>
-						<command>/sbin/chkconfig</command> &mdash; The <command>/sbin/chkconfig</command> utility is a simple command line tool for maintaining the <filename>/etc/rc.d/init.d/</filename> directory hierarchy.
-					</para>
-				</listitem>
-
-				<listitem>
-					<para>
-						<application>/usr/sbin/ntsysv</application> &mdash; The ncurses-based <application>/sbin/ntsysv</application> utility provides an interactive text-based interface, which some find easier to use than <command>chkconfig</command>.
-					</para>
-				</listitem>
-
-				<listitem>
-					<para>
-						<application>Services Configuration Tool</application> &mdash; The graphical <application>Services Configuration Tool</application> (<command>system-config-services</command>) program is a flexible utility for configuring runlevels.
-					</para>
-				</listitem>
-			</itemizedlist>
-			 
-			<para>
-				Refer to the chapter titled <citetitle>Controlling Access to Services</citetitle> in the <citetitle>Red Hat Enterprise Linux Deployment Guide</citetitle> for more information regarding these tools.
-			</para>
-		</section>
-	</section>
-	<section id="s1-boot-init-shutdown-shutdown">
-		<title>Shutting Down</title>
-		<indexterm significance="normal">
-			<primary>shutdown</primary>
-			<seealso>halt</seealso>
-		</indexterm>
-		<indexterm significance="normal">
-			<primary>halt</primary>
-			<seealso>shutdown</seealso>
-		</indexterm>
-		<para>
-			To shut down Fedora, the root user may issue the <command>/sbin/shutdown</command> command. The <command>shutdown</command> man page has a complete list of options, but the two most common uses are:
-		</para>
-<screen>
-<command>/sbin/shutdown -h now</command>
-</screen>
-		<para>
-			and
-		</para>
-<screen>
-<command>/sbin/shutdown -r now</command>
-</screen>
-		<para>
-			After shutting everything down, the <command>-h</command> option halts the machine, and the <command>-r</command> option reboots.
-		</para>
-		 
-		<para>
-			PAM console users can use the <command>reboot</command> and <command>halt</command> commands to shut down the system while in runlevels 1 through 5. For more information about PAM console users, refer to the Red Hat Enterprise Linux Deployment Guide.
-		</para>
-		 
-		<para>
-			If the computer does not power itself down, be careful not to turn off the computer until a message appears indicating that the system is halted.
-		</para>
-		 
-		<para>
-			Failure to wait for this message can mean that not all the hard drive partitions are unmounted, which can lead to file system corruption.
-		</para>
-	</section>
-</appendix>
diff --git a/en-US/Boot_Order-para-1.xml b/en-US/Boot_Order-para-1.xml
deleted file mode 100644
index 43e4d51..0000000
--- a/en-US/Boot_Order-para-1.xml
+++ /dev/null
@@ -1,7 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<para>
-	You might need to press a specific key or combination of keys to boot from the media. On most computers, a message appears briefly on the screen very soon after you turn on the computer. Typically, it is worded something like <literal>Press F10 to select boot device</literal>, although the specific wording and the key that you must press varies widely from computer to computer. Consult the documentation for your computer or motherboard, or seek support from the hardware manufacturer or vendor. On Apple computers, the <keycap>C</keycap> key boots the system from the DVD drive. On older Apple hardware you might need to  press <keycombo><keycap>Cmd</keycap> <keycap>Opt</keycap><keycap>Shift</keycap><keycap>Del</keycap></keycombo> to boot from the DVD drive.
-</para>
diff --git a/en-US/Boot_Order-para-2.xml b/en-US/Boot_Order-para-2.xml
deleted file mode 100644
index dc4f0f4..0000000
--- a/en-US/Boot_Order-para-2.xml
+++ /dev/null
@@ -1,7 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<para>
-	If your computer does not allow you to select a boot device as it starts up, you might need to configure your system's <firstterm>Basic Input/Output System</firstterm> (<acronym>BIOS</acronym>) to boot from the media.
-</para>
diff --git a/en-US/Boot_Order-para-3.xml b/en-US/Boot_Order-para-3.xml
deleted file mode 100644
index 8113aee..0000000
--- a/en-US/Boot_Order-para-3.xml
+++ /dev/null
@@ -1,7 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<para>
-	To change your BIOS settings on an x86, AMD64, or <trademark class="registered">Intel</trademark> 64 system, watch the instructions provided on your display when your computer first boots. A line of text appears, telling you which key to press to enter the BIOS settings.
-</para>
diff --git a/en-US/Boot_Order-para-4.xml b/en-US/Boot_Order-para-4.xml
deleted file mode 100644
index 715bc28..0000000
--- a/en-US/Boot_Order-para-4.xml
+++ /dev/null
@@ -1,7 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<para>
-	Once you have entered your BIOS setup program, find the section where you can alter your boot sequence. The default is often C, A or A, C (depending on whether you boot from your hard drive [C] or a diskette drive [A]). Change this sequence so that the CD-ROM is first in your boot order and that C or A (whichever is your typical boot default) is second. This instructs the computer to first look at the CD-ROM drive for bootable media; if it does not find bootable media on the CD-ROM drive, it then checks your hard drive or diskette drive.
-</para>
diff --git a/en-US/Boot_Order-para-5.xml b/en-US/Boot_Order-para-5.xml
deleted file mode 100644
index e3caff1..0000000
--- a/en-US/Boot_Order-para-5.xml
+++ /dev/null
@@ -1,7 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<para>
-	Save your changes before exiting the BIOS. For more information, refer to the documentation that came with your system.
-</para>
diff --git a/en-US/Boot_x86_ppc-figure-1.xml b/en-US/Boot_x86_ppc-figure-1.xml
deleted file mode 100644
index 8ed14dc..0000000
--- a/en-US/Boot_x86_ppc-figure-1.xml
+++ /dev/null
@@ -1,16 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
- "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
-]>
-
-<figure float="0">
-	<title>The boot screen</title>
-	<mediaobject>
-		<imageobject><imagedata fileref="images/boot/boot_screen.png" format="PNG"/></imageobject>
-		<textobject><para>
-				The boot screen
-			</para>
-		</textobject>
-	</mediaobject>
-</figure>
-
diff --git a/en-US/Boot_x86_ppc-indexterm-1.xml b/en-US/Boot_x86_ppc-indexterm-1.xml
deleted file mode 100644
index 4d9d0ed..0000000
--- a/en-US/Boot_x86_ppc-indexterm-1.xml
+++ /dev/null
@@ -1,9 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-<!DOCTYPE indexterm PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
- "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd">
-
-<indexterm>
-	<primary>CD/DVD media</primary>
-	<secondary>booting</secondary>
-</indexterm>
-
diff --git a/en-US/Boot_x86_ppc-indexterm-2.xml b/en-US/Boot_x86_ppc-indexterm-2.xml
deleted file mode 100644
index a806ce0..0000000
--- a/en-US/Boot_x86_ppc-indexterm-2.xml
+++ /dev/null
@@ -1,9 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-<!DOCTYPE indexterm PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
- "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd">
-
-<indexterm>
-	<primary>USB media</primary>
-	<secondary>booting</secondary>
-</indexterm>
-
diff --git a/en-US/Boot_x86_ppc-para-1.xml b/en-US/Boot_x86_ppc-para-1.xml
deleted file mode 100644
index 3546650..0000000
--- a/en-US/Boot_x86_ppc-para-1.xml
+++ /dev/null
@@ -1,8 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
- "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd">
-
-<para>
-	To start the installation program from a Red Hat Enterprise Linux CD, DVD, or minimal boot media, follow this procedure:
-</para>
-
diff --git a/en-US/Boot_x86_ppc-para-2.xml b/en-US/Boot_x86_ppc-para-2.xml
deleted file mode 100644
index aa60d74..0000000
--- a/en-US/Boot_x86_ppc-para-2.xml
+++ /dev/null
@@ -1,8 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
- "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd">
-
-<para>
-	The boot media displays a graphical boot menu with several options.  If no key is hit within 60 seconds, the default boot option runs.  To choose the default, either wait for the timer to run out or hit <keycap>Enter</keycap> on the keyboard.  To select a different option than the default, use the arrow keys on your keyboard, and hit <keycap>Enter</keycap> when the correct option is highlighted.  If you want to customize the boot options for a particular option, press the <keycap>Tab</keycap> key.
-</para>
-
diff --git a/en-US/Boot_x86_ppc-para-3.xml b/en-US/Boot_x86_ppc-para-3.xml
deleted file mode 100644
index 2c7524d..0000000
--- a/en-US/Boot_x86_ppc-para-3.xml
+++ /dev/null
@@ -1,8 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
- "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd">
-
-<para>
-	For a listing and explanation of common boot options, refer to <xref linkend="ap-admin-options"/>.
-</para>
-
diff --git a/en-US/Boot_x86_ppc-para-4.xml b/en-US/Boot_x86_ppc-para-4.xml
deleted file mode 100644
index 6fbde22..0000000
--- a/en-US/Boot_x86_ppc-para-4.xml
+++ /dev/null
@@ -1,8 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
- "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd">
-
-<para>
-	If you boot the DVD, rescue CD, or minimal boot media, the boot menu options are:
-</para>
-
diff --git a/en-US/Boot_x86_ppc-para-5.xml b/en-US/Boot_x86_ppc-para-5.xml
deleted file mode 100644
index c704311..0000000
--- a/en-US/Boot_x86_ppc-para-5.xml
+++ /dev/null
@@ -1,8 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
- "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd">
-
-<para>
-	You can install Fedora from the ISO images stored on hard disk, or from a network using NFS, FTP, or HTTP methods. Experienced users frequently use one of these methods because it is often faster to read data from a hard disk or network server than from a CD or DVD.
-</para>
-
diff --git a/en-US/Boot_x86_ppc-para-6.xml b/en-US/Boot_x86_ppc-para-6.xml
deleted file mode 100644
index 2d910c2..0000000
--- a/en-US/Boot_x86_ppc-para-6.xml
+++ /dev/null
@@ -1,8 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
- "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd">
-
-<para>
-	The following table summarizes the different boot methods and recommended installation methods to use with each:
-</para>
-
diff --git a/en-US/Boot_x86_ppc-para-7.xml b/en-US/Boot_x86_ppc-para-7.xml
deleted file mode 100644
index d354203..0000000
--- a/en-US/Boot_x86_ppc-para-7.xml
+++ /dev/null
@@ -1,8 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
- "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd">
-
-<para>
-	To boot with <indexterm> <primary>PXE (Pre-boot eXecution Environment)</primary> </indexterm> PXE, you need a properly configured server, and a network interface in your computer that supports PXE.  For information on how to configure a PXE server, refer to <xref linkend="ap-install-server"/>.
-</para>
-
diff --git a/en-US/Boot_x86_ppc-para-8.xml b/en-US/Boot_x86_ppc-para-8.xml
deleted file mode 100644
index 2cb4461..0000000
--- a/en-US/Boot_x86_ppc-para-8.xml
+++ /dev/null
@@ -1,8 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
- "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd">
-
-<para>
-	To boot a computer from a PXE server:
-</para>
-
diff --git a/en-US/Boot_x86_ppc-procedure-1.xml b/en-US/Boot_x86_ppc-procedure-1.xml
deleted file mode 100644
index 7118848..0000000
--- a/en-US/Boot_x86_ppc-procedure-1.xml
+++ /dev/null
@@ -1,23 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-<!DOCTYPE procedure PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
- "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd">
-
-<procedure>
-	<step>
-		<para>
-			Ensure that the network cable is attached.  The link indicator light on the network socket should be lit, even if the computer is not switched on.
-		</para>
-	</step>
-	<step>
-		<para>
-			Switch on the computer.
-		</para>
-	</step>
-	<step>
-		<para>
-			A menu screen appears.  Press the number key that corresponds to the desired option.
-		</para>
-	</step>
-</procedure>
-
-
diff --git a/en-US/Boot_x86_ppc-table-1.xml b/en-US/Boot_x86_ppc-table-1.xml
deleted file mode 100644
index 1dfcc1a..0000000
--- a/en-US/Boot_x86_ppc-table-1.xml
+++ /dev/null
@@ -1,29 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
- "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd">
-
-<table frame='all'><title>Boot methods and installation methods</title>
-	<tgroup cols='2' align='left' colsep='1' rowsep='1'>
-		<thead>
-			<row>
-				<entry>Boot method</entry>
-				<entry>Installation method</entry>
-			</row>
-		</thead>
-		<tbody>
-			<row>
-				<entry>DVD</entry>
-				<entry>DVD, network, or hard disk</entry>
-			</row>
-			<row>
-				<entry>Minimal boot CD or USB, rescue CD</entry>
-				<entry>Network or hard disk</entry>
-			</row>
-			<row>
-				<entry>Live CD or USB</entry>
-				<entry><application>Install to Hard Disk</application> application</entry>
-			</row>
-		</tbody>
-	</tgroup>
-</table>    
-
diff --git a/en-US/Boot_x86_ppc-title-1.xml b/en-US/Boot_x86_ppc-title-1.xml
deleted file mode 100644
index 0d32370..0000000
--- a/en-US/Boot_x86_ppc-title-1.xml
+++ /dev/null
@@ -1,6 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
- "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd">
-
-<title>Booting the Installer</title>
-
diff --git a/en-US/Boot_x86_ppc-title-2.xml b/en-US/Boot_x86_ppc-title-2.xml
deleted file mode 100644
index 6a25b30..0000000
--- a/en-US/Boot_x86_ppc-title-2.xml
+++ /dev/null
@@ -1,6 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
- "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd">
-
-<title>The Boot Menu</title>
-
diff --git a/en-US/Boot_x86_ppc-title-3.xml b/en-US/Boot_x86_ppc-title-3.xml
deleted file mode 100644
index 7a9b500..0000000
--- a/en-US/Boot_x86_ppc-title-3.xml
+++ /dev/null
@@ -1,9 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
- "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd">
-
-
-<title>
-	Installing from a Different Source
-</title>
-
diff --git a/en-US/Boot_x86_ppc-title-4.xml b/en-US/Boot_x86_ppc-title-4.xml
deleted file mode 100644
index 662c75f..0000000
--- a/en-US/Boot_x86_ppc-title-4.xml
+++ /dev/null
@@ -1,8 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
- "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd">
-
-<title>
-	Booting from the Network using PXE
-</title>
-
diff --git a/en-US/Boot_x86_ppc-variablelist-1.xml b/en-US/Boot_x86_ppc-variablelist-1.xml
deleted file mode 100644
index c6eece6..0000000
--- a/en-US/Boot_x86_ppc-variablelist-1.xml
+++ /dev/null
@@ -1,56 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-<!DOCTYPE variablelist PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
- "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd">
-
-<variablelist>
-	<varlistentry>
-		<term>Install or upgrade an existing system</term>
-		<listitem>
-			<para>
-				This option is the default.  Choose this option to install Fedora onto your computer system using the graphical installation program.
-			</para>
-		</listitem>
-	</varlistentry>
-	<varlistentry>
-		<term>Install system with basic video driver</term>
-		<listitem>
-			<para>
-				This option allows you to install Fedora in graphical mode even if the installation program is unable to load the correct driver for your video card. If your screen appears distorted or goes blank when using the the <guilabel>Install or upgrade an existing system</guilabel> option, restart your computer and try this option instead.
-			</para>
-		</listitem>
-	</varlistentry>
-	<varlistentry>
-		<term>Rescue installed system</term>
-		<listitem>
-			<para>
-				Choose this option to repair a problem with your installed Fedora system that prevents you from booting normally.  Although Fedora is an exceptionally stable computing platform, it is still possible for occasional problems to occur that prevent booting.  The rescue environment contains utility programs that allow you fix a wide variety of these problems.
-			</para>
-		</listitem>
-	</varlistentry>
-	<varlistentry>
-		<term>Boot from local drive</term>
-		<listitem>
-			<para>
-				This option boots the system from the first installed disk. If you booted this disc accidentally, use this option to boot from the hard disk immediately without starting the installer.
-			</para>
-		</listitem>
-	</varlistentry>
-	<!-- Not in RHEL6 Beta <varlistentry>
-		<term>Memory Test</term>
-		<listitem>
-			<para>
-				This option runs an exhaustive test on the memory on your system.  For more information, refer to <xref linkend="sn-memtest"/>.
-			</para>
-		</listitem>
-	</varlistentry>   -->
-	<!-- <section id="sn-verifying-livecd">
-      <title>Verifying the Live CD</title>
-      <para>If you boot from the Live CD, choose <guilabel>Verify and
-	  Boot</guilabel> from the boot menu.  The
-	verification process runs automatically during the boot process,
-	and if it succeeds, the Live CD continues loading.  If the
-	verification fails, create a new Live CD using the ISO image you
-	downloaded earlier.</para>
-    </section> -->
-</variablelist>
-
diff --git a/en-US/Complete-x86.xml b/en-US/Complete-x86.xml
deleted file mode 100644
index 6c5209f..0000000
--- a/en-US/Complete-x86.xml
+++ /dev/null
@@ -1,34 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<section id="s1-complete-x86">
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Complete_common-title-1.xml"/>
-	<!-- Installation Complete -->
-	 
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Complete_common-para-1.xml"/>
-	<!-- Congratulations! Your installation is now complete! -->
-	 
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Complete_x86-para-2.xml"/>
-	<!-- The installation program prompts you to prepare your -->
-	 
-<!-- for RHEL only	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Complete_common-para-3.xml"/> -->
-	<!-- After your computer's normal power-up sequence has completed -->
-	 
-<!-- for RHEL only	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Complete_common-itemizedlist-1.xml"/> -->
-	<!-- Press Enter - causes the default boot entry to be booted.,etc... -->
-	 
-<!-- for RHEL only	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Complete_common-para-4.xml"/> -->
-	<!-- Do whatever is appropriate to boot Red Hat Enterprise -->
-	 
-<!-- for RHEL only	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Complete_common-para-5.xml"/> -->
-	<!-- The first time you start your Red Hat Enterprise Linux -->
-	
-<!-- for RHEL only	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Complete_common-para-6.xml"/> -->
-	<!-- For information on registering your Red Hat Enterprise Linux subscription -->
-	     
-	      
-</section>
diff --git a/en-US/Complete_common-para-1.xml b/en-US/Complete_common-para-1.xml
deleted file mode 100644
index 894ed67..0000000
--- a/en-US/Complete_common-para-1.xml
+++ /dev/null
@@ -1,7 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]> 
-
-<para>
-	Congratulations! Your Fedora installation is now complete!
-</para>
\ No newline at end of file
diff --git a/en-US/Complete_common-title-1.xml b/en-US/Complete_common-title-1.xml
deleted file mode 100644
index 3e59c52..0000000
--- a/en-US/Complete_common-title-1.xml
+++ /dev/null
@@ -1,8 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE title PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<title>Installation Complete</title>
\ No newline at end of file
diff --git a/en-US/Complete_x86-para-2.xml b/en-US/Complete_x86-para-2.xml
deleted file mode 100644
index 1b9e6a5..0000000
--- a/en-US/Complete_x86-para-2.xml
+++ /dev/null
@@ -1,10 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]> 
-
-<para>
-	The installation program prompts you to prepare your system for reboot. Remember to remove any installation media if it is not ejected automatically upon reboot.
-</para>
\ No newline at end of file
diff --git a/en-US/Contributors_and_production_methods.xml b/en-US/Contributors_and_production_methods.xml
deleted file mode 100644
index 688537c..0000000
--- a/en-US/Contributors_and_production_methods.xml
+++ /dev/null
@@ -1,554 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-
-<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
- "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd">
-<!-- $Id: -->
-
-<appendix id="ch-Contributors_and_production_methods">
-  <title>Contributors and production methods</title>
-  <section id="sn-Contributors">
-    <title>Contributors</title>
-    <itemizedlist>
-      <listitem>
-	<para>
-	  <ulink url="http://fedoraproject.org/wiki/User:Fab">Fabian Affolter</ulink> (translator - German)
-	</para>
-      </listitem>
-      <listitem>
-	<para>
-	  <ulink url="http://fedoraproject.org/wiki/AmanAlam">Amanpreet Singh Alam</ulink> (translator - Punjabi)
-	</para>
-      </listitem>
-      <listitem>
-	<para>
-	  Jean-Paul Aubry (translator - French)
-	</para>
-      </listitem>
-      <listitem>
-	<para>
-	  David Barzilay (translator - Brazilian Portuguese)
-	</para>
-      </listitem>
-      <listitem>
-	<para>
-	  <ulink url="http://fedoraproject.org/wiki/User:Beckerde">Domingo Becker</ulink> (translator - Spanish)
-	</para>
-      </listitem>
-      <listitem>
-	<para>
-	  Subhransu Behera (translator - Oriya)
-	</para>
-      </listitem>
-      <listitem>
-	<para>
-	  MichaÅ‚ Bentkowski (translator - Polish)
-	</para>
-      </listitem>
-      <listitem>
-	<para>
-	  Rahul Bhalerao (translator - Marathi)
-	</para>
-      </listitem>
-      <listitem>
-	<para>
-	  Runa Bhattacharjee (translator - Bengali (India))
-	</para>
-      </listitem>
-      <listitem>
-	<para>
-	  <ulink url="http://fedoraproject.org/wiki/TetaBilianou">Teta Bilianou</ulink> (translator - Greek)
-	</para>
-      </listitem>
-      <listitem>
-	<para>
-	  Vitor Vilas Boas (translator - Brazilian Portuguese)
-	</para>
-      </listitem>
-      <listitem>
-	<para>
-	  Lucas Brausch (translator - German)
-	</para>
-      </listitem>
-      <listitem>
-	<para>
-	  <ulink url="http://fedoraproject.org/wiki/User:Logan">Hector Daniel Cabrera </ulink> (translator - Spanish)
-	</para>
-      </listitem>
-      <listitem>
-	<para>
-	  <ulink url="https://fedoraproject.org/wiki/DavidCantrell">David Cantrell</ulink> (writer - VNC installation)
-	</para>
-      </listitem>
-      <listitem>
-	<para>
-	  Guido Caruso (translator - Italian)
-	</para>
-      </listitem>
-      <listitem>
-	<para>
-	  Guillaume Chardin (translator - French)
-	</para>
-      </listitem>
-      <listitem>
-	<para>
-	  <ulink url="http://fedoraproject.org/wiki/NikosCharonitakis">Nikos Charonitakis</ulink> (translator - Greek)
-	</para>
-      </listitem>
-      <listitem>
-	<para>
-	  Chester Cheng (translator - Chinese (Traditional))
-	</para>
-      </listitem>
-      <listitem>
-	<para>
-	  <ulink url="http://fedoraproject.org/wiki/Tomchiukc">Tom K. C. Chiu</ulink> (translator - Chinese (Traditional)) 
-	</para>
-      </listitem>
-      <listitem>
-	<para>
-	  Glaucia Cintra (translator - Brazilian Portuguese)
-	</para>
-      </listitem>
-      <listitem>
-	<para>
-	  Fabien Decroux (translator - French)
-	</para>
-      </listitem>
-      <listitem>
-	<para>
-	  <ulink url="https://fedoraproject.org/wiki/HansdeGoede">Hans De Goede</ulink> (writer - iSCSI)
-	</para>
-      </listitem>
-      <listitem>
-	<para>
-	  Claudio Rodrigo Pereyra Diaz (translator - Spanish)
-	</para>
-      </listitem>
-      <listitem>
-	<para>
-	  <ulink url="http://fedoraproject.org/wiki/PiotrDr%C4%85g">Piotr DrÄ…g</ulink> (translator - Polish)
-	</para>
-      </listitem>
-      <listitem>
-	<para>
-	  <ulink url="http://fedoraproject.org/wiki/DamienDurand">Damien Durand</ulink> (translator - French)
-	</para>
-      </listitem>
-      <listitem>
-	<para>
-	  <ulink url="https://fedoraproject.org/wiki/StuartEllis"> Stuart Ellis</ulink> (writer, editor) 
-	</para>
-      </listitem>
-      <listitem>
-	<para>
-	  <ulink url="http://fedoraproject.org/wiki/User:Fakoor"> Ali Fakoor</ulink> (translator - Persian) 
-	</para>
-      </listitem>
-      <listitem>
-	<para>
-	  Felix I (translator - Tamil)
-	</para>
-      </listitem>
-      <listitem>
-	<para>
-	  Tony Fu (translator - Chinese (Simplified)) 
-	</para>
-      </listitem>
-      <listitem>
-	<para>
-	  <ulink url="https://fedoraproject.org/wiki/User:Pfrields"> Paul W. Frields</ulink> (writer, editor) 
-	</para> 
-      </listitem>
-      <listitem>
-	<para>
-	  Paul Gampe (translator - Japanese)
-	</para>
-      </listitem>
-      <listitem>
-	<para>
-	  Sree Ganesh (translator - Telugu)
-	</para>
-      </listitem>
-      <listitem>
-	<para>
-	  <ulink url="http://fedoraproject.org/wiki/DimitrisGlezos">Dimitris Glezos</ulink> (translator - Greek)
-	</para>
-      </listitem>
-      <listitem>
-	<para>
-	  <ulink url="http://fedoraproject.org/wiki/GuillermoGomez">Guillermo GÃ³mez</ulink> (translator - Spanish)
-	</para>
-      </listitem>
-      <listitem>
-	<para>
-	  <ulink url="http://fedoraproject.org/wiki/Igorbounov">Igor Gorbounov</ulink> (translator - Russian)
-	</para>
-      </listitem>
-      <listitem>
-	<para>
-	  <ulink url="http://fedoraproject.org/wiki/RuiGouveia">Rui Gouveia</ulink> (translator - Portuguese)
-	</para>
-      </listitem>
-      <listitem>
-	<para>
-	  Kiyoto James Hashida (translator - Japanese)
-	</para>
-      </listitem>
-      <listitem>
-	<para>
-	  Severin Heiniger (translator - German)
-	</para>
-      </listitem>
-      <listitem>
-	<para>
-	  Xi Huang (translator - Chinese (Simplified)) 
-	</para>
-      </listitem>
-      <listitem>
-	<para>
-	  Ryuichi Hyugabaru (translator - Japanese)
-	</para>
-      </listitem>
-      <listitem>
-	<para>
-	  Jayaradha N (translator - Tamil)
-	</para>
-      </listitem>
-      <listitem>
-	<para>
-	  Chris Johnson (writer) 
-	</para>
-      </listitem>
-      <listitem>
-	<para>
-	  Eunju Kim (translator - Korean)
-	</para>
-      </listitem>
-      <listitem>
-	<para>
-	  Michelle J Kim (translator - Korean)
-	</para>
-      </listitem>
-      <listitem>
-	<para>
-	  <ulink url="http://translate.fedoraproject.org/people/kmilos">MiloÅ¡ KomarÄeviÄ‡</ulink> (translator - Serbian)
-	</para>
-      </listitem>
-      <listitem>
-	<para>
-	  Alexey Kostyuk (translator - Russian)
-	</para>
-      </listitem>
-      <listitem>
-	<para>
-	  Daniela Kugelmann (translator - German) 
-	</para>
-      </listitem>
-      <listitem>
-	<para>
-	  <ulink url="https://fedoraproject.org/wiki/User:Rlandmann">RÃ¼diger Landmann</ulink> (writer, editor)
-	</para>
-      </listitem>
-      <listitem>
-	<para>
-	  <ulink url="http://translate.fedoraproject.org/people/raada">Magnus Larsson</ulink> (translator - Swedish)
-	</para>
-      </listitem>
-      <listitem>
-	<para>
-	  <ulink url="https://fedoraproject.org/wiki/ChristopherusLaurentius">Christopherus Laurentius</ulink> (translator - Indonesian)
-	</para>
-      </listitem>
-      <listitem>
-	<para>
-	  Florent Le Coz (translator - French)
-	</para>
-      </listitem>
-      <listitem>
-	<para>
-	  Erick Lemon (writer) 
-	</para>
-      </listitem>
-      <listitem>
-	<para>
-	  Andy Liu (translator - Chinese (Traditional))
-	</para>
-      </listitem>
-      <listitem>
-	<para>
-	  Wei Liu (translator - Chinese (Simplified))
-	</para>
-      </listitem>
-      <listitem>
-	<para>
-	  Yelitza Louze (translator - Spanish) 
-	</para>
-      </listitem>
-      <listitem>
-	<para>
-	  Gan Lu (translator - Chinese (Simplified))
-	</para>
-      </listitem>
-      <listitem>
-	<para>
-	  <ulink url="http://fedoraproject.org/wiki/User:Jensm">Jens Maucher</ulink> (translator - German)
-	</para>
-      </listitem>
-      <listitem>
-	<para>
-	  <ulink url="http://fedoraproject.org/wiki/IgorMiletic">Igor MiletiÄ‡</ulink> (translator - Serbian)
-	</para>
-      </listitem>
-      <listitem>
-	<para>
-	  Noriko Mizumoto (translator - Japanese)
-	</para>
-      </listitem>
-      <listitem>
-	<para>
-	  Jeremy W. Mooney (writer) 
-	</para>
-      </listitem>
-      <listitem>
-	<para>
-	  EnikÅ‘ Nagy (translator - Hungarian)
-	</para>
-      </listitem>
-      <listitem>
-	<para>
-	  Igor NestoroviÄ‡ (translator - Serbian)
-	</para>
-      </listitem>
-      <listitem>
-	<para>
-	  <ulink url="https://fedoraproject.org/wiki/User:ke4qqq"> David Nalley</ulink>  (writer, editor)
-	</para>
-      </listitem>
-      <listitem>
-	<para>
-	  John Nguyen (writer) 
-	</para>
-      </listitem>
-      <listitem>
-	<para>
-	  Manuel Ospina (translator - Spanish) 
-	</para>
-      </listitem>
-      <listitem>
-	<para>
-	  Janis Ozolins (translator - Latvian)
-	</para>
-      </listitem>
-      <listitem>
-	<para>
-	  Ankit Patel (translator - Gujarati)
-	</para>
-      </listitem>
-      <listitem>
-	<para>
-	  <ulink url="http://fedoraproject.org/wiki/User:Dpaulo">Davidson Paulo</ulink> (translator - Brazilian Portuguese)
-	</para>
-      </listitem>
-      <listitem>
-	<para>
-	  Ani Peter (translator - Malayalam) 
-	</para>
-      </listitem>
-      <listitem>
-	<para>
-	  <ulink url="https://translate.fedoraproject.org/people/aphukan">Amitakhya Phukan</ulink> (translator - Assamese)
-	</para>
-      </listitem>
-      <listitem>
-	<para>
-	  <ulink url="https://fedoraproject.org/wiki/User:Perplex">Silvio Pierro</ulink> (translator - Italian)
-	</para>
-      </listitem>
-      <listitem>
-	<para>
-	  <ulink url="https://fedoraproject.org/wiki/User:Barney">Micha Pietsch</ulink> (translator - German)
-	</para>
-      </listitem>
-      <listitem>
-	<para>
-	  JosÃ© Nuno Pires (translator - Portuguese)
-	</para>
-      </listitem>
-      <listitem>
-	<para>
-	  Piotr PodgÃ³rski (translator - Polish)
-	</para>
-      </listitem>
-      <listitem>
-	<para>
-	  Yulia Poyarkova (translator - Russian)
-	</para>
-      </listitem>
-      <listitem>
-	<para>
-	  Shankar Prasad (translator - Kannada)
-	</para>
-      </listitem>
-      <listitem>
-	<para>
-	  Rajesh Ranjan (translator - Hindi)
-	</para>
-      </listitem>
-      <listitem>
-	<para>
-	  <ulink url="https://fedoraproject.org/wiki/TommyReynolds"> Tommy Reynolds </ulink> (writer) 
-	</para>
-      </listitem>
-      <listitem>
-	<para>
-	  Tim Richert (translator - German)
-	</para>
-      </listitem>
-      <listitem>
-	<para>
-	  <ulink url="http://fedoraproject.org/wiki/DominikSandjaja">Dominik Sandjaja</ulink> (translator - German)
-	</para>
-      </listitem>
-      <listitem>
-	<para>
-	  <ulink url="http://translate.fedoraproject.org/people/szaman">Sharuzzaman Ahmat Raslan</ulink> (translator - Malay)
-	</para>
-      </listitem>
-      <listitem>
-	<para>
-	  <ulink url="https://fedoraproject.org/wiki/User:Saeedi">Mohsen Saeedi</ulink> (translator - Persian)
-	</para>
-      </listitem>
-      <listitem>
-	<para>
-	  <ulink url="https://fedoraproject.org/wiki/User:Tiansworld">Tian Shixiong</ulink> (translator - Chinese (Simplified))
-	</para>
-      </listitem>
-      <listitem>
-	<para>
-	  Audrey Simons (translator - French)
-	</para>
-      </listitem>
-      <listitem>
-	<para>
-	  Keld Simonsen (translator - Danish)
-	</para>
-      </listitem>
-      <listitem>
-	<para>
-	  <ulink url="https://fedoraproject.org/wiki/User:Jsmith"> Jared K. Smith</ulink> (writer, editor) 	
-	</para>
-      </listitem>
-      <listitem>
-	<para>
-	  Espen Stefansen (translator - Norwegian BokmÃ¥l)
-	</para>
-      </listitem>
-      <listitem>
-	<para>
-	  <ulink url="https://fedoraproject.org/wiki/User:Peti"> Sulyok PÃ©ter</ulink>  (translator - Hungarian)
-	</para>
-      </listitem>
-      <listitem>
-	<para>
-	  <ulink url="https://fedoraproject.org/wiki/User:Zoli73"> SÃ¼megi ZoltÃ¡n</ulink>  (translator - Hungarian)
-	</para>
-      </listitem>
-      <listitem>
-	<para>
-	  <ulink url="https://fedoraproject.org/wiki/User:Tombo">Francesco Tombolini</ulink> (translator - Italian)
-	</para>
-      </listitem>
-      <listitem>
-	<para>
-	  Timo Trinks (translator - German) 
-	</para>
-      </listitem>
-      <listitem>
-	<para>
-	  <ulink url="http://fedoraproject.org/wiki/DimitriosTypaldos">Dimitris Typaldos</ulink> (translator - Greek)
-	</para>
-      </listitem>
-      <listitem>
-	<para>
-	  GÃ¶ran Uddeborg (translator - Swedish)
-	</para>
-      </listitem>
-      <listitem>
-	<para>
-	  <ulink url="http://fedoraproject.org/wiki/MichaelUghetto">MichaÃ«l Ughetto</ulink> (translator - French)
-	</para>
-      </listitem>
-      <listitem>
-	<para>
-	  Francesco Valente (translator - Italian)
-	</para>
-      </listitem>
-      <listitem>
-	<para>
-	  <ulink url="http://fedoraproject.org/wiki/KarstenWade"> Karsten Wade</ulink>  (writer, editor, publisher)
-	</para>
-      </listitem>
-      <listitem>
-	<para>
-	  Sarah Saiying Wang (translator - Chinese (Simplified)) 
-	</para>
-      </listitem>
-      <listitem>
-	<para>
-	  <ulink url="http://fedoraproject.org/wiki/GeertWarrink">Geert Warrink</ulink> (translator - Dutch)
-	</para>
-      </listitem>
-      <listitem>
-	<para>
-	  Elizabeth Ann West (editor) 
-	</para>
-      </listitem>
-      <listitem>
-	<para>
-	  Tyronne Wickramarathne (translator - Sinhalese)
-	</para>
-      </listitem>
-      <listitem>
-	<para>
-	  Ben Wu (translator - Chinese (Traditional))
-	</para>
-      </listitem>
-      <listitem>
-	<para>
-	  Xiaofan Yang (translator - Chinese (Simplified))
-	</para>
-      </listitem>
-      <listitem>
-	<para>
-	  <ulink url="http://translate.fedoraproject.org/people/bbbush">Yuan Yijun</ulink> (translator - Chinese (Simplified))
-	</para>
-      </listitem>
-      <listitem>
-	<para>
-	  <ulink url="http://fedoraproject.org/wiki/DiegoZacarao">Diego BÃºrigo ZacarÃ£o</ulink> (translator - Brazilian Portuguese)
-	</para>
-      </listitem>
-      <listitem>
-	<para>
-	  <ulink url="http://fedoraproject.org/wiki/User:Izaac">Izaac Zavaleta</ulink> (translator - Spanish)
-	</para>
-      </listitem>
-    </itemizedlist>
-    <para>
-      <ulink
-	url="http://docs.fedoraproject.org/install-guide/">http://docs.fedoraproject.org/install-guide/</ulink>
-    </para>
-  </section><section id="sn-Production_methods">
-    <title>Production methods</title>
-    <para>Writers produce the Install Guide directly in DocBook XML in a 
-	revision control repository.  They collaborate with other 
-	subject matter experts during the beta release phase of Fedora 
-	to explain the installation process.  The editorial team ensures 
-	consistency and quality of the finished guide. At this point, the
-	team of translators produces other language versions of the
-	release notes, and then they become available to the general
-	public as part of Fedora.  The publication team also makes the guide,
-	and subsequent errata, available via the Web.</para>
-  </section>
-</appendix>
diff --git a/en-US/Create_LVM-common-important-1.xml b/en-US/Create_LVM-common-important-1.xml
deleted file mode 100644
index 7c81bfb..0000000
--- a/en-US/Create_LVM-common-important-1.xml
+++ /dev/null
@@ -1,10 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<important>
-	<title>Important â€” LVM Unavailable in Text Installs</title>
-	<para>
-		LVM initial set up is not available in a text-mode installation.  The installer allows you to edit pre-configured LVM volumes.  If you need to create an LVM configuration from scratch, hit <keycombo> <keycap function="alt">Alt</keycap> <keycap function="other" otherfunction="F2">F2</keycap> </keycombo> to use the terminal, and run the <command>lvm</command> command.  To return to the text-mode installation, hit <keycombo> <keycap function="alt">Alt</keycap> <keycap function="other" otherfunction="F1">F1</keycap> </keycombo>.
-	</para>
-</important>
diff --git a/en-US/Create_LVM-common-para-1.xml b/en-US/Create_LVM-common-para-1.xml
deleted file mode 100644
index b42fcb6..0000000
--- a/en-US/Create_LVM-common-para-1.xml
+++ /dev/null
@@ -1,7 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<para>
-	<firstterm>Logical Volume Management</firstterm> (LVM) presents a simple logical view of underlying physical storage space, such as a hard drives or LUNs. Partitions on physical storage are represented as <firstterm>physical volumes</firstterm> that can be grouped together into <firstterm>volume groups</firstterm>. Each volume group can be divided into multiple <firstterm>logical volumes</firstterm>, each of which is analogous to a standard disk partition. Therefore, LVM logical volumes function as partitions that can span multiple physical disks.
-</para>
diff --git a/en-US/Create_LVM-common-para-2.xml b/en-US/Create_LVM-common-para-2.xml
deleted file mode 100644
index 43405cc..0000000
--- a/en-US/Create_LVM-common-para-2.xml
+++ /dev/null
@@ -1,7 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<para>
-	To read more about LVM, refer to the <citetitle>Red Hat Enterprise Linux Deployment Guide</citetitle>. Note, LVM is only available in the graphical installation program.
-</para>
diff --git a/en-US/Create_LVM-common-title-1.xml b/en-US/Create_LVM-common-title-1.xml
deleted file mode 100644
index 95644cc..0000000
--- a/en-US/Create_LVM-common-title-1.xml
+++ /dev/null
@@ -1,8 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE title PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<title>
-	Create LVM Logical Volume
-</title>
-
diff --git a/en-US/Create_LVM-common-variablelist-1.xml b/en-US/Create_LVM-common-variablelist-1.xml
deleted file mode 100644
index 1c89e89..0000000
--- a/en-US/Create_LVM-common-variablelist-1.xml
+++ /dev/null
@@ -1,54 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE variablelist PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<variablelist>
-
-
-	<varlistentry>
-		<term><guilabel>Make LVM Volume Group</guilabel></term>
-		<listitem>
-			<para>
-				Choose this option to create LVM volume groups from the available LVM physical volumes, or to add existing logical volumes to a volume group. 
-			</para>
-
-			<figure float="0" ><title>Make LVM Volume Group</title>
-				<mediaobject>
-					<imageobject><imagedata fileref="images/diskpartitioning/lvm-vg.png" format="PNG"/></imageobject>
-					<textobject><para>
-							The Make LVM Volume Group dialog.
-						</para>
-					</textobject>
-				</mediaobject>
-			</figure>
-			<para>
-				To assign one or more physical volumes to a volume group, first name the volume group. Then select the physical volumes to be used in the volume group. Finally, configure logical volumes on any volume groups using the <guilabel>Add</guilabel>, <guilabel>Edit</guilabel> and <guilabel>Delete</guilabel> options.
-			</para>
-			<para>
-				You may not remove a physical volume from a volume group if doing so would leave insufficient space for that group's logical volumes. Take for example a volume group made up of two 5 GB LVM physical volume partitions, which contains an 8 GB logical volume. The installer would not allow you to remove either of the component physical volumes, since that would leave only 5 GB in the group for an 8 GB logical volume. If you reduce the total size of any logical volumes appropriately, you may then remove a physical volume from the volume group. In the example, reducing the size of the logical volume to 4 GB would allow you to remove one of the 5 GB physical volumes.
-			</para>
-		</listitem>
-	</varlistentry>
-
-	<varlistentry>
-		<term><guilabel>Make Logical Volume</guilabel></term>
-		<listitem>
-			<para>
-				Choose this option to create an LVM logical volume. Select a mount point, file system type, and size (in MB) just as if it were a standard disk partition. You can also choose a name for the logical volume and specify the volume group to which it will belong. 
-			</para>
-
-			<figure float="0" ><title>Make Logical Volume</title>
-				<mediaobject>
-					<imageobject><imagedata fileref="images/diskpartitioning/lvm-lv.png" format="PNG"/></imageobject>
-					<textobject><para>
-							The Make Logical Volume dialog.
-						</para>
-					</textobject>
-				</mediaobject>
-			</figure>
-
-		</listitem>
-	</varlistentry>
-</variablelist>
-
-
diff --git a/en-US/Create_LVM-x86.xml b/en-US/Create_LVM-x86.xml
deleted file mode 100644
index 0cfa0e5..0000000
--- a/en-US/Create_LVM-x86.xml
+++ /dev/null
@@ -1,45 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE listitem PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<section id="Create_LVM-x86">
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Create_LVM-common-title-1.xml"/>
-	<!-- Create LVM Logical Volume -->
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Create_LVM-common-important-1.xml"/>
-	<!-- Important â€” LVM Unavailable in Text Installs -->
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Create_LVM-common-para-1.xml"/>
-	<!-- Logical Volume Management (LVM) presents a simple logical view of underlying physical storage space -->
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Create_LVM-common-para-2.xml"/>
-	<!-- To read more about LVM, refer to the Red Hat Enterprise Linux Deployment Guide -->
-	
-	<variablelist>
-		<varlistentry>
-			<term>LVM Physical Volume</term>
-			<listitem>
-				<para>
-					Choose this option to configure a partition or device as an LVM physical volume. This option is the only choice available if your storage does not already contain LVM Volume Groups. This is the same dialog that appears when you add a standard partition â€” refer to <xref linkend="Adding_Partitions-x86"/> for a description of the available options. Note, however, that <guilabel>File System Type</guilabel> must be set to <literal>physical volume (LVM)</literal>
-				</para>
-
-				<figure float="0" ><title>Create an LVM Physical Volume</title>
-					<mediaobject>
-						<imageobject><imagedata fileref="images/diskpartitioning/lvm-pv.png" format="PNG"/></imageobject>
-						<textobject><para>
-								The Create an LVM Physical Volume dialog.
-							</para>
-						</textobject>
-					</mediaobject>
-				</figure>
-
-
-			</listitem>
-		</varlistentry>
-	</variablelist>
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Create_LVM-common-variablelist-1.xml"/>
-	<!-- LVM Physical Volume - Choose this option to configure a partition or device as an LVM physical volume. -->
-
-</section>
-
diff --git a/en-US/Create_Software_RAID-common-para-1.xml b/en-US/Create_Software_RAID-common-para-1.xml
deleted file mode 100644
index 0c867f5..0000000
--- a/en-US/Create_Software_RAID-common-para-1.xml
+++ /dev/null
@@ -1,9 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<para>
-	<firstterm>Redundant arrays of independent disks</firstterm> (RAIDs) are constructed from multiple storage devices that are arranged to provided increased performance and â€” in some configurations â€” greater fault tolerance. 
-</para>
-	
-
diff --git a/en-US/Create_Software_RAID-common-para-2.xml b/en-US/Create_Software_RAID-common-para-2.xml
deleted file mode 100644
index fe07134..0000000
--- a/en-US/Create_Software_RAID-common-para-2.xml
+++ /dev/null
@@ -1,9 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<para>
-	To make a RAID device, you must first create software RAID partitions. Once you have created two or more software RAID partitions, select <guibutton>RAID</guibutton> to join the software RAID partitions into a RAID device.
-</para>
-	
-
diff --git a/en-US/Create_Software_RAID-common-title-1.xml b/en-US/Create_Software_RAID-common-title-1.xml
deleted file mode 100644
index acc2ab0..0000000
--- a/en-US/Create_Software_RAID-common-title-1.xml
+++ /dev/null
@@ -1,8 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE title PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<title>
-	Create Software RAID
-</title>
-
diff --git a/en-US/Create_Software_RAID-common-variablelist-1.xml b/en-US/Create_Software_RAID-common-variablelist-1.xml
deleted file mode 100644
index 8e0cc34..0000000
--- a/en-US/Create_Software_RAID-common-variablelist-1.xml
+++ /dev/null
@@ -1,99 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE variablelist PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<variablelist>
-
-
-
-	<varlistentry>
-		<term><guilabel>RAID Device</guilabel></term>
-		<listitem>
-			<para>
-				Choose this option to construct a RAID device from two or more existing software RAID partitions. This option is available if two or more software RAID partitions have been configured.
-			</para>
-
-			<figure float="0" ><title>Create a RAID device</title>
-				<mediaobject>
-					<imageobject><imagedata fileref="images/diskpartitioning/raid-device.png" format="PNG"/></imageobject>
-					<textobject><para>
-							The create a RAID device dialog.
-						</para>
-					</textobject>
-				</mediaobject>
-			</figure>
-			
-			<para>
-				Select the file system type as for a standard partion. 
-			</para>
-			
-			<para>
-				<application>Anaconda</application> automatically suggests a name for the RAID device, but you can manually select names from <literal>md0</literal> to <literal>md15</literal>.
-			</para>
-			
-			<para>
-				Click the checkboxes beside individual storage devices to include or remove them from this RAID.
-			</para>
-			
-			<para>
-				The <guilabel>RAID Level</guilabel> corresponds to a particular type of RAID. Choose from the following options:
-			</para>
-			
-			<itemizedlist>
-				<listitem>
-					<para>
-						<guilabel>RAID 0</guilabel> â€” distributes data across multiple storage devices. Level 0 RAIDs offer increased performance over standard partitions, and can be used to pool the storage of multiple devices into one large virtual device. Note that Level 0 RAIDS offer no redundancy and that the failure of one device in the array destroys the entire array. RAID 0 requires at least two RAID partitions.
-					</para>
-				</listitem>
-				<listitem>
-					<para>
-						<guilabel>RAID 1</guilabel> â€” mirrors the data on one storage device onto one or more other storage devices. Additional devices in the array provide increasing levels of redundancy. RAID 1 requires at least two RAID partitions.
-					</para>
-				</listitem>
-				<listitem>
-					<para>
-						<guilabel>RAID 4</guilabel> â€” distributes data across multiple storage devices, but uses one device in the array to store parity information that safeguards the array in case any device within the array fails. Because all parity information is stored on the one device, access to this device creates a bottleneck in the performance of the array. RAID 4 requires at least three RAID partitions.
-					</para>
-				</listitem>
-				<listitem>
-					<para>
-						<guilabel>RAID 5</guilabel> â€” distributes data and parity information across multiple storage devices. Level 5 RAIDs therefore offer the performance advantages of distributing data across multiple devices, but do not share the performance bottleneck of level 4 RAIDs because the parity information is also distributed through the array. RAID 5 requires at least three RAID partitions.
-					</para>
-				</listitem>
-				<listitem>
-					<para>
-						<guilabel>RAID 6</guilabel> â€” level 6 RAIDs are similar to level 5 RAIDs, but instead of storing only one set of parity data, they store two sets.  RAID 6 requires at least four RAID partitions.
-					</para>
-				</listitem>
-				<listitem>
-					<para>
-						<guilabel>RAID 10</guilabel> â€” level 10 RAIDs are <firstterm>nested RAIDs</firstterm> or <firstterm>hybrid RAIDs</firstterm>. Level 10 RAIDs are constructed by distributing data over mirrored sets of storage devices. For example, a level 10 RAID contructed from four RAID partitions consists of two pairs of partitions in which one partition mirrors the other. Data is then distributed across both pairs of storage devices, as in a level 0 RAID. RAID 10 requires at least four RAID partitions.
-					</para>
-				</listitem>
-			</itemizedlist>
-
-		</listitem>
-	</varlistentry>
-
-	<varlistentry>
-		<term><guilabel>RAID Clone</guilabel></term>
-		<listitem>
-			<para>
-				Choose this option to set up a RAID <firstterm>mirror</firstterm> of an existing disk. This option is available if two or more disks are attached to the system.
-			</para>
-
-			<figure float="0" ><title>Clone a RAID device</title>
-				<mediaobject>
-					<imageobject><imagedata fileref="images/diskpartitioning/raid-clone.png" format="PNG"/></imageobject>
-					<textobject><para>
-							The clone a RAID device dialog.
-						</para>
-					</textobject>
-				</mediaobject>
-			</figure>
-
-		</listitem>
-	</varlistentry>
-</variablelist>
-
-
diff --git a/en-US/Create_Software_RAID-x86.xml b/en-US/Create_Software_RAID-x86.xml
deleted file mode 100644
index dfe8756..0000000
--- a/en-US/Create_Software_RAID-x86.xml
+++ /dev/null
@@ -1,42 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<section id="Create_Software_RAID-x86">
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Create_Software_RAID-common-title-1.xml"/>
-	<!-- Create Software RAID -->
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Create_Software_RAID-common-para-1.xml"/>
-	<!-- Redundant arrays of independent disks (RAIDs) are constructed from multiple storage devices -->
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Create_Software_RAID-common-para-2.xml"/>
-	<!-- To make a RAID device, you must first create software RAID partitions. -->
-	
-	<variablelist>
-		<varlistentry>
-			<term>RAID Partition</term>
-			<listitem>
-				<para>
-					Choose this option to configure a partition for software RAID. This option is the only choice available if your disk contains no software RAID partitions. This is the same dialog that appears when you add a standard partition â€” refer to <xref linkend="Adding_Partitions-x86"/> for a description of the available options. Note, however, that <guilabel>File System Type</guilabel> must be set to <literal>software RAID</literal>
-				</para>
-
-				<figure float="0" ><title>Create a software RAID partition</title>
-					<mediaobject>
-						<imageobject><imagedata fileref="images/diskpartitioning/software-raid.png" format="PNG"/></imageobject>
-						<textobject><para>
-								The create a software RAID partition dialog.
-							</para>
-						</textobject>
-					</mediaobject>
-				</figure>
-
-
-			</listitem>
-		</varlistentry>
-	</variablelist>
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Create_Software_RAID-common-variablelist-1.xml"/>
-	<!-- To make a RAID device, you must first create software RAID partitions. -->
-
-</section>
-
diff --git a/en-US/Create_Storage-common-figure-1.xml b/en-US/Create_Storage-common-figure-1.xml
deleted file mode 100644
index 5b370c4..0000000
--- a/en-US/Create_Storage-common-figure-1.xml
+++ /dev/null
@@ -1,14 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE figure PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<figure float="0"><title>Creating Storage</title>
-	<mediaobject>
-		<imageobject><imagedata fileref="images/diskpartitioning/part-create.png" format="PNG"/></imageobject>
-		<textobject><para>
-				Creating new storage
-			</para>
-		</textobject>
-	</mediaobject>
-</figure>
-
diff --git a/en-US/Create_Storage-common-listitem-1.xml b/en-US/Create_Storage-common-listitem-1.xml
deleted file mode 100644
index 35086b4..0000000
--- a/en-US/Create_Storage-common-listitem-1.xml
+++ /dev/null
@@ -1,13 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE listitem PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<listitem>
-	<para>
-		<guilabel>Standard Partition</guilabel> â€” create a standard disk partition (as described in <xref linkend="ch-partitions-x86"/>) in unallocated space.
-	</para>
-</listitem>
-			
-			
-			
-			
\ No newline at end of file
diff --git a/en-US/Create_Storage-common-listitem-2.xml b/en-US/Create_Storage-common-listitem-2.xml
deleted file mode 100644
index 42aeb29..0000000
--- a/en-US/Create_Storage-common-listitem-2.xml
+++ /dev/null
@@ -1,10 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE listitem PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<listitem>
-	<para>
-		<guilabel>RAID Partition</guilabel> â€” create a partition in unallocated space to form part of a software RAID device. To form a software RAID device, two or more RAID partitions must be available on the system.
-	</para>
-</listitem>	
-			
\ No newline at end of file
diff --git a/en-US/Create_Storage-common-listitem-3.xml b/en-US/Create_Storage-common-listitem-3.xml
deleted file mode 100644
index c11ee28..0000000
--- a/en-US/Create_Storage-common-listitem-3.xml
+++ /dev/null
@@ -1,10 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE listitem PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<listitem>
-	<para>
-		<guilabel>RAID Device</guilabel> â€” combine two or more RAID partitions into a software RAID device. When you choose this option, you can specify the type of RAID device to create (the <firstterm>RAID level</firstterm>. This option is only available when two or more RAID partitions are available on the system. 
-	</para>
-</listitem>
-			
\ No newline at end of file
diff --git a/en-US/Create_Storage-common-listitem-4.xml b/en-US/Create_Storage-common-listitem-4.xml
deleted file mode 100644
index 26de117..0000000
--- a/en-US/Create_Storage-common-listitem-4.xml
+++ /dev/null
@@ -1,10 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE listitem PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<listitem>
-	<para>
-		<guilabel>RAID Clone</guilabel> â€” create a mirror of a RAID partition on one storage device on another storage device. This option is only available when at least one RAID partition is available on the system.
-	</para>
-</listitem>
-			
\ No newline at end of file
diff --git a/en-US/Create_Storage-common-listitem-5.xml b/en-US/Create_Storage-common-listitem-5.xml
deleted file mode 100644
index ca3e4d7..0000000
--- a/en-US/Create_Storage-common-listitem-5.xml
+++ /dev/null
@@ -1,10 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE listitem PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<listitem>
-	<para>
-		<guilabel>LVM Physical Volume</guilabel> â€” create a <firstterm>physical volume</firstterm> in unallocated space.
-	</para>
-</listitem>
-			
\ No newline at end of file
diff --git a/en-US/Create_Storage-common-listitem-6.xml b/en-US/Create_Storage-common-listitem-6.xml
deleted file mode 100644
index 2a3b61d..0000000
--- a/en-US/Create_Storage-common-listitem-6.xml
+++ /dev/null
@@ -1,10 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE listitem PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<listitem>
-	<para>
-		<guilabel>LVM Volume Group</guilabel> â€” create a <firstterm>volume group</firstterm> from one or more physical volumes. This option is only available when at least one physical volume is available on the system.
-	</para>
-</listitem>
-			
\ No newline at end of file
diff --git a/en-US/Create_Storage-common-listitem-7.xml b/en-US/Create_Storage-common-listitem-7.xml
deleted file mode 100644
index 1f84b35..0000000
--- a/en-US/Create_Storage-common-listitem-7.xml
+++ /dev/null
@@ -1,10 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE listitem PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<listitem>
-	<para>
-		<guilabel>LVM Logical Volume</guilabel> â€” create a <firstterm>logical volume</firstterm> on a volume group. This option is only available when at least one volume group is available on the system.
-	</para>
-</listitem>
-	
\ No newline at end of file
diff --git a/en-US/Create_Storage-common-para-1.xml b/en-US/Create_Storage-common-para-1.xml
deleted file mode 100644
index 7835a65..0000000
--- a/en-US/Create_Storage-common-para-1.xml
+++ /dev/null
@@ -1,8 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<para>
-	The <guilabel>Create Storage</guilabel> dialog allows you to create new storage partitions, logical volumes, and software RAIDs. <application>Anaconda</application> presents options as available or unavailable depending on the storage already present on the system or configured to transfer to the system.
-</para>
-
diff --git a/en-US/Create_Storage-common-para-2.xml b/en-US/Create_Storage-common-para-2.xml
deleted file mode 100644
index 7e173d0..0000000
--- a/en-US/Create_Storage-common-para-2.xml
+++ /dev/null
@@ -1,8 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE title PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<para>
-	Options are grouped under <guilabel>Create Partition</guilabel>, <guilabel>Create Software RAID</guilabel> and <guilabel>Create LVM</guilabel> as follows:
-</para>
-
diff --git a/en-US/Create_Storage-common-title-1.xml b/en-US/Create_Storage-common-title-1.xml
deleted file mode 100644
index 399af73..0000000
--- a/en-US/Create_Storage-common-title-1.xml
+++ /dev/null
@@ -1,8 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE title PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<title>
-	Create Storage
-</title>
-
diff --git a/en-US/Create_Storage-common-title-2.xml b/en-US/Create_Storage-common-title-2.xml
deleted file mode 100644
index 17f6973..0000000
--- a/en-US/Create_Storage-common-title-2.xml
+++ /dev/null
@@ -1,8 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE title PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<title>
-	Create Partition
-</title>
-
diff --git a/en-US/Create_Storage-common-title-3.xml b/en-US/Create_Storage-common-title-3.xml
deleted file mode 100644
index a687660..0000000
--- a/en-US/Create_Storage-common-title-3.xml
+++ /dev/null
@@ -1,8 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE ttile PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<title>
-	Create Software RAID
-</title>
-
diff --git a/en-US/Create_Storage-common-title-4.xml b/en-US/Create_Storage-common-title-4.xml
deleted file mode 100644
index c5d160b..0000000
--- a/en-US/Create_Storage-common-title-4.xml
+++ /dev/null
@@ -1,8 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE ttile PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<title>
-	Create LVM Logical Volume
-</title>
-
diff --git a/en-US/Create_Storage-x86.xml b/en-US/Create_Storage-x86.xml
deleted file mode 100644
index 85c7ec5..0000000
--- a/en-US/Create_Storage-x86.xml
+++ /dev/null
@@ -1,57 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<section id="Create_Storage-x86">
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Create_Storage-common-title-1.xml"/>
-	<!-- Create Storage -->
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Create_Storage-common-para-1.xml"/>
-	<!-- The Create Storage dialog allows you to create new storage partitions -->
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Create_Storage-common-figure-1.xml"/>
-	<!-- Creating Storage -->
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Create_Storage-common-para-2.xml"/>
-	<!-- Options are grouped under Create Partition, Create Software RAID and Create LVM as follows -->
-	
-	<itemizedlist>
-		<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Create_Storage-common-title-2.xml"/>
-		<!-- Create Partition -->
-		<para>
-			Refer to <xref linkend="Adding_Partitions-x86"/> for details of the <guilabel>Add Partition</guilabel> dialog.
-		</para>
-		<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Create_Storage-common-listitem-1.xml"/>
-		<!-- Standard Partition â€” create a standard disk partition -->
-	</itemizedlist>
-	
-	<itemizedlist>
-		<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Create_Storage-common-title-3.xml"/>
-		<!-- Create Software RAID -->
-		<para>
-			Refer to <xref linkend="Create_Software_RAID-x86"/> for more detail.
-		</para>
-		<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Create_Storage-common-listitem-2.xml"/>
-		<!-- RAID Partition â€” create a partition in unallocated space to form part of a software RAID device. -->
-		<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Create_Storage-common-listitem-3.xml"/>
-		<!-- RAID Device â€” combine two or more RAID partitions into a software RAID device. -->
-		<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Create_Storage-common-listitem-4.xml"/>
-		<!-- RAID Clone â€” create a mirror of a RAID partition on one storage device on another storage device. -->
-	</itemizedlist>
-	
-	<itemizedlist>
-		<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Create_Storage-common-title-4.xml"/>
-		<!-- Create LVM Logical Volume -->
-		<para>
-			Refer to <xref linkend="Create_LVM-x86"/> for more detail.
-		</para>
-		<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Create_Storage-common-listitem-5.xml"/>
-		<!-- LVM Physical Volume â€” create a physical volume in unallocated space. -->
-		<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Create_Storage-common-listitem-6.xml"/>
-		<!-- LVM Volume Group â€” create a volume group from one or more physical volumes. -->
-		<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Create_Storage-common-listitem-7.xml"/>
-		<!-- LVM Logical Volume â€” create a logical volume on a volume group. -->
-	</itemizedlist>
-
-</section>
-
diff --git a/en-US/DU-Preparing_a_driver_update_disk_ppc_x86-warning-1.xml b/en-US/DU-Preparing_a_driver_update_disk_ppc_x86-warning-1.xml
deleted file mode 100644
index 8439888..0000000
--- a/en-US/DU-Preparing_a_driver_update_disk_ppc_x86-warning-1.xml
+++ /dev/null
@@ -1,10 +0,0 @@
-<?xml version='1.0' encoding='utf-8' ?>
-<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
-]>
-
-<warning>
-	<title>These instructions could destroy data</title>
-	<para>
-		If you perform this procedure with a disk or USB storage device that already contains data, this data will be destroyed with no warning. Make sure that you specify the correct disk or USB storage device, and make sure that this disk or storage device does not contain any data that you want to keep.
-	</para>
-</warning>
diff --git a/en-US/DiskEncryptionUserGuide.xml b/en-US/DiskEncryptionUserGuide.xml
deleted file mode 100644
index 6a0b86b..0000000
--- a/en-US/DiskEncryptionUserGuide.xml
+++ /dev/null
@@ -1,336 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd">
-
-<appendix id="Disk_Encryption_Guide">
-  <title>Disk Encryption</title>
-
-    <section>
-      <title>What is block device encryption? </title>
-      <para> Block device encryption protects the data on a block device by encrypting it. To access the device's decrypted contents, a user must provide a passphrase or key as authentication. This provides additional security beyond existing OS security mechanisms in that it protects the device's contents even if it has been physically removed from the system.</para>
-    </section>
-    <section>
-      <title>Encrypting block devices using dm-crypt/LUKS </title>
-      <para>
-	<firstterm>Linux Unified Key Setup</firstterm> (LUKS) is a specification for block device encryption. It establishes an on-disk format for the data, as well as a passphrase/key management policy.</para>
-      <para>LUKS uses the kernel device mapper subsystem via the <command>dm-crypt</command> module. This arrangement provides a low-level mapping that handles encryption and decryption of the device's data. User-level operations, such as creating and accessing encrypted devices, are accomplished through the use of the <command>cryptsetup</command> utility. 
-      </para>
-      <section>
-	<title>Overview of LUKS </title>
-	<itemizedlist>
-	  <listitem>
-            <para>What LUKS does:
-	      <itemizedlist>
-		<listitem>
-		  <para>LUKS encrypts entire block devices
-		    <itemizedlist>
-		      <listitem>
-			<para>LUKS is thereby well-suited for protecting the contents of mobile devices such as:
-			  <itemizedlist>
-			    <listitem>
-			      <para>Removable storage media</para>
-			    </listitem>
-			    <listitem>
-			      <para>Laptop disk drives</para>
-			    </listitem>
-			  </itemizedlist>
-			</para>
-		      </listitem>
-		    </itemizedlist>
-                  </para>
-		</listitem>
-		<listitem>
-		  <para>The underlying contents of the encrypted block device are arbitrary.
-		    <itemizedlist>
-		      <listitem>
-			<para>This makes it useful for encrypting <command>swap</command> devices.</para>
-		      </listitem>
-		      <listitem>
-			<para>This can also be useful with certain databases that use specially formatted block devices for data storage.</para>
-		      </listitem>
-		    </itemizedlist>
-                  </para>
-		</listitem>
-		<listitem>
-		  <para>LUKS uses the existing device mapper kernel subsystem.
-		    <itemizedlist>
-		      <listitem>
-			<para>This is the same subsystem used by LVM, so it is well tested.</para>
-		      </listitem>
-		    </itemizedlist>
-                  </para>
-                </listitem>
-		<listitem>
-		  <para>LUKS provides passphrase strengthening.
-		    <itemizedlist>
-                      <listitem>
-			<para>This protects against dictionary attacks.</para>
-                      </listitem>
-		    </itemizedlist>
-                  </para>
-		</listitem>
-		<listitem>
-		  <para>LUKS devices contain multiple key slots.
-		    <itemizedlist>
-                      <listitem>
-			<para>This allows users to add backup keys/passphrases.</para>
-                      </listitem>
-		    </itemizedlist>
-                  </para>
-		</listitem>
-              </itemizedlist>
-            </para>
-	  </listitem>
-	  <listitem>
-            <para>What LUKS does <emphasis>not</emphasis> do:
-	      <itemizedlist>
-                <listitem>
-                  <para>LUKS is not well-suited for applications requiring many (more than eight) users to have distinct access keys to the same device.</para>
-                </listitem>
-                <listitem>
-                  <para>LUKS is not well-suited for applications requiring file-level encryption.</para>
-                </listitem>
-	      </itemizedlist>
-            </para>
-	  </listitem>
-        </itemizedlist>
-        <para>
-		More detailed information about LUKS is available from the project website at <ulink url="http://code.google.com/p/cryptsetup/">http://code.google.com/p/cryptsetup/</ulink>.
-        </para>
-      </section>
-      <section>
-	<title>How will I access the encrypted devices after installation? (System Startup) </title>
-	<para> During system startup you will be presented with a passphrase prompt. After the correct passphrase has been provided the system will continue to boot normally. If you used different passphrases for multiple encypted devices you may need to enter more than one passphrase during the startup.</para>
-	<para>
-	  <note><title>Tip</title>
-            <para>Consider using the same passphrase for all encrypted block devices in a given system. This will simplify system startup and you will have fewer passphrases to remember. Just make sure you choose a good passphrase!</para>
-          </note>
-	</para>
-      </section>
-      <section>
-	<title>Choosing a Good Passphrase </title>
-	<para> While dm-crypt/LUKS supports both keys and passphrases, the anaconda installer only supports the use of passphrases for creating and accessing encrypted block devices during installation.</para>
-	<para>LUKS does provide passphrase strengthening but it is still a good idea to choose a good (meaning "difficult to guess") passphrase. Note the use of the term "passphrase", as opposed to the term "password". This is intentional. Providing a phrase containing multiple words to increase the security of your data is important.</para>
-      </section>
-    </section>
-    
-    <section>
-      <title>Creating Encrypted Block Devices in Anaconda </title>
-      <para> You can create encrypted devices during system installation. This allows you to easily configure a system with encrypted partitions.</para>
-      <para>To enable block device encryption, check the "Encrypt System" checkbox when selecting automatic partitioning or the "Encrypt" checkbox when creating an individual partition, software RAID array, or logical volume. After you finish partitioning, you will be prompted for an encryption passphrase. This passphrase will be required to access the encrypted devices. If you have pre-existing LUKS devices and provided correct passphrases for them earlier in the install process the passphrase entry dialog will also contain a checkbox. Checking this checkbox indicates that you would like the new passphrase to be added to an available slot in each of the pre-existing encrypted block devices.</para>
-      <para>
-	<note><title>Tip</title>
-          <para>Checking the "Encrypt System" checkbox on the "Automatic Partitioning" screen and then choosing "Create custom layout" does not cause any block devices to be encrypted automatically.</para>
-        </note>
-      </para>
-      <para>
-	<note><title>Tip</title>
-          <para>You can use <command>kickstart</command> to set a separate passphrase for each new encrypted block device.</para>
-        </note>
-      </para>
-      <section>
-	<title>What Kinds of Block Devices Can Be Encrypted? </title>
-	<para> Most types of block devices can be encrypted using LUKS. From anaconda you can encrypt partitions, LVM physical volumes, LVM logical volumes, and software RAID arrays.</para>
-      </section>
-<!--      <section>
-	<title>Limitations of Anaconda's Block Device Encryption Support </title>
-	<para>This section is about Anaconda's Block Device Encryption Support</para>
-	section>
-	  <title>Filling the Device with Random Data Before Encrypting </title>
-	  <para> Filling a device with random data prior to encrypting improves the strength of the encryption. However, it can take a very long time to fill the device with random data. It is because of those time requirements that anaconda does not offer this option. This step can be performed manually, using a <command>kickstart %pre</command> script. Instructions can be found <xref linkend="randomize_device"/>.</para>
-	</section>
-	section>
-	  <title>Using a Key Comprised of Randomly Generated Data to Access Encrypted Devices </title>
-	  <para> In addition to passphrases, LUKS devices can be accessed with a key comprised of randomly generated data. Setting up one or more keys to access the encrypted devices can be done on the installed system or through the use of a <command>kickstart %post</command> script. Instructions can be found <xref linkend="new_key"/>.</para>
-	</section>
- 	</section> -->
-	<section id="Disk_Encryption_Guide-Saving_Passphrases">
-		<title>Saving Passphrases</title>
-		<indexterm significance="normal">
-			<primary>Encryption</primary>
-			<secondary>Passphrases</secondary>
-			<tertiary>Saving passphrases</tertiary>
-		</indexterm>
-		<indexterm significance="normal">
-			<primary>Passphrases</primary>
-			<secondary>Block device encryption passphrases</secondary>
-			<tertiary>Saving block device encryption passphrases</tertiary>
-		</indexterm>
-		<para>
-			If you use a kickstart file during installation, you can automatically save the passphrases used during installation to an encrypted file on the local file system. To use this feature, you must have an X.509 certificate available at a location that <application>anaconda</application> can access. To specify the URL of this certificate, add the  <parameter>--escrowcert</parameter> parameter to any of the <command>autopart</command>, <command>logvol</command>, <command>part</command> or <command>raid</command> commands. During installation, the encryption keys for the specified devices are saved in files in <filename>/</filename> (root), encrypted with the certificate. 
-		</para>
-		<para>
-			Note that this feature is available only while performing a kickstart installation. Refer to <xref linkend="ch-kickstart2"/> for more detail. 
-		</para>
-	</section>
-	<section id="Disk_Encryption_Guide-Creating_and_Saving_Backup_Passphrases">
-		<title>Creating and Saving Backup Passphrases</title>
-		<indexterm significance="normal">
-			<primary>Encryption</primary>
-			<secondary>Backup passphrases</secondary>
-			<tertiary>Creating backup passphrases</tertiary>
-		</indexterm>
-		<indexterm significance="normal">
-			<primary>Encryption</primary>
-			<secondary>Backup passphrases</secondary>
-			<tertiary>Saving backup passphrases</tertiary>
-		</indexterm>
-		<indexterm significance="normal">
-			<primary>Passphrases</primary>
-			<secondary>Block device encryption passphrases</secondary>
-			<tertiary>Creating backup block device encryption passphrases</tertiary>
-		</indexterm>
-		<indexterm significance="normal">
-			<primary>Passphrases</primary>
-			<secondary>Block device encryption passphrases</secondary>
-			<tertiary>Saving backup block device encryption passphrases</tertiary>
-		</indexterm>
-		<para>
-			If you use a kickstart file during installation, <application>anaconda</application> can add a randomly generated backup passphrase to each block device on the system and save each passphrase to an encrypted file on the local file system. Specify the URL of this certificate with the  <parameter>--escrowcert</parameter> parameter as described in <xref linkend="Disk_Encryption_Guide-Saving_Passphrases"/>, followed by the  <parameter>--backuppassphrase</parameter> parameter for each of the kickstart commands that relate to the devices for which you want to create backup passphrases.
-		</para>
-		<para>
-			Note that this feature is available only while performing a kickstart installation. Refer to <xref linkend="ch-kickstart2"/> for more detail. 
-		</para>
-	</section>
-      </section>
-   
-    <section>
-      <title>Creating Encrypted Block Devices on the Installed System After Installation </title>
-      <para> Encrypted block devices can be created and configured after installation. </para>
-	<section>
-		<title>Create the block devices </title>
-		<para> Create the block devices you want to encrypt by using <command>parted</command>, <command>pvcreate</command>, <command>lvcreate</command> and <command>mdadm</command>.</para>
-	</section>
-	<section id="randomize_device">
-		<title>Optional: Fill the device with random data</title>
-		<para> Filling &lt;device&gt; (eg: <filename>/dev/sda3</filename>) with random data before encrypting it greatly increases the strength of the encryption. The downside is that it can take a very long time.</para>
-		<para>
-		<warning><title>Warning</title>
-		<para>The commands below will destroy any existing data on the device.</para>
-		</warning>
-		</para>
-		<itemizedlist>
-		<listitem>
-		<para> The best way, which provides high quality random data but takes a long time (several minutes per gigabyte on most systems):</para>
-<programlisting>dd if=/dev/urandom of=&lt;device&gt;</programlisting>
-		</listitem>
-		<listitem>
-		<para> Fastest way, which provides lower quality random data:</para>
-<programlisting>badblocks -c 10240 -s -w -t random -v &lt;device&gt;</programlisting>
-		</listitem>
-		</itemizedlist>
-	</section>
-	<section>
-		<title>Format the device as a dm-crypt/LUKS encrypted device </title>
-		
-		<warning>
-			<title>Warning</title>
-			<para>The command below will destroy any existing data on the device.</para>
-		</warning>
-		
-<programlisting>cryptsetup luksFormat &lt;device&gt;</programlisting>
-		
-		<para>
-		<note><title>Tip</title>
-		<para>For more information, read the <command>cryptsetup(8)</command> man page.</para>
-		</note>
-		</para><para>After supplying the passphrase twice the device will be formatted for use. To verify, use the following command:</para>
-		<programlisting>cryptsetup isLuks &lt;device&gt; &amp;&amp; echo Success</programlisting>
-		<para>To see a summary of the encryption information for the device, use the following command:</para>
-		<programlisting>cryptsetup luksDump &lt;device&gt;</programlisting>
-	</section>
-	<section>
-		<title>Create a mapping to allow access to the device's decrypted contents </title>
-		<para> To access the device's decrypted contents, a mapping must be established using the kernel <command>device-mapper</command>.</para><para>It is useful to choose a meaningful name for this mapping. LUKS provides a UUID (Universally Unique Identifier) for each device. This, unlike the device name (eg: <filename>/dev/sda3</filename>), is guaranteed to remain constant as long as the LUKS header remains intact. To find a LUKS device's UUID, run the following command:</para>
-		<programlisting>cryptsetup luksUUID &lt;device&gt;</programlisting>
-		
-		<para>An example of a reliable, informative and unique mapping name would be <command>luks-&lt;uuid&gt;</command>, where &lt;uuid&gt; is replaced with the device's LUKS UUID (eg:  <command>luks-50ec957a-5b5a-47ee-85e6-f8085bbc97a8</command>). This naming convention might seem unwieldy but is it not necessary to type it often.</para>
-		<programlisting>cryptsetup luksOpen &lt;device&gt; &lt;name&gt;</programlisting>
-		
-		<para>There should now be a device node, <filename>/dev/mapper/&lt;name&gt;</filename>, which represents the decrypted device. This block device can be read from and written to like any other unencrypted block device.</para>
-		<para>To see some information about the mapped device, use the following command:</para>
-		
-		<programlisting>dmsetup info &lt;name&gt;</programlisting>
-		
-		<para>
-		<note><title>Tip</title>
-		<para>For more information, read the <command>dmsetup(8)</command> man page.</para>
-		</note>
-		</para>
-	</section>
-	<section>
-		<title>Create filesystems on the mapped device, or continue to build complex storage structures using the mapped device </title>
-		<para> Use the mapped device node (<filename>/dev/mapper/&lt;name&gt;</filename>) as any other block device. To create an <command>ext2</command> filesystem on the mapped device, use the following command:</para>
-		
-		<programlisting>mke2fs /dev/mapper/&lt;name&gt;</programlisting>
-		
-		<para>To mount this filesystem on <filename>/mnt/test</filename>, use the following command:</para>
-		<para>
-		<important>
-		<para>The directory <filename>/mnt/test</filename> must exist before executing this command.</para>
-		</important>
-		</para>
-		<programlisting>mount /dev/mapper/&lt;name&gt; /mnt/test</programlisting>
-		
-	</section>
-	<section>
-		<title>Add the mapping information to <filename>/etc/crypttab</filename></title>
-		<para> In order for the system to set up a mapping for the device, an entry must be present in the <filename>/etc/crypttab</filename> file. If the file doesn't exist, create it and change the owner and group to root (<command>root:root</command>) and change the mode to <command>0744</command>. Add a line to the file with the following format:</para>
-		
-		<programlisting>&lt;name&gt;  &lt;device&gt;  none</programlisting>
-		
-		<para>The &lt;device&gt; field should be given in the form "UUID=&lt;luks_uuid&gt;", where &lt;luks_uuid&gt; is the LUKS uuid as given by the command <command>cryptsetup luksUUID &lt;device&gt;</command>. This ensures the correct device will be identified and used even if the device node (eg: <filename>/dev/sda5</filename>) changes.</para>
-		<para>
-		<note><title>Tip</title>
-		<para>For details on the format of the <filename>/etc/crypttab</filename> file, read the <command>crypttab(5)</command> man page.</para>
-		</note>
-		</para>
-	</section>
-	<section>
-		<title>Add an entry to <filename>/etc/fstab</filename></title>
-		<para> Add an entry to /etc/fstab. This is only necessary if you want to establish a persistent association between the device and a mountpoint. Use the decrypted device, <filename>/dev/mapper/&lt;name&gt;</filename> in the <filename>/etc/fstab</filename> file.</para>
-		<para>In many cases it is desirable to list devices in <filename>/etc/fstab</filename> by UUID or by a filesystem label. The main purpose of this is to provide a constant identifier in the event that the device name (eg: <filename>/dev/sda4</filename>) changes. LUKS device names in the form of <filename>/dev/mapper/luks-&lt;luks_uuid&gt;</filename> are based only on the device's LUKS UUID, and are therefore guaranteed to remain constant. This fact makes them suitable for use in <filename>/etc/fstab</filename>.</para>
-		<para>
-		<note><title>Title</title>
-		<para>For details on the format of the <filename>/etc/fstab</filename> file, read the <command>fstab(5)</command> man page.</para>
-		</note>
-		</para>
-	</section>
-    </section>
-    <section>
-      <title>Common Post-Installation Tasks </title>
-      <para>The following sections are about common post-installation tasks.</para> 
-      		<section id="new_key">
-		<title>Set a randomly generated key as an additional way to access an encrypted block device</title>
-		<para>These sections are about generating keys and adding keys.</para>
-			<section>
-			<title>Generate a key </title>
-			<para> This will generate a 256-bit key in the file <filename>$HOME/keyfile</filename>.</para>
-			
-			<programlisting>
-		dd if=/dev/urandom of=$HOME/keyfile bs=32 count=1
-		chmod 600 $HOME/keyfile
-		</programlisting>
-			</section>
-			<section>
-			<title>Add the key to an available keyslot on the encrypted device </title>
-			<programlisting>cryptsetup luksAddKey &lt;device&gt; ~/keyfile</programlisting>
-			</section>
-	
-      </section>
-      <section>
-	<title>Add a new passphrase to an existing device </title>
-	
-	<programlisting>cryptsetup luksAddKey &lt;device&gt;</programlisting>
-	
-	<para>After being prompted for any one of the existing passprases for authentication, you will be prompted to enter the new passphrase.</para>
-      </section>
-      <section>
-	<title>Remove a passphrase or key from a device </title>
-	
-	<programlisting>cryptsetup luksRemoveKey &lt;device&gt;</programlisting>
-	
-	<para>You will be prompted for the passphrase you wish to remove and then for any one of the remaining passphrases for authentication.</para>
-      </section>
-</section>
-</appendix>
-
diff --git a/en-US/Disk_Partitioning-x86.xml b/en-US/Disk_Partitioning-x86.xml
deleted file mode 100644
index 11d22b1..0000000
--- a/en-US/Disk_Partitioning-x86.xml
+++ /dev/null
@@ -1,126 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<section id="s1-diskpartitioning-x86">
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Disk_Partitioning_common-title-1.xml"/>
-	<!-- Partitioning Your System -->
-	
-	<!-- Begin Index terms -->
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Disk_Partitioning_common-indexterm-1.xml"/>
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Disk_Partitioning_common-indexterm-2.xml"/>
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Disk_Partitioning_common-indexterm-3.xml"/>
-	<!-- End Index terms -->
-	
-	<para>
-		If you chose one of the four automatic partitioning options and did not select <guilabel>Review</guilabel>, skip ahead to <xref linkend="s1-pkgselection-x86"/>.
-	</para>
-
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Disk_Partitioning_x86_ppc-para-1.xml"/>
-	<!-- If you chose one of the automatic partitioning options and selected... -->
-
-	<para>
-		If you chose to create a custom layout, you must tell the installation program where to install Fedora. This is done by defining mount points for one or more disk partitions in which Fedora is installed. You may also need to create and/or delete partitions at this time.
-	</para>
-	
-	<para>
-		If you have not yet planned how to set up your partitions, refer to <xref linkend="ch-partitions-x86"/> and <xref linkend="s2-diskpartrecommend-x86"/>. At a bare minimum, you need an appropriately-sized root partition, and usually a swap partition appropriate to the amount of RAM you have on the system. 
-	</para>
-
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Disk_Partitioning_common-para-1.xml"/>
-	<!-- The partitioning tool used by the installation program -->
-	
-	<figure float="0" id="fig-diskpart-ddmain-x86"><title>Partitioning on x86, AMD64, and Intel 64 Systems</title>
-		<mediaobject>
-			<imageobject><imagedata fileref="images/diskpartitioning/ddmain.png" format="PNG"/></imageobject>
-			<textobject><para>
-					The main partitioning screen.
-				</para>
-			</textobject>
-		</mediaobject>
-	</figure>
-	
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Disk_Partitioning_Graphical_x86_ppc-para-1.xml"/>
-	<!-- The partitioning screen offers a graphical representation... -->
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Disk_Partitioning_Graphical_common-para-2.xml"/>
-	<!-- Above the graphical representation of the device... -->
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Disk_Partitioning_Graphical_common-para-1.xml"/>
-	<!-- Anaconda displays several details for each device listed -->
-	
-	<para>
-		The lower pane contains a list of all drives, logical volumes, and RAID devices to be used during installation, as specified earlier in the installation process â€” refer to <xref linkend="Assign_Storage_Devices-x86"/>
-	</para>
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Disk_Partitioning_Graphical_common-para-3.xml"/>
-	<!-- Devices are grouped by type. -->
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Disk_Partitioning_Graphical_common-para-4.xml"/>
-	<!-- Using your mouse, click once to highlight a particular field... -->
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Disk_Partitioning_Graphical_common-variablelist-1.xml"/>
-	<!-- the name of the device, logical volume, or partition -->
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Disk_Partitioning_Graphical_common-para-5.xml"/>
-	<!-- Beneath the lower pane are four buttons: -->
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Disk_Partitioning_Graphical_common-para-6.xml"/>
-	<!-- Select a device or partition by clicking on it -->
-	
-	<variablelist>
-		<varlistentry>
-			<term>Create</term>
-			<listitem>
-				<para>
-					create a new partition, logical volume, or software RAID
-				</para>
-			</listitem>
-		</varlistentry>
-		<varlistentry>
-			<term>Edit</term>
-			<listitem>
-				<para>
-					change an existing new partition, logical volume, or software RAID
-				</para>
-			</listitem>
-		</varlistentry>
-		<varlistentry>
-			<term>Delete</term>
-			<listitem>
-				<para>
-					remove a partition, logical volume, or software RAID
-				</para>
-			</listitem>
-		</varlistentry>
-		<varlistentry>
-			<term>Reset</term>
-			<listitem>
-				<para>
-					undo all changes made in this screen
-				</para>
-			</listitem>
-		</varlistentry>
-	</variablelist>
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Create_Storage-x86.xml"/>
-	<!-- Create Storage -->
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Adding_Partitions-x86.xml"/>
-	<!-- Adding Partitions -->
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Create_Software_RAID-x86.xml"/>
-	<!-- Create Software RAID -->
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Create_LVM-x86.xml"/>
-	<!-- Create LVM Logical Volume -->
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Disk_Partitioning_Scheme-x86.xml"/>
-	<!-- Recommended Partitioning Scheme -->
-	
-	
-	
-</section>
-
diff --git a/en-US/Disk_Partitioning_Advanced_Storage-indexterm1.xml b/en-US/Disk_Partitioning_Advanced_Storage-indexterm1.xml
deleted file mode 100644
index e345a63..0000000
--- a/en-US/Disk_Partitioning_Advanced_Storage-indexterm1.xml
+++ /dev/null
@@ -1,10 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE indexterm PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-<indexterm significance="normal">
-	<primary>iscsi</primary>
-	<secondary>installation</secondary>
-</indexterm>
\ No newline at end of file
diff --git a/en-US/Disk_Partitioning_Advanced_Storage-indexterm2.xml b/en-US/Disk_Partitioning_Advanced_Storage-indexterm2.xml
deleted file mode 100644
index 911f9c8..0000000
--- a/en-US/Disk_Partitioning_Advanced_Storage-indexterm2.xml
+++ /dev/null
@@ -1,10 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE indexterm PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-<indexterm significance="normal">
-	<primary>FCoE</primary>
-	<secondary>installation</secondary>
-</indexterm>
\ No newline at end of file
diff --git a/en-US/Disk_Partitioning_Advanced_Storage-x86.xml b/en-US/Disk_Partitioning_Advanced_Storage-x86.xml
deleted file mode 100644
index e251ead..0000000
--- a/en-US/Disk_Partitioning_Advanced_Storage-x86.xml
+++ /dev/null
@@ -1,70 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-	    
-<section id="s1-advanced-storage-x86">
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Disk_Partitioning_Advanced_Storage_common-title.xml"/>
-	<!-- Title: Advanced Storage Options -->
-		
-	<!-- Begin Index Terms -->
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Disk_Partitioning_Advanced_Storage-indexterm1.xml"/>
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Disk_Partitioning_Advanced_Storage-indexterm2.xml"/>
-	<!-- End Index Terms -->
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Disk_Partitioning_Advanced_Storage_common-para-1.xml"/>
-	<!-- From this screen you can configure an iSCSI (SCSI over TCP/IP) target -->
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Disk_Partitioning_Advanced_Storage_common-figure-1.xml"/>
-	<!-- Advanced Storage Options -->
-	
-	<section id="sn-netconfig_manual-configuration-x86">
-	<xi:include href="Netconfig_common-title-2.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
-	<!-- Manual configuration -->
-		<xi:include href="Netconfig_common-para-7.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
-		<!-- Installations that require certain advanced configurations cannot succeed without network connectivity -->
-		
-		<xi:include href="Netconfig_common-figure-2.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
-		<!-- Manual network configuration -->
-	
-		<xi:include href="Netconfig_common-para-8.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
-		<!-- If your network does not have DHCP enabled, or if you need to override the DHCP settings, -->
-		
-		<xi:include href="Netconfig_common-para-9.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
-		<!-- Click <guilabel>OK</guilabel> to accept these settings and continue. -->
-			  
-	</section>
-	
-	<section id="s1-advanced-storage-iSCSI-x86">
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Disk_Partitioning_Advanced_Storage_common-title-2.xml"/>
-	<!-- Configure iSCSI Parameters -->
-	
-		<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Disk_Partitioning_Advanced_Storage_common-para-2.xml"/>
-		<!-- To configure an ISCSI target invoke the 'Configure ISCSI Parameters' dialog -->
-		
-		<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Disk_Partitioning_Advanced_Storage_common-figure-2.xml"/>
-		<!-- Configure ISCSI Parameters -->
-		
-		<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Disk_Partitioning_Advanced_Storage_common-para-3.xml"/>
-		<!-- Please note that you will be able to reattempt with a different ISCSI target IP -->
-		
-	</section>
-	
-	<section id="s1-advanced-storage-FCoE-x86">
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Disk_Partitioning_Advanced_Storage_common-title-3.xml"/>
-	<!-- Configure FCoE Parameters -->
-	
-		<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Disk_Partitioning_Advanced_Storage_common-para-4.xml"/>
-		<!-- To configure an FCoE SAN... -->
-		
-		<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Disk_Partitioning_Advanced_Storage_common-para-5.xml"/>
-		<!-- On the menu that appears in the next... -->
-		
-		<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Disk_Partitioning_Advanced_Storage_common-figure-3.xml"/>
-		<!-- Configure FCoE Parameters -->
-		
-		<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Disk_Partitioning_Advanced_Storage_common-para-6.xml"/>
-		<!-- DCB (Data Center Bridging) is a set of enhancements to the Ethernet protocols  -->
-		
-	</section>
-
-</section>
diff --git a/en-US/Disk_Partitioning_Advanced_Storage_common-figure-1.xml b/en-US/Disk_Partitioning_Advanced_Storage_common-figure-1.xml
deleted file mode 100644
index 46c1757..0000000
--- a/en-US/Disk_Partitioning_Advanced_Storage_common-figure-1.xml
+++ /dev/null
@@ -1,13 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE figure PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<figure float="0"><title>Advanced Storage Options</title>
-	<mediaobject>
-		<imageobject><imagedata fileref="images/diskpartadvanced/advanced_storage.png" format="PNG"/></imageobject>
-		<textobject><para>
-				Advanced Storage Options.
-			</para>
-		</textobject>
-	</mediaobject>
-</figure>
\ No newline at end of file
diff --git a/en-US/Disk_Partitioning_Advanced_Storage_common-figure-2.xml b/en-US/Disk_Partitioning_Advanced_Storage_common-figure-2.xml
deleted file mode 100644
index 48190d3..0000000
--- a/en-US/Disk_Partitioning_Advanced_Storage_common-figure-2.xml
+++ /dev/null
@@ -1,13 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE figure PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<figure float="0"><title>Configure ISCSI Parameters</title>
-	<mediaobject>
-		<imageobject><imagedata fileref="images/diskpartadvanced/iscsi-config.png" format="PNG"/></imageobject>
-		<textobject><para>
-				Configure ISCSI Parameters.
-			</para>
-		</textobject>
-	</mediaobject>
-</figure>
\ No newline at end of file
diff --git a/en-US/Disk_Partitioning_Advanced_Storage_common-figure-3.xml b/en-US/Disk_Partitioning_Advanced_Storage_common-figure-3.xml
deleted file mode 100644
index b6e4b9b..0000000
--- a/en-US/Disk_Partitioning_Advanced_Storage_common-figure-3.xml
+++ /dev/null
@@ -1,13 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE figure PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<figure float="0"><title>Configure FCoE Parameters</title>
-	<mediaobject>
-		<imageobject><imagedata fileref="images/diskpartadvanced/fcoe-config.png" format="PNG"/></imageobject>
-		<textobject><para>
-				Configure FCoE Parameters
-			</para>
-		</textobject>
-	</mediaobject>
-</figure>
\ No newline at end of file
diff --git a/en-US/Disk_Partitioning_Advanced_Storage_common-para-1.xml b/en-US/Disk_Partitioning_Advanced_Storage_common-para-1.xml
deleted file mode 100644
index e263795..0000000
--- a/en-US/Disk_Partitioning_Advanced_Storage_common-para-1.xml
+++ /dev/null
@@ -1,7 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<para>
-	From this screen you can configure an <firstterm>iSCSI</firstterm> (SCSI over TCP/IP) target or <firstterm>FCoE</firstterm> (Fibre channel over ethernet) <firstterm>SAN</firstterm> (storage area network). Refer to <xref linkend="ISCSI_disks" /> for an introduction to iSCSI.
-</para>
\ No newline at end of file
diff --git a/en-US/Disk_Partitioning_Advanced_Storage_common-para-2.xml b/en-US/Disk_Partitioning_Advanced_Storage_common-para-2.xml
deleted file mode 100644
index d8c41b9..0000000
--- a/en-US/Disk_Partitioning_Advanced_Storage_common-para-2.xml
+++ /dev/null
@@ -1,7 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<para>
-	To configure an ISCSI target invoke the 'Configure ISCSI Parameters' dialog by selecting 'Add ISCSI target' and clicking on the 'Add Drive' button. Fill in the details for the ISCSI target IP and provide a unique ISCSI initiator name to identify this system. If the ISCSI target uses CHAP (Challenge Handshake Authentication Protocol) for authentication, enter the CHAP username and password. If your enviroment uses 2-way CHAP (also called "Mutual CHAP"), also enter the reverse CHAP username and password. Click the 'Add target' button to attempt connection to the ISCSI target using this information.
-</para>
\ No newline at end of file
diff --git a/en-US/Disk_Partitioning_Advanced_Storage_common-para-3.xml b/en-US/Disk_Partitioning_Advanced_Storage_common-para-3.xml
deleted file mode 100644
index eb88154..0000000
--- a/en-US/Disk_Partitioning_Advanced_Storage_common-para-3.xml
+++ /dev/null
@@ -1,10 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<para>
-	Please note that you will be able to reattempt with a different ISCSI target IP should you enter it incorrectly, but in order to change the ISCSI initiator name you will need to restart the installation.
-</para>
\ No newline at end of file
diff --git a/en-US/Disk_Partitioning_Advanced_Storage_common-para-4.xml b/en-US/Disk_Partitioning_Advanced_Storage_common-para-4.xml
deleted file mode 100644
index 5ee5b56..0000000
--- a/en-US/Disk_Partitioning_Advanced_Storage_common-para-4.xml
+++ /dev/null
@@ -1,7 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<para>
-	To configure an FCoE SAN, select <guilabel>Add FCoE SAN</guilabel> and click <guibutton>Add Drive</guibutton>. 
-</para>
\ No newline at end of file
diff --git a/en-US/Disk_Partitioning_Advanced_Storage_common-para-5.xml b/en-US/Disk_Partitioning_Advanced_Storage_common-para-5.xml
deleted file mode 100644
index 0fb9d22..0000000
--- a/en-US/Disk_Partitioning_Advanced_Storage_common-para-5.xml
+++ /dev/null
@@ -1,7 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<para>
-	On the menu that appears in the next dialog box, select the network interface that is connected to your FCoE switch and click <guibutton>Add FCoE Disk(s)</guibutton>.
-</para>
\ No newline at end of file
diff --git a/en-US/Disk_Partitioning_Advanced_Storage_common-para-6.xml b/en-US/Disk_Partitioning_Advanced_Storage_common-para-6.xml
deleted file mode 100644
index 1b627b4..0000000
--- a/en-US/Disk_Partitioning_Advanced_Storage_common-para-6.xml
+++ /dev/null
@@ -1,7 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<para>
-	<firstterm>Data Center Bridging</firstterm> (DCB) is a set of enhancements to the Ethernet protocols designed to increase the efficiency of Ethernet connections in storage networks and clusters. Enable or disable the installer's awareness of DCB with the checkbox in this dialog. 
-</para>
diff --git a/en-US/Disk_Partitioning_Advanced_Storage_common-title-2.xml b/en-US/Disk_Partitioning_Advanced_Storage_common-title-2.xml
deleted file mode 100644
index e13bd41..0000000
--- a/en-US/Disk_Partitioning_Advanced_Storage_common-title-2.xml
+++ /dev/null
@@ -1,7 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE title PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<title>
-	Configure iSCSI Parameters
-</title>
\ No newline at end of file
diff --git a/en-US/Disk_Partitioning_Advanced_Storage_common-title-3.xml b/en-US/Disk_Partitioning_Advanced_Storage_common-title-3.xml
deleted file mode 100644
index 8bcbba9..0000000
--- a/en-US/Disk_Partitioning_Advanced_Storage_common-title-3.xml
+++ /dev/null
@@ -1,7 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE title PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<title>
-	Configure FCoE Parameters
-</title>
\ No newline at end of file
diff --git a/en-US/Disk_Partitioning_Advanced_Storage_common-title.xml b/en-US/Disk_Partitioning_Advanced_Storage_common-title.xml
deleted file mode 100644
index 3eaa532..0000000
--- a/en-US/Disk_Partitioning_Advanced_Storage_common-title.xml
+++ /dev/null
@@ -1,10 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE title PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<title>
-	Advanced Storage Options
-</title>
\ No newline at end of file
diff --git a/en-US/Disk_Partitioning_Graphical_common-para-1.xml b/en-US/Disk_Partitioning_Graphical_common-para-1.xml
deleted file mode 100644
index 3b6fe6a..0000000
--- a/en-US/Disk_Partitioning_Graphical_common-para-1.xml
+++ /dev/null
@@ -1,10 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-	  
-	  
-	  
-]>
-
-<para>
-	Using your mouse, click once to highlight a particular field in the graphical display. Double-click to edit an existing partition or to create a partition out of existing free space.
-</para>
\ No newline at end of file
diff --git a/en-US/Disk_Partitioning_Graphical_common-para-2.xml b/en-US/Disk_Partitioning_Graphical_common-para-2.xml
deleted file mode 100644
index 1e8d99f..0000000
--- a/en-US/Disk_Partitioning_Graphical_common-para-2.xml
+++ /dev/null
@@ -1,11 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-	  
-	  
-	  
-]>
-
-<para>
-	Above the graphical representation of the device, you can review the name of the drive (such as <literal>/dev/sda</literal> or <literal>LogVol00</literal>), its size (in MB), and its model as detected by the installation program.
-</para>
-
diff --git a/en-US/Disk_Partitioning_Graphical_common-para-3.xml b/en-US/Disk_Partitioning_Graphical_common-para-3.xml
deleted file mode 100644
index db0a17c..0000000
--- a/en-US/Disk_Partitioning_Graphical_common-para-3.xml
+++ /dev/null
@@ -1,8 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<para>
-	Devices are grouped by type. Click on the small triangles to the left of each device type to view or hide devices of that type.
-</para>
-
diff --git a/en-US/Disk_Partitioning_Graphical_common-para-4.xml b/en-US/Disk_Partitioning_Graphical_common-para-4.xml
deleted file mode 100644
index 0d605b7..0000000
--- a/en-US/Disk_Partitioning_Graphical_common-para-4.xml
+++ /dev/null
@@ -1,8 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<para>
-	<application>Anaconda</application> displays several details for each device listed: 
-</para>
-
diff --git a/en-US/Disk_Partitioning_Graphical_common-para-5.xml b/en-US/Disk_Partitioning_Graphical_common-para-5.xml
deleted file mode 100644
index b1f3bf0..0000000
--- a/en-US/Disk_Partitioning_Graphical_common-para-5.xml
+++ /dev/null
@@ -1,8 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<para>
-	Beneath the lower pane are four buttons: <guibutton>Create</guibutton>, <guibutton>Edit</guibutton>, <guibutton>Delete</guibutton>, and <guibutton>Reset</guibutton>.
-</para>
-
diff --git a/en-US/Disk_Partitioning_Graphical_common-para-6.xml b/en-US/Disk_Partitioning_Graphical_common-para-6.xml
deleted file mode 100644
index a5438ce..0000000
--- a/en-US/Disk_Partitioning_Graphical_common-para-6.xml
+++ /dev/null
@@ -1,8 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<para>
-	Select a device or partition by clicking on it in either the graphical representation in the upper pane of in the list in the lower pane, then click one of the four buttons to carry out the following actions:
-</para>
-
diff --git a/en-US/Disk_Partitioning_Graphical_common-variablelist-1.xml b/en-US/Disk_Partitioning_Graphical_common-variablelist-1.xml
deleted file mode 100644
index 82f3dd4..0000000
--- a/en-US/Disk_Partitioning_Graphical_common-variablelist-1.xml
+++ /dev/null
@@ -1,47 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE variablelist PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<variablelist>
-	<varlistentry>
-		<term>Device</term>
-		<listitem>
-			<para>
-				the name of the device, logical volume, or partition
-			</para>
-		</listitem>
-	</varlistentry>
-	<varlistentry>
-		<term>Size (MB)</term>
-		<listitem>
-			<para>
-				the size of the device, logical volume, or partition (in MB)
-			</para>
-		</listitem>
-	</varlistentry>
-	<varlistentry>
-		<term>Mount Point/RAID/Volume</term>
-		<listitem>
-			<para>
-				the <firstterm>mount point</firstterm> (location within a file system) on which a partition is to be mounted, or the name of the RAID or logical volume group of which it is a part
-			</para>
-		</listitem>
-	</varlistentry>
-	<varlistentry>
-		<term>Type</term>
-		<listitem>
-			<para>
-				the type of partition. If the partition is a standard partition, this field displays the type of file system on the partition (for example, ext4). Otherwise, it indicates that the partition is a <literal>physical volume (LVM)</literal>, or part of a <literal>software RAID</literal>
-			</para>
-		</listitem>
-	</varlistentry>
-	<varlistentry>
-		<term>Format</term>
-		<listitem>
-			<para>
-				A check mark in this column indicates that the partition will be formatted during installation.
-			</para>
-		</listitem>
-	</varlistentry>
-</variablelist>
-
diff --git a/en-US/Disk_Partitioning_Graphical_x86_ppc-para-1.xml b/en-US/Disk_Partitioning_Graphical_x86_ppc-para-1.xml
deleted file mode 100644
index dfa3671..0000000
--- a/en-US/Disk_Partitioning_Graphical_x86_ppc-para-1.xml
+++ /dev/null
@@ -1,8 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<para>
-	The screen contains two panes. The top pane contains a graphical representation of the hard drive, logical volume, or RAID device selected in the lower pane.
-</para>
-
diff --git a/en-US/Disk_Partitioning_Scheme-x86.xml b/en-US/Disk_Partitioning_Scheme-x86.xml
deleted file mode 100644
index 093e389..0000000
--- a/en-US/Disk_Partitioning_Scheme-x86.xml
+++ /dev/null
@@ -1,19 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<section id="s2-diskpartrecommend-x86">
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Disk_Partitioning_Scheme_common-title.xml"/>
-	<!-- Recommended Partitioning Scheme -->
-	
-	<!-- Begin Index Terms -->
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Disk_Partitioning_Scheme_common-indexterm-1.xml"/>
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Disk_Partitioning_Scheme_common-indexterm-2.xml"/>
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Disk_Partitioning_Scheme_common-indexterm-3.xml"/>
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Disk_Partitioning_Scheme_common-indexterm-4.xml"/>
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Disk_Partitioning_Scheme_common-indexterm-5.xml"/>
-	<!-- End Index Terms -->
-	
-	<!-- <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Disk_Partitioning_IA64_Partitions.xml"/> -->
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Disk_Partitioning_X86_Partitions.xml"/>
-</section>
diff --git a/en-US/Disk_Partitioning_Scheme_common-indexterm-1.xml b/en-US/Disk_Partitioning_Scheme_common-indexterm-1.xml
deleted file mode 100644
index 8d5cb5c..0000000
--- a/en-US/Disk_Partitioning_Scheme_common-indexterm-1.xml
+++ /dev/null
@@ -1,11 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE indexterm PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<indexterm significance="normal">
-		<primary>swap partition</primary>
-		<secondary>recommended partitioning</secondary>
-	</indexterm>
\ No newline at end of file
diff --git a/en-US/Disk_Partitioning_Scheme_common-indexterm-2.xml b/en-US/Disk_Partitioning_Scheme_common-indexterm-2.xml
deleted file mode 100644
index 091eec0..0000000
--- a/en-US/Disk_Partitioning_Scheme_common-indexterm-2.xml
+++ /dev/null
@@ -1,12 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE indexterm PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-
-<indexterm significance="normal">
-		<primary>partitioning</primary>
-		<secondary>recommended</secondary>
-	</indexterm>
\ No newline at end of file
diff --git a/en-US/Disk_Partitioning_Scheme_common-indexterm-3.xml b/en-US/Disk_Partitioning_Scheme_common-indexterm-3.xml
deleted file mode 100644
index ed7c34f..0000000
--- a/en-US/Disk_Partitioning_Scheme_common-indexterm-3.xml
+++ /dev/null
@@ -1,11 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE indexterm PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<indexterm significance="normal">
-		<primary><filename>/boot/</filename> partition</primary>
-		<secondary>recommended partitioning</secondary>
-	</indexterm>
\ No newline at end of file
diff --git a/en-US/Disk_Partitioning_Scheme_common-indexterm-4.xml b/en-US/Disk_Partitioning_Scheme_common-indexterm-4.xml
deleted file mode 100644
index f43c08f..0000000
--- a/en-US/Disk_Partitioning_Scheme_common-indexterm-4.xml
+++ /dev/null
@@ -1,11 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE indexterm PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<indexterm significance="normal">
-		<primary><filename>/var/</filename> partition</primary>
-		<secondary>recommended partitioning</secondary>
-	</indexterm>
\ No newline at end of file
diff --git a/en-US/Disk_Partitioning_Scheme_common-indexterm-5.xml b/en-US/Disk_Partitioning_Scheme_common-indexterm-5.xml
deleted file mode 100644
index 2278631..0000000
--- a/en-US/Disk_Partitioning_Scheme_common-indexterm-5.xml
+++ /dev/null
@@ -1,8 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE indexterm PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<indexterm significance="normal">
-		<primary>root <filename>/</filename> partition</primary>
-		<secondary>recommended partitioning</secondary>
-	</indexterm>
\ No newline at end of file
diff --git a/en-US/Disk_Partitioning_Scheme_common-listitem-1.xml b/en-US/Disk_Partitioning_Scheme_common-listitem-1.xml
deleted file mode 100644
index e110585..0000000
--- a/en-US/Disk_Partitioning_Scheme_common-listitem-1.xml
+++ /dev/null
@@ -1,25 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE listitem PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<listitem>
-	<formalpara>
-		<title>A <filename>root</filename> partition (3.0 GB - 5.0 GB)</title> <para>
-		  This is where "<filename>/</filename>" (the root directory) is located. In this setup, all files (except those stored in
-		<filename>/boot</filename>) are on the root partition.
-		</para>
-	</formalpara>
-
-	<para>
-		A 3.0 GB partition allows you to install a minimal installation, while a 5.0 GB root partition lets you perform a full installation, choosing all package groups.
-	</para>
-	
-	<important>
-	  <title>Root and <filename
-	  class="directory">/root</filename></title>
-	  <para>
-	    The <filename class="partition">/</filename> (or root) partition is the top of the directory structure. The <filename class="directory">/root</filename> directory (sometimes pronounced "slash-root") directory is the home directory of the user account for system administration.
-	  </para>
-	</important>
-	
-</listitem>
diff --git a/en-US/Disk_Partitioning_Scheme_common-title.xml b/en-US/Disk_Partitioning_Scheme_common-title.xml
deleted file mode 100644
index ad87d64..0000000
--- a/en-US/Disk_Partitioning_Scheme_common-title.xml
+++ /dev/null
@@ -1,8 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE title PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<title>Recommended Partitioning Scheme</title>
\ No newline at end of file
diff --git a/en-US/Disk_Partitioning_Scheme_x86_s390-para-1.xml b/en-US/Disk_Partitioning_Scheme_x86_s390-para-1.xml
deleted file mode 100644
index 865d75e..0000000
--- a/en-US/Disk_Partitioning_Scheme_x86_s390-para-1.xml
+++ /dev/null
@@ -1,10 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<formalpara>
-	<title>A <filename>/boot/</filename> partition (250 MB)</title>
-	<para>
-	  The partition mounted on <filename>/boot/</filename> contains the operating system kernel (which allows your system to boot Fedora), along with files used during the bootstrap process. For most users, a 250 MB boot partition is sufficient. 
-	</para>
-</formalpara>
diff --git a/en-US/Disk_Partitioning_Setup-x86.xml b/en-US/Disk_Partitioning_Setup-x86.xml
deleted file mode 100644
index 1bcde44..0000000
--- a/en-US/Disk_Partitioning_Setup-x86.xml
+++ /dev/null
@@ -1,72 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<section id="s1-diskpartsetup-x86">
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Disk_Partitioning_Setup_common-title.xml"/>
-	<!-- Disk Partitioning Setup -->
-	
-	<!-- Index terms -->
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Disk_Partitioning_Setup_common-indexterm-1.xml"/>
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Disk_Partitioning_Setup_common-indexterm-2.xml"/>
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Automatic_Partitioning_common-indexterm-1.xml"/>
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Automatic_Partitioning_common-indexterm-2.xml"/>
-	<!-- End Index terms -->
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Automatic_Partitioning_common-caution-1.xml"/>
-	<!-- It is always a good idea to back up any data ... -->
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Automatic_Partitioning_common-note-1.xml"/>
-	<!-- Installation in text mode... -->
-	
-	<important><title>Important â€” Booting from RAIDs</title>
-		
-		<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Automatic_Partitioning_x86_ppc-tip-para-1.xml"/>
-		<!-- If you have a RAID card, be aware that some BIOSes... -->
-		
-		<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Automatic_Partitioning_x86_ppc-tip-para-2.xml"/>
-		<!-- A /boot/ partition is also necessary for ... -->
-		
-		<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Automatic_Partitioning_x86_ppc-tip-para-3.xml"/>
-		<!-- If you have chosen to automatically partition your system ... -->
-	</important>
-	
-	<para>
-		Partitioning allows you to divide your hard drive into isolated sections, where each section behaves as its own hard drive. Partitioning is particularly useful if you run multiple operating systems. If you are not sure how you want your system to be partitioned, read <xref linkend="ch-partitions-x86"/> for more information.
-	</para>
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Disk_Partitioning_Setup_common-figure-1.xml"/>
-	<!-- Choose automatic partitioning or manual partitioning... -->
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Disk_Partitioning_Setup_common-para-1.xml"/>
-	<!-- On this screen, you can choose between three different automatic partitioning...  -->
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Disk_Partitioning_Setup_common-para-2.xml"/>
-	<!-- The first three options allow you to perform an installation -->
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Automatic_Partitioning_common-para-1.xml"/>
-	<!-- Your options are: -->
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Automatic_Partitioning_x86-variablelist-1.xml"/>
-	<!-- Remove all partitions on selected drives and create default layout
-	     Remove linux partitions on selected drives and create default layout
-	     Caution
-	     Use free space on selected drives and create default layout -->
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Automatic_Partitioning_common-para-2.xml"/>
-	<!-- Choose your preferred partitioning method... -->
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Automatic_Partitioning_common-para-5.xml"/>
-	<!-- Select Encrypt system to encrypt all partitions...  -->
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Automatic_Partitioning_common-para-3.xml"/>
-	<!-- To review and make any necessary changes to the partitions... -->
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Automatic_Partitioning_common-para-4.xml"/>
-	<!-- Click Next once you have made your selection... -->
-	
-	
-</section>
-	
-
diff --git a/en-US/Disk_Partitioning_Setup_common-figure-1.xml b/en-US/Disk_Partitioning_Setup_common-figure-1.xml
deleted file mode 100644
index 8e8404c..0000000
--- a/en-US/Disk_Partitioning_Setup_common-figure-1.xml
+++ /dev/null
@@ -1,13 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE figure PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<figure float="0"><title>Disk Partitioning Setup</title>
-	<mediaobject>
-		<imageobject><imagedata fileref="images/diskpartsetup/disk-setup.png" format="PNG"/></imageobject>
-		<textobject><para>
-				Choose automatic partitioning or manual partitioning.
-			</para>
-		</textobject>
-	</mediaobject>
-</figure>
\ No newline at end of file
diff --git a/en-US/Disk_Partitioning_Setup_common-indexterm-1.xml b/en-US/Disk_Partitioning_Setup_common-indexterm-1.xml
deleted file mode 100644
index d2adf6b..0000000
--- a/en-US/Disk_Partitioning_Setup_common-indexterm-1.xml
+++ /dev/null
@@ -1,10 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE indexterm PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<indexterm significance="normal">
-	<primary>disk partitioning</primary>
-</indexterm>
\ No newline at end of file
diff --git a/en-US/Disk_Partitioning_Setup_common-indexterm-2.xml b/en-US/Disk_Partitioning_Setup_common-indexterm-2.xml
deleted file mode 100644
index f32bdae..0000000
--- a/en-US/Disk_Partitioning_Setup_common-indexterm-2.xml
+++ /dev/null
@@ -1,9 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE indexterm PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-<indexterm significance="normal">
-	<primary>automatic partitioning</primary>
-</indexterm>
\ No newline at end of file
diff --git a/en-US/Disk_Partitioning_Setup_common-indexterm-6.xml b/en-US/Disk_Partitioning_Setup_common-indexterm-6.xml
deleted file mode 100644
index 68314c5..0000000
--- a/en-US/Disk_Partitioning_Setup_common-indexterm-6.xml
+++ /dev/null
@@ -1,8 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE indexterm PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<indexterm significance="normal">
-	<primary>RAID</primary>
-	<secondary>hardware</secondary>
-      </indexterm>
\ No newline at end of file
diff --git a/en-US/Disk_Partitioning_Setup_common-indexterm-7.xml b/en-US/Disk_Partitioning_Setup_common-indexterm-7.xml
deleted file mode 100644
index 7ac1985..0000000
--- a/en-US/Disk_Partitioning_Setup_common-indexterm-7.xml
+++ /dev/null
@@ -1,8 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE indexterm PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<indexterm significance="normal">
-	<primary>array</primary>
-	<see>RAID</see>
-      </indexterm>
\ No newline at end of file
diff --git a/en-US/Disk_Partitioning_Setup_common-indexterm-8.xml b/en-US/Disk_Partitioning_Setup_common-indexterm-8.xml
deleted file mode 100644
index 612e659..0000000
--- a/en-US/Disk_Partitioning_Setup_common-indexterm-8.xml
+++ /dev/null
@@ -1,8 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE indexterm PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<indexterm significance="normal">
-	<primary>RAID</primary>
-	<secondary>software</secondary>
-      </indexterm>
\ No newline at end of file
diff --git a/en-US/Disk_Partitioning_Setup_common-para-1.xml b/en-US/Disk_Partitioning_Setup_common-para-1.xml
deleted file mode 100644
index dfd253f..0000000
--- a/en-US/Disk_Partitioning_Setup_common-para-1.xml
+++ /dev/null
@@ -1,8 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<para>
-	On this screen you can choose to create the default partition layout in one of four different ways, or choose to partition storage devices manually to create a custom layout.
-</para>
-
diff --git a/en-US/Disk_Partitioning_Setup_common-para-2.xml b/en-US/Disk_Partitioning_Setup_common-para-2.xml
deleted file mode 100644
index 3798e1c..0000000
--- a/en-US/Disk_Partitioning_Setup_common-para-2.xml
+++ /dev/null
@@ -1,8 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<para>
-	The first four options allow you to perform an automated installation without having to partition your storage devices yourself. If you do not feel comfortable with partitioning your system, choose one of these options and let the installation program partition the storage devices for you. Depending on the option that you choose, you can still control what data (if any) is removed from the system.
-</para>
-
diff --git a/en-US/Disk_Partitioning_Setup_common-title.xml b/en-US/Disk_Partitioning_Setup_common-title.xml
deleted file mode 100644
index 0042f2e..0000000
--- a/en-US/Disk_Partitioning_Setup_common-title.xml
+++ /dev/null
@@ -1,8 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE title PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<title>Disk Partitioning Setup</title>
\ No newline at end of file
diff --git a/en-US/Disk_Partitioning_X86_Partitions.xml b/en-US/Disk_Partitioning_X86_Partitions.xml
deleted file mode 100644
index eb34f17..0000000
--- a/en-US/Disk_Partitioning_X86_Partitions.xml
+++ /dev/null
@@ -1,146 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-<section><title>x86, AMD64, and <trademark class="registered">Intel</trademark> 64 systems</title>
-<para>
-	<emphasis>Unless you have a reason for doing otherwise, we recommend that you create the following partitions for x86, AMD64, and <trademark class="registered">Intel</trademark> 64 systems</emphasis>:
-</para>
-
-    <itemizedlist>
-      <listitem>
-        <para>
-          A <systemitem class="filesystem">swap</systemitem> partition
-        </para>
-      </listitem>
-      <listitem>
-        <para>
-          A <filename class="partition">/boot</filename> partition
-        </para>
-      </listitem>
-      <listitem>
-        <para>
-          A <filename class="partition">/</filename> partition
-        </para>
-      </listitem>
-    </itemizedlist>
-
-<itemizedlist>
-<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Swap_Partrecommend.xml"/>
-<!-- from
-     A swap partition (at least 256 MB)
-     to
-     For systems with really large amounts of RAM
-     -->
-     
-	<listitem>
-		
-		<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Disk_Partitioning_Scheme_x86_s390-para-1.xml"/>
-		<!-- A /boot/ partition (250 MB) - the partition mounted... -->
-		<xi:include href="ext4-and-btrfs.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
-		<note><title>Note</title>
-			<para>
-				If your hard drive is more than 1024 cylinders (and your system was manufactured more than two years ago), you may need to create a <filename>/boot/</filename> partition if you want the <filename>/</filename> (root)
-				partition to use all of the remaining space on your hard drive.
-			</para>
-		</note>
-		<note><title>Note</title>
-			<para>
-				If you have a RAID card, be aware that some BIOSes do not support booting from the RAID card. In cases such as these, the <filename>/boot/</filename> partition must be created on a partition outside of the RAID array, such as on a
-				separate hard drive.
-			</para>
-		</note>
-	</listitem>
-
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Disk_Partitioning_Scheme_common-listitem-1.xml"/>
-		<!-- A root partition (500 MB - 5.0 GB) - this is where / (the root directory) is
-		     and
-		A 500MB partition allows you to install... -->
-</itemizedlist>
-
-    <para>
-      Many systems have more partitions than the minimum listed above.
-      Choose partitions based on your particular system needs. For
-      example, consider creating a separate <filename
-	class="partition">/home</filename> partition on systems that
-      store user data.  Refer to <xref
-      linkend="sn-partitioning-advice"/> for more information.
-    </para>
-
-    <para>
-      If you create many partitions instead of one large <filename
-	class="partition">/</filename> partition, upgrades become
-      easier. Refer to the description the Edit
-	option in <xref linkend="s1-diskpartitioning-x86"/> for more information.
-    </para>
-    
-    
-    <para>
-	The following table summarizes minimum partition sizes for
-	the partitions containing the listed directories.  You
-	<emphasis>do not</emphasis> have to make a separate partition
-	for each of these directories.  For instance, if the partition
-	containing <filename class="directory">/foo</filename> must be
-	at least 500 MB, and you do not make a separate <filename
-	  class="partition">/foo</filename> partition, then the
-	<filename class="partition">/</filename> (root) partition must
-	be at least 500 MB.
-    </para>
-
-       <table id="tb-Minumum_partition_sizes" frame='all'><title>Minimum partition sizes</title>
-	<tgroup cols='2' align='left' colsep='1' rowsep='1'>
-	  <thead>
-	      <row>
-		<entry>Directory</entry>
-		<entry>Minimum size</entry>
-	      </row>
-	  </thead>
-	  <tbody>
-	      <row>
-		<entry><filename class="directory">/</filename></entry>
-		<entry>250 MB</entry>
-	      </row>
-	      <row>
-		<entry><filename class="directory">/usr</filename></entry>
-		<entry>250 MB, but avoid placing this on a separate partition</entry>
-	      </row>
-	      <row>
-		<entry><filename class="directory">/tmp</filename></entry>
-		<entry>50 MB</entry>
-	      </row>
-	      <row>
-		<entry><filename class="directory">/var</filename></entry>
-		<entry>384 MB</entry>
-	      </row>
-	      <row>
-		<entry><filename class="directory">/home</filename></entry>
-		<entry>100 MB</entry>
-	      </row>
-	      <row>
-		<entry><filename class="directory">/boot</filename></entry>
-		<entry>250 MB</entry>
-	      </row>
-	    </tbody>
-	  </tgroup>
-      </table>
-    
-    
-    <note>
-      <title>Leave Excess Capacity Unallocated</title>
-      <para>
-        Only assign storage capacity to those partitions you require
-	immediately. You may allocate free space at any time, to meet
-	needs as they occur. To learn about a more flexible method for
-	storage management, refer to <xref
-	  linkend="sn-partitioning-lvm"/>.
-      </para>
-    </note>
-
-    <para>
-      If you are not sure how best to configure the partitions for your
-      computer, accept the default partition layout.
-    </para>
-
-<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Advice_on_Partitions.xml"/>
-<!-- Optimal partition setup depends on the usage for the Linux system -->
-
-</section>
\ No newline at end of file
diff --git a/en-US/Disk_Partitioning_common-indexterm-1.xml b/en-US/Disk_Partitioning_common-indexterm-1.xml
deleted file mode 100644
index c6ff6ab..0000000
--- a/en-US/Disk_Partitioning_common-indexterm-1.xml
+++ /dev/null
@@ -1,11 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE indexterm PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-	  
-	  
-	  
-]>
-
-
-<indexterm significance="normal">
-	<primary>partitioning</primary>
-</indexterm>
\ No newline at end of file
diff --git a/en-US/Disk_Partitioning_common-indexterm-2.xml b/en-US/Disk_Partitioning_common-indexterm-2.xml
deleted file mode 100644
index cbfae69..0000000
--- a/en-US/Disk_Partitioning_common-indexterm-2.xml
+++ /dev/null
@@ -1,8 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE indexterm PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<indexterm significance="normal">
-	<primary><application>Partitioning</application>
-	</primary>
-</indexterm>
\ No newline at end of file
diff --git a/en-US/Disk_Partitioning_common-indexterm-3.xml b/en-US/Disk_Partitioning_common-indexterm-3.xml
deleted file mode 100644
index f410176..0000000
--- a/en-US/Disk_Partitioning_common-indexterm-3.xml
+++ /dev/null
@@ -1,11 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE indexterm PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-	  
-	  
-	  
-]>
-
-<indexterm significance="normal">
-	<primary>installation</primary>
-	<secondary>partitioning</secondary>
-</indexterm>
\ No newline at end of file
diff --git a/en-US/Disk_Partitioning_common-para-1.xml b/en-US/Disk_Partitioning_common-para-1.xml
deleted file mode 100644
index 071bfa8..0000000
--- a/en-US/Disk_Partitioning_common-para-1.xml
+++ /dev/null
@@ -1,7 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<para>
-	 With the exception of certain esoteric situations, <application>anaconda</application> can handle the partitioning requirements for a typical installation.
-</para>
\ No newline at end of file
diff --git a/en-US/Disk_Partitioning_common-title-1.xml b/en-US/Disk_Partitioning_common-title-1.xml
deleted file mode 100644
index d105e01..0000000
--- a/en-US/Disk_Partitioning_common-title-1.xml
+++ /dev/null
@@ -1,8 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE title PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<title>
-	Creating a Custom Layout or Modifying the Default Layout
-</title>
-
diff --git a/en-US/Disk_Partitioning_x86_ppc-para-1.xml b/en-US/Disk_Partitioning_x86_ppc-para-1.xml
deleted file mode 100644
index d71d759..0000000
--- a/en-US/Disk_Partitioning_x86_ppc-para-1.xml
+++ /dev/null
@@ -1,7 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<para>
-	If you chose one of the automatic partitioning options and selected <guilabel>Review</guilabel>, you can either accept the current partition settings (click <guibutton>Next</guibutton>), or modify the setup manually in the partitioning screen.
-</para>
\ No newline at end of file
diff --git a/en-US/Encrypt-x86.xml b/en-US/Encrypt-x86.xml
deleted file mode 100644
index f69e010..0000000
--- a/en-US/Encrypt-x86.xml
+++ /dev/null
@@ -1,19 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<section id="encrypt-x86">
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Encrypt_common-title-1.xml"/>
-	<!-- Encrypt Partitions -->
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Encrypt_common-para-1.xml"/>
-	<!-- Encrypt Partitions -->
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Encrypt_common-figure-1.xml"/>
-	<!-- Enter passphrase for encrypted partition -->
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Encrypt_common-para-2.xml"/>
-	<!-- Choose a phassphrase -->
-	
-</section>
-
diff --git a/en-US/Encrypt_common-figure-1.xml b/en-US/Encrypt_common-figure-1.xml
deleted file mode 100644
index 5c3e3ec..0000000
--- a/en-US/Encrypt_common-figure-1.xml
+++ /dev/null
@@ -1,19 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE figure PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<figure> 
-	<title>
-		Enter passphrase for encrypted partition
-	</title>
-	<mediaobject>
-		<imageobject>
-			<imagedata fileref="images/encrypt/passphrase.png" format="PNG"/>
-		</imageobject>
-		<textobject>
-			<para>
-				The dialog contains text boxes to enter a passphrase and to confirm it.
-			</para>
-		</textobject>
-	</mediaobject>
-</figure>
diff --git a/en-US/Encrypt_common-para-1.xml b/en-US/Encrypt_common-para-1.xml
deleted file mode 100644
index f407c75..0000000
--- a/en-US/Encrypt_common-para-1.xml
+++ /dev/null
@@ -1,7 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<para>
-	If you selected the <guilabel>Encrypt System</guilabel> option, the installater prompts you for a passphrase with which to encrypt the partitions on the system.
-</para>
diff --git a/en-US/Encrypt_common-para-2.xml b/en-US/Encrypt_common-para-2.xml
deleted file mode 100644
index 116b7ba..0000000
--- a/en-US/Encrypt_common-para-2.xml
+++ /dev/null
@@ -1,7 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<para>
-	Choose a passphrase and type it into each of the two fields in the dialog box. You must provide this passphrase every time that the system boots.
-</para>
diff --git a/en-US/Encrypt_common-title-1.xml b/en-US/Encrypt_common-title-1.xml
deleted file mode 100644
index 2782f83..0000000
--- a/en-US/Encrypt_common-title-1.xml
+++ /dev/null
@@ -1,7 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<title>
-	Encrypt Partitions
-</title>
diff --git a/en-US/Graphical_Installation-x86.xml b/en-US/Graphical_Installation-x86.xml
deleted file mode 100644
index f5ed8ec..0000000
--- a/en-US/Graphical_Installation-x86.xml
+++ /dev/null
@@ -1,310 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-	  
-<chapter id="ch-guimode-x86"><title>Installing on <trademark class="registered">Intel</trademark> and AMD Systems</title>
-	<indexterm significance="normal">
-		<primary>installation</primary>
-		<secondary>GUI</secondary>
-		<tertiary>CD-ROM</tertiary>
-	</indexterm>
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Graphical_Installation_x86_ppc-para-1.xml"/>
-	<!-- This chapter explains how to perform a... -->
-	
- 	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Graphical_Installation_common-list-1.xml"/> 
-	<!-- Contains: Becoming familiar with the installation program's user interface, etc. -->
-	
-	<xi:include href="Graphical_and_Text_Interfaces.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
-	<!-- Graphical Interface Usage - Installing in text mode does not prevent you from using a graphical interface. -->
-	
-	<section id="s1-guimode-interface-x86">
-		<title>The Graphical Installation Program User Interface</title>
-		<indexterm significance="normal">
-			<primary>installation</primary>
-			<secondary>program</secondary>
-			<tertiary>graphical user interface</tertiary>
-		</indexterm>
-		<indexterm significance="normal">
-			<primary>user interface, graphical</primary>
-			<secondary>installation program</secondary>
-		</indexterm>
-		
-		<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Graphical_Installation_common-para-1.xml"/>
-		<!-- If you have used a graphical user interface (GUI) before... -->
-		
- 		<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Graphical_Installation_common-para-2.xml"/> 
-		<!-- You can also navigate through the installation using the keyboard... -->
-
-
-		<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Graphical_Installation_User_Interface_x86_ppc-note-Fedora.xml"/>
-		<!-- If you are using an x86, AMD64, or Intel 64 system, and you do not... -->
-
-<!-- 		<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="IA64_starting-text-mode.xml"/> -->
-		<!-- If you are using an Itanium system, and you do not wish to use the GUI installation program... -->
-
-		<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Graphical_Installation_screenshots.xml"/>
-		<!-- Anaconda allows you to take screenshots during the installation process. -->
-
-		<section id="sn-guimode-virtual-consoles-x86">
-			<title>A Note about Virtual Consoles</title>
-			
-			<indexterm>
-				<primary>consoles, virtual</primary>
-			</indexterm>
-			
-			<indexterm>
-				<primary>virtual consoles</primary>
-			</indexterm>
-			
-			<indexterm>
-				<primary>installation</primary>
-				<secondary>program</secondary>
-				<tertiary>virtual consoles</tertiary>
-			</indexterm>
-			
-			<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Graphical_Installation_x86_ppc-para-3.xml"/> 
-			<!-- The Fedora installation program offers more than the dialog boxes -->
-			
-			<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Graphical_Installation_x86_ppc-para-4.xml"/>
-			<!-- A virtual console is a shell prompt in a non-graphical environment, -->
-			
-			<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Graphical_Installation_x86-para-5.xml"/>
-			<!-- These virtual consoles can be helpful if you encounter a problem -->
-			
-			<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Graphical_Installation_x86_ppc-para-6.xml"/>
-			<!-- Generally, there is no reason to leave the default console -->
-			
-			<table id="tb-guimode-console-x86">
-				<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Graphical_Installation_x86_ppc-table-1-title.xml"/> 
-				
-				<tgroup cols="3">
-	<colspec colnum="1" colname="console"></colspec>
-		
-	<colspec colnum="2" colname="keystroke"></colspec>
-		
-	<colspec colnum="3" colname="contents"></colspec>
-	<thead><row>
-			<entry>
-				console
-			</entry>
-				
-			<entry>
-				keystrokes
-			</entry>
-				
-			<entry>
-				contents
-			</entry>
-		</row>
-	</thead>
-	<tbody>
-		<row>
-			<entry>
-				1
-			</entry>
-				
-			<entry>
-				<keycombo><keycap>ctrl</keycap><keycap>alt</keycap><keycap>f1</keycap>
-				</keycombo>
-			</entry>
-				
-			<entry>
-				installation dialog
-			</entry>
-		</row>
-			
-		<row>
-			<entry>
-				2
-			</entry>
-				
-			<entry>
-				<keycombo><keycap>ctrl</keycap><keycap>alt</keycap><keycap>f2</keycap>
-				</keycombo>
-			</entry>
-				
-			<entry>
-				shell prompt
-			</entry>
-		</row>
-			
-		<row>
-			<entry>
-				3
-			</entry>
-				
-			<entry>
-				<keycombo><keycap>ctrl</keycap><keycap>alt</keycap><keycap>f3</keycap>
-				</keycombo>
-			</entry>
-				
-			<entry>
-				install log (messages from installation program)
-			</entry>
-		</row>
-			
-		<row>
-			<entry>
-				4
-			</entry>
-				
-			<entry>
-				<keycombo><keycap>ctrl</keycap><keycap>alt</keycap><keycap>f4</keycap>
-				</keycombo>
-			</entry>
-				
-			<entry>
-				system-related messages
-			</entry>
-		</row>
-			
-		<row>
-			<entry>
-				5
-			</entry>
-				
-			<entry>
-				<keycombo><keycap>ctrl</keycap><keycap>alt</keycap><keycap>f5</keycap>
-				</keycombo>
-			</entry>
-				
-			<entry>
-				other messages
-			</entry>
-		</row>
-			
-		<row>
-			<entry>
-				6
-			</entry>
-				
-			<entry>
-				<keycombo><keycap>ctrl</keycap><keycap>alt</keycap><keycap>f6</keycap>
-				</keycombo>
-			</entry>
-				
-			<entry>
-				graphical display
-			</entry>
-		</row>
-	</tbody>
-</tgroup>
-				
-			</table>
-		</section>
-	</section>
-		
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude"  href="Graphical_Installation_x86-common-section-1.xml"/>
-	<!-- The Text Mode Installation Program User Interface
-	     links to Graphical_Installation_common-section-2.xml:
-	     Using the Keyboard to Navigate -->
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Graphical_Installation_x86_Starting.xml"/>
-	<!-- Starting the Installation Program
-	     Booting the Installation Program on x86, AMD64,and Intel 64 systems
-	     Booting the Installation Program on Itanium Systems
-	     Booting the Installation Program from an LS-120 Diskette
-	     Additional Boot Options
-	     Kernel Options-->
-	
- 	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Graphical_Installation_x86-Installation-methods.xml"/>
-	<!-- Selecting an Installation Method -->
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Installation_Method-x86.xml"/>
-	<!-- Installation Method -->
-		
-	<xi:include href="Verifying_Media.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
-	<!-- Verifying Media - The DVD offers an option to verify the integrity of the media. -->
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Welcome-x86.xml"/>
-	<!-- Welcome to Fedora -->
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Language_Selection-x86.xml"/>
-	<!-- Language Selection -->
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Key_Board_Configuration-x86.xml"/>  
-	<!-- Keyboard Configuration -->
-	
-<!--	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Beginning_Installation_FTP-x86.xml"/>  -->
-	<!-- Installing via FTP -->
-	
-<!--	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Beginning_Installation_HTTP-x86.xml"/>  -->
-	<!-- Installing via HTTP -->
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Storage_Devices-x86.xml"/>  
-	<!-- Storage devices -->
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Assign_Storage_Devices-x86.xml"/>  
-	<!-- Assign Storage devices -->
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Initializing_Hard_Disk-x86.xml"/>  
-	<!-- Initializing Hard Disk -->
-	
-<!--	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Installation_Number-x86.xml"/>   -->
-	<!-- Installation Number for RHEL-->
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="upgrading-fedora.xml"/>  
-	<!-- The installation system automatically detects any existing... -->
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="networkconfig-fedora.xml"/>  
-	<!-- The installation system automatically detects any existing... -->
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Time_Zone-x86.xml"/>  
-	<!-- Time Zone -->
-	<!-- for Fedora goes here -->
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Account_Configuration-common.xml"/>
-	<!-- Account Configuration -->
-	<!-- for Fedora goes here -->
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Disk_Partitioning_Setup-x86.xml"/>
-	<!-- Disk Partitioning Setup -->
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Encrypt-x86.xml"/>
-	<!-- Disk Encryption -->
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Disk_Partitioning-x86.xml"/>  
-	<!-- Partitioning Your System
-	     Graphical Display of Hard Drives
-	     The partitioning screen
-	     Partition Fields
-	     Recommended Partitioning Scheme
-	     Adding Partitions
-	     Editing Partitions-->
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Write_changes_to_disk.xml"/> 
-	<!-- The installer prompts you to confirm the partitioning options that you selected. -->
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="X86_Bootloader.xml"/> 
-	<!-- x86, AMD64, and Intel 64 Boot Loader Configuration -->
-	
-<!--	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Netconfig-x86.xml"/>  -->
-	<!-- Network Configuration -->
-
-	
-<!--	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Time_Zone-x86.xml"/>  -->
-	<!-- Time Zone -->
-	<!-- for RHEL goes here -->
-	
-<!--	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Account_Configuration-common.xml"/>  -->
-	<!-- Account Configuration -->
-	<!-- for RHEL goes here -->
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Package_Selection-x86.xml"/>
-	<!-- Package Selection -->
-	
-<!--	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Prepare_To_Install-x86.xml"/> -->
-	<!-- Prepare to Install -->
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Installing_Packages-x86.xml"/>
-	<!-- Installing Packages -->
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Complete-x86.xml"/>
-	<!-- Installation Complete -->
-	 
-<!--	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="IA64_Post_Installation.xml"/>   -->
-	<!-- Itanium Systems - Booting Your Machine and Post-Installation Setup -->
-
-
-</chapter>
\ No newline at end of file
diff --git a/en-US/Graphical_Installation_User_Interface_x86_ppc-note-Fedora.xml b/en-US/Graphical_Installation_User_Interface_x86_ppc-note-Fedora.xml
deleted file mode 100644
index 7fdc307..0000000
--- a/en-US/Graphical_Installation_User_Interface_x86_ppc-note-Fedora.xml
+++ /dev/null
@@ -1,20 +0,0 @@
-		<note>
-			<title>Note</title>			
-			<para>
-				If you are using an x86, AMD64, or <trademark class="registered">Intel</trademark> 64 system, and you do not wish to use the GUI installation program, the text mode installation program is also available. To start the text mode installation program, press the <keycap>Esc</keycap> key while the Fedora boot menu is displayed, then use the following command at the <prompt>boot:</prompt> prompt:
-			</para>
-<screen>
-<userinput>linux text</userinput>
-</screen>
-
-			<!-- The following paragraph is in both x86 and ppc guides, but is included here because of the arch-specific link -->
-			<para>
-				Refer to <xref linkend="sn-boot-menu-x86"/> for a description of the Fedora boot menu and to <xref linkend="s1-guimode-textinterface-x86"/> for a brief overview of text mode installation instructions.
-			</para>
-			
-			<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Graphical_Installation_User_Interface_x86_ppc-note-para-1.xml"/>
-			<!-- It is highly recommended that installs... -->
-			
-			<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Graphical_Installation_User_Interface_x86_ppc-note-para-2.xml"/>
-			<!-- Users who must use the text mode... -->
-		</note>
\ No newline at end of file
diff --git a/en-US/Graphical_Installation_User_Interface_x86_ppc-note-para-1.xml b/en-US/Graphical_Installation_User_Interface_x86_ppc-note-para-1.xml
deleted file mode 100644
index 13ee25d..0000000
--- a/en-US/Graphical_Installation_User_Interface_x86_ppc-note-para-1.xml
+++ /dev/null
@@ -1,10 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-	  
-	  
-	  
-]>
-
-<para>
-	It is highly recommended that installs be performed using the GUI installation program. The GUI installation program offers the full functionality of the Fedora installation program, including LVM configuration which is not available during a text mode installation.
-</para>
\ No newline at end of file
diff --git a/en-US/Graphical_Installation_User_Interface_x86_ppc-note-para-2.xml b/en-US/Graphical_Installation_User_Interface_x86_ppc-note-para-2.xml
deleted file mode 100644
index 3a9e6f5..0000000
--- a/en-US/Graphical_Installation_User_Interface_x86_ppc-note-para-2.xml
+++ /dev/null
@@ -1,11 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-	  
-	  
-	  
-]>
-
-
-<para>
-	Users who must use the text mode installation program can follow the GUI installation instructions and obtain all needed information.
-</para>
\ No newline at end of file
diff --git a/en-US/Graphical_Installation_common-list-1.xml b/en-US/Graphical_Installation_common-list-1.xml
deleted file mode 100644
index 74035a3..0000000
--- a/en-US/Graphical_Installation_common-list-1.xml
+++ /dev/null
@@ -1,38 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE itemizedlist PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-	  
-	  
-	  
-]>
-	  
-<itemizedlist>
-	<listitem>
-		<para>
-			Becoming familiar with the installation program's user interface
-		</para>
-	</listitem>
-	
-	<listitem>
-		<para>
-			Starting the installation program
-		</para>
-	</listitem>
-	
-	<listitem>
-		<para>
-			Selecting an installation method
-		</para>
-	</listitem>
-	
-	<listitem>
-		<para>
-			Configuration steps during the installation (language, keyboard, mouse, partitioning, etc.)
-		</para>
-	</listitem>
-	
-	<listitem>
-		<para>
-			Finishing the installation
-		</para>
-	</listitem>
-</itemizedlist>
\ No newline at end of file
diff --git a/en-US/Graphical_Installation_common-list-item-1.xml b/en-US/Graphical_Installation_common-list-item-1.xml
deleted file mode 100644
index 74d2b17..0000000
--- a/en-US/Graphical_Installation_common-list-item-1.xml
+++ /dev/null
@@ -1,13 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE listitem PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-	  
-	  
-	  
-]>
-	  
-<listitem>	
-	<para>
-		Window &mdash; Windows (usually referred to as <firstterm>dialogs</firstterm> in this manual) appear on your screen throughout the installation process. At times, one window may overlay another; in these cases, you can only interact with the window
-		on top. When you are finished in that window, it disappears, allowing you to continue working in the window underneath.
-	</para>
-</listitem>
\ No newline at end of file
diff --git a/en-US/Graphical_Installation_common-list-item-2.xml b/en-US/Graphical_Installation_common-list-item-2.xml
deleted file mode 100644
index 353c630..0000000
--- a/en-US/Graphical_Installation_common-list-item-2.xml
+++ /dev/null
@@ -1,13 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE listitem PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-	  
-	  
-	  
-]>
-	  
-<listitem>
-	<para>
-		Checkbox &mdash; Checkboxes allow you to select or deselect a feature. The box displays either an asterisk (selected) or a space (unselected). When the cursor is within a checkbox, press <keycap>Space</keycap> to select or deselect a
-		feature.
-	</para>
-</listitem>
\ No newline at end of file
diff --git a/en-US/Graphical_Installation_common-list-item-3.xml b/en-US/Graphical_Installation_common-list-item-3.xml
deleted file mode 100644
index 8bf3c28..0000000
--- a/en-US/Graphical_Installation_common-list-item-3.xml
+++ /dev/null
@@ -1,12 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE listitem PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-	  
-	  
-	  
-]>
-
-<listitem>
-	<para>
-		Text Input &mdash; Text input lines are regions where you can enter information required by the installation program. When the cursor rests on a text input line, you may enter and/or edit information on that line.
-	</para>
-</listitem>
\ No newline at end of file
diff --git a/en-US/Graphical_Installation_common-list-item-4.xml b/en-US/Graphical_Installation_common-list-item-4.xml
deleted file mode 100644
index 8c428e8..0000000
--- a/en-US/Graphical_Installation_common-list-item-4.xml
+++ /dev/null
@@ -1,12 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE listitem PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-	  
-	  
-	  
-]>
-
-<listitem>
-	<para>
-		Text Widget &mdash; Text widgets are regions of the screen for the display of text. At times, text widgets may also contain other widgets, such as checkboxes. If a text widget contains more information than can be displayed in the space reserved for it, a scroll bar appears; if you position the cursor within the text widget, you can then use the <keycap>Up</keycap> and <keycap>Down</keycap> arrow keys to scroll through all the information available. Your current position is shown on the scroll bar by a <guiicon>#</guiicon> character, which moves up and down the scroll bar as you scroll.
-	</para>
-</listitem>
\ No newline at end of file
diff --git a/en-US/Graphical_Installation_common-list-item-5.xml b/en-US/Graphical_Installation_common-list-item-5.xml
deleted file mode 100644
index d2e0ca0..0000000
--- a/en-US/Graphical_Installation_common-list-item-5.xml
+++ /dev/null
@@ -1,12 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE listitem PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-	  
-	  
-	  
-]>
-
-<listitem>
-	<para>
-		Scroll Bar &mdash; Scroll bars appear on the side or bottom of a window to control which part of a list or document is currently in the window's frame. The scroll bar makes it easy to move to any part of a file.
-	</para>
-</listitem>
\ No newline at end of file
diff --git a/en-US/Graphical_Installation_common-list-item-6.xml b/en-US/Graphical_Installation_common-list-item-6.xml
deleted file mode 100644
index ab67f81..0000000
--- a/en-US/Graphical_Installation_common-list-item-6.xml
+++ /dev/null
@@ -1,13 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE listitem PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-	  
-	  
-	  
-]>
-
-<listitem>
-	<para>
-		Button Widget &mdash; Button widgets are the primary method of interacting with the installation program. You progress through the windows of the installation program by navigating these buttons, using the <keycap>Tab</keycap> and
-		<keycap>Enter</keycap> keys. Buttons can be selected when they are highlighted.
-	</para>
-</listitem>
\ No newline at end of file
diff --git a/en-US/Graphical_Installation_common-note-1.xml b/en-US/Graphical_Installation_common-note-1.xml
deleted file mode 100644
index f85eef8..0000000
--- a/en-US/Graphical_Installation_common-note-1.xml
+++ /dev/null
@@ -1,31 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE note PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<note>
-	<title>Note</title>
-	
-	<para>
-		While text mode installations are not explicitly documented, those using the text mode installation program can easily follow the GUI installation instructions. However, because text mode presents you with a simpler, more streamlined insatallation process, certain options that are available in graphical mode are not also available in text mode. These differences are noted in the description of the installation process in this guide, and include: 
-		
-		<itemizedlist>
-			<listitem>
-				<para>
-					customizing the partition layout.
-				</para>
-			</listitem>
-			<listitem>
-				<para>
-					customizing the bootloader configuration.
-				</para>
-			</listitem>
-			<listitem>
-				<para>
-					selecting packages during installation. 
-				</para>
-			</listitem>
-		</itemizedlist>
-		
-		Note also that manipulation of LVM (Logical Volume Management) disk volumes is only possible in graphical mode. In text mode it is only possible to view and accept the default LVM setup. 
-	</para>
-</note>
\ No newline at end of file
diff --git a/en-US/Graphical_Installation_common-note-2.xml b/en-US/Graphical_Installation_common-note-2.xml
deleted file mode 100644
index 3c1bb1c..0000000
--- a/en-US/Graphical_Installation_common-note-2.xml
+++ /dev/null
@@ -1,11 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE note PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<note>
-	<title>Note</title>
-	
-	<para>
-		Not every language supported in graphical installation mode is also supported in text mode. Specifically, languages written with a character set other than the Latin or Cyrillic alphabets are not available in text mode. If you choose a language written with a character set that is not supported in text mode, the installation program will present you with the English versions of the screens.
-	</para>
-</note>
\ No newline at end of file
diff --git a/en-US/Graphical_Installation_common-para-1.xml b/en-US/Graphical_Installation_common-para-1.xml
deleted file mode 100644
index 0fd976a..0000000
--- a/en-US/Graphical_Installation_common-para-1.xml
+++ /dev/null
@@ -1,10 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-	  
-	  
-	  
-]>
-
-<para>
-			If you have used a <firstterm>graphical user interface (GUI)</firstterm> before, you are already familiar with this process; use your mouse to navigate the screens, click buttons, or enter text fields.
-</para>
\ No newline at end of file
diff --git a/en-US/Graphical_Installation_common-para-2.xml b/en-US/Graphical_Installation_common-para-2.xml
deleted file mode 100644
index 0e63a0c..0000000
--- a/en-US/Graphical_Installation_common-para-2.xml
+++ /dev/null
@@ -1,10 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-	  
-	  
-	  
-]>
-	  
-<para>
-			You can also navigate through the installation using the keyboard. The <keycap>Tab</keycap> key allows you to move around the screen, the Up and Down arrow keys to scroll through lists, <keycap>+</keycap> and <keycap>-</keycap> keys expand and collapse lists, while <keycap>Space</keycap> and <keycap>Enter</keycap> selects or removes from selection a highlighted item. You can also use the <keycombo><keycap>Alt</keycap><keycap><replaceable>X</replaceable></keycap> </keycombo> key command combination as a way of clicking on buttons or making other screen selections, where <keycap><replaceable>X</replaceable></keycap> is replaced with any underlined letter appearing within that screen.
-</para>
\ No newline at end of file
diff --git a/en-US/Graphical_Installation_common-section-2.xml b/en-US/Graphical_Installation_common-section-2.xml
deleted file mode 100644
index 01ae379..0000000
--- a/en-US/Graphical_Installation_common-section-2.xml
+++ /dev/null
@@ -1,40 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-	  
-	  
-	  
-]>
-
-<section>	
-	<title>Using the Keyboard to Navigate</title>
-	<indexterm significance="normal">
-		<primary>installation</primary>
-		<secondary>keyboard navigation</secondary>
-	</indexterm>
-	<indexterm significance="normal">
-		<primary>keyboard</primary>
-		<secondary>navigating the installation program using</secondary>
-	</indexterm>
-	<para>
-		Navigation through the installation dialogs is performed through a simple set of keystrokes. To move the cursor, use the <keycap>Left</keycap>, <keycap>Right</keycap>, <keycap>Up</keycap>, and <keycap>Down</keycap> arrow keys. Use <keycap>Tab</keycap>, and <keycap>Shift</keycap>-<keycap>Tab</keycap> to cycle forward or backward through each widget on the screen. Along the bottom,
-		most screens display a summary of available cursor positioning keys.
-	</para>
-	
-	<para>
-		To "press" a button, position the cursor over the button (using <keycap>Tab</keycap>, for example) and press <keycap>Space</keycap> or <keycap>Enter</keycap>. To select an item from a list of items, move
-		the cursor to the item you wish to select and press <keycap>Enter</keycap>. To select an item with a checkbox, move the cursor to the checkbox and press <keycap>Space</keycap> to select an item. To deselect, press
-		<keycap>Space</keycap> a second time.
-	</para>
-	
-	<para>
-		Pressing <keycap>F12</keycap> accepts the current values and proceeds to the next dialog; it is equivalent to pressing the <guibutton>OK</guibutton> button.
-	</para>
-	
-	<warning>
-		<title>Warning</title>
-	
-		<para>
-			Unless a dialog box is waiting for your input, do not press any keys during the installation process (doing so may result in unpredictable behavior).
-		</para>
-	</warning>
-</section>
\ No newline at end of file
diff --git a/en-US/Graphical_Installation_screenshots.xml b/en-US/Graphical_Installation_screenshots.xml
deleted file mode 100644
index 4e009fd..0000000
--- a/en-US/Graphical_Installation_screenshots.xml
+++ /dev/null
@@ -1,16 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<section id="sect-adminoptions-screenshots"><title>Screenshots during installation</title>
-	<indexterm significance="normal">
-		<primary>screenshots</primary>
-		<secondary>during installation</secondary>
-	</indexterm>
-	<para>
-		<application>Anaconda</application> allows you to take screenshots during the installation process. At any time during installation, press <keycombo><keycap>Shift</keycap><keycap>Print Screen</keycap></keycombo> and <application>anaconda</application> will save a screenshot to <filename>/root/anaconda-screenshots</filename>.
-	</para>
-	<para>
-		If you are performing a Kickstart installation, use the <option>autostep --autoscreenshot</option> option to generate a screenshot of each step of the installation automatically. Refer to <xref linkend="s1-kickstart2-file"/> for details of configuring a Kickstart file.
-	</para>
-</section>
diff --git a/en-US/Graphical_Installation_x86-Installation-methods.xml b/en-US/Graphical_Installation_x86-Installation-methods.xml
deleted file mode 100644
index 63573ab..0000000
--- a/en-US/Graphical_Installation_x86-Installation-methods.xml
+++ /dev/null
@@ -1,93 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<section id="s1-installmethod-x86">
-	<title>Selecting an Installation Method</title>
-	<indexterm significance="normal">
-		<primary>installation</primary>
-		<secondary>method</secondary>
-		<tertiary>selecting</tertiary>
-	</indexterm>
-	<para>
-		What type of installation method do you wish to use? The following installation methods are available:
-	</para>
-	<indexterm significance="normal">
-		<primary>installation</primary>
-		<secondary>method</secondary>
-		<tertiary>CD-ROM</tertiary>
-	</indexterm>
-	<variablelist>
-		<varlistentry>
-			<term>	DVD/CD-ROM      </term>
-			<listitem>
-				<para>
-					If you have a DVD/CD-ROM drive and the Fedora CD-ROMs or DVD you can use this method. Refer to <xref linkend="s1-begininstall-cd-inst-x86"/>, for DVD/CD-ROM installation instructions.
-				</para>
-				<para>
-					If you booted the installation from a piece of media other than the installation CD-ROM or DVD, you can specify the CD-ROM or DVD as the installation source with the <command>linux askmethod</command> or <command>linux repo=cdrom:<replaceable>device</replaceable>:/<replaceable>device</replaceable></command> boot option, or by selecting <guimenuitem>Local CD/DVD</guimenuitem> on the <guimenu>Installation Method</guimenu> menu (refer to <xref linkend="s1-installationmethod-x86"/>).
-				</para>
-			</listitem>
-		</varlistentry>
-
-		<varlistentry>
-			<term>	Hard Drive       </term>
-			<listitem>
-				<indexterm significance="normal">
-					<primary>installation</primary>
-					<secondary>method</secondary>
-					<tertiary>hard drive</tertiary>
-				</indexterm>
-				<para>
-					If you have copied the Fedora ISO images to a local hard drive, you can use this method. You need a boot CD-ROM (use the <command>linux askmethod</command> or <command>linux repo=hd:<replaceable>device</replaceable>:/<replaceable>path</replaceable></command> boot option), or by selecting <guimenuitem>Hard drive</guimenuitem> on the <guimenu>Installation Method</guimenu> menu (refer to <xref linkend="s1-installationmethod-x86"/>). Refer to <xref linkend="s1-begininstall-hd-x86"/>, for hard drive installation instructions.
-				</para>
-			</listitem>
-		</varlistentry>
-
-		<varlistentry>
-			<term>	NFS       </term>
-			<listitem>
-				<indexterm significance="normal">
-					<primary>installation</primary>
-					<secondary>method</secondary>
-					<tertiary>NFS image</tertiary>
-				</indexterm>
-				<para>
-					If you are installing from an NFS server using ISO images or a mirror image of Fedora, you can use this method. You need a boot CD-ROM (use the <command>linux askmethod</command> or <command>linux repo=nfs:<replaceable>server</replaceable> <replaceable>:options</replaceable>:/<replaceable>path</replaceable></command> boot option, or the <guimenuitem>NFS directory</guimenuitem> option on the <guimenu>Installation Method</guimenu> menu described in <xref linkend="s1-installationmethod-x86"/>). Refer to <xref linkend="s1-begininstall-nfs-x86"/> for network installation instructions. Note that NFS installations may also be performed in GUI mode.
-				</para>
-			</listitem>
-		</varlistentry>
-
-		<varlistentry>
-			<term>	URL       </term>
-			<listitem>
-				<indexterm significance="normal">
-					<primary>installation</primary>
-					<secondary>method</secondary>
-					<tertiary>URL</tertiary>
-				</indexterm>
-				<para>
-					If you are installing directly from an HTTP (Web) server or FTP server, use this method. You need a boot CD-ROM (use the <command>linux askmethod</command>, <command>linux repo=ftp://<replaceable>user</replaceable>:<replaceable>password</replaceable>@<replaceable>host</replaceable>/<replaceable>path</replaceable></command>, or <command>linux repo=http://<replaceable>host</replaceable>/<replaceable>path</replaceable></command> boot option, or the <guimenuitem>URL</guimenuitem> option on the <guimenu>Installation Method</guimenu> menu described in <xref linkend="s1-installationmethod-x86"/>). Refer to  <xref linkend="s1-begininstall-url-x86"/>, for FTP and HTTP installation
-					instructions.
-				</para>
-			</listitem>
-		</varlistentry>
-	</variablelist>
-      <para>If you booted the distribution DVD and did not use the
-	alternate installation source option <option>askmethod</option>,
-	the next stage loads automatically from the DVD.  Proceed to
-	<xref linkend="s1-langselection-x86"/>.</para>
-  <note>
-    <title>CD/DVD Activity</title>
-    <para>
-      If you boot any Fedora installation media, the installation
-      program loads its next stage from that disc.  This happens
-      regardless of which installation method you choose, unless you
-      eject the disc before you proceed.  The installation program still
-      downloads <emphasis>package data</emphasis> from the source you
-      choose.
-    </para>
-  </note>
-
-</section>
-
diff --git a/en-US/Graphical_Installation_x86-common-section-1.xml b/en-US/Graphical_Installation_x86-common-section-1.xml
deleted file mode 100644
index de60127..0000000
--- a/en-US/Graphical_Installation_x86-common-section-1.xml
+++ /dev/null
@@ -1,77 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<section id="s1-guimode-textinterface-x86">	
-	<title>The Text Mode Installation Program User Interface</title>
-	<indexterm significance="normal">
-		<primary>installation</primary>
-		<secondary>program</secondary>
-		<tertiary>text mode user interface</tertiary>
-	</indexterm>
-	<indexterm significance="normal">
-		<primary>user interface, text mode</primary>
-		<secondary>installation program</secondary>
-	</indexterm>
-	
-	<note>
-		<para>
-		Graphical installation remains the recommended method for installing Fedora. If you are installing Fedora on a system that lacks a graphical display, consider performing the installation over a VNC connection &ndash; see <xref linkend="vncwhitepaperadded"/>.
-		</para>
-		<para>
-		If your system has a graphical display, but graphical installation fails, try booting with the <command>xdriver=vesa</command> option &ndash; see <xref linkend="ap-admin-options"/>
-		</para>
-	</note>
-	
-	<para>
-		The Fedora text mode installation program uses a screen-based interface that includes most of the on-screen <wordasword>widgets</wordasword> commonly found on graphical user interfaces. <xref linkend="fig-install-widget1-x86"/>, and
-		<xref linkend="fig-install-widget2-x86"/>, illustrate the screens that appear during the installation process.
-	</para>
-	<para>
-		The cursor is used to select (and interact with) a particular widget. As the cursor is moved from widget to widget, it may cause the widget to change color, or the cursor itself may only appear positioned in or
-		next to the widget. 
-	</para>
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Graphical_Installation_common-note-1.xml"/>
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Graphical_Installation_common-note-2.xml"/>
-	
-	<figure float="0" id="fig-install-widget1-x86"><title>Installation Program Widgets as seen in <guilabel>Boot Loader Configuration</guilabel></title>
-		<mediaobject>
-			<imageobject><imagedata fileref="images/guimode/widget1.png" format="PNG"/></imageobject>
-			<textobject><para>
-					Installation Program Widgets as seen in <guilabel>Boot Loader Configuration</guilabel>
-				</para>
-			</textobject>
-		</mediaobject>
-	</figure>
-	
-	<orderedlist>
-	<title>Legend</title>    
-	    <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Graphical_Installation_common-list-item-1.xml"/>
-	    <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Graphical_Installation_common-list-item-2.xml"/>
-	    <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Graphical_Installation_common-list-item-3.xml"/>
-	</orderedlist>
-	
-	<!--
-	<figure float="0" id="fig-install-widget2">
-	-->
-	
-	<figure float="0" id="fig-install-widget2-x86">
-		<title>Installation Program Widgets as seen in the partitioning screen</title>
-		<mediaobject>
-			<imageobject><imagedata fileref="images/guimode/widget2.png" format="PNG"/></imageobject>
-			<textobject><para>
-					Installation Program Widgets as seen in the partitioning screen
-				</para>
-			</textobject>
-		</mediaobject>
-	</figure>
-
-	<orderedlist>
-	<title>Legend</title>
-	    <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Graphical_Installation_common-list-item-4.xml"/>
-	    <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Graphical_Installation_common-list-item-5.xml"/>
-	    <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Graphical_Installation_common-list-item-6.xml"/>
-	</orderedlist>
-
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Graphical_Installation_common-section-2.xml"/>
-</section>
\ No newline at end of file
diff --git a/en-US/Graphical_Installation_x86-para-5.xml b/en-US/Graphical_Installation_x86-para-5.xml
deleted file mode 100644
index 9d850e5..0000000
--- a/en-US/Graphical_Installation_x86-para-5.xml
+++ /dev/null
@@ -1,12 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
- 
-]> 
-
-  <para>These virtual consoles can be helpful if you encounter a problem
-    while installing Fedora.  Messages displayed on
-    the installation or system consoles can help pinpoint a
-    problem. Refer to <xref linkend="tb-guimode-console-x86"/> for a listing
-      of the virtual consoles, keystrokes used to switch to them, and their
-      contents.
-  </para>
\ No newline at end of file
diff --git a/en-US/Graphical_Installation_x86_Starting.xml b/en-US/Graphical_Installation_x86_Starting.xml
deleted file mode 100644
index b28ee2d..0000000
--- a/en-US/Graphical_Installation_x86_Starting.xml
+++ /dev/null
@@ -1,280 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<section id="s1-x86-starting">
-	<title>Starting the Installation Program</title>
-	<indexterm significance="normal">
-		<primary>installation</primary>
-		<secondary>program</secondary>
-		<tertiary>starting</tertiary>
-	</indexterm>
-	<indexterm significance="normal">
-		<primary>starting</primary>
-		<secondary>installation</secondary>
-	</indexterm>
-	<xi:include href="Important_UEFI.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
-	<para>
-		To start, first make sure that you have all necessary resources for the installation. If you have already read through <xref linkend="ch-steps-x86"/>, and followed the instructions, you should be ready to start the installation process. When you have verified that you are ready to begin, boot the installation program using the Fedora DVD or CD-ROM #1 or any boot media that you have created.
-	</para>
-	<!-- FIXME Not in F11
-	<note>
-		<title>Note</title>
-		<indexterm significance="normal">
-			<primary>driver diskette</primary>
-		</indexterm>
-		<para>
-			Occasionally, some hardware components require a <firstterm>driver diskette</firstterm> during the installation. A driver diskette adds support for hardware that is not otherwise supported by the installation program. Refer to <xref linkend="ch-driverdisk-x86"/> for more information.
-		</para>
-	</note>
-	 -->
-	<section id="s2-x86-starting-booting">
-		<title>Booting the Installation Program on x86, AMD64, and <trademark class="registered">Intel</trademark> 64 Systems</title>
-		<indexterm significance="normal">
-			<primary>installation program</primary>
-			<secondary>x86, AMD64 and <trademark class="registered">Intel</trademark> 64</secondary>
-			<tertiary>booting</tertiary>
-		</indexterm>
-		<indexterm significance="normal">
-			<primary>booting</primary>
-			<secondary>installation program</secondary>
-			<tertiary>x86, AMD64 and <trademark class="registered">Intel</trademark> 64</tertiary>
-		</indexterm>
-		
-		<para>
-			You can boot the installation program using any one of the following media (depending upon what your system can support):
-		</para>
-		 
-		<itemizedlist>
-			<listitem>
-				<para>
-					<emphasis>Fedora DVD/CD-ROM</emphasis> &mdash; Your machine supports a bootable DVD/CD-ROM drive and you have the Fedora CD-ROM set or DVD.
-				</para>
-			</listitem>
-
-			<listitem>
-				<para>
-					<emphasis>Boot CD-ROM</emphasis> &mdash; Your machine supports a bootable CD-ROM drive and you want to perform network or hard drive installation.
-				</para>
-			</listitem>
-
-			<listitem>
-				<para>
-					<emphasis>USB pen drive</emphasis> &mdash; Your machine supports booting from a USB device.
-				</para>
-			</listitem>
-			
-			<listitem>
-				<para>
-					<emphasis>PXE boot via network</emphasis> &mdash; Your machine supports booting from the network. This is an advanced installation path. Refer to <xref linkend="ap-install-server"/> for additional information on this method.
-				</para>
-			</listitem>
-		</itemizedlist>
-		 
-		<para>
-			To create a boot CD-ROM or to prepare your USB pen drive for installation, refer to <xref linkend="sect-New_Users-Alternative_Boot_Methods"/>.
-		</para>
-		 
-		<para>
-			Insert the boot media and reboot the system.
-		</para>
-		<xi:include href="Boot_Order-para-1.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
-		<xi:include href="Boot_Order-para-2.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
-		<xi:include href="Boot_Order-para-3.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
-		<xi:include href="Boot_Order-para-4.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
-		<xi:include href="Boot_Order-para-5.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
-		<para>
-			After a short delay, a screen containing boot options appears.<!-- the RHEL <prompt>boot:</prompt> prompt should appear. The screen contains information on a variety of boot options. Each boot option also has one or more help screens associated with it. To access a help screen, press the appropriate function key as listed in the line at the bottom of the screen.-->
-		</para>
-		 
-		<para>
-			As you boot the installation program, be aware of two issues:
-		</para>
-		 
-		<itemizedlist>
-			<listitem>
-				<para>
-					Once the <prompt>boot:</prompt> prompt appears, the installation program automatically begins if you take no action within the first minute. To disable this feature, press one of the help screen function keys.
-				</para>
-			</listitem>
-
-			<listitem>
-				<para>
-					If you press a help screen function key, there is a slight delay while the help screen is read from the boot media.
-				</para>
-			</listitem>
-		</itemizedlist>
-		 
-		<para>
-			Normally, you only need to press <keycap>Enter</keycap> to boot. Be sure to watch the boot messages to review if the Linux kernel detects your hardware. If your hardware is properly detected, continue to the next section. If it does not properly detect your hardware, you may need to restart the installation and use one of the boot options provided in <xref linkend="ap-admin-options"/>.
-		</para>
-	</section>
-	 
-<!--	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="IA64_Starting.xml"/> -->
-	<!-- Booting the Installation Program on Itanium Systems -->
-
-	<section id="s2-x86-starting-bootopts">
-		<title>Additional Boot Options</title>
-		<indexterm significance="normal">
-			<primary>boot options</primary>
-		</indexterm>
-		<para>
-			While it is easiest to boot using a CD-ROM or DVD and perform a graphical installation, sometimes there are installation scenarios where booting in a different manner may be needed. This section discusses additional boot options available for Fedora.
-		</para>
-		 
-<!--	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="IA64_Additional_Boot_Options-para-1.xml"/> -->
-	<!-- For Itanium users: -->
-<!--	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="IA64_Additional_Boot_Options-para-2.xml"/> -->
-	<!-- To pass options to the boot loader on an Itanium... -->
-<!--	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="IA64_Additional_Boot_Options-screen-1.xml"/> -->
-	<!-- elilo linux option -->
-<!--	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="IA64_Additional_Boot_Options-para-3.xml"/> -->
-	<!-- For x86, AMD64, and Intel 64 users: -->
-		 
-		<para>
-			To pass options to the boot loader on an x86, AMD64, or <trademark class="registered">Intel</trademark> 64 system, use the instructions as provided in the boot loader option samples below.
-		</para>
-	 
-		<note>
-			<title>Note</title>
-
-			<para>
-				Refer to <xref linkend="ap-admin-options"/> for additional boot options not covered in this section.
-			</para>
-		</note>
-		 
-		<itemizedlist>
-			<listitem>
-				<para>
-			<indexterm significance="normal">
-				<primary>installation</primary>
-				<secondary>text mode</secondary>
-			</indexterm>
-			<indexterm significance="normal">
-				<primary>boot options</primary>
-				<secondary>text mode</secondary>
-			</indexterm>
-					To perform a text mode installation, at the installation boot prompt, type:
-				</para>
-<screen>
-<userinput>linux text</userinput>
-</screen>
-			</listitem>
-			<listitem>
-				<para>
-			<indexterm significance="normal">
-				<primary>installation</primary>
-				<secondary>mediacheck</secondary>
-			</indexterm>
-			<indexterm significance="normal">
-				<primary>boot options</primary>
-				<secondary>mediacheck</secondary>
-			</indexterm>
-			<indexterm significance="normal">
-				<primary>troubleshooting</primary>
-				<secondary>CD-ROM failure</secondary>
-				<tertiary>CD-ROM verification</tertiary>
-			</indexterm>
-					ISO images have an md5sum embedded in them. To test the checksum integrity of an ISO image, at the installation boot prompt, type:
-				</para>
-<screen>
-<userinput>linux mediacheck</userinput>
-</screen>
-				<para>
-					The installation program prompts you to insert a CD or select an ISO image to test, and select <guibutton>OK</guibutton> to perform the checksum operation. This checksum operation can be performed on any Fedora CD and does not have to be performed in a specific order (for example, CD #1 does not have to be the first CD you verify). It is strongly recommended to perform this operation on any Fedora CD that was created from downloaded ISO images. This command works with the CD, DVD, hard drive ISO, and NFS ISO installation methods.
-				</para>
-			</listitem>
-			<listitem>
-				<para>
-			<indexterm significance="normal">
-				<primary><filename>boot.iso</filename>
-				</primary>
-			</indexterm>
-			<indexterm significance="normal">
-				<primary>boot options</primary>
-				<secondary><filename>boot.iso</filename>
-				</secondary>
-			</indexterm>
-					The <filename>boot.iso</filename> image file is available for download from the same servers that host images of the Fedora installation disks &mdash; refer to <xref linkend="sect-Obtaining_Fedora-Downloading_Fedora"/>. This file is an image of a disc that you can burn to a CD and use to boot the installation program. To use this boot CD, your computer must be able to boot from its CD-ROM drive, and its BIOS settings must be configured to do so. 
-				</para>
-			</listitem>
-			<listitem>
-				<para>
-			<indexterm significance="normal">
-				<primary>installation</primary>
-				<secondary>serial mode</secondary>
-			</indexterm>
-			<indexterm significance="normal">
-				<primary>boot options</primary>
-				<secondary>serial mode</secondary>
-			</indexterm>
-			<indexterm significance="normal">
-				<primary>installation</primary>
-				<secondary>serial mode</secondary>
-				<tertiary>UTF-8</tertiary>
-			</indexterm>
-			<indexterm significance="normal">
-				<primary>boot options</primary>
-				<secondary>serial mode</secondary>
-				<tertiary>UTF-8</tertiary>
-			</indexterm>
-					If you need to perform the installation in <firstterm>serial mode</firstterm>, type the following command:
-				</para>
-<screen>
-<userinput>linux console=<replaceable>&lt;device&gt;</replaceable></userinput>
-</screen>
-				<para>
-					For text mode installations, use:
-				</para>
-<screen>
-<userinput>linux text console=<replaceable>&lt;device&gt;</replaceable></userinput>
-</screen>
-				<para>
-					In the above command, <replaceable>&lt;device&gt;</replaceable> should be the device you are using (such as ttyS0 or ttyS1). For example, <command>linux text console=ttyS0</command>.
-				</para>
-
-				<para>
-					Text mode installations using a serial terminal work best when the terminal supports UTF-8. Under UNIX and Linux, Kermit supports UTF-8. For Windows, Kermit '95 works well. Non-UTF-8 capable terminals works as long as only English is used during the installation process. An enhanced serial display can be used by passing the <command>utf8</command> command as a boot-time option to the installation program. For example:
-				</para>
-<screen>
-<command>linux console=ttyS0 utf8</command>
-</screen>
-			</listitem>
-		</itemizedlist>
-		 
-		<section id="s3-x86-starting-kernelopts">
-			<title>Kernel Options</title>
-			 
-			<para>
-				Options can also be passed to the kernel. For example, to apply updates for the anaconda installation program from a floppy disk enter:
-			</para>
-			<indexterm significance="normal">
-				<primary>kernel options</primary>
-			</indexterm>
-<screen>
-<userinput>linux updates</userinput>
-</screen>
-			<para>
-				For text mode installations, use:
-			</para>
-<screen>
-<userinput>linux text updates</userinput>
-</screen>
-			<para>
-				This command will prompt you to insert a floppy diskette containing updates for anaconda. It is not needed if you are performing a network installation and have already placed the updates image contents in <command>rhupdates/</command> on the server. 
-			</para>
-			 
-			<para>
-				After entering any options, press <keycap>Enter</keycap> to boot using those options.
-			</para>
-			 
-			<para>
-				If you need to specify boot options to identify your hardware, please write them down. The boot options are needed during the boot loader configuration portion of the installation (refer to <xref linkend="s1-x86-bootloader"/> for more information).
-			</para>
-			
-			<para>
-				For more information on kernel options refer to <xref linkend="ap-admin-options"/>.
-			</para>
-		</section>
-	</section>
-</section>
diff --git a/en-US/Graphical_Installation_x86_ppc-para-1.xml b/en-US/Graphical_Installation_x86_ppc-para-1.xml
deleted file mode 100644
index aed1753..0000000
--- a/en-US/Graphical_Installation_x86_ppc-para-1.xml
+++ /dev/null
@@ -1,10 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-	  
-	  
-	  
-]>
-	  
-<para>
-	This chapter explains how to perform a Fedora installation from the DVD/CD-ROM, using the graphical, mouse-based installation program. The following topics are discussed:
-</para>
\ No newline at end of file
diff --git a/en-US/Graphical_Installation_x86_ppc-para-3.xml b/en-US/Graphical_Installation_x86_ppc-para-3.xml
deleted file mode 100644
index 8032142..0000000
--- a/en-US/Graphical_Installation_x86_ppc-para-3.xml
+++ /dev/null
@@ -1,9 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [	  
-]>
-	  
-<para>The Fedora installation program offers more than the dialog boxes of the installation process. Several kinds of diagnostic messages are available to you, as well as a way to enter commands from a shell prompt. The installation program displays these messages on five <firstterm>virtual consoles</firstterm>, among which you can switch using a single keystroke combination.
-  </para>
-
-
-
diff --git a/en-US/Graphical_Installation_x86_ppc-para-4.xml b/en-US/Graphical_Installation_x86_ppc-para-4.xml
deleted file mode 100644
index fccff16..0000000
--- a/en-US/Graphical_Installation_x86_ppc-para-4.xml
+++ /dev/null
@@ -1,10 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-	  
-	  
-	  
-]> 
-
- <para>A virtual console is a shell prompt in a non-graphical environment,
-    accessed from the physical machine, not remotely. Multiple virtual
-    consoles can be accessed simultaneously.</para>
\ No newline at end of file
diff --git a/en-US/Graphical_Installation_x86_ppc-para-6.xml b/en-US/Graphical_Installation_x86_ppc-para-6.xml
deleted file mode 100644
index 517cbfe..0000000
--- a/en-US/Graphical_Installation_x86_ppc-para-6.xml
+++ /dev/null
@@ -1,9 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-	  
-	  
-	  
-]> 
-
-  <para>Generally, there is no reason to leave the default console (virtual console #6) for graphical installations unless you are attempting to diagnose installation problems.
-  </para>
\ No newline at end of file
diff --git a/en-US/Graphical_Installation_x86_ppc-table-1-title.xml b/en-US/Graphical_Installation_x86_ppc-table-1-title.xml
deleted file mode 100644
index 4972558..0000000
--- a/en-US/Graphical_Installation_x86_ppc-table-1-title.xml
+++ /dev/null
@@ -1,8 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE title PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<title>Console, Keystrokes, and Contents</title>
\ No newline at end of file
diff --git a/en-US/Graphical_and_Text_Interfaces.xml b/en-US/Graphical_and_Text_Interfaces.xml
deleted file mode 100644
index 5f5085e..0000000
--- a/en-US/Graphical_and_Text_Interfaces.xml
+++ /dev/null
@@ -1,49 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
- "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd">
-
-<section>
-	<title>Graphical and Text Interfaces</title>
-	<important>
-		<title>Graphical Interface Usage</title>
-		<para>
-			Installing in text mode does not prevent you from using a graphical interface on your system once it is installed.
-		</para>
-	</important>
-	<important>
-		<title>Important â€” Minimum RAM requirements</title>
-		<para>
-			If your system has less than 137&nbsp;MB of RAM, installation will not continue on any architecture.
-		</para>
-		<para>
-			Furthermore, installation from a hard drive or a network location requires an image of stage 2 of the installation program (<filename>installer.img</filename>) to be stored in memory. This additional requirement increases the minimum RAM required to at least 256&nbsp;MB for these installation methods.
-		</para>
-	</important>
-	<para>
-		Fedora &PRODVER; supports graphical and text-based installations. Only systems with more than 397&nbsp;MB of RAM can use the graphical installer. Systems with less RAM automatically scale back to using the text-based installer. Note that you must still have a minimum of 137&nbsp;MB of RAM for installation to proceed even in text mode, and some architectures and installation methods require more RAM than others. If you prefer to use the text-based installer, type <option>linux text</option> at the <prompt>boot:</prompt> prompt.
-	</para> 
-	<para>
-		If one of the following situations occurs, the installation program uses text mode:
-	</para>
-	<itemizedlist>
-		<listitem>
-			<para>
-				The installation system fails to identify the display hardware on your computer
-			</para>
-		</listitem>
-		<listitem>
-			<para>
-				Your computer has less the minimum amount of RAM required for graphical installation on your architecture with your chosen installation method (397&nbsp;MB at the very least).
-			</para>
-		</listitem>
-		<listitem>
-			<para>
-				You choose the text mode installation from the boot menu
-			</para>
-		</listitem>
-	</itemizedlist>
-	<para>
-		The text screens provide most of the same functions as the standard screens, although disk partitioning is simplified, and bootloader configuration and package selection are handled automatically in text mode. If you choose to install Fedora in text mode, you can still configure your system to use a graphical interface after installation. Refer to <xref linkend="sn-switching-to-gui-login"/> for instructions.
-	</para>
-</section>
-
diff --git a/en-US/Grub.xml b/en-US/Grub.xml
deleted file mode 100644
index 4fd33d8..0000000
--- a/en-US/Grub.xml
+++ /dev/null
@@ -1,1111 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-]>
-
-<appendix id="ch-grub"><title>The GRUB Boot Loader</title>
-	<indexterm significance="normal">
-		<primary>boot loaders</primary>
-		<secondary>definition of</secondary>
-	</indexterm>
-
-	<para>
-		When a computer running Linux is turned on, the operating system is loaded into memory by a special program called a <firstterm>boot loader</firstterm>. A boot loader usually exists on the system's primary hard drive (or other media device) and has the sole responsibility of loading the Linux kernel with its required files or (in some cases) other operating systems into memory.
-	</para>
-	<!-- (RHEL) <section id="s1-grub-arch">
-		<title>Boot Loaders and System Architecture</title>
-		<indexterm significance="normal">
-			<primary>ELILO</primary>
-			<seealso>boot loaders</seealso>
-		</indexterm>
-		<indexterm significance="normal">
-			<primary>OS/400</primary>
-			<seealso>boot loaders</seealso>
-		</indexterm>
-		<indexterm significance="normal">
-			<primary>YABOOT</primary>
-			<seealso>boot loaders</seealso>
-		</indexterm>
-		<indexterm significance="normal">
-			<primary>z/IPL</primary>
-			<seealso>boot loaders</seealso>
-		</indexterm>
-		<indexterm significance="normal">
-			<primary>GRUB</primary>
-			<seealso>boot loaders</seealso>
-		</indexterm>
-		<indexterm significance="normal">
-			<primary>boot loaders</primary>
-			<secondary>types of</secondary>
-			<tertiary>ELILO</tertiary>
-		</indexterm>
-		<indexterm significance="normal">
-			<primary>boot loaders</primary>
-			<secondary>types of</secondary>
-			<tertiary>OS/400</tertiary>
-		</indexterm>
-		<indexterm significance="normal">
-			<primary>boot loaders</primary>
-			<secondary>types of</secondary>
-			<tertiary>YABOOT</tertiary>
-		</indexterm>
-		<indexterm significance="normal">
-			<primary>boot loaders</primary>
-			<secondary>types of</secondary>
-			<tertiary>z/IPL</tertiary>
-		</indexterm>
-		<indexterm significance="normal">
-			<primary>boot loaders</primary>
-			<secondary>types of</secondary>
-			<tertiary>GRUB</tertiary>
-		</indexterm>
-		<para>
-			Each architecture capable of running Fedora uses a different boot loader. The following table lists the boot loaders available for each architecture:
-		</para>
-		 
-		<table id="tb-grub-arch-loaders">
-			<title>Boot Loaders by Architecture</title>
-			 
-			<tgroup cols="2">
-				<colspec colnum="1" colname="architecture" colwidth="20*"></colspec>
-				 
-				<colspec colnum="2" colname="bootloader" colwidth="10*"></colspec>
-				<thead><row>
-						<entry>
-							Architecture
-						</entry>
-						 
-						<entry>
-							Boot Loaders
-						</entry>
-					</row>
-				</thead>
-				<tbody>
-					<row>
-						<entry>
-							<trademark class="registered">AMD</trademark> AMD64
-						</entry>
-						 
-						<entry>
-							GRUB
-						</entry>
-					</row>
-					 
-					<row>
-						<entry>
-							<trademark class="registered">IBM</trademark> <trademark class="trade">eServer</trademark> <trademark class="trade">System i</trademark>
-						</entry>
-						 
-						<entry>
-							<trademark class="registered">OS/400</trademark>
-						</entry>
-					</row>
-					 
-					<row>
-						<entry>
-							<trademark class="registered">IBM</trademark> <trademark class="trade">eServer</trademark> <trademark class="trade">System p</trademark>
-						</entry>
-						 
-						<entry>
-							YABOOT
-						</entry>
-					</row>
-					 
-					<row>
-						<entry>
-							<trademark class="registered">IBM</trademark> <trademark class="registered">System z</trademark>
-						</entry>
-						 
-						<entry>
-							z/IPL
-						</entry>
-					</row>
-					 
-					<row>
-						<entry>
-							<trademark class="registered">IBM</trademark> <trademark class="registered">System z</trademark>
-						</entry>
-						 
-						<entry>
-							z/IPL
-						</entry>
-					</row>
-					 
-					<row>
-						<entry>
-							<trademark class="registered">Intel</trademark> <trademark class="trade">Itanium</trademark>
-						</entry>
-						 
-						<entry>
-							ELILO
-						</entry>
-					</row>
-					 
-					<row>
-						<entry>
-							x86
-						</entry>
-						 
-						<entry>
-							GRUB
-						</entry>
-					</row>
-				</tbody>
-			</tgroup>
-		</table> -->
-		 
-		<para>
-			This appendix discusses commands and configuration options for the GRUB boot loader included with Fedora for the x86 architecture.
-		</para>
-		
-		<xi:include href="ext4-and-btrfs.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
-		
-	<!-- (RHEL) </section> -->
-	<section id="s1-grub-whatis">
-		<title>GRUB</title>
-		<indexterm significance="normal">
-			<primary>GRUB</primary>
-			<secondary>definition of</secondary>
-		</indexterm>
-		<indexterm significance="normal">
-			<primary>boot loaders</primary>
-			<seealso>GRUB</seealso>
-		</indexterm>
-		<para>
-			The <firstterm>GNU GRand Unified Boot loader</firstterm> (GRUB) is a program which enables the selection of the installed operating system or kernel to be loaded at system boot time. It also allows the user to pass arguments to the kernel.
-		</para>
-		 
-		<section id="s2-grub-whatis-booting">
-			<title>GRUB and the x86 Boot Process</title>
-			<indexterm significance="normal">
-				<primary>GRUB</primary>
-				<secondary>boot process</secondary>
-			</indexterm>
-			<indexterm significance="normal">
-				<primary>boot process</primary>
-				<secondary>direct loading</secondary>
-			</indexterm>
-			<indexterm significance="normal">
-				<primary>boot process</primary>
-				<secondary>chain loading</secondary>
-			</indexterm>
-			<para>
-				This section discusses the specific role GRUB plays when booting an x86 system. For a look at the overall boot process, refer to <xref linkend="s1-boot-init-shutdown-process"/>.
-			</para>
-			 
-			<para>
-				GRUB loads itself into memory in the following stages:
-			</para>
-			 
-			<orderedlist inheritnum="ignore" continuation="restarts">
-				<listitem>
-					<para>
-						<emphasis>The Stage 1 or primary boot loader is read into memory by the BIOS from the MBR <footnote>
-						<para>
-							For more on the system BIOS and the MBR, refer to <xref linkend="s2-boot-init-shutdown-bios"/>.
-						</para>
-						</footnote>.</emphasis> The primary boot loader exists on less than 512 bytes of disk space within the MBR and is capable of loading either the Stage 1.5 or Stage 2 boot loader.
-					</para>
-				</listitem>
-
-				<listitem>
-					<para>
-						<emphasis>The Stage 1.5 boot loader is read into memory by the Stage 1 boot loader, if necessary.</emphasis> Some hardware requires an intermediate step to get to the Stage 2 boot loader. This is sometimes true when the
-						<filename>/boot/</filename> partition is above the 1024 cylinder head of the hard drive or when using LBA mode. The Stage 1.5 boot loader is found either on the <filename>/boot/</filename> partition or on a small part
-						of the MBR and the <filename>/boot/</filename> partition.
-					</para>
-				</listitem>
-
-				<listitem>
-					<para>
-						<emphasis>The Stage 2 or secondary boot loader is read into memory.</emphasis> The secondary boot loader displays the GRUB menu and command environment. This interface allows the user to select which kernel or operating system to boot, pass arguments
-						to the kernel, or look at system parameters.
-					</para>
-				</listitem>
-
-				<listitem>
-					<para>
-						<emphasis>The secondary boot loader reads the operating system or kernel as well as the contents of <filename>/boot/sysroot/</filename> into memory.</emphasis> Once GRUB determines which operating system or kernel to start, it loads
-						it into memory and transfers control of the machine to that operating system.
-					</para>
-				</listitem>
-			</orderedlist>
-			 
-			<para>
-				The method used to boot Linux is called <firstterm>direct loading</firstterm> because the boot loader loads the operating system directly. There is no intermediary between the boot loader and the kernel.
-			</para>
-			 
-			<para>
-				The boot process used by other operating systems may differ. For example, the <trademark class="registered">Microsoft</trademark> <trademark class="registered">Windows</trademark> operating system, as well as other operating systems, are loaded using
-				<firstterm>chain loading</firstterm>. Under this method, the MBR points to the first sector of the partition holding the operating system, where it finds the files necessary to actually boot that operating system.
-			</para>
-			 
-			<para>
-				GRUB supports both direct and chain loading boot methods, allowing it to boot almost any operating system.
-			</para>
-			 
-			<warning>
-				<title>Warning</title>
-
-				<para>
-					During installation, Microsoft's DOS and Windows installation programs completely overwrite the MBR, destroying any existing boot loaders. If creating a dual-boot system, it is best to install the Microsoft operating system first.
-				</para>
-			</warning>
-		</section>
-		 
-		<section id="s2-grub-whatis-features">
-			<title>Features of GRUB</title>
-			<indexterm significance="normal">
-				<primary>GRUB</primary>
-				<secondary>features</secondary>
-			</indexterm>
-			<para>
-				GRUB contains several features that make it preferable to other boot loaders available for the x86 architecture. Below is a partial list of some of the more important features:
-			</para>
-			 
-			<itemizedlist>
-				<listitem>
-					<para>
-						<emphasis>GRUB provides a true command-based, pre-OS environment on x86 machines.</emphasis> This feature affords the user maximum flexibility in loading operating systems with specified options or gathering information about the system. For years,
-						many non-x86 architectures have employed pre-OS environments that allow system booting from a command line.
-					</para>
-				</listitem>
-
-				<listitem>
-					<para>
-						<emphasis>GRUB supports <firstterm>Logical Block Addressing (LBA)</firstterm> mode.</emphasis> LBA places the addressing conversion used to find files in the hard drive's firmware, and is used on many IDE and all SCSI hard devices. Before LBA, boot
-						loaders could encounter the 1024-cylinder BIOS limitation, where the BIOS could not find a file after the 1024 cylinder head of the disk. LBA support allows GRUB to boot operating systems from partitions beyond the 1024-cylinder limit, so long as the
-						system BIOS supports LBA mode. Most modern BIOS revisions support LBA mode.
-					</para>
-				</listitem>
-
-				<listitem>
-					<para>
-						<emphasis>GRUB can read ext2 partitions.</emphasis> This functionality allows GRUB to access its configuration file, <filename>/boot/grub/grub.conf</filename>, every time the system boots, eliminating the need for the user to write a
-						new version of the first stage boot loader to the MBR when configuration changes are made. The only time a user needs to reinstall GRUB on the MBR is if the physical location of the <filename>/boot/</filename> partition is moved on
-						the disk. For details on installing GRUB to the MBR, refer to <xref linkend="s1-grub-installing"/>.
-					</para>
-				</listitem>
-			</itemizedlist>
-		</section>
-	</section>
-	<section id="s1-grub-installing">
-		<title>Installing GRUB</title>
-		<indexterm significance="normal">
-			<primary>GRUB</primary>
-			<secondary>installing</secondary>
-		</indexterm>
-		<para>
-			If GRUB was not installed during the installation process, it can be installed afterward. Once installed, it automatically becomes the default boot loader.
-		</para>
-		 
-		<para>
-			Before installing GRUB, make sure to use the latest GRUB package available or use the GRUB package from the installation CD-ROMs. <!-- (RHEL) For instructions on installing packages, refer to the chapter titled <citetitle>Package Management with RPM</citetitle> in
-			the <citetitle>Red Hat Enterprise Linux Deployment Guide</citetitle>. -->
-		</para>
-		 
-		<para>
-			Once the GRUB package is installed, open a root shell prompt and run the command <command>/sbin/grub-install <replaceable>&lt;location&gt;</replaceable></command>, where <replaceable>&lt;location&gt;</replaceable> is the location
-			that the GRUB Stage 1 boot loader should be installed. For example, the following command installs GRUB to the MBR of the master IDE device on the primary IDE bus:
-		</para>
-<screen>
-<command>/sbin/grub-install /dev/hda</command>
-</screen>
-		<para>
-			The next time the system boots, the GRUB graphical boot loader menu appears before the kernel loads into memory.
-		</para>
-		 
-		<important>
-			<title>Important â€” GRUB and RAID</title>
-			<indexterm significance="normal">
-			<primary>RAID</primary>
-			<secondary>system unbootable after disk failure</secondary>
-			</indexterm>
-			<para>
-				<application>GRUB</application> cannot construct a software RAID. Therefore, the <filename>/boot</filename> directory must reside on a single, specific disk partition. The <filename>/boot</filename> directory cannot be striped across multiple disks, as in a level 0 RAID. To use a level 0 RAID on your system, place /boot on a separate partition outside the RAID.
-			</para>
-			<para>
-				Similarly, because the <filename>/boot</filename> directory must reside on a single, specific disk partition, <application>GRUB</application> cannot boot the system if the disk holding that partition fails or is removed from the system. This is true even if the disk is mirrored in a level 1 RAID. The following Red Hat Knowledgebase article describes how to make the system bootable from another disk in the mirrored set: <ulink url="http://kbase.redhat.com/faq/docs/DOC-7095">http://kbase.redhat.com/faq/docs/DOC-7095</ulink> 
-			</para>
-			<para>
-				Note that these issues apply only to RAID that is implemented in software, where the individual disks that make up the array are still visible as individual disks on the system. These issues do not apply to hardware RAID where multiple disks are represented as a single device.
-			</para>
-		</important>
-	</section>
-	<section id="s1-grub-terminology">
-		<title>GRUB Terminology</title>
-		<indexterm significance="normal">
-			<primary>GRUB</primary>
-			<secondary>terminology</secondary>
-		</indexterm>
-		<para>
-			One of the most important things to understand before using GRUB is how the program refers to devices, such as hard drives and partitions. This information is particularly important when configuring GRUB to boot multiple operating systems.
-		</para>
-		 
-		<section id="s2-grub-terminology-devices">
-			<title>Device Names</title>
-			<indexterm significance="normal">
-				<primary>GRUB</primary>
-				<secondary>terminology</secondary>
-				<tertiary>devices</tertiary>
-			</indexterm>
-			<para>
-				When referring to a specific device with GRUB, do so using the following format (note that the parentheses and comma are very important syntactically):
-			</para>
-			 
-			<para>
-				<command> (<replaceable>&lt;type-of-device&gt;&lt;bios-device-number&gt;</replaceable>,<replaceable>&lt;partition-number&gt;</replaceable>) </command>
-			</para>
-			 
-			<para>
-				The <replaceable>&lt;type-of-device&gt;</replaceable> specifies the type of device from which GRUB boots. The two most common options are <command>hd</command> for a hard disk or <command>fd</command> for a 3.5
-				diskette. A lesser used device type is also available called <command>nd</command> for a network disk. Instructions on configuring GRUB to boot over the network are available online at
-				<ulink url="http://www.gnu.org/software/grub/manual/">http://www.gnu.org/software/grub/manual/</ulink>.
-			</para>
-			 
-			<para>
-				The <replaceable>&lt;bios-device-number&gt;</replaceable> is the BIOS device number. The primary IDE hard drive is numbered <command>0</command> and a secondary IDE hard drive is numbered <command>1</command>. This
-				syntax is roughly equivalent to that used for devices by the kernel. For example, the <command>a</command> in <command>hda</command> for the kernel is analogous to the <command>0</command> in
-				<command>hd0</command> for GRUB, the <command>b</command> in <command>hdb</command> is analogous to the <command>1</command> in <command>hd1</command>, and so on.
-			</para>
-			 
-			<para>
-				The <replaceable>&lt;partition-number&gt;</replaceable> specifies the number of a partition on a device. Like the <replaceable>&lt;bios-device-number&gt;</replaceable>, most types of partitions are numbered starting at
-				<command>0</command>. However, BSD partitions are specified using letters, with <command>a</command> corresponding to <command>0</command>, <command>b</command> corresponding to
-				<command>1</command>, and so on.
-			</para>
-			<note><title>Note</title>
-				<para>
-					The numbering system for devices under GRUB always begins with <command>0</command>, not <command>1</command>. Failing to make this distinction is one of the most common mistakes made by new users.
-				</para>
-			</note>
-			<para>
-				To give an example, if a system has more than one hard drive, GRUB refers to the first hard drive as <command>(hd0)</command> and the second as <command>(hd1)</command>. Likewise, GRUB refers to the first partition on
-				the first drive as <command>(hd0,0)</command> and the third partition on the second hard drive as <command>(hd1,2)</command>.
-			</para>
-			 
-			<para>
-				In general the following rules apply when naming devices and partitions under GRUB:
-			</para>
-			 
-			<itemizedlist>
-				<listitem>
-					<para>
-						It does not matter if system hard drives are IDE or SCSI, all hard drives begin with the letters <command>hd</command>. The letters <command>fd</command> are used to specify 3.5 diskettes.
-					</para>
-				</listitem>
-
-				<listitem>
-					<para>
-						To specify an entire device without respect to partitions, leave off the comma and the partition number. This is important when telling GRUB to configure the MBR for a particular disk. For example, <command>(hd0)</command> specifies
-						the MBR on the first device and <command>(hd3)</command> specifies the MBR on the fourth device.
-					</para>
-				</listitem>
-
-				<listitem>
-					<para>
-						If a system has multiple drive devices, it is very important to know how the drive boot order is set in the BIOS. This is a simple task if a system has only IDE or SCSI drives, but if there is a mix of devices, it becomes critical that the type of
-						drive with the boot partition be accessed first.
-					</para>
-				</listitem>
-			</itemizedlist>
-		</section>
-		 
-		<section id="s2-grub-terminology-files">
-			<title>File Names and Blocklists</title>
-			<indexterm significance="normal">
-				<primary>GRUB</primary>
-				<secondary>terminology</secondary>
-				<tertiary>files</tertiary>
-			</indexterm>
-			<para>
-				When typing commands to GRUB that reference a file, such as a menu list, it is necessary to specify an absolute file path immediately after the device and partition numbers.
-			</para>
-			 
-			<para>
-				The following illustrates the structure of such a command:
-			</para>
-			 
-			<para>
-				<command> (<replaceable>&lt;device-type&gt;&lt;device-number&gt;</replaceable>,<replaceable>&lt;partition-number&gt;</replaceable>)<replaceable>&lt;/path/to/file&gt;</replaceable> </command>
-			</para>
-			 
-			<para>
-				In this example, replace <replaceable>&lt;device-type&gt;</replaceable> with <command>hd</command>, <command>fd</command>, or <command>nd</command>. Replace <replaceable>&lt;device-number&gt;</replaceable> with the integer for the device. Replace <replaceable>&lt;/path/to/file&gt;</replaceable> with an absolute path relative to the top-level of the device.
-			</para>
-			 
-			<para>
-				It is also possible to specify files to GRUB that do not actually appear in the file system, such as a chain loader that appears in the first few blocks of a partition. To load such files, provide a <firstterm>blocklist</firstterm> that specifies block
-				by block where the file is located in the partition. Since a file is often comprised of several different sets of blocks, blocklists use a special syntax. Each block containing the file is specified by an offset number of blocks, followed by the number
-				of blocks from that offset point. Block offsets are listed sequentially in a comma-delimited list.
-			</para>
-			 
-			<para>
-				The following is a sample blocklist:
-			</para>
-<screen>
-<command>0+50,100+25,200+1</command>
-</screen>
-			<para>
-				This sample blocklist specifies a file that starts at the first block on the partition and uses blocks 0 through 49, 100 through 124, and 200.
-			</para>
-			 
-			<para>
-				Knowing how to write blocklists is useful when using GRUB to load operating systems which require chain loading. It is possible to leave off the offset number of blocks if starting at block 0. As an example, the chain loading file in the first
-				partition of the first hard drive would have the following name:
-			</para>
-<screen>
-<command>(hd0,0)+1</command>
-</screen>
-			<para>
-				The following shows the <command>chainloader</command> command with a similar blocklist designation at the GRUB command line after setting the correct device and partition as root:
-			</para>
-<screen>
-<command>chainloader +1</command>
-</screen>
-		</section>
-		 
-		<section id="s2-grub-terminology-rootfs">
-			<title>The Root File System and GRUB</title>
-			<indexterm significance="normal">
-				<primary>GRUB</primary>
-				<secondary>terminology</secondary>
-				<tertiary>root file system</tertiary>
-			</indexterm>
-			<para>
-				The use of the term <emphasis>root file system</emphasis> has a different meaning in regard to GRUB. It is important to remember that GRUB's root file system has nothing to do with the Linux root file system.
-			</para>
-			 
-			<para>
-				The GRUB root file system is the top level of the specified device. For example, the image file <command>(hd0,0)/grub/splash.xpm.gz</command> is located within the <filename>/grub/</filename> directory at the top-level
-				(or root) of the <command>(hd0,0)</command> partition (which is actually the <filename>/boot/</filename> partition for the system).
-			</para>
-			 
-			<para>
-				Next, the <command>kernel</command> command is executed with the location of the kernel file as an option. Once the Linux kernel boots, it sets up the root file system that Linux users are familiar with. The original GRUB root file
-				system and its mounts are forgotten; they only existed to boot the kernel file.
-			</para>
-			 
-			<para>
-				Refer to the <command>root</command> and <command>kernel</command> commands in <xref linkend="s1-grub-commands"/> for more information.
-			</para>
-		</section>
-	</section>
-	<section id="s1-grub-interfaces">
-		<title>GRUB Interfaces</title>
-		<indexterm significance="normal">
-			<primary>GRUB</primary>
-			<secondary>interfaces</secondary>
-		</indexterm>
-		<indexterm significance="normal">
-			<primary>GRUB</primary>
-			<secondary>interfaces</secondary>
-			<tertiary>menu</tertiary>
-		</indexterm>
-		<indexterm significance="normal">
-			<primary>GRUB</primary>
-			<secondary>interfaces</secondary>
-			<tertiary>menu entry editor</tertiary>
-		</indexterm>
-		<indexterm significance="normal">
-			<primary>GRUB</primary>
-			<secondary>changing runlevels with</secondary>
-		</indexterm>
-		<indexterm significance="normal">
-			<primary>runlevels</primary>
-			<secondary>changing with GRUB</secondary>
-		</indexterm>
-		<indexterm significance="normal">
-			<primary>GRUB</primary>
-			<secondary>interfaces</secondary>
-			<tertiary>command line</tertiary>
-		</indexterm>
-		<para>
-			GRUB features three interfaces which provide different levels of functionality. Each of these interfaces allows users to boot the Linux kernel or another operating system.
-		</para>
-		 
-		<para>
-			The interfaces are as follows:
-		</para>
-		 
-		<note>
-			<title>Note</title>
-
-			<para>
-				The following GRUB interfaces can only be accessed by pressing any key within the three seconds of the GRUB menu bypass screen.
-			</para>
-		</note>
-		 
-		<variablelist>
-			<varlistentry>
-				<term><emphasis>Menu Interface</emphasis></term>
-				<listitem>
-					<para>
-						This is the default interface shown when GRUB is configured by the installation program. A menu of operating systems or preconfigured kernels are displayed as a list, ordered by name. Use the arrow keys to select an operating system or kernel version and press the <keycap>Enter</keycap> key to boot it. If you do nothing on this screen, then after the time out period expires GRUB will load the default option.
-					</para>
-
-					<para>
-						Press the <keycap>e</keycap> key to enter the entry editor interface or the <keycap>c</keycap> key to load a command line interface.
-					</para>
-
-					<para>
-						Refer to <xref linkend="s1-grub-configfile"/> for more information on configuring this interface.
-					</para>
-				</listitem>
-			</varlistentry>
-
-			<varlistentry>
-				<term><emphasis>Menu Entry Editor Interface</emphasis></term>
-				<listitem>
-					<para>
-						To access the menu entry editor, press the <keycap>e</keycap> key from the boot loader menu. The GRUB commands for that entry are displayed here, and users may alter these command lines before booting the operating system by adding a
-						command line (<keycap>o</keycap> inserts a new line after the current line and <keycap>O</keycap> inserts a new line before it), editing one (<keycap>e</keycap>), or deleting one
-						(<keycap>d</keycap>).
-					</para>
-
-					<para>
-						After all changes are made, the <keycap>b</keycap> key executes the commands and boots the operating system. The <keycap>Esc</keycap> key discards any changes and reloads the standard menu interface. The
-						<keycap>c</keycap> key loads the command line interface.
-					</para>
-					<note><title>Note</title>
-						<para>
-							For information about changing runlevels using the GRUB menu entry editor, refer to <xref linkend="s1-grub-runlevels"/>.
-						</para>
-					</note>
-				</listitem>
-			</varlistentry>
-
-			<varlistentry>
-				<term><emphasis>Command Line Interface</emphasis></term>
-				<listitem>
-					<para>
-						The command line interface is the most basic GRUB interface, but it is also the one that grants the most control. The command line makes it possible to type any relevant GRUB commands followed by the <keycap>Enter</keycap> key to execute them. This interface features some advanced shell-like features, including <keycap>Tab</keycap> key completion based on context, and <keycap>Ctrl</keycap> key combinations when typing commands, such as <keycombo><keycap>Ctrl</keycap><keycap>a</keycap> </keycombo> to move to the beginning of a line and <keycombo><keycap>Ctrl</keycap><keycap>e</keycap> </keycombo> to move to the end of a line. In addition, the arrow, <keycap>Home</keycap>, <keycap>End</keycap>, and <keycap>Delete</keycap> keys work as they do in the <command>bash</command> shell.
-					</para>
-
-					<para>
-						Refer to <xref linkend="s1-grub-commands"/> for a list of common commands.
-					</para>
-				</listitem>
-			</varlistentry>
-		</variablelist>
-		 
-		<section id="s2-grub-interfaces-orderofuse">
-			<title>Interfaces Load Order</title>
-			<indexterm significance="normal">
-				<primary>GRUB</primary>
-				<secondary>interfaces</secondary>
-				<tertiary>order of</tertiary>
-			</indexterm>
-			<para>
-				When GRUB loads its second stage boot loader, it first searches for its configuration file. Once found, the menu interface bypass screen is displayed. If a key is pressed within three seconds, GRUB builds a menu list and displays the menu interface. If
-				no key is pressed, the default kernel entry in the GRUB menu is used.
-			</para>
-			 
-			<para>
-				If the configuration file cannot be found, or if the configuration file is unreadable, GRUB loads the command line interface, allowing the user to type commands to complete the boot process.
-			</para>
-			 
-			<para>
-				If the configuration file is not valid, GRUB prints out the error and asks for input. This helps the user see precisely where the problem occurred. Pressing any key reloads the menu interface, where it is then possible to edit the menu option and
-				correct the problem based on the error reported by GRUB. If the correction fails, GRUB reports an error and reloads the menu interface.
-			</para>
-		</section>
-	</section>
-	<section id="s1-grub-commands">
-		<title>GRUB Commands</title>
-		<indexterm significance="normal">
-			<primary>GRUB</primary>
-			<secondary>commands</secondary>
-		</indexterm>
-		<para>
-			GRUB allows a number of useful commands in its command line interface. Some of the commands accept options after their name; these options should be separated from the command and other options on that line by space characters.
-		</para>
-		 
-		<para>
-			The following is a list of useful commands:
-		</para>
-		 
-		<itemizedlist>
-			<listitem>
-				<para>
-					<command>boot</command> &mdash; Boots the operating system or chain loader that was last loaded.
-				</para>
-			</listitem>
-
-			<listitem>
-				<para>
-					<command>chainloader <replaceable>&lt;/path/to/file&gt;</replaceable></command> &mdash; Loads the specified file as a chain loader. If the file is located on the first sector of the specified partition, use the blocklist notation,
-					<command>+1</command>, instead of the file name.
-				</para>
-
-				<para>
-					The following is an example <command>chainloader</command> command:
-				</para>
-<screen>
-<command>chainloader +1</command>
-</screen>
-			</listitem>
-
-			<listitem>
-				<para>
-					<command>displaymem</command> &mdash; Displays the current use of memory, based on information from the BIOS. This is useful to determine how much RAM a system has prior to booting it.
-				</para>
-			</listitem>
-
-			<listitem>
-				<para>
-					<command>initrd <replaceable>&lt;/path/to/initrd&gt;</replaceable></command> &mdash; Enables users to specify an initial RAM disk to use when booting. An <filename>initrd</filename> is necessary when the kernel needs
-					certain modules in order to boot properly, such as when the root partition is formatted with the ext3 or ext4 file system.
-				</para>
-
-				<para>
-					The following is an example <command>initrd</command> command:
-				</para>
-<screen>
-<command>initrd /initrd-2.6.8-1.523.img</command>
-</screen>
-			</listitem>
-
-			<listitem>
-				<para>
-					<command>install <replaceable>&lt;stage-1&gt;</replaceable> <replaceable>&lt;install-disk&gt;</replaceable> <replaceable>&lt;stage-2&gt;</replaceable> <option>p</option> <replaceable>config-file</replaceable></command> &mdash;
-					Installs GRUB to the system MBR.
-				</para>
-
-				<itemizedlist>
-					<listitem>
-						<para>
-							<command><replaceable>&lt;stage-1&gt;</replaceable></command> &mdash; Signifies a device, partition, and file where the first boot loader image can be found, such as <command>(hd0,0)/grub/stage1</command>.
-						</para>
-					</listitem>
-
-					<listitem>
-						<para>
-							<command><replaceable>&lt;install-disk&gt;</replaceable></command> &mdash; Specifies the disk where the stage 1 boot loader should be installed, such as <command>(hd0)</command>.
-						</para>
-					</listitem>
-
-					<listitem>
-						<para>
-							<command><replaceable>&lt;stage-2&gt;</replaceable></command> &mdash; Passes the stage 2 boot loader location to the stage 1 boot loader, such as <command>(hd0,0)/grub/stage2</command>.
-						</para>
-					</listitem>
-
-					<listitem>
-						<para>
-							<option>p</option> <command><replaceable>&lt;config-file&gt;</replaceable></command> &mdash; This option tells the <command>install</command> command to look for the menu configuration file specified by
-							<command><replaceable>&lt;config-file&gt;</replaceable></command>, such as <command>(hd0,0)/grub/grub.conf</command>.
-						</para>
-					</listitem>
-				</itemizedlist>
-
-				<warning>
-					<title>Warning</title>
-
-					<para>
-						The <command>install</command> command overwrites any information already located on the MBR.
-					</para>
-				</warning>
-			</listitem>
-
-			<listitem>
-				<para>
-					<command>kernel <replaceable>&lt;/path/to/kernel&gt;</replaceable> <replaceable>&lt;option-1&gt;</replaceable> <replaceable>&lt;option-N&gt;</replaceable></command> ... &mdash; Specifies the kernel file to load when booting the
-					operating system. Replace <replaceable>&lt;/path/to/kernel&gt;</replaceable> with an absolute path from the partition specified by the root command. Replace <replaceable>&lt;option-1&gt;</replaceable> with options for the Linux kernel, such as
-					<command>root=/dev/VolGroup00/LogVol00</command> to specify the device on which the root partition for the system is located. Multiple options can be passed to the kernel in a space separated list.
-				</para>
-
-				<para>
-					The following is an example <command>kernel</command> command:
-				</para>
-<screen>
-<command>kernel /vmlinuz-2.6.8-1.523 ro root=/dev/VolGroup00/LogVol00</command>
-</screen>
-				<para>
-					The option in the previous example specifies that the root file system for Linux is located on the <command>hda5</command> partition.
-				</para>
-			</listitem>
-
-			<listitem>
-				<para>
-					<command>root (<replaceable>&lt;device-type&gt;</replaceable><replaceable>&lt;device-number&gt;</replaceable>,<replaceable>&lt;partition&gt;</replaceable>)</command> &mdash; Configures the root partition for GRUB, such as
-					<command>(hd0,0)</command>, and mounts the partition.
-				</para>
-
-				<para>
-					The following is an example <command>root</command> command:
-				</para>
-<screen>
-<command>root (hd0,0)</command>
-</screen>
-			</listitem>
-
-			<listitem>
-				<para>
-					<command>rootnoverify (<replaceable>&lt;device-type&gt;</replaceable><replaceable>&lt;device-number&gt;</replaceable>,<replaceable>&lt;partition&gt;</replaceable>)</command> &mdash; Configures the root partition for GRUB, just
-					like the <command>root</command> command, but does not mount the partition.
-				</para>
-			</listitem>
-		</itemizedlist>
-		 
-		<para>
-			Other commands are also available; type <command>help --all</command> for a full list of commands. For a description of all GRUB commands, refer to the documentation available online at
-			<ulink url="http://www.gnu.org/software/grub/manual/">http://www.gnu.org/software/grub/manual/</ulink>.
-		</para>
-	</section>
-	<section id="s1-grub-configfile">
-		<title>GRUB Menu Configuration File</title>
-		<indexterm significance="normal">
-			<primary>GRUB</primary>
-			<secondary>menu configuration file</secondary>
-		</indexterm>
-		<para>
-			The configuration file (<filename>/boot/grub/grub.conf</filename>), which is used to create the list of operating systems to boot in GRUB's menu interface, essentially allows the user to select a pre-set group of commands to execute. The
-			commands given in <xref linkend="s1-grub-commands"/> can be used, as well as some special commands that are only available in the configuration file.
-		</para>
-		 
-		<section id="s2-grub-configfile-structure">
-			<title>Configuration File Structure</title>
-			<indexterm significance="normal">
-				<primary>GRUB</primary>
-				<secondary>configuration file</secondary>
-				<tertiary>structure</tertiary>
-			</indexterm>
-			<indexterm significance="normal">
-				<primary>GRUB</primary>
-				<secondary>configuration file</secondary>
-				<tertiary><filename>/boot/grub/grub.conf</filename>
-				</tertiary>
-			</indexterm>
-			<indexterm significance="normal">
-				<primary><filename>grub.conf</filename>
-				</primary>
-				<seealso>GRUB</seealso>
-			</indexterm>
-			<para>
-				The GRUB menu interface configuration file is <filename>/boot/grub/grub.conf</filename>. The commands to set the global preferences for the menu interface are placed at the top of the file, followed by stanzas for each operating kernel
-				or operating system listed in the menu.
-			</para>
-			 
-			<para>
-				The following is a very basic GRUB menu configuration file designed to boot either Fedora or Microsoft Windows Vista:
-			</para>
-<!-- (RHEL) <screen>default=0 
-timeout=10 
-splashimage=(hd0,0)/grub/splash.xpm.gz 
-hiddenmenu 
-title Fedora Server (2.6.18-2.el5PAE)         
-root (hd0,0)         
-kernel /boot/vmlinuz-2.6.18-2.el5PAE ro root=LABEL=/1 rhgb quiet       
-initrd /boot/initrd-2.6.18-2.el5PAE.img
-
-# section to load Windows 
-title Windows         
-rootnoverify (hd0,0)         
-chainloader +1
-</screen> -->
-
-<screen>default=0 
-timeout=10 
-splashimage=(hd0,0)/grub/splash.xpm.gz 
-hiddenmenu 
-title Fedora (2.6.27.19-170.2.35.fc10.i686)
-root (hd0,1)
-kernel /vmlinuz-2.6.27.19-170.2.35.fc10.i686 ro root=UUID=04a07c13-e6bf-6d5a-b207-002689545705 rhgb quiet
-initrd /initrd-2.6.27.19-170.2.35.fc10.i686.img 
-
-# section to load Windows 
-title Windows         
-rootnoverify (hd0,0)         
-chainloader +1
-</screen>
-
-			<para>
-				This file configures GRUB to build a menu with Fedora as the default operating system and sets it to autoboot after 10 seconds. Two sections are given, one for each operating system entry, with commands specific to the system disk
-				partition table.
-			</para>
-			 
-			<note>
-				<title>Note</title>
-
-				<para>
-					Note that the default is specified as an integer. This refers to the first <command>title</command> line in the GRUB configuration file. For the <command>Windows</command> section to be set as the default in the
-					previous example, change the <command>default=0</command> to <command>default=1</command>.
-				</para>
-			</note>
-			 
-			<para>
-				Configuring a GRUB menu configuration file to boot multiple operating systems is beyond the scope of this chapter. Consult <xref linkend="s1-grub-additional-resources"/> for a list of additional resources.
-			</para>
-		</section>
-		 
-		<section id="s2-grub-configfile-commands">
-			<title>Configuration File Directives</title>
-			<indexterm significance="normal">
-				<primary>GRUB</primary>
-				<secondary>menu configuration file</secondary>
-				<tertiary>directives</tertiary>
-			</indexterm>
-			<para>
-				The following are directives commonly used in the GRUB menu configuration file:
-			</para>
-			 
-			<itemizedlist>
-				<listitem>
-					<para>
-						<command>chainloader <replaceable>&lt;/path/to/file&gt;</replaceable></command> &mdash; Loads the specified file as a chain loader. Replace <replaceable>&lt;/path/to/file&gt;</replaceable> with the absolute path to the chain
-						loader. If the file is located on the first sector of the specified partition, use the blocklist notation, <command>+1</command>.
-					</para>
-				</listitem>
-
-				<listitem>
-					<para>
-						<command>color <replaceable>&lt;normal-color&gt;</replaceable> <replaceable>&lt;selected-color&gt;</replaceable></command> &mdash; Allows specific colors to be used in the menu, where two colors are configured as the foreground
-						and background. Use simple color names such as <command>red/black</command>. For example:
-					</para>
-<screen>
-<command>color red/black green/blue</command>
-</screen>
-				</listitem>
-
-				<listitem>
-					<para>
-						<command>default=<replaceable>&lt;integer&gt;</replaceable></command> &mdash; Replace <replaceable>&lt;integer&gt;</replaceable> with the default entry title number to be loaded if the menu interface times out.
-					</para>
-				</listitem>
-
-				<listitem>
-					<para>
-						<command>fallback=<replaceable>&lt;integer&gt;</replaceable></command> &mdash; Replace <replaceable>&lt;integer&gt;</replaceable> with the entry title number to try if the first attempt fails.
-					</para>
-				</listitem>
-
-				<listitem>
-					<para>
-						<command>hiddenmenu</command> &mdash; Prevents the GRUB menu interface from being displayed, loading the <command>default</command> entry when the <command>timeout</command> period expires. The user
-						can see the standard GRUB menu by pressing the <keycap>Esc</keycap> key.
-					</para>
-				</listitem>
-
-				<listitem>
-					<para>
-						<command>initrd <replaceable>&lt;/path/to/initrd&gt;</replaceable></command> &mdash; Enables users to specify an initial RAM disk to use when booting. Replace <replaceable>&lt;/path/to/initrd&gt;</replaceable> with the absolute
-						path to the initial RAM disk.
-					</para>
-				</listitem>
-
-				<listitem>
-					<para>
-						<command>kernel <replaceable>&lt;/path/to/kernel&gt;</replaceable> <replaceable>&lt;option-1&gt;</replaceable> <replaceable>&lt;option-N&gt;</replaceable></command> &mdash; Specifies the kernel file to load when booting the
-						operating system. Replace <replaceable>&lt;/path/to/kernel&gt;</replaceable> with an absolute path from the partition specified by the root directive. Multiple options can be passed to the kernel when it is loaded.
-					</para>
-					<para>
-						These options include:
-						<itemizedlist>
-							<listitem>
-								<para>
-									<literal>rhgb</literal> (<firstterm>Red Hat graphical boot</firstterm>) &mdash; displays an animation during the boot process, rather than lines of text.
-								</para>
-							</listitem>
-							<listitem>
-								<para>
-									<literal>quiet</literal> &mdash; suppresses all but the most important messages in the part of the boot sequence before the Red Hat graphical boot animation begins.
-								</para>
-							</listitem>
-						</itemizedlist>
-					</para>
-				</listitem>
-
-				<listitem>
-					<para>
-						<command>password=<replaceable>&lt;password&gt;</replaceable></command> &mdash; Prevents a user who does not know the password from editing the entries for this menu option.
-					</para>
-
-					<para>
-						Optionally, it is possible to specify an alternate menu configuration file after the <command>password=<replaceable>&lt;password&gt;</replaceable></command> directive. In this case, GRUB restarts the second stage boot loader and
-						uses the specified alternate configuration file to build the menu. If an alternate menu configuration file is left out of the command, a user who knows the password is allowed to edit the current configuration file.
-					</para>
-
-					<para>
-						For more information about securing GRUB, refer to the chapter titled <citetitle>Workstation Security</citetitle> in the <citetitle>Red Hat Enterprise Linux Deployment Guide</citetitle>.
-					</para>
-				</listitem>
-				
-				<listitem>
-					<para>
-						<command>map</command> &mdash; Swaps the numbers assigned to two hard drives. For example:
-					</para>
-<screen>map (hd0) (hd3)
-map (hd3) (hd0)</screen>
-					<para>
-						assigns the number <literal>0</literal> to the fourth hard drive, and the number <literal>3</literal> to the first hard drive. This option is especially useful if you configure your system with an option to boot a Windows operating system, becausehe Windows boot loader must find the Windows installation on the first hard drive.
-					</para>
-					<para>
-						For example, if your Windows installation is on the fourth hard drive, the following entry in <filename>grub.conf</filename> will allow the Windows boot loader to load Windows correctly:
-					</para>
-<screen>title Windows
-map (hd0) (hd3)
-map (hd3) (hd0)
-rootnoverify (hd3,0)
-chainloader +1
-</screen>
-				</listitem>
-
-				<listitem>
-					<para>
-						<command>root (<replaceable>&lt;device-type&gt;</replaceable><replaceable>&lt;device-number&gt;</replaceable>,<replaceable>&lt;partition&gt;</replaceable>)</command> &mdash; Configures the root partition for GRUB, such as
-						<command>(hd0,0)</command>, and mounts the partition.
-					</para>
-				</listitem>
-
-				<listitem>
-					<para>
-						<command>rootnoverify (<replaceable>&lt;device-type&gt;</replaceable><replaceable>&lt;device-number&gt;</replaceable>,<replaceable>&lt;partition&gt;</replaceable>)</command> &mdash; Configures the root partition for GRUB, just
-						like the <command>root</command> command, but does not mount the partition.
-					</para>
-				</listitem>
-
-				<listitem>
-					<para>
-						<command>timeout=<replaceable>&lt;integer&gt;</replaceable></command> &mdash; Specifies the interval, in seconds, that GRUB waits before loading the entry designated in the <command>default</command> command.
-					</para>
-				</listitem>
-
-				<listitem>
-					<para>
-						<command>splashimage=<replaceable>&lt;path-to-image&gt;</replaceable></command> &mdash; Specifies the location of the splash screen image to be used when GRUB boots.
-					</para>
-				</listitem>
-
-				<listitem>
-					<para>
-						<command>title <replaceable>group-title</replaceable></command> &mdash; Specifies a title to be used with a particular group of commands used to load a kernel or operating system.
-					</para>
-				</listitem>
-			</itemizedlist>
-			 
-			<para>
-				To add human-readable comments to the menu configuration file, begin the line with the hash mark character (<command>#</command>).
-			</para>
-		</section>
-	</section>
-	<section id="s1-grub-runlevels">
-		<title>Changing Runlevels at Boot Time</title>
-		<indexterm significance="normal">
-			<primary>GRUB</primary>
-			<secondary>Changing Runlevels at Boot Time</secondary>
-		</indexterm>
-		<para>
-			Under Fedora, it is possible to change the default runlevel at boot time.
-		</para>
-		 
-		<para>
-			To change the runlevel of a single boot session, use the following instructions:
-		</para>
-		 
-		<itemizedlist>
-			<listitem>
-				<para>
-					When the GRUB menu bypass screen appears at boot time, press any key to enter the GRUB menu (within the first three seconds).
-				</para>
-			</listitem>
-
-			<listitem>
-				<para>
-					Press the <keycap>a</keycap> key to append to the <command>kernel</command> command.
-				</para>
-			</listitem>
-
-			<listitem>
-				<para>
-					Add <command>&lt;space&gt;<replaceable>&lt;runlevel&gt;</replaceable></command> at the end of the boot options line to boot to the desired runlevel. For example, the following entry would initiate a boot process into runlevel 3:
-				</para>
-<screen>
-<command>grub append&gt; ro root=/dev/VolGroup00/LogVol00 rhgb quiet 3</command>
-</screen>
-			</listitem>
-		</itemizedlist>
-	</section>
-	<section id="s1-grub-additional-resources">
-		<title>Additional Resources</title>
-		<indexterm significance="normal">
-			<primary>GRUB</primary>
-			<secondary>additional resources</secondary>
-		</indexterm>
-		<para>
-			This chapter is only intended as an introduction to GRUB. Consult the following resources to discover more about how GRUB works.
-		</para>
-		 
-		<section id="s2-grub-installed-documentation">
-			<title>Installed Documentation</title>
-			<indexterm significance="normal">
-				<primary>GRUB</primary>
-				<secondary>additional resources</secondary>
-				<tertiary>installed documentation</tertiary>
-			</indexterm>
-			<itemizedlist>
-				<listitem>
-					<para>
-						<filename>/usr/share/doc/grub-<replaceable>&lt;version-number&gt;</replaceable>/</filename> &mdash; This directory contains good information about using and configuring GRUB, where <replaceable>&lt;version-number&gt;</replaceable> corresponds to the version of the GRUB package installed.
-					</para>
-				</listitem>
-
-				<listitem>
-					<para>
-						<command>info grub</command> &mdash; The GRUB info page contains a tutorial, a user reference manual, a programmer reference manual, and a FAQ document about GRUB and its usage.
-					</para>
-				</listitem>
-			</itemizedlist>
-		</section>
-		 
-		<section id="s2-grub-useful-websites">
-			<title>Useful Websites</title>
-			<indexterm significance="normal">
-				<primary>GRUB</primary>
-				<secondary>additional resources</secondary>
-				<tertiary>useful websites</tertiary>
-			</indexterm>
-			<itemizedlist>
-				<listitem>
-					<para>
-						<ulink url="http://www.gnu.org/software/grub">http://www.gnu.org/software/grub/</ulink> &mdash; The home page of the GNU GRUB project. This site contains information concerning the state of GRUB development and an FAQ.
-					</para>
-				</listitem>
-
-				<listitem>
-					<para>
-						<ulink url="http://kbase.redhat.com/faq/docs/DOC-6864">http://kbase.redhat.com/faq/docs/DOC-6864</ulink> &mdash; Details booting operating systems other
-						than Linux.
-					</para>
-				</listitem>
-
-				<!-- DEAD LINK <listitem>
-					<para>
-						<ulink url="http://www.linuxgazette.com/issue64/kohli.html">http://www.linuxgazette.com/issue64/kohli.html</ulink> &mdash; An introductory article discussing the configuration of GRUB on a system from scratch, including an overview of GRUB command
-						line options.
-					</para>
-				</listitem> -->
-			</itemizedlist>
-		</section>
-		 
-		<section id="s2-grub-related-books">
-			<title>Related Books</title>
-			<indexterm significance="normal">
-				<primary>GRUB</primary>
-				<secondary>additional resources</secondary>
-				<tertiary>related books</tertiary>
-			</indexterm>
-			<itemizedlist>
-				<listitem>
-					<para>
-						<citetitle>Red Hat Enterprise Linux Deployment Guide</citetitle>; Red Hat, Inc. &mdash; The <citetitle>Workstation Security</citetitle> chapter explains, in a concise manner, how to secure the GRUB boot loader.
-					</para>
-					<para>
-					You can find the current version of the <citetitle>Red Hat Enterprise Linux Deployment Guide</citetitle> at <ulink url="http://www.redhat.com/docs/manuals/enterprise/"></ulink>. In the version of the book for Red Hat Enterprise Linux 5, the relevant section is <citetitle>43.1.2. BIOS and Boot Loader Security</citetitle>: <ulink url="
-					http://www.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/5/html/Deployment_Guide/ch-sec-network.html#s1-wstation-boot-sec"></ulink>.
-					</para>
-				</listitem>
-			</itemizedlist>
-		</section>
-	</section>
-</appendix>
diff --git a/en-US/Important-Enable_EPEL.xml b/en-US/Important-Enable_EPEL.xml
deleted file mode 100644
index 3aeadf1..0000000
--- a/en-US/Important-Enable_EPEL.xml
+++ /dev/null
@@ -1,14 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-<!DOCTYPE important PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
- "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
-]>
-
-<important>
-	<title>
-		Important â€” Enable Extra Packages for Enterprise Linux
-	</title>
-	<para>
-		To perform this procedure on Red Hat Enterprise Linux and Linux distributions derived from it, enable the <firstterm>Extra Packages for Enterprise Linux</firstterm> (EPEL) repository. Refer to <ulink url="http://fedoraproject.org/wiki/EPEL/FAQ#howtouse"></ulink> for instructions.
-	</para>
-</important>
-
diff --git a/en-US/Important-Kickstart_and_Firstboot.xml b/en-US/Important-Kickstart_and_Firstboot.xml
deleted file mode 100644
index c50a119..0000000
--- a/en-US/Important-Kickstart_and_Firstboot.xml
+++ /dev/null
@@ -1,10 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE important PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<important>
-	<title>Important â€” Kickstart installations and Firstboot</title>
-	<para>
-		<application>Firstboot</application> does not run after a system is installed from this Kickstart file. Either specify a user with the <option>user</option> option in the Kickstart file before installing additional systems from it (refer to <xref linkend="s1-kickstart2-options"/> for details) or log into the installed system with a virtual console as root and add users with the <command>adduser</command> command. 
-	</para>
-</important>
diff --git a/en-US/Important_UEFI.xml b/en-US/Important_UEFI.xml
deleted file mode 100644
index 2a7a23d..0000000
--- a/en-US/Important_UEFI.xml
+++ /dev/null
@@ -1,14 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE important PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<important>
-	<title>Important â€” Booting Older Systems from CD or DVD Media</title>
-	<para>
-		The CD and DVD media include boot catalog entries for both BIOS and UEFI firmware interfaces. This allows you to boot systems based on either firmware interface from the same CD or DVD. However, some systems with very old BIOS implementations cannot handle media with more than one boot catalog entry. These systems will not boot from the CD or DVD and you must instead boot them from USB or PXE. 
-	</para>
-	<para>
-		Note that the boot configurations of UEFI and BIOS differ significantly from each other. Therefore, the installed system must boot using the same firmware that was used during installation. You cannot install the operating system on a system that uses BIOS and then boot this installation on a system that uses UEFI. 
-	</para>
-</important>
-
diff --git a/en-US/Initializing_Hard_Disk-x86.xml b/en-US/Initializing_Hard_Disk-x86.xml
deleted file mode 100644
index 8c91060..0000000
--- a/en-US/Initializing_Hard_Disk-x86.xml
+++ /dev/null
@@ -1,40 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<section id="sn-initialize-hdd-x86">
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" 
-	href="Initializing_Hard_Disk_common-title.xml"/>
-	<!-- Title: Initializing the Hard Disk -->
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" 
-	href="Initializing_Hard_Disk_common-indexterm.xml"/>
-
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" 
-	href="Initializing_Hard_Disk_common-para-1.xml"/>
-	<!-- If no readable partition tables are found on existing hard disks... -->
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" 
-	href="Initializing_Hard_Disk_common-para-3.xml"/>
-	<!-- The installation program presents you with a separate dialog for each disk... -->
-	
-	<figure float="0" id="fig-initializing-x86"><title>Warning screen &ndash; initializing hard drive</title>
-		<mediaobject>
-			<imageobject><imagedata fileref="images/initializing/initializing.png" format="PNG"/></imageobject>
-			<textobject><para>
-					Warning screen &ndash; initializing hard drive.
-				</para>
-			</textobject>
-		</mediaobject>
-	</figure>
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" 
-	href="Initializing_Hard_Disk_common-para-2.xml"/>
-	<!-- Certain RAID systems or other nonstandard configurations... -->
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" 
-	href="Initializing_Hard_Disk_common-note-1.xml"/>
-	<!-- Detach Unneeded Disks -->
-		
-</section>
-
diff --git a/en-US/Initializing_Hard_Disk_common-indexterm.xml b/en-US/Initializing_Hard_Disk_common-indexterm.xml
deleted file mode 100644
index a1cc0a2..0000000
--- a/en-US/Initializing_Hard_Disk_common-indexterm.xml
+++ /dev/null
@@ -1,9 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE indexterm PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<indexterm significance="normal">
-	<primary>Hard disk</primary>
-	<secondary>initializing</secondary>
-</indexterm>
-
diff --git a/en-US/Initializing_Hard_Disk_common-note-1.xml b/en-US/Initializing_Hard_Disk_common-note-1.xml
deleted file mode 100644
index 4371646..0000000
--- a/en-US/Initializing_Hard_Disk_common-note-1.xml
+++ /dev/null
@@ -1,12 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-    <warning>
-      <title>Detach Unneeded Disks</title>
-      <para>If you have a nonstandard disk configuration that can be
-	detached during installation and detected and configured
-	afterward, power off the system, detach it, and restart the
-	installation.</para>
-    </warning>
-
diff --git a/en-US/Initializing_Hard_Disk_common-para-1.xml b/en-US/Initializing_Hard_Disk_common-para-1.xml
deleted file mode 100644
index 0be9422..0000000
--- a/en-US/Initializing_Hard_Disk_common-para-1.xml
+++ /dev/null
@@ -1,9 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-    <para>
-      If no readable partition tables are found on existing hard disks, the installation program asks to initialize the hard disk. This operation makes any existing data on the hard disk unreadable.  If your system has a brand new hard disk with no operating system installed, or you have removed all partitions on the hard disk, click <guibutton>Re-initialize drive</guibutton>.
-    </para>
-    
-
diff --git a/en-US/Initializing_Hard_Disk_common-para-2.xml b/en-US/Initializing_Hard_Disk_common-para-2.xml
deleted file mode 100644
index 3d798b6..0000000
--- a/en-US/Initializing_Hard_Disk_common-para-2.xml
+++ /dev/null
@@ -1,9 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-    <para>
-      Certain RAID systems or other nonstandard configurations may be unreadable to the installation program and the prompt to initialize the hard disk may appear.  The installation program responds to the physical disk structures it is able to detect.
-    </para>
-    
-
diff --git a/en-US/Initializing_Hard_Disk_common-para-3.xml b/en-US/Initializing_Hard_Disk_common-para-3.xml
deleted file mode 100644
index b1a9060..0000000
--- a/en-US/Initializing_Hard_Disk_common-para-3.xml
+++ /dev/null
@@ -1,9 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<para>
-	The installation program presents you with a separate dialog for each disk on which it cannot read a valid partition table. Click the <guibutton>Ignore all</guibutton> button or <guibutton>Re-initialize all</guibutton> button to apply the same answer to all devices. 
-</para>
-    
-
diff --git a/en-US/Initializing_Hard_Disk_common-title.xml b/en-US/Initializing_Hard_Disk_common-title.xml
deleted file mode 100644
index 3e12d0b..0000000
--- a/en-US/Initializing_Hard_Disk_common-title.xml
+++ /dev/null
@@ -1,6 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE title PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<title>Initializing the Hard Disk</title>
-
diff --git a/en-US/Installation_Guide.ent b/en-US/Installation_Guide.ent
deleted file mode 100644
index 0dbe2dc..0000000
--- a/en-US/Installation_Guide.ent
+++ /dev/null
@@ -1,6 +0,0 @@
-<!ENTITY PRODUCT "Fedora Documentation">
-<!ENTITY PRODVER "13">
-<!ENTITY PREVVER "12">
-<!ENTITY BOOKID "install-guide">
-<!ENTITY YEAR "2010">
-<!ENTITY HOLDER "Red Hat, Inc. and others">
diff --git a/en-US/Installation_Guide.xml b/en-US/Installation_Guide.xml
deleted file mode 100644
index 15905f6..0000000
--- a/en-US/Installation_Guide.xml
+++ /dev/null
@@ -1,148 +0,0 @@
-<?xml version='1.0'?>
-<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
-]>
-
-<book>
-	<xi:include href="Book_Info.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
-	<xi:include href="Preface.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> 
-	<xi:include href="intro.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
-	<xi:include href="expert-quickstart.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
-	<part id="pt-Preparing_for_Installation">
-	<title>Preparing for Installation</title>
-		<partintro>
-			<para>
-				This part of the <citetitle>Fedora Installation Guide</citetitle> covers decisions that you should make and resources that you should gather before installing Fedora, including:
-			</para>
-			<itemizedlist>
-				<listitem>
-					<para>
-						the decision whether to upgrade an existing installation of Fedora or install a new copy.
-					</para>
-				</listitem>
-				<listitem>
-					<para>
-						hardware considerations, and hardware details that you may need during installation.
-					</para>
-				</listitem>
-				<listitem>
-					<para>
-						preparing to install Fedora over a network.
-					</para>
-				</listitem>
-				<!-- <listitem>
-					<para>
-						preparing driver media.
-					</para>
-				</listitem> -->
-			</itemizedlist>
-		</partintro>
-		<xi:include href="new-users.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
-		<xi:include href="Making_Fedora_Media.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
-		<xi:include href="Steps-x86.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
-		<xi:include href="System_Requirements_Table.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
-		
-	</part>
-	<part id="pt-The_installation_process">
-	<title>The installation process</title>
-	<partintro>
-			<para>
-				This part of the <citetitle>Fedora Installation Guide</citetitle> details the installation process itself, from various methods of booting the installer up to the point where the computer must restart to finalize the installation. This part of the manual also includes a chapter on troubleshooting problems with the installation process.
-			</para>
-	</partintro>
-		<xi:include href="Boot-x86.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
-		<xi:include href="Graphical_Installation-x86.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
-		<xi:include href="Trouble-x86.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
-	</part>
-	<part id="pt-Advanced_installation_options">
-	<title>Advanced installation options</title>
-	<partintro>
-			<para>
-				This part of the <citetitle>Fedora Installation Guide</citetitle> covers more complex and uncommon methods of installing Fedora, including:
-			</para>
-			<itemizedlist>
-				<!-- <listitem>
-					<para>
-						updating drivers during installation.
-					</para>
-				</listitem> -->
-				<listitem>
-					<para>
-						boot options.
-					</para>
-				</listitem>
-				<listitem>
-					<para>
-						installing without media.
-					</para>
-				</listitem>
-				<listitem>
-					<para>
-						installing through VNC.
-					</para>
-				</listitem>
-				<listitem>
-					<para>
-						using <application>kickstart</application> to automate the installation process.
-					</para>
-				</listitem>
-			</itemizedlist>
-	</partintro>
-		<!-- <xi:include href="DU-Updating_drivers_during_installation_x86.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/> -->
-		<xi:include href="adminoptions.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
-		<xi:include href="medialess.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/> 
-		<xi:include href="pxe-server.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
-		<xi:include href="vnc_VNC_Whitepaper.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
-		<xi:include href="Kickstart2.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
-		<xi:include href="Ksconfig.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
-	</part>
-	<part id="pt-After_installation">
-	<title>After installation</title>
-	<partintro>
-			<para>
-				This part of the <citetitle>Fedora Installation Guide</citetitle> covers finalizing the installation, as well as some installation-related tasks that you might perform at some time in the future. These include:
-			</para>
-			<itemizedlist>
-				<listitem>
-					<para>
-						using a Fedora installation disk to rescue a damaged system.
-					</para>
-				</listitem>
-				<listitem>
-					<para>
-						upgrading to a new version of Fedora.
-					</para>
-				</listitem>
-				<listitem>
-					<para>
-						removing Fedora from your computer.
-					</para>
-				</listitem>
-			</itemizedlist>
-	</partintro>
-		<xi:include href="firstboot.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
-		<xi:include href="nextsteps.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/> 
-		<xi:include href="Rescue_Mode.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
-		<xi:include href="Upgrade-x86.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
-		<xi:include href="X86_Uninstall.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
-	</part>
-	<!-- Appendixes -->
-	<part id="pt-Technical_appendixes">
-	<title>Technical appendixes</title>
-	<partintro>
-			<para>
-				The appendixes in this section do not contain instructions that tell you how to install Fedora. Instead, they provide technical background that you might find helpful to understand the options that Fedora offers you at various points in the installation process. 
-			</para>
-	</partintro>
-		<xi:include href="Partitions-x86.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
-		<xi:include href="iSCSI.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
-		<xi:include href="DiskEncryptionUserGuide.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
-		<xi:include href="Understanding_LVM.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
-		<xi:include href="Grub.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
-		<xi:include href="Boot_Init_Shutdown.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
-		<xi:include href="techref.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
-	</part>
-	<xi:include href="Contributors_and_production_methods.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
-	<xi:include href="Revision_History.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> 
-	<index />
-</book>
-
diff --git a/en-US/Installation_Method-x86.xml b/en-US/Installation_Method-x86.xml
deleted file mode 100644
index 916ba9e..0000000
--- a/en-US/Installation_Method-x86.xml
+++ /dev/null
@@ -1,44 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<section id="s1-installationmethod-x86">
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" 
-	href="Installation_Method_common-title.xml"/>
-	<!-- Title: Language Selection -->
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" 
-	href="Installation_Method_common-indexterm.xml"/>
-
-	<para>
-		Use the arrow keys on your keyboard to select an installation method (refer to <xref linkend="fig-installationmethod-x86"/>). With your selected method highlighted, press the <keycap>Tab</keycap> key to move to the <guibutton>OK</guibutton> button and press the <keycap>Enter</keycap> key to confirm your choice.
-	</para>
-
-	<figure float="0" id="fig-installationmethod-x86"><title>Language Selection</title>
-		<mediaobject>
-			<imageobject><imagedata fileref="images/installationmethod/method.png" format="PNG"/></imageobject>
-			<textobject><para>
-					Installation method screen.
-				</para>
-			</textobject>
-		</mediaobject>
-	</figure>
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Beginning_Installation-x86.xml"/>
-	<!-- Installing from CD-ROM or DVD-->
-	     
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Beginning_Installation_Hard_Disk-x86.xml"/>
-	<!-- Installing from a Hard Drive -->
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Beginning_Installation_Network-x86.xml"/>
-	<!-- Performing a Network Installation  -->
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Beginning_Installation_NFS-x86.xml"/>
-	<!-- Installing via NFS -->
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Beginning_Installation_URL-x86.xml"/> 
-	<!-- Installing via FTP or HTTP -->
-	
-
-</section>
-
diff --git a/en-US/Installation_Method_common-indexterm.xml b/en-US/Installation_Method_common-indexterm.xml
deleted file mode 100644
index 0d51156..0000000
--- a/en-US/Installation_Method_common-indexterm.xml
+++ /dev/null
@@ -1,9 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE indexterm PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<indexterm significance="normal">
-	<primary>installation method</primary>
-	<secondary>selecting</secondary>
-</indexterm>
-
diff --git a/en-US/Installation_Method_common-title.xml b/en-US/Installation_Method_common-title.xml
deleted file mode 100644
index 9e012c0..0000000
--- a/en-US/Installation_Method_common-title.xml
+++ /dev/null
@@ -1,6 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE title PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<title>Installation Method</title>
-
diff --git a/en-US/Installing_Packages-x86.xml b/en-US/Installing_Packages-x86.xml
deleted file mode 100644
index be006a1..0000000
--- a/en-US/Installing_Packages-x86.xml
+++ /dev/null
@@ -1,27 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<section id="s1-installpkgs-x86">
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Installing_Packages_common-title.xml"/>
-	<!-- Installing Packages -->
-	 
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Installing_Packages_common-para-1.xml"/>
-	<!-- At this point there is nothing left for you to do until -->
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Installing_Packages_common-para-2.xml"/>
-	<!-- Fedora reports the installation progress on the screen -->
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Installing_Packages_common-para-2a.xml"/>
-	<!-- For your reference, a complete log of your installation can be found -->
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Installing_Packages_common-para-3.xml"/>
-	<!-- After installation completes, select Reboot -->
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Installing_Packages_common-note-1.xml"/>
-	<!-- Installing from a Live Image -->
-	
-</section>
diff --git a/en-US/Installing_Packages_common-note-1.xml b/en-US/Installing_Packages_common-note-1.xml
deleted file mode 100644
index aa766c3..0000000
--- a/en-US/Installing_Packages_common-note-1.xml
+++ /dev/null
@@ -1,13 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
- "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
-]>
-
-  <note>
-    <title>Installing from a Live Image</title>
-    <para>If you install from a Fedora Live image, no reboot prompt
-      appears.  You may continue to use the Live image as desired, and
-      reboot the system at any time to enjoy the newly installed
-      Fedora system.</para>
-  </note>
-  
\ No newline at end of file
diff --git a/en-US/Installing_Packages_common-para-1.xml b/en-US/Installing_Packages_common-para-1.xml
deleted file mode 100644
index 41122bb..0000000
--- a/en-US/Installing_Packages_common-para-1.xml
+++ /dev/null
@@ -1,7 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<para>
-	At this point there is nothing left for you to do until all the packages have been installed. How quickly this happens depends on the number of packages you have selected and your computer's speed.
-</para>
\ No newline at end of file
diff --git a/en-US/Installing_Packages_common-para-2.xml b/en-US/Installing_Packages_common-para-2.xml
deleted file mode 100644
index 9912d36..0000000
--- a/en-US/Installing_Packages_common-para-2.xml
+++ /dev/null
@@ -1,12 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
- "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
-]>
-
-  <para>
-    Fedora reports the installation progress on the screen as it writes
-    the selected packages to your system.  Network and DVD installations
-    require no further action. If you are using CDs to install, Fedora
-    prompts you to change discs periodically. After you insert a disc,
-    select <guibutton>OK</guibutton> to resume the installation.
-  </para>
diff --git a/en-US/Installing_Packages_common-para-2a.xml b/en-US/Installing_Packages_common-para-2a.xml
deleted file mode 100644
index e9487eb..0000000
--- a/en-US/Installing_Packages_common-para-2a.xml
+++ /dev/null
@@ -1,17 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<para>
-	<indexterm significance="normal">
-		<primary>install log file</primary>
-		<secondary><filename>/root/install.log</filename>
-		</secondary>
-	</indexterm>
-	<indexterm significance="normal">
-		<primary><filename>/root/install.log</filename>
-		</primary>
-		<secondary>install log file location</secondary>
-	</indexterm>
-	For your reference, a complete log of your installation can be found in <filename>/root/install.log</filename> once you reboot your system.
-</para>
diff --git a/en-US/Installing_Packages_common-para-3.xml b/en-US/Installing_Packages_common-para-3.xml
deleted file mode 100644
index 4914f5c..0000000
--- a/en-US/Installing_Packages_common-para-3.xml
+++ /dev/null
@@ -1,10 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
- "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
-]>
-
-  <para>
-    After installation completes, select <guibutton>Reboot</guibutton>
-    to restart your computer.  Fedora ejects any loaded discs before the
-    computer reboots.
-  </para>
diff --git a/en-US/Installing_Packages_common-title.xml b/en-US/Installing_Packages_common-title.xml
deleted file mode 100644
index eae07d6..0000000
--- a/en-US/Installing_Packages_common-title.xml
+++ /dev/null
@@ -1,8 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE title PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<title>Installing Packages</title>
\ No newline at end of file
diff --git a/en-US/Key_Board_Configuration-x86.xml b/en-US/Key_Board_Configuration-x86.xml
deleted file mode 100644
index cf874d3..0000000
--- a/en-US/Key_Board_Configuration-x86.xml
+++ /dev/null
@@ -1,41 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-
-<section>
-
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Key_Board_Configuration_x86_ppc-title-1.xml"/>
-	<!-- Keyboard Configuration -->
-	
-	<!-- Index terms -->
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Key_Board_Configuration_x86_ppc-indexterm-1.xml"/>
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Key_Board_Configuration_x86_ppc-indexterm-2.xml"/>
-	<!-- End Index terms -->
-	
-	<para>
-		Using your mouse, select the correct layout type (for example, U.S. English) for the keyboard you would prefer to use for the installation and as the system default (refer to the figure below).
-	</para>
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Key_Board_Configuration_x86_ppc-para-1.xml"/>
-	<!-- Using your mouse, select the correct layout type ... -->
-	
-	<figure float="0"><title>Keyboard Configuration</title>
-		<mediaobject>
-			<imageobject><imagedata fileref="images/kbdconfig/keyboard.png" format="PNG"/></imageobject>
-			<textobject><para>
-					Keyboard configuration screen
-				</para>
-			</textobject>
-		</mediaobject>
-	</figure>
-	
-	<para>
-		Fedora includes support for more than one keyboard layout for many languages. In particular, most European languages include a <literal>latin1</literal> option, which uses <firstterm>dead keys</firstterm> to access certain characters, such as those with diacritical marks. When you press a dead key, nothing will appear on your screen until you press another key to "complete" the character. For example, to type <literal>Ã©</literal> on a latin1 keyboard layout, you would press (and release) the <keycap>'</keycap> key, and then press the <literal>E</literal> key. By contrast, you access this character on some other keyboards by pressing and holding down a key (such as <keycap>Alt-Gr</keycap>) while you press the <literal>E</literal> key. Other keyboards might have a dedicated key for this character.
-	</para>
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Key_Board_Configuration_x86_ppc-para-2.xml"/>
-	<!-- Actually, despite the name, this is a tip. 
-	     
-	     To change your keyboard layout type after you have completed... -->
-</section>
\ No newline at end of file
diff --git a/en-US/Key_Board_Configuration_x86_ppc-indexterm-1.xml b/en-US/Key_Board_Configuration_x86_ppc-indexterm-1.xml
deleted file mode 100644
index b221728..0000000
--- a/en-US/Key_Board_Configuration_x86_ppc-indexterm-1.xml
+++ /dev/null
@@ -1,11 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE indexterm PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<indexterm significance="normal">
-	<primary>keymap</primary>
-	<secondary>selecting type of keyboard</secondary>
-</indexterm>
\ No newline at end of file
diff --git a/en-US/Key_Board_Configuration_x86_ppc-indexterm-2.xml b/en-US/Key_Board_Configuration_x86_ppc-indexterm-2.xml
deleted file mode 100644
index 210b1e7..0000000
--- a/en-US/Key_Board_Configuration_x86_ppc-indexterm-2.xml
+++ /dev/null
@@ -1,11 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE indexterm PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<indexterm significance="normal">
-	<primary>keyboard</primary>
-	<secondary>configuration</secondary>
-</indexterm>
\ No newline at end of file
diff --git a/en-US/Key_Board_Configuration_x86_ppc-para-1.xml b/en-US/Key_Board_Configuration_x86_ppc-para-1.xml
deleted file mode 100644
index a2efc84..0000000
--- a/en-US/Key_Board_Configuration_x86_ppc-para-1.xml
+++ /dev/null
@@ -1,10 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<para>
-	Once you have made your selection, click <guibutton>Next</guibutton> to continue.
-</para>
\ No newline at end of file
diff --git a/en-US/Key_Board_Configuration_x86_ppc-para-2.xml b/en-US/Key_Board_Configuration_x86_ppc-para-2.xml
deleted file mode 100644
index 09bfaaf..0000000
--- a/en-US/Key_Board_Configuration_x86_ppc-para-2.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE tip PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<note><title>Note</title>
-	<para>
-		To change your keyboard layout type after you have completed the installation, use the <application>Keyboard Configuration Tool</application>.
-	</para>
-	<para>
-		Type the <command>system-config-keyboard</command> command in a shell prompt to launch the <application>Keyboard Configuration Tool</application>. If you are not root, it prompts you for the root password to continue.
-	</para>
-	</note>
\ No newline at end of file
diff --git a/en-US/Key_Board_Configuration_x86_ppc-title-1.xml b/en-US/Key_Board_Configuration_x86_ppc-title-1.xml
deleted file mode 100644
index cee248d..0000000
--- a/en-US/Key_Board_Configuration_x86_ppc-title-1.xml
+++ /dev/null
@@ -1,8 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE title PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<title>Keyboard Configuration</title>
\ No newline at end of file
diff --git a/en-US/Kickstart-note-1.xml b/en-US/Kickstart-note-1.xml
deleted file mode 100644
index 56a1717..0000000
--- a/en-US/Kickstart-note-1.xml
+++ /dev/null
@@ -1,9 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<important>
-	<para>
-		If you select text mode for a kickstart installation, make sure that you specify choices for the partitioning, bootloader, and package selection options. These steps are automated in text mode, and <application>anaconda</application> cannot prompt you for missing information. If you do not provide choices for these options,  <application>anaconda</application> will stop the installation process.
-	</para>
-</important>
diff --git a/en-US/Kickstart2.xml b/en-US/Kickstart2.xml
deleted file mode 100644
index 6a68c1d..0000000
--- a/en-US/Kickstart2.xml
+++ /dev/null
@@ -1,3680 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<chapter id="ch-kickstart2"><title>Kickstart Installations</title>
-	<indexterm significance="normal">
-		<primary>installation</primary>
-		<secondary>kickstart</secondary>
-		<see>kickstart installations</see>
-	</indexterm>
-	<indexterm significance="normal">
-		<primary>kickstart installations</primary>
-	</indexterm>
-	<section id="s1-kickstart2-whatis">
-		
-		<title>What are Kickstart Installations?</title>
-		
-		<indexterm significance="normal">
-			<primary>log files</primary>
-			<secondary>kickstart installations</secondary>
-		</indexterm>
-		 
-		<para>
-			Many system administrators would prefer to use an automated installation method to install Fedora on their machines. To answer this need, Red Hat created the kickstart installation method. Using kickstart, a system administrator can create a single file containing the answers to all the questions that would normally be asked during a typical installation.
-		</para>
-		 
-		<para>
-			Kickstart files can be kept on a single server system and read by individual computers during the installation. This installation method can support the use of a single kickstart file to install Fedora on multiple machines, making it ideal for network and system administrators.
-		</para>
-		 
-		<para>
-			Kickstart provides a way for users to automate a Fedora installation.
-		</para>
-		
-		<para>
-			All kickstart scriptlets and the log files of their execution are stored in the <filename>/tmp</filename> directory to assist with debugging installation failures.
-		</para>
-	</section>
-	<section id="s1-kickstart2-howuse">
-		<title>How Do You Perform a Kickstart Installation?</title>
-		 
-		<para>
-			Kickstart installations can be performed using a local CD-ROM, a local hard drive, or via NFS, FTP, or HTTP.
-		</para>
-		 
-		<para>
-			To use kickstart, you must:
-		</para>
-		 
-		<orderedlist inheritnum="ignore" continuation="restarts">
-			<listitem>
-				<para>
-					Create a kickstart file.
-				</para>
-			</listitem>
-
-			<listitem>
-				<para>
-					Create a boot media with the kickstart file or make the kickstart file available on the network.
-				</para>
-			</listitem>
-
-			<listitem>
-				<para>
-					Make the installation tree available.
-				</para>
-			</listitem>
-
-			<listitem>
-				<para>
-					Start the kickstart installation.
-				</para>
-			</listitem>
-		</orderedlist>
-		 
-		<para>
-			This chapter explains these steps in detail.
-		</para>
-	</section>
-	<section id="s1-kickstart2-file">
-		<title>Creating the Kickstart File</title>
-		<indexterm significance="normal">
-			<primary>kickstart installations</primary>
-			<secondary>file format</secondary>
-		</indexterm>
-		<indexterm significance="normal">
-			<primary>kickstart file</primary>
-			<secondary>format of</secondary>
-		</indexterm>
-		<indexterm significance="normal">
-			<primary>kickstart file</primary>
-			<secondary>what it looks like</secondary>
-		</indexterm>
-		<para>
-			The kickstart file is a simple text file, containing a list of items, each identified by a keyword. You can create it by using the <application>Kickstart Configurator</application> application, or writing it from scratch. The Fedora installation program also creates a sample kickstart file based on the options that you selected during installation. It is written to the file <filename>/root/anaconda-ks.cfg</filename>. You should be able to edit it with any text editor or word processor that can save files as ASCII text.
-		</para>
-		 
-		<para>
-			First, be aware of the following issues when you are creating your kickstart file:
-		</para>
-		 
-		<itemizedlist>
-			<listitem>
-				<para>
-					Sections must be specified <emphasis>in order</emphasis>. Items within the sections do not have to be in a specific order unless otherwise specified. The section order is:
-				</para>
-
-				<itemizedlist>
-					<listitem>
-						<para>
-Command section &mdash; Refer to <xref linkend="s1-kickstart2-options"/> for a list of kickstart options. You must include the required options.
-						</para>
-					</listitem>
-
-					<listitem>
-						<para>
-The <command>%packages</command> section &mdash; Refer to <xref linkend="s1-kickstart2-packageselection"/> for details.
-						</para>
-					</listitem>
-
-					<listitem>
-						<para>
-The <command>%pre</command> and <command>%post</command> sections &mdash; These two sections can be in any order and are not required. Refer to <xref linkend="s1-kickstart2-preinstallconfig"/> and
-<xref linkend="s1-kickstart2-postinstallconfig"/> for details.
-						</para>
-					</listitem>
-				</itemizedlist>
-			</listitem>
-
-			<listitem>
-				<para>
-					Items that are not required can be omitted.
-				</para>
-			</listitem>
-
-			<listitem>
-				<para>
-					Omitting any required item results in the installation program prompting the user for an answer to the related item, just as the user would be prompted during a typical installation. Once the answer is given, the installation continues unattended
-					(unless it finds another missing item).
-				</para>
-			</listitem>
-
-			<listitem>
-				<para>
-					Lines starting with a pound (also known as hash) sign (#) are treated as comments and are ignored.
-				</para>
-			</listitem>
-
-			<listitem>
-				<para>
-					For kickstart <emphasis>upgrades</emphasis>, the following items are required:
-				</para>
-
-				<itemizedlist>
-					<listitem>
-						<para>
-Language
-						</para>
-					</listitem>
-
-					<listitem>
-						<para>
-Installation method
-						</para>
-					</listitem>
-
-					<listitem>
-						<para>
-Device specification (if device is needed to perform the installation)
-						</para>
-					</listitem>
-
-					<listitem>
-						<para>
-Keyboard setup
-						</para>
-					</listitem>
-
-					<listitem>
-						<para>
-The <command>upgrade</command> keyword
-						</para>
-					</listitem>
-
-					<listitem>
-						<para>
-Boot loader configuration
-						</para>
-					</listitem>
-				</itemizedlist>
-
-				<para>
-					If any other items are specified for an upgrade, those items are ignored (note that this includes package selection).
-				</para>
-			</listitem>
-		</itemizedlist>
-	</section>
-	<section id="s1-kickstart2-options">
-		<title>Kickstart Options</title>
-		<indexterm significance="normal">
-			<primary>kickstart file</primary>
-			<secondary>options</secondary>
-		</indexterm>
-		<indexterm significance="normal">
-			<primary>kickstart file</primary>
-			<secondary>creating</secondary>
-		</indexterm>
-		<para>
-			The following options can be placed in a kickstart file. If you prefer to use a graphical interface for creating your kickstart file, use the <application>Kickstart Configurator</application> application. Refer to
-			<xref linkend="ch-redhat-config-kickstart"/> for details.
-		</para>
-		 
-		<note>
-			<title>Note</title>
-
-			<para>
-				If the option is followed by an equals mark (=), a value must be specified after it. In the example commands, options in brackets ([]) are optional arguments for the command.
-			</para>
-		</note>
-		 
-		<variablelist>
-	
-			<varlistentry>
-				<term><command>autopart</command> (optional) 	  </term>
-
-				<listitem>
-					<para>
-				<indexterm significance="normal">
-					<primary>kickstart file</primary>
-					<secondary><command>autopart</command>
-					</secondary>
-				</indexterm>						Automatically create partitions &mdash; 1 GB or more root (<filename>/</filename>) partition, a swap partition, and an appropriate boot partition for the architecture. One or more of the default partition sizes can be redefined with
-						the <command>part</command> directive.
-					</para>
-					
-					<itemizedlist>
-<listitem>
-	<para>
-		<command>--encrypted</command> &mdash; Should all devices with support be encrypted by default? This is equivalent to checking the <guilabel>Encrypt</guilabel> checkbox on the initial partitioning screen. 
-	</para>
-</listitem>
-<listitem>
-	<para>
-		<command>--passphrase=</command> &mdash; Provide a default system-wide passphrase for all encrypted devices.
-	</para>
-</listitem>
-<listitem>
-	<para>
-		<command>--escrowcert=<replaceable>URL_of_X.509_certificate</replaceable></command> &mdash; Store data encryption keys of all encrypted volumes as files in <filename>/</filename> (root), encrypted using the X.509 certificate from the URL specified with <replaceable>URL_of_X.509_certificate</replaceable>. The keys are stored as a separate file for each encrypted volume. This option is only meaningful if <command>--encrypted</command> is specified. 
-	</para>
-</listitem>
-<listitem>
-	<para>
-		<command>--backuppassphrase=</command> &mdash; Add a randomly-generated passphrase to each encrypted volume. Store these passphrases in separate files in <filename>/</filename> (root), encrypted using the X.509 certificate specified with <command>--escrowcert</command>. This option is only meaningful if <command>--escrowcert</command> is specified. 
-	</para>
-</listitem>
-					</itemizedlist>
-					
-				</listitem>
-			</varlistentry>
-
-			<varlistentry>
-				<term><command>ignoredisk</command> (optional) 	  </term>
-
-				<listitem>
-					<para>
-				<indexterm significance="normal">
-					<primary>kickstart file</primary>
-					<secondary><command>ignoredisk</command>
-					</secondary>
-				</indexterm>						Causes the installer to ignore the specified disks. This is useful if you use autopartition and want to be sure that some disks are ignored. For example, without <literal>ignoredisk</literal>, attempting to deploy on a SAN-cluster the
-						kickstart would fail, as the installer detects passive paths to the SAN that return no partition table.
-					</para>
-
-					<para>
-						The <literal>ignoredisk</literal> option is also useful if you have multiple paths to your disks.
-					</para>
-
-					<para>
-						The syntax is:
-					</para>
-<screen>ignoredisk --drives=<replaceable>drive1,drive2</replaceable>,...</screen>
-					<para>
-						where <replaceable>driveN</replaceable> is one of <literal>sda</literal>, <literal>sdb</literal>,..., <literal>hda</literal>,... etc.
-					</para>
-				</listitem>
-			</varlistentry>
-
-			<varlistentry>
-				<term><command>autostep</command> (optional) 	  </term>
-
-				<listitem>
-					<para>
-					<indexterm significance="normal">
-					<primary>kickstart file</primary>
-					<secondary><command>autostep</command>
-					</secondary>
-				</indexterm>					Similar to <command>interactive</command> except it goes to the next screen for you. It is used mostly for debugging.
-					</para>
-					
-					<itemizedlist>
-<listitem>
-	<para>
-		<command>--autoscreenshot</command> &mdash; Take a screenshot at every step during installation and copy the images over to <command>/root/anaconda-screenshots</command> after installation is complete.  This is most useful for documentation.
-	</para>
-</listitem>
-					</itemizedlist>
-				</listitem>
-			</varlistentry>
-
-			<varlistentry>
-				<term><command>auth</command> or <command>authconfig</command> (required) 	  </term>
-				<listitem>
-					<para>
-					<indexterm significance="normal">
-					<primary>kickstart file</primary>
-					<secondary><command>auth</command>
-					</secondary>
-				</indexterm>
-				<indexterm significance="normal">
-					<primary>kickstart file</primary>
-					<secondary><command>authconfig</command>
-					</secondary>
-				</indexterm>
-					Sets up the authentication options for the system. It is similar to the <command>authconfig</command> command, which can be run after the install. By default, passwords are normally encrypted and are not shadowed.
-					</para>
-
-					<itemizedlist>
-
-<listitem>
-	<para>
-		<command>--enablemd5</command> &mdash; Use md5 encryption for user passwords.
-	</para>
-</listitem>
-
-<listitem>
-	<para>
-		<command>--enablenis</command> &mdash; Turns on NIS support. By default, <command>--enablenis</command> uses whatever domain it finds on the network. A domain should almost always be set by hand with the <command>--nisdomain=</command> option.
-	</para>
-</listitem>
-
-<listitem>
-	<para>
-		<command>--nisdomain=</command> &mdash; NIS domain name to use for NIS services.
-	</para>
-</listitem>
-
-<listitem>
-	<para>
-		<command>--nisserver=</command> &mdash; Server to use for NIS services (broadcasts by default).
-	</para>
-</listitem>
-
-<listitem>
-	<para>
-		<command>--useshadow</command> or <command>--enableshadow</command> &mdash; Use shadow passwords.
-	</para>
-</listitem>
-
-<listitem>
-	<para>
-		<command>--enableldap</command> &mdash; Turns on LDAP support in <filename>/etc/nsswitch.conf</filename>, allowing your system to retrieve information about users (UIDs, home directories, shells, etc.) from an LDAP directory. To use this option, you must install the
-		<filename>nss_ldap</filename> package. You must also specify a server and a base DN (distinguished name) with <command>--ldapserver=</command> and <command>--ldapbasedn=</command>.
-	</para>
-</listitem>
-
-<listitem>
-	<para>
-		<command>--enableldapauth</command> &mdash; Use LDAP as an authentication method. This enables the <filename>pam_ldap</filename> module for authentication and changing passwords, using an LDAP directory. To use this option, you must have the
-		<filename>nss_ldap</filename> package installed. You must also specify a server and a base DN with <command>--ldapserver=</command> and <command>--ldapbasedn=</command>.
-	</para>
-</listitem>
-						
-
-						
-
-<listitem>
-	<para>
-		<command>--ldapserver=</command> &mdash; If you specified either <command>--enableldap</command> or <command>--enableldapauth</command>, use this option to specify the name of the LDAP server to use. This option is set in the
-		<filename>/etc/ldap.conf</filename> file.
-	</para>
-</listitem>
-						
-<listitem>
-	<para>
-		<command>--ldapbasedn=</command> &mdash; If you specified either <command>--enableldap</command> or <command>--enableldapauth</command>, use this option to specify the DN in your LDAP directory tree under which user information is stored. This option is
-		set in the <filename>/etc/ldap.conf</filename> file.
-	</para>
-</listitem>
-						
-<listitem>
-	<para>
-		<command>--enableldaptls</command> &mdash; Use TLS (Transport Layer Security) lookups. This option allows LDAP to send encrypted usernames and passwords to an LDAP server before authentication.
-	</para>
-</listitem>
-						
-<listitem>
-	<para>
-		<command>--enablekrb5</command> &mdash; Use Kerberos 5 for authenticating users. Kerberos itself does not know about home directories, UIDs, or shells. If you enable Kerberos, you must make users' accounts known to this workstation by enabling LDAP, NIS, or Hesiod or by using the
-		<command>/usr/sbin/useradd</command> command. If you use this option, you must have the <filename>pam_krb5</filename> package installed.
-	</para>
-</listitem>
-						
-<listitem>
-	<para>
-		<command>--krb5realm=</command> &mdash; The Kerberos 5 realm to which your workstation belongs.
-	</para>
-</listitem>
-
-<listitem>
-	<para>
-		<command>--krb5kdc=</command> &mdash; The KDC (or KDCs) that serve requests for the realm. If you have multiple KDCs in your realm, separate their names with commas (,).
-	</para>
-</listitem>
-
-<listitem>
-	<para>
-		<command>--krb5adminserver=</command> &mdash; The KDC in your realm that is also running kadmind. This server handles password changing and other administrative requests. This server must be run on the master KDC if you have more than one KDC.
-	</para>
-</listitem>
-
-<listitem>
-	<para>
-		<command>--enablehesiod</command> &mdash; Enable Hesiod support for looking up user home directories, UIDs, and shells. More information on setting up and using Hesiod on your network is in <filename>/usr/share/doc/glibc-2.x.x/README.hesiod</filename>, which is included in
-		the <filename>glibc</filename> package. Hesiod is an extension of DNS that uses DNS records to store information about users, groups, and various other items.
-	</para>
-</listitem>
-
-<listitem>
-	<para>
-		<command>--hesiodlhs</command> &mdash; The Hesiod LHS ("left-hand side") option, set in <filename>/etc/hesiod.conf</filename>. This option is used by the Hesiod library to determine the name to search DNS for when looking up information, similar to LDAP's use of a base
-		DN.
-	</para>
-</listitem>
-						
-<listitem>
-	<para>
-		<command>--hesiodrhs</command> &mdash; The Hesiod RHS ("right-hand side") option, set in <filename>/etc/hesiod.conf</filename>. This option is used by the Hesiod library to determine the name to search DNS for when looking up information, similar to LDAP's use of a base
-		DN.
-	</para>
-	<note><title>Note</title>
-		<para>
-To look up user information for "jim", the Hesiod library looks up <emphasis>jim.passwd&lt;LHS&gt;&lt;RHS&gt;</emphasis>, which should resolve to a TXT record that looks like what his passwd entry would look like
-(<computeroutput>jim:*:501:501:Jungle Jim:/home/jim:/bin/bash</computeroutput>). For groups, the situation is identical, except <emphasis>jim.group&lt;LHS&gt;&lt;RHS&gt;</emphasis> would be used.
-		</para>
-		<para>
-Looking up users and groups by number is handled by making "501.uid" a CNAME for "jim.passwd", and "501.gid" a CNAME for "jim.group". Note that the library does not place a period <keycap>.</keycap> in front of the LHS and RHS values when performing a search. Therefore the LHS and RHS values need to have a period placed in front of them in order if they require this.
-		</para>
-	</note>
-</listitem>
-
-<listitem>
-	<para>
-		<command>--enablesmbauth</command> &mdash; Enables authentication of users against an SMB server (typically a Samba or Windows server). SMB authentication support does not know about home directories, UIDs, or shells. If you enable SMB, you must make users' accounts known to the
-		workstation by enabling LDAP, NIS, or Hesiod or by using the <command>/usr/sbin/useradd</command> command to make their accounts known to the workstation. To use this option, you must have the
-		<filename>pam_smb</filename> package installed.
-	</para>
-</listitem>
-						
-<listitem>
-	<para>
-		<command>--smbservers=</command> &mdash; The name of the server(s) to use for SMB authentication. To specify more than one server, separate the names with commas (,).
-	</para>
-</listitem>
-						
-<listitem>
-	<para>
-		<command>--smbworkgroup=</command> &mdash; The name of the workgroup for the SMB servers.
-	</para>
-</listitem>
-
-<listitem>
-	<para>
-		<command>--enablecache</command> &mdash; Enables the <command>nscd</command> service. The <command>nscd</command> service caches information about users, groups, and various other types of information. Caching is especially helpful if you choose to
-		distribute information about users and groups over your network using NIS, LDAP, or hesiod.
-	</para>
-</listitem>
-						
-					</itemizedlist>
-				</listitem>
-			</varlistentry>
-
-			<varlistentry>
-				<term><command>bootloader</command> (required)</term>
-				<listitem>
-					<para>
-					<indexterm significance="normal">
-					<primary>kickstart file</primary>
-					<secondary><command>bootloader</command>
-					</secondary>
-				</indexterm>
-					Specifies how the boot loader should be installed. This option is required for both installations and upgrades. 
-					</para>
-					
-					<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Kickstart-note-1.xml"/>
-					<!-- If you select text mode for a kickstart installation, you must ensure -->
-
-					<itemizedlist>
-
-<listitem>
-	<para>
-		<command>--append=</command> &mdash; Specifies kernel parameters. To specify multiple parameters, separate them with spaces. For example:
-	</para>
-<screen>bootloader --location=mbr --append="hdd=ide-scsi ide=nodma"</screen>
-</listitem>
-
-<listitem>
-	<para>
-		<command>--driveorder</command> &mdash; Specify which drive is first in the BIOS boot order. For example:
-	</para>
-<screen>bootloader --driveorder=sda,hda</screen>
-</listitem>
-
-<listitem>
-	<para>
-		<command>--location=</command> &mdash; Specifies where the boot record is written. Valid values are the following: <command>mbr</command> (the default), <command>partition</command> (installs the boot loader on the first sector of the partition
-		containing the kernel), or <command>none</command> (do not install the boot loader).
-	</para>
-</listitem>
-
-<listitem>
-	<para>
-		<command>--password=</command> &mdash; If using GRUB, sets the GRUB boot loader password to the one specified with this option. This should be used to restrict access to the GRUB shell, where arbitrary kernel options can be passed.
-	</para>
-</listitem>
-
-<listitem>
-	<para>
-		<command>--md5pass=</command> &mdash; If using GRUB, similar to <command>--password=</command> except the password should already be encrypted.
-	</para>
-</listitem>
-
-<listitem>
-	<para>
-		<command>--upgrade</command> &mdash; Upgrade the existing boot loader configuration, preserving the old entries. This option is only available for upgrades.
-	</para>
-</listitem>
-
-					</itemizedlist>
-				</listitem>
-			</varlistentry>
-
-			<varlistentry>
-				<term><command>clearpart</command> (optional) 	  </term>
-				<listitem>
-					<para>
-				<indexterm significance="normal">
-					<primary>kickstart file</primary>
-					<secondary><command>clearpart</command>
-					</secondary>
-				</indexterm>
-						Removes partitions from the system, prior to creation of new partitions. By default, no partitions are removed.
-					</para>
-
-					<note>
-						<title>Note</title>
-
-						<para>
-If the <command>clearpart</command> command is used, then the <command>--onpart</command> command cannot be used on a logical partition.
-						</para>
-					</note>
-
-					<itemizedlist>
-						
-  
-<listitem>
-	<para>
-		<command>--all</command> &mdash; Erases all partitions from the system.
-	</para>
-</listitem>
-
-<listitem>
-	<para>
-		<command>--drives=</command> &mdash; Specifies which drives to clear partitions from. For example, the following clears all the partitions on the first two drives on the primary IDE controller:
-	</para>
-<screen>clearpart --drives=hda,hdb --all</screen>
-</listitem>
-
-<listitem>
-	<para>
-		<command>--initlabel</command> &mdash; Initializes the disk label to the default for your architecture (for example <command>msdos</command> for x86). It is useful so that the installation program does not ask if it
-		should initialize the disk label if installing to a brand new hard drive.
-	</para>
-</listitem>
-						
-
-						
-
-<listitem>
-	<para>
-		  <command>--linux</command> &mdash; Erases all Linux partitions.
-	</para>
-</listitem>
-						
-
-						
-  
-<listitem>
-	<para>
-		<command>--none</command> (default) &mdash; Do not remove any partitions.
-	</para>
-</listitem>
-						
-					</itemizedlist>
-				</listitem>
-			</varlistentry>
-
-			<varlistentry>
-				<term><command>cmdline</command> (optional) 	  </term>
-				<listitem>
-					<para>
-				<indexterm significance="normal">
-					<primary>kickstart file</primary>
-					<secondary><command>cmdline</command>
-					</secondary>
-				</indexterm>
-						Perform the installation in a completely non-interactive command line mode. Any prompts for interaction halts the install. This mode is useful on IBM System z systems with the x3270 console.
-					</para>
-				</listitem>
-			</varlistentry>
-
-			<varlistentry>
-				<term><command>device</command> (optional) 	  </term>
-				<listitem>
-					<para>
-				<indexterm significance="normal">
-					<primary>kickstart file</primary>
-					<secondary><command>device</command>
-					</secondary>
-				</indexterm>
-						On most PCI systems, the installation program autoprobes for Ethernet and SCSI cards properly. On older systems and some PCI systems, however, kickstart needs a hint to find the proper devices. The <command>device</command> command,
-						which tells the installation program to install extra modules, is in this format:
-					</para>
-<screen>device <replaceable>&lt;type&gt;</replaceable> <replaceable>&lt;moduleName&gt;</replaceable> --opts=<replaceable>&lt;options&gt;</replaceable>
-</screen>
-					<itemizedlist>
-
-<listitem>
-	<para>
-		<replaceable>&lt;type&gt;</replaceable> &mdash; Replace with either <command>scsi</command> or <command>eth</command>.
-	</para>
-</listitem>
-
-<listitem>
-	<para>
-		<replaceable>&lt;moduleName&gt;</replaceable> &mdash; Replace with the name of the kernel module which should be installed.
-	</para>
-</listitem>
-
-<listitem>
-	<para><command>--opts=</command> &mdash; Mount options to use for mounting the NFS export.  Any options that can be specified in <filename>/etc/fstab</filename> for an NFS mount are allowed.  The options are listed in the <command>nfs(5)</command> man page. Multiple options are separated with a comma.</para>
-</listitem>
-						
-					</itemizedlist>
-				</listitem>
-			</varlistentry>
-
-			<varlistentry>
-				<term><command>driverdisk</command> (optional) 	  </term>
-				<listitem>
-					<para>
-				<indexterm significance="normal">
-					<primary>kickstart file</primary>
-					<secondary><command>driverdisk</command>
-					</secondary>
-				</indexterm>
-						Driver diskettes can be used during kickstart installations. You must copy the driver diskettes's contents to the root directory of a partition on the system's hard drive. Then you must use the <command>driverdisk</command> command to
-						tell the installation program where to look for the driver disk.
-					</para>
-<screen>driverdisk <replaceable>&lt;partition&gt;</replaceable> --source=<replaceable>&lt;url&gt;</replaceable> --biospart=<replaceable>&lt;biospart&gt;</replaceable> [--type=<replaceable>&lt;fstype&gt;</replaceable>]</screen>
-					<para>
-						Alternatively, a network location can be specified for the driver diskette:
-					</para>
-<screen>driverdisk --source=ftp://path/to/dd.img
-driverdisk --source=http://path/to/dd.img
-driverdisk --source=nfs:host:/path/to/img</screen>
-					<itemizedlist>
-
-<listitem>
-	<para>
-		<replaceable>&lt;partition&gt;</replaceable> &mdash; Partition containing the driver disk.
-	</para>
-</listitem>
-
-<listitem>
-	<para>
-		<replaceable>&lt;url&gt;</replaceable> &mdash; URL for the driver disk. NFS locations can be given in the form <literal>nfs:<replaceable>host</replaceable>:/<replaceable>path/to/img</replaceable></literal>.
-	</para>
-</listitem>
-
-<listitem>
-	<para>
-		<replaceable>&lt;biospart&gt;</replaceable> &mdash; BIOS partition containing the driver disk (for example, <literal>82p2</literal>). 
-	</para>
-</listitem>
-
-<listitem>
-	<para>
-		<command>--type=</command> &mdash; File system type (for example, vfat or ext2).
-	</para>
-</listitem>
-						
-					</itemizedlist>
-				</listitem>
-			</varlistentry>
-
-			<varlistentry>
-				<term><command>firewall</command> (optional) 	  </term>
-				<listitem>
-					<para>
-				<indexterm significance="normal">
-					<primary>kickstart file</primary>
-					<secondary><command>firewall</command>
-					</secondary>
-				</indexterm>
-						This option corresponds to the <guilabel>Firewall Configuration</guilabel> screen in the installation program:
-					</para>
-<screen>firewall --enabled|--disabled [--trust=] <replaceable>&lt;device&gt;</replaceable> [--port=]</screen>
-<itemizedlist>
-					<listitem>
-	<para>
-		<command>--enabled</command> or <command>--enable</command> &mdash; Reject incoming connections that are not in response to outbound requests, such as DNS replies or DHCP requests. If access to services running on this machine is needed, you can choose to allow specific services through the firewall.
-	</para>
-</listitem>
-
-<listitem>
-	<para>
-		<command>--disabled</command> or <command>--disable</command> &mdash; Do not configure any iptables rules.
-	</para>
-</listitem>
-						
-<listitem>
-	<para>
-		<command>--trust=</command> &mdash; Listing a device here, such as eth0, allows all traffic coming from that device to go through the firewall. To list more than one device, use <command>--trust eth0 --trust eth1</command>. Do NOT use a comma-separated format such as
-		<command>--trust eth0, eth1</command>.
-	</para>
-</listitem>
-
-<listitem>
-	<para>
-		<replaceable>&lt;incoming&gt;</replaceable> &mdash; Replace with one or more of the following to allow the specified services through the firewall.
-	</para>
-
-	<itemizedlist>
-		<listitem>
-<para>
-	<command>--ssh</command>
-</para>
-		</listitem>
-
-		<listitem>
-<para>
-	<command>--telnet</command>
-</para>
-		</listitem>
-
-		<listitem>
-<para>
-	<command>--smtp</command>
-</para>
-		</listitem>
-
-		<listitem>
-<para>
-	<command>--http</command>
-</para>
-		</listitem>
-
-		<listitem>
-<para>
-	<command>--ftp</command>
-</para>
-		</listitem>
-	</itemizedlist>
-</listitem>
-
-<listitem>
-	<para>
-		<command>--port=</command> &mdash; You can specify that ports be allowed through the firewall using the port:protocol format. For example, to allow IMAP access through your firewall, specify <command>imap:tcp</command>. Numeric ports can also be specified
-		explicitly; for example, to allow UDP packets on port 1234 through, specify <command>1234:udp</command>. To specify multiple ports, separate them by commas.
-	</para>
-</listitem>
-						
-					</itemizedlist>
-				</listitem>
-			</varlistentry>
-
-			<varlistentry>
-				<term><command>firstboot</command> (optional) 	  </term>
-				<listitem>
-					<para>
-				<indexterm significance="normal">
-					<primary>kickstart file</primary>
-					<secondary><command>firstboot</command>
-					</secondary>
-				</indexterm>
-				<indexterm significance="normal">
-					<primary><application>Setup Agent</application>
-					</primary>
-					<secondary>via Kickstart</secondary>
-				</indexterm>
-						Determine whether the <application>Setup Agent</application> starts the first time the system is booted. If enabled, the <command>firstboot</command> package must be installed. If not specified, this option is disabled
-						by default.
-					</para>
-
-					<itemizedlist>
-						
-
-<listitem>
-	<para>
-		<command>--enable</command> or <command>--enabled</command> &mdash; The <application>Setup Agent</application> is started the first time the system boots.
-	</para>
-</listitem>
-
-<listitem>
-	<para>
-		<command>--disable</command> or <command>--disabled</command> &mdash; The <application>Setup Agent</application> is not started the first time the system boots.
-	</para>
-</listitem>
-
-<listitem>
-	<para>
-		<command>--reconfig</command> &mdash; Enable the <application>Setup Agent</application> to start at boot time in reconfiguration mode. This mode enables the language, mouse, keyboard, root password, security level, time zone, and networking configuration options in
-		addition to the default ones.
-	</para>
-</listitem>
-						
-					</itemizedlist>
-				</listitem>
-			</varlistentry>
-
-			<varlistentry>
-				<term><command>halt</command> (optional) 	  </term>
-				<listitem>
-					<para>
-				<indexterm significance="normal">
-					<primary>kickstart file</primary>
-					<secondary><command>halt</command>
-					</secondary>
-				</indexterm>
-						Halt the system after the installation has successfully completed. This is similar to a manual installation, where anaconda displays a message and waits for the user to press a key before rebooting. During a kickstart installation, if no completion
-						method is specified, the <command>reboot</command> option is used as default.
-					</para>
-
-					<para>
-						The <command>halt</command> option is roughly equivalent to the <command>shutdown -h</command> command.
-					</para>
-
-					<para>
-						For other completion methods, refer to the <command>poweroff</command>, <command>reboot</command>, and <command>shutdown</command> kickstart options.
-					</para>
-				</listitem>
-			</varlistentry>
-
-			<varlistentry>
-				<term><command>graphical</command> (optional) 	  </term>
-				<listitem>
-					<para>
-				<indexterm significance="normal">
-					<primary>kickstart file</primary>
-					<secondary><command>graphical</command>
-					</secondary>
-				</indexterm>
-						Perform the kickstart installation in graphical mode. This is the default.
-					</para>
-				</listitem>
-			</varlistentry>
-			
-			<varlistentry>
-				<term><command>install</command> (optional) 	  </term>
-				<listitem>
-					<para>
-				<indexterm significance="normal">
-					<primary>kickstart file</primary>
-					<secondary><command>install</command>
-					</secondary>
-				</indexterm>
-						Tells the system to install a fresh system rather than upgrade an existing system. This is the default mode. For installation, you must specify the type of installation from <command>cdrom</command>,
-						<command>harddrive</command>, <command>nfs</command>, or <command>url</command> (for FTP or HTTP installations). The <command>install</command> command and the installation method
-						command must be on separate lines.
-					</para>
-					<indexterm significance="normal">
-<primary>kickstart file</primary>
-<secondary>installation methods</secondary>
-						</indexterm>
-
-					<itemizedlist>
-						
-						
-
-<listitem>
-	<para>
-		<command>cdrom</command> &mdash; Install from the first CD-ROM drive on the system.
-	</para>
-</listitem>
-						
-
-						
-
-<listitem>
-	<para>
-		<command>harddrive</command> &mdash; Install from a Red Hat installation tree on a local drive, which must be either vfat or ext2.
-	</para>
-
-	<itemizedlist>
-		<listitem>
-<para>
-	<command>--biospart=</command>
-</para>
-
-<para>
-	BIOS partition to install from (such as 82).
-</para>
-		</listitem>
-		<listitem>
-<para>
-	<command>--partition=</command>
-</para>
-
-<para>
-	Partition to install from (such as sdb2).
-</para>
-		</listitem>
-
-		<listitem>
-<para>
-	<command>--dir=</command>
-</para>
-
-<para>
-	Directory containing the <filename><replaceable>variant</replaceable></filename> directory of the installation tree.
-</para>
-		</listitem>
-	</itemizedlist>
-
-	<para>
-		For example:
-	</para>
-<screen>harddrive --partition=hdb2 --dir=/tmp/install-tree</screen>
-</listitem>
-						
-
-						
-
-<listitem>
-	<para>
-		<command>nfs</command> &mdash; Install from the NFS server specified.
-	</para>
-
-	<itemizedlist>
-		<listitem>
-<para>
-	<command>--server=</command>
-</para>
-
-<para>
-	Server from which to install (hostname or IP).
-</para>
-		</listitem>
-
-		<listitem>
-<para>
-	<command>--dir=</command>
-</para>
-
-<para>
-	Directory containing the <filename><replaceable>variant</replaceable></filename> directory of the installation tree.
-</para>
-		</listitem>
-		
-		<listitem>
-<para>
-	<command>--opts=</command>
-</para>
-
-<para>
-	Mount options to use for mounting the NFS export. (optional)
-</para>
-		</listitem>
-	</itemizedlist>
-
-	<para>
-		For example:
-	</para>
-<screen>nfs --server=nfsserver.example.com --dir=/tmp/install-tree</screen>
-</listitem>
-						
-
-						
-
-<listitem>
-	<para>
-		<command>url</command> &mdash; Install from an installation tree on a remote server via FTP or HTTP.
-	</para>
-
-	<para>
-		For example:
-	</para>
-<screen>url --url http://<replaceable>&lt;server&gt;</replaceable>/<replaceable>&lt;dir&gt;</replaceable></screen>
-	<para>
-		or:
-	</para>
-<screen>url --url ftp://<replaceable>&lt;username&gt;</replaceable>:<replaceable>&lt;password&gt;@&lt;server&gt;</replaceable>/<replaceable>&lt;dir&gt;</replaceable></screen>
-</listitem>
-						
-					</itemizedlist>
-				</listitem>
-			</varlistentry>
-<!-- BZ#306001, listed twice
-			<varlistentry>
-				<term><command>ignore disk</command> (optional) 	  </term>
-
-				<listitem>
-					<para>
-					<indexterm significance="normal">
-					<primary>kickstart file</primary>
-					<secondary><command>ignoredisk</command>
-					</secondary>
-				</indexterm>					Used to specify disks that anaconda should not touch when partitioning, formatting, and clearing. This command has a single required argument, which takes a comma-separated list of drive names to ignore.
-					</para>
-					<screen>ignoredisk -drives=[disk1,disk2,...]</screen>
-				</listitem>
-			</varlistentry>-->
-			
-			<varlistentry>
-				<term><command>interactive</command> (optional) 	  </term>
-
-				<listitem>
-					<para>
-					<indexterm significance="normal">
-					<primary>kickstart file</primary>
-					<secondary><command>interactive</command>
-					</secondary>
-				</indexterm>					Uses the information provided in the kickstart file during the installation, but allow for inspection and modification of the values given. You are presented with each screen of the installation program with the values from the kickstart file. Either accept the values by clicking <guibutton>Next</guibutton> or change the values and click <guibutton>Next</guibutton> to continue. Refer to the <command>autostep</command> command.
-					</para>
-				</listitem>
-			</varlistentry>
-
-			<varlistentry>
-				<term><command>iscsi</command> (optional)</term>
-				<listitem>
-					<para><indexterm significance="normal">
-					<primary>kickstart file</primary>
-					<secondary><command>iscsi</command>
-					</secondary>
-				</indexterm>
-						iscsi --ipaddr= [options].
-					</para>
-					<para>
-						Specifies additional iSCSI storage to be attached during installation. If you use the <parameter>iscsi</parameter> parameter, you must also assign a name to the iSCSI node, using the <parameter>iscsiname</parameter> parameter. The <parameter>iscsiname</parameter> parameter must appear before the <parameter>iscsi</parameter> parameter in the kickstart file. 
-					</para>
-					<para>
-						We recommend that wherever possible you configure iSCSI storage in the system BIOS or firmware (iBFT for Intel systems) rather than use the <parameter>iscsi</parameter> parameter. <application>Anaconda</application> automatically detects and uses disks configured in BIOS or firmware and no special configuration is necessary in the kickstart file. 
-					</para>
-					<para>
-						If you must use the <parameter>iscsi</parameter> parameter, ensure that networking is activated at the beginning of the installation, and that the <parameter>iscsi</parameter> parameter appears in the kickstart file before you refer to iSCSI disks with parameters such as <parameter>clearpart</parameter> or <parameter>ignoredisk</parameter>.
-					</para>
-
-					<itemizedlist>
-
-<listitem>
-	<para>
-<command>--port=</command> (mandatory) &mdash; the port number (typically, <command>--port=3260</command>)
-	</para>
-</listitem>
-
-<listitem>
-	<para>
-	<command>--user=</command> &mdash; the username required to authenticate with the target
-	</para>
-</listitem>
-
-<listitem>
-	<para>
-	<command>--password=</command> &mdash; the password that corresponds with the username specified for the target
-	</para>
-</listitem>
-
-<listitem>
-	<para>
-	<command>--reverse-user=</command> &mdash; the username required to authenticate with the initiator from a target that uses reverse CHAP authentication
-	</para>
-</listitem>
-
-<listitem>
-	<para>
-	<command>--reverse-password=</command> &mdash; the password that corresponds with the username specified for the initiator
-	</para>
-</listitem>
-
-						
-					</itemizedlist>
-				</listitem>
-			</varlistentry>
-		
-			<varlistentry>
-				<term><command>iscsiname</command> (optional) 	  </term>
-
-				<listitem>
-					<para>
-					<indexterm significance="normal">
-					<primary>kickstart file</primary>
-					<secondary><command>iscsiname</command>
-					</secondary>
-				</indexterm>			
-				Assigns a name to an iSCSI node specified by the iscsi parameter. If you use the <parameter>iscsi</parameter> parameter in your kickstart file, this parameter is mandatory, and you must specify <parameter>iscsiname</parameter> in the kickstart file before you specify <parameter>iscsi</parameter>.
-					</para>
-				</listitem>
-			</varlistentry>
-			
-			<varlistentry>
-				<term><command>key</command> (optional)</term>
-				<listitem>
-					<para><indexterm significance="normal">
-					<primary>kickstart file</primary>
-					<secondary><command>key</command>
-					</secondary>
-				</indexterm>
-						Specify an installation key, which is needed to aid in package selection and identify your system for support purposes. This command is specific to Red Hat Enterprise Linux; it has no meaning for Fedora and will be ignored.
-					</para>
-
-					<itemizedlist>
-
-<listitem>
-	<para>
-		<command>--skip</command> &mdash; Skip entering a key. Usually if the key command is not given, anaconda will pause at this step to prompt for a key. This option allows automated installation to continue if you do not have a key or do not want to provide one.
-	</para>
-</listitem>
-						
-					</itemizedlist>
-				</listitem>
-			</varlistentry>
-			
-			<varlistentry>
-				<term><command>keyboard</command> (required) 	  </term>
-
-				<listitem>
-					<para>
-					<indexterm significance="normal">
-					<primary>kickstart file</primary>
-					<secondary><command>keyboard</command>
-					</secondary>
-				</indexterm>					Sets system keyboard type. Here is the list of available keyboards on i386 and Alpha machines:
-					</para>
-<screen>
-be-latin1, bg, br-abnt2, cf, cz-lat2, cz-us-qwertz, de, de-latin1, 
-de-latin1-nodeadkeys, dk, dk-latin1, dvorak, es, et, fi, fi-latin1, 
-fr, fr-latin0, fr-latin1, fr-pc, fr_CH, fr_CH-latin1, gr, hu, hu101, 
-is-latin1, it, it-ibm, it2, jp106, la-latin1, mk-utf, no, no-latin1, 
-pl, pt-latin1, ro_win, ru, ru-cp1251, ru-ms, ru1, ru2,  ru_win, 
-se-latin1, sg, sg-latin1, sk-qwerty, slovene, speakup,  speakup-lt, 
-sv-latin1, sg, sg-latin1, sk-querty, slovene, trq, ua,  uk, us, us-acentos
-</screen>
-					<para>
-						The file <filename>/usr/lib/python2.2/site-packages/rhpl/keyboard_models.py</filename> also contains this list and is part of the <filename>rhpl</filename> package.
-					</para>
-				</listitem>
-			</varlistentry>
-
-			<varlistentry>
-				<term><command>lang</command> (required) 	       	    <indexterm significance="normal">
-						<primary>kickstart file</primary>
-						<secondary><command>lang</command>
-						</secondary>
-					</indexterm></term>
-				<listitem>
-					<para>
-						Sets the language to use during installation and the default
-       language to use on the installed system. For example, to set the language to English, the kickstart file should contain the following line:
-					</para>
-<screen>lang en_US</screen>
-					<para>
-						The file <filename>/usr/share/system-config-language/locale-list</filename> provides a list of the valid language codes in the first column of each line and is part of the <filename>system-config-language</filename>
-						package.
-					</para>
-					
-					<para>
-						Certain languages (mainly Chinese, Japanese, Korean, and Indic languages) are not supported during text mode installation.  If one of these languages is specified using the lang command, installation will continue in English though the running system will have the specified langauge by default.	
-					</para>
-				</listitem>
-			</varlistentry>
-
-			
-			<varlistentry>
-				<term><command>langsupport</command> (deprecated)
-				<indexterm significance="normal">
-					<primary>kickstart file</primary>
-					<secondary><command>langsupport</command>
-					</secondary>
-				</indexterm>
-				 	  </term>
-				<listitem>
-					<para>
-						The langsupport keyword is deprecated and its use will cause an error message to be printed to the screen and installation to halt. Instead of using the langsupport keyword, you should now list the support package groups for all languages you want supported in the <command>%packages</command> section of your kickstart file.  For instance, adding support for French means you should add the following to <command>%packages</command>:
-					</para>
-					
-					<screen>@french-support</screen>
-
-				</listitem>
-			</varlistentry>
-
-			<varlistentry>
-				<term><command>logvol</command> (optional)				<indexterm significance="normal">
-					<primary>kickstart file</primary>
-					<secondary><command>logvol</command>
-					</secondary>
-				</indexterm>
-				<indexterm significance="normal">
-					<primary>LVM</primary>
-					<secondary>with kickstart</secondary>
-				</indexterm>
-				<indexterm significance="normal">
-					<primary>kickstart installations</primary>
-					<secondary>LVM</secondary>
-				</indexterm>
- 	  </term>
-				<listitem>
-					<para>
-						Create a logical volume for Logical Volume Management (LVM) with the syntax:
-					</para>
-<screen>logvol <replaceable>&lt;mntpoint&gt;</replaceable> --vgname=<replaceable>&lt;name&gt;</replaceable> --size=<replaceable>&lt;size&gt;</replaceable> --name=<replaceable>&lt;name&gt;</replaceable> <replaceable>&lt;options&gt;</replaceable></screen>
-					<para>
-						The options are as follows:
-					</para>
-
-					<itemizedlist>
-						
-
-<listitem>
-	<para>
-		<command>--noformat</command> &mdash; Use an existing logical volume and do not format it.
-	</para>
-</listitem>
-						
-
-<listitem>
-	<para>
-		<command>--useexisting</command> &mdash; Use an existing logical volume and reformat it.
-	</para>
-</listitem>
-						
-<listitem>
-	<para>
-		<command>--fstype=</command> &mdash; Sets the file system type for the logical volume. Valid values are <command>xfs</command>, <command>ext2</command>, <command>ext3</command>, <command>ext4</command>, <command>swap</command>, <command>vfat</command>, and <command>hfs</command>.
-	</para>
-</listitem>
-
-<!--	BZ#435069, edit!-->					
-<listitem>
-	<para>
-	<command>--fsoptions=</command> &mdash; Specifies a free form string of options to be used when mounting the filesystem. This string will be copied into the <filename>/etc/fstab</filename> file of the installed system and should be enclosed in quotes.
-	</para>
-	</listitem>
-						
-<listitem>
-	<para>
-		<command>--bytes-per-inode=</command> &mdash; Specifies the size of inodes on the filesystem to be made on the logical volume. Not all filesystems support this option, so it is silently ignored for those cases.
-	</para>
-</listitem>
-						
-<listitem>
-	<para>
-		<command>--grow=</command> &mdash; Tells the logical volume to grow to fill available space (if any), or up to the maximum size setting.
-	</para>
-</listitem>
-
-<listitem>
-	<para>
-		<command>--maxsize=</command> &mdash; The maximum size in megabytes when the logical volume is set to grow. Specify an integer value here, and do not append the number with MB.
-	</para>
-</listitem>
-						
-<listitem>
-	<para>
-		<command>--recommended=</command> &mdash; Determine the size of the logical volume automatically.
-	</para>
-</listitem>
-						
-<listitem>
-	<para>
-		 <command>--percent=</command> &mdash; Specify the size of the logical volume as a percentage of available space in the volume group.
-	</para>
-</listitem>
-<listitem>
-	<para>
-		<command>--encrypted</command> &mdash; Specifies that this logical volume should be encrypted.  
-	</para>
-</listitem>
-
-<listitem>
-	<para>
-		<command>--passphrase=</command> &mdash; Specifies the passphrase to use when encrypting this logical volume. Without the above <command>--encrypted</command> option, this option does nothing. If no passphrase is specified, the default system-wide one is used, or the installer will stop and prompt if there is no default. 
-	</para>
-</listitem>
-<listitem>
-	<para>
-		<command>--escrowcert=<replaceable>URL_of_X.509_certificate</replaceable></command> &mdash; Store data encryption keys of all encrypted volumes as files in <filename>/</filename> (root), encrypted using the X.509 certificate from the URL specified with <replaceable>URL_of_X.509_certificate</replaceable>. The keys are stored as a separate file for each encrypted volume. This option is only meaningful if <command>--encrypted</command> is specified. 
-	</para>
-</listitem>
-<listitem>
-	<para>
-		<command>--backuppassphrase=</command> &mdash; Add a randomly-generated passphrase to each encrypted volume. Store these passphrases in separate files in <filename>/</filename> (root), encrypted using the X.509 certificate specified with <command>--escrowcert</command>. This option is only meaningful if <command>--escrowcert</command> is specified. 
-	</para>
-</listitem>	
-					</itemizedlist>
-
-					<para>
-						Create the partition first, create the logical volume group, and then create the logical volume. For example:
-					</para>
-<screen>part pv.01 --size 3000 
-volgroup myvg pv.01
-logvol / --vgname=myvg --size=2000 --name=rootvol
-</screen>
-				</listitem>
-			</varlistentry>
-
-			<varlistentry>
-				<term><command>logging</command> (optional)				<indexterm significance="normal">
-					<primary>kickstart file</primary>
-					<secondary><command>logging</command>
-					</secondary>
-				</indexterm>
- 	  			</term>
-				<listitem>
-					<para>
-						This command controls the error logging of anaconda during installation. It has no effect on the installed system.
-					</para>
-
-					<itemizedlist>
-
-<listitem>
-	<para>
-		 <command>--host=</command> &mdash; Send logging information to the given remote host, which must be running a syslogd process configured to accept remote logging.
-	</para>
-</listitem>
-						
-<listitem>
-	<para>
-		  <command>--port=</command> &mdash; If the remote syslogd process uses a port other than the default, it may be specified with this option.
-	</para>
-</listitem>
-						
-<listitem>
-	<para>
-		  <command>--level=</command> &mdash; One of debug, info, warning, error, or critical.
-	</para>
-	
-	<para>
-		Specify the minimum level of messages that appear on tty3.  All messages will still be sent to the log file regardless of this level, however.
-	</para>
-</listitem>
-						
-					</itemizedlist>
-				</listitem>
-			</varlistentry>
-			
-			<varlistentry>
-				<term><command>mediacheck</command> (optional)				<indexterm significance="normal">
-					<primary>kickstart file</primary>
-					<secondary><command>mediacheck</command>
-					</secondary>
-				</indexterm>
- 	  			</term>
-				<listitem>
-					<para>
-						If given, this will force anaconda to run mediacheck on the installation media.  This command requires that installs be attended, so it is disabled by default.
-					</para>
-				</listitem>
-			</varlistentry>
-
-			<varlistentry>
-				<term><command>monitor</command> (optional)				<indexterm significance="normal">
-					<primary>kickstart file</primary>
-					<secondary><command>mediacheck</command>
-					</secondary>
-				</indexterm>
- 	  			</term>
-				<listitem>
-					<para>
-						 If the monitor command is not given, anaconda will use X to automatically detect your monitor settings.  Please try this before manually configuring your monitor.
-					</para>
-					
-					<itemizedlist>
-						
-<listitem>
-	<para>
-		  <command>--hsync=</command> &mdash; Specifies the horizontal sync frequency of the monitor.
-	</para>
-</listitem>
-
-<listitem>
-	<para>
-		   <command>--monitor=</command> &mdash; Use specified monitor; monitor name should be from the list of monitors in /usr/share/hwdata/MonitorsDB from the hwdata package. The list of monitors can also be found on the X Configuration screen of the Kickstart Configurator. This is ignored if --hsync or --vsync is provided. If no monitor information is provided, the installation program tries to probe for it automatically.
-	</para>
-</listitem>
-
-<listitem>
-	<para>
-		  <command>--noprobe=</command> &mdash; Do not try to probe the monitor.
-	</para>
-	
-</listitem>
-
-<listitem>
-	<para>
-		  <command>--vsync=</command> &mdash; Specifies the vertical sync frequency of the monitor.
-	</para>
-</listitem>
-						
-					</itemizedlist>
-				</listitem>
-			</varlistentry>
-
-			<varlistentry>
-				<term><command>mouse</command> (deprecated)				<indexterm significance="normal">
-					<primary>kickstart file</primary>
-					<secondary><command>mouse</command>
-					</secondary>
-				</indexterm>
- 	  			</term>
-				<listitem>
-					<para>The mouse keyword is deprecated.</para>
-
-				</listitem>
-			</varlistentry>
-
-			<varlistentry>
-				<term><command>network</command> (optional) 	  				<indexterm significance="normal">
-					<primary>kickstart file</primary>
-					<secondary><command>network</command>
-					</secondary>
-				</indexterm></term>
-
-				<listitem>
-					<para>
-						Configures network information for the system. If the kickstart installation does not require networking (in other words, it is not installed over NFS, HTTP, or FTP), networking is not configured for the system. If the installation does require networking and network information is not provided in the kickstart file, the installation program assumes that the installation should be done over eth0 via a dynamic IP address (BOOTP/DHCP), and configures the final, installed system to determine its IP address dynamically. The <command>network</command> option configures networking information for kickstart installations via a network as well as for the installed system.
-					</para>
-					<itemizedlist>
-
-<listitem>
-	<para>
-		<command>--bootproto=</command> &mdash; One of <command>dhcp</command>, <command>bootp</command>, or <command>static</command>.
-	</para>
-
-	<para>
-		It defaults to <command>dhcp</command>. <command>bootp</command> and <command>dhcp</command> are treated the same.
-	</para>
-
-	<para>
-		The DHCP method uses a DHCP server system to obtain its networking configuration. As you might guess, the BOOTP method is similar, requiring a BOOTP server to supply the networking configuration. To direct a system to use DHCP:
-	</para>
-<screen>network --bootproto=dhcp</screen>
-	<para>
-		To direct a machine to use BOOTP to obtain its networking configuration, use the following line in the kickstart file:
-	</para>
-<screen>network --bootproto=bootp</screen>
-	<para>
-		The static method requires that you enter all the required networking information in the kickstart file. As the name implies, this information is static and is used during and after the installation. The line for static networking is more complex, as you must include all network configuration information on one line. You must specify the IP address, netmask, gateway, and nameserver.
-	</para>
-	<para>
-		Note that although the presentation of this example on this page has broken the line, in a real kickstart file, you must include all this information on a single line with no break.
-	</para>
-<screen>network --bootproto=static --ip=10.0.2.15 --netmask=255.255.255.0
- --gateway=10.0.2.254 --nameserver=10.0.2.1
-</screen>
-	<para>
-		If you use the static method, be aware of the following two restrictions:
-	</para>
-
-	<itemizedlist>
-		<listitem>
-<para>
-	All static networking configuration information must be specified on <emphasis>one</emphasis> line; you cannot wrap lines using a backslash, for example.
-</para>
-		</listitem>
-
-		<listitem>
-
-					<para>You can also configure multiple nameservers here. To do so, specify them as a comma-delimited list in the command line.</para>
-					<para>
-						Note that although the presentation of this example on this page has broken the line, in a real kickstart file, you must include all this information on a single line with no break.
-					</para>
-					
-<screen>network --bootproto=static --ip=10.0.2.15 --netmask=255.255.255.0
- --gateway=10.0.2.254 --nameserver 192.168.2.1,192.168.3.1
-</screen>					
-<!--	BZ#255901, above replaces below, can specify multiple nameservers		<para>
-	You can only specify one nameserver here. However, you can use the kickstart file's <command>%post</command> section (described in <xref linkend="s1-kickstart2-postinstallconfig"/>) to add more name servers, if needed.
-</para>-->
-		</listitem>
-	</itemizedlist>
-</listitem>
-					
-<listitem>
-	<para>
-		<command>--device=</command> &mdash; Used to select a specific Ethernet device for installation. Note that using <command>--device=</command> is not effective unless the kickstart file is a local file (such as <command>ks=floppy</command>), since the installation program configures the network to find the kickstart file. For example:
-	</para>
-<screen>network --bootproto=dhcp --device=eth0</screen>
-</listitem>
-						
-<listitem>
-	<para>
-		<command>--ip=</command> &mdash; IP address for the machine to be installed.
-	</para>
-</listitem>
-						
-<listitem>
-	<para>
-		<command>--gateway=</command> &mdash; Default gateway as an IP address.
-	</para>
-</listitem>
-						
-<listitem>
-	<para>
-		<command>--nameserver=</command> &mdash; Primary nameserver, as an IP address.
-	</para>
-</listitem>
-
-<listitem>
-	<para>
-		<command>--nodns</command> &mdash; Do not configure any DNS server.
-	</para>
-</listitem>
-						
-<listitem>
-	<para>
-		<command>--netmask=</command> &mdash; Netmask for the installed system.
-	</para>
-</listitem>
-						
-<listitem>
-	<para>
-		<command>--hostname=</command> &mdash; Hostname for the installed system.
-	</para>
-</listitem>
-						
-<listitem>
-	<para>
-		<command>--ethtool=</command> &mdash; Specifies additional low-level settings for the network device which will be passed to the ethtool program.
-	</para>
-</listitem>
-						
-<listitem>
-	<para>
-		<command>--essid=</command> &mdash; The network ID for wireless networks.
-	</para>
-</listitem>
-						
-<listitem>
-	<para>
-		<command>--wepkey=</command> &mdash; The encryption key for wireless networks.
-	</para>
-</listitem>
-						
-<listitem>
-	<para>
-		<command>--onboot=</command> &mdash; Whether or not to enable the device at boot time.
-	</para>
-</listitem>
-						
-<listitem>
-	<para>
-		<command>--class=</command> &mdash; The DHCP class.
-	</para>
-</listitem>
-						
-<listitem>
-	<para>
-		<command>--mtu=</command> &mdash; The MTU of the device.
-	</para>
-</listitem>
-						
-<listitem>
-	<para>
-		<command>--noipv4</command> &mdash; Disable IPv4 on this device.
-	</para>
-</listitem>
-						
-<listitem>
-	<para>
-		<command>--noipv6</command> &mdash; Disable IPv6 on this device.
-	</para>
-</listitem>
-						
-					</itemizedlist>
-				</listitem>
-			</varlistentry>
-
-			<varlistentry>
-				<term><command>multipath</command> (optional)				<indexterm significance="normal">
-					<primary>kickstart file</primary>
-					<secondary><command>multipath</command>
-					</secondary>
-				</indexterm>
- 	  			</term>
-				<listitem>
-					<para>
-						multipath --name= --device= --rule=
-					</para>
-
-				</listitem>
-			</varlistentry>
-
-			
-			<varlistentry>
-				<term>	<indexterm significance="normal">
-					<primary>kickstart file</primary>
-					<secondary><command>part</command>
-					</secondary>
-				</indexterm>
-				<indexterm significance="normal">
-					<primary>kickstart file</primary>
-					<secondary><command>partition</command>
-					</secondary>
-				</indexterm>
-<command>part</command> or <command>partition</command> (required for installs, ignored for upgrades) 	  </term>
-				<listitem>
-					<para>
-						Creates a partition on the system.
-					</para>
-
-					<para>
-						If more than one Fedora installation exists on the system on different partitions, the installation program prompts the user and asks which installation to upgrade.
-					</para>
-
-					<warning>
-						<title>Warning</title>
-
-						<para>
-All partitions created are formatted as part of the installation process unless <command>--noformat</command> and <command>--onpart</command> are used.
-						</para>
-					</warning>
-					
-					<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Kickstart-note-1.xml"/>
-					<!-- If you select text mode for a kickstart installation, you must ensure -->
-
-					<para>
-						For a detailed example of <command>part</command> in action, refer to <xref linkend="s2-kickstart2-options-part-examples"/>.
-					</para>
-
-					<itemizedlist>
-						
-
-<listitem>
-	<para>
-		<replaceable>&lt;mntpoint&gt;</replaceable> &mdash; The <replaceable>&lt;mntpoint&gt;</replaceable> is where the partition is mounted and must be of one of the following forms:
-	</para>
-
-	<itemizedlist>
-		<listitem>
-<para>
-	<filename>/<replaceable>&lt;path&gt;</replaceable></filename>
-</para>
-
-<para>
-	For example, <command>/</command>, <command>/usr</command>, <command>/home</command>
-</para>
-		</listitem>
-
-		<listitem>
-<para>
-	<command>swap</command>
-</para>
-
-<para>
-	The partition is used as swap space.
-</para>
-
-<para>
-	To determine the size of the swap partition automatically, use the <command>--recommended</command> option:
-</para>
-<screen>swap --recommended</screen>
-
-<para>The recommended maximum swap size for machines with less than 2GB of RAM is twice the amount of RAM. For machines with 2GB or more, this recommendation changes to 2GB plus the amount of RAM. </para>
-
-		</listitem>
-
-		<listitem>
-<para>
-	<command>raid.<replaceable>&lt;id&gt;</replaceable></command>
-</para>
-
-<para>
-	The partition is used for software RAID (refer to <command>raid</command>).
-</para>
-		</listitem>
-
-		<listitem>
-<para>
-	<command>pv.<replaceable>&lt;id&gt;</replaceable></command>
-</para>
-
-<para>
-	The partition is used for LVM (refer to <command>logvol</command>).
-</para>
-		</listitem>
-	</itemizedlist>
-</listitem>
-						
-<listitem>
-	<para>
-		<command>--size=</command> &mdash; The minimum partition size in megabytes. Specify an integer value here such as 500. Do not append the number with MB.
-	</para>
-</listitem>
-						
-<listitem>
-	<para>
-		<command>--grow</command> &mdash; Tells the partition to grow to fill available space (if any), or up to the maximum size setting.
-	</para>
-<!-- BZ#471148	 -->
-<note>
-	<title>Note</title>
-	<para>If you use <command>--grow=</command> without setting <command>--maxsize=</command> on a swap partition, <application>Anaconda</application> will limit the maximum size of the swap partition. For systems that have less than 2GB of physical memory, the imposed limit is twice the amount of physical memory.  For systems with more than 2GB, the imposed limit is the size of physical memory plus 2GB.</para>
-
-</note>	
-</listitem>
-						
-<listitem>
-	<para>
-		<command>--maxsize=</command> &mdash; The maximum partition size in megabytes when the partition is set to grow. Specify an integer value here, and do not append the number with MB.
-	</para>
-</listitem>
-						
-<listitem>
-	<para>
-		<command>--noformat</command> &mdash; Tells the installation program not to format the partition, for use with the <command>--onpart</command> command.
-	</para>
-</listitem>
-						
-<listitem>
-	<para>
-		<command>--onpart=</command> or <command>--usepart=</command> &mdash; Put the partition on the <emphasis>already existing</emphasis> device. For example:
-	</para>
-<screen>partition /home --onpart=hda1</screen>
-	<para>
-		puts <filename>/home</filename> on <filename>/dev/hda1</filename>, which must already exist.
-	</para>
-</listitem>
-						
-<listitem>
-	<para>
-		<command>--ondisk=</command> or <command>--ondrive=</command> &mdash; Forces the partition to be created on a particular disk. For example, <command>--ondisk=sdb</command> puts the partition on the second SCSI disk on the system.
-	</para>
-</listitem>
-						
-<listitem>
-	<para>
-		<command>--asprimary</command> &mdash; Forces automatic allocation of the partition as a primary partition, or the partitioning fails.
-	</para>
-</listitem>
-						
-<listitem>
-	<para>
-		<command>--type=</command> (replaced by <command>fstype</command>) &mdash; This option is no longer available. Use <command>fstype</command>.
-	</para>
-</listitem>
-						
-<listitem>
-	<para>
-		<command>--fstype=</command> &mdash; Sets the file system type for the partition. Valid values are <command>xfs</command>, <command>ext2</command>, <command>ext3</command>, <command>ext4</command>, <command>swap</command>, <command>vfat</command>, and <command>hfs</command>.
-	</para>
-</listitem>
-						
-<listitem>
-	<para>
-		<command>--bytes-per-inode=</command> &mdash; Specifies the size of inodes on the filesystem to be made on the partition. Not all filesystems support this option, so it is silently ignored for those cases.
-	</para>
-</listitem>
-						
-<listitem>
-	<para>
-		<command>--recommended</command> &mdash; Determine the size of the partition automatically.
-	</para>
-</listitem>
-						
-<listitem>
-	<para>
-		<command>--onbiosdisk</command> &mdash; Forces the partition to be created on a particular disk as discovered by the BIOS.
-	</para>
-</listitem>
-
-<listitem>
-	<para>
-		<command>--encrypted</command> &mdash; Specifies that this partition should be encrypted.  
-	</para>
-</listitem>
-
-<listitem>
-	<para>
-		<command>--passphrase=</command> &mdash; Specifies the passphrase to use when encrypting this partition. Without the above <command>--encrypted</command> option, this option does nothing. If no passphrase is specified, the default system-wide one is used, or the installer will stop and prompt if there is no default. 
-	</para>
-</listitem>
-<listitem>
-	<para>
-		<command>--escrowcert=<replaceable>URL_of_X.509_certificate</replaceable></command> &mdash; Store data encryption keys of all encrypted partitions as files in <filename>/</filename> (root), encrypted using the X.509 certificate from the URL specified with <replaceable>URL_of_X.509_certificate</replaceable>. The keys are stored as a separate file for each encrypted partition. This option is only meaningful if <command>--encrypted</command> is specified. 
-	</para>
-</listitem>
-<listitem>
-	<para>
-		<command>--backuppassphrase=</command> &mdash; Add a randomly-generated passphrase to each encrypted partition. Store these passphrases in separate files in <filename>/</filename> (root), encrypted using the X.509 certificate specified with <command>--escrowcert</command>. This option is only meaningful if <command>--escrowcert</command> is specified. 
-	</para>
-</listitem>
-					</itemizedlist>
-
-					<note>
-						<title>Note</title>
-
-						<para>
-If partitioning fails for any reason, diagnostic messages appear on virtual console 3.
-						</para>
-					</note>
-				</listitem>
-			</varlistentry>
-
-			<varlistentry>
-				<term><indexterm significance="normal">
-					<primary>kickstart file</primary>
-					<secondary><command>poweroff</command>
-					</secondary>
-				</indexterm>
-<command>poweroff</command> (optional) 	  </term>
-				<listitem>
-					<para>
-						Shut down and power off the system after the installation has successfully completed. Normally during a manual installation, anaconda displays a message and waits for the user to press a key before rebooting. During a kickstart installation, if no
-						completion method is specified, the <command>reboot</command> option is used as default.
-					</para>
-
-					<para>
-						The <command>poweroff</command> option is roughly equivalent to the <command>shutdown -p</command> command.
-					</para>
-
-					<note>
-						<title>Note</title>
-
-						<para>
-The <command>poweroff</command> option is highly dependent on the system hardware in use. Specifically, certain hardware components such as the BIOS, APM (advanced power management), and ACPI (advanced configuration and power
-interface) must be able to interact with the system kernel. Contact your manufacturer for more information on you system's APM/ACPI abilities.
-						</para>
-					</note>
-
-					<para>
-						For other completion methods, refer to the <command>halt</command>, <command>reboot</command>, and <command>shutdown</command> kickstart options.
-					</para>
-				</listitem>
-			</varlistentry>
-
-			<varlistentry>
-				<term><indexterm significance="normal">
-					<primary>kickstart file</primary>
-					<secondary><command>raid</command>
-					</secondary>
-				</indexterm>
-				<indexterm significance="normal">
-					<primary>RAID</primary>
-					<secondary>kickstart installations</secondary>
-				</indexterm>
-<command>raid</command> (optional) 	  </term>
-				<listitem>
-					<para>
-						Assembles a software RAID device. This command is of the form:
-					</para>
-<screen>raid <replaceable>&lt;mntpoint&gt;</replaceable> --level=<replaceable>&lt;level&gt;</replaceable> --device=<replaceable>&lt;mddevice&gt;</replaceable> <replaceable>&lt;partitions*&gt;</replaceable></screen>
-					<itemizedlist>
-						
-<listitem>
-	<para>
-		<replaceable>&lt;mntpoint&gt;</replaceable> &mdash; Location where the RAID file system is mounted. If it is <filename>/</filename>, the RAID level must be 1 unless a boot partition (<filename>/boot</filename>) is present. If a boot partition is present, the
-		<filename>/boot</filename> partition must be level 1 and the root (<filename>/</filename>) partition can be any of the available types. The <replaceable>&lt;partitions*&gt;</replaceable> (which denotes that
-		multiple partitions can be listed) lists the RAID identifiers to add to the RAID array.
-	</para>
-</listitem>
-						
-<listitem>
-	<para>
-		<command>--level=</command> &mdash; RAID level to use (0, 1, or 5).
-	</para>
-</listitem>
-<!-- 	BZ#432917, was 8 RAID devices; corrected as "16" (md0-md15) -->
-<listitem>
-	<para>
-		<command>--device=</command> &mdash; Name of the RAID device to use (such as md0 or md1). RAID devices range from md0 to md15, and each may only be used once.
-	</para>
-</listitem>
-						
-<listitem>
-	<para>
-		 <command>--bytes-per-inode=</command> &mdash; Specifies the size of inodes on the filesystem to be made on the RAID device. Not all filesystems support this option, so it is silently ignored for those cases.
-	</para>
-</listitem>
-						
-<listitem>
-	<para>
-		<command>--spares=</command> &mdash; Specifies the number of spare drives allocated for the RAID array. Spare drives are used to rebuild the array in case of drive failure.
-	</para>
-</listitem>
-						
-<listitem>
-	<para>
-		<command>--fstype=</command> &mdash; Sets the file system type for the RAID array. Valid values are <command>xfs</command>, <command>ext2</command>, <command>ext3</command>, <command>ext4</command>, <command>swap</command>, <command>vfat</command>, and <command>hfs</command>.
-	</para>
-</listitem>
-						
-<listitem>
-	<para>
-		<command>--fsoptions=</command> &mdash; Specifies a free form string of options to be used when mounting the filesystem. This string will be copied into the /etc/fstab file of the installed system and should be enclosed in quotes.
-	</para>
-</listitem>
-						
-<listitem>
-	<para>
-		<command>--noformat</command> &mdash; Use an existing RAID device and do not format the RAID array.
-	</para>
-</listitem>
-						
-<listitem>
-	<para>
-		<command>--useexisting</command> &mdash; Use an existing RAID device and reformat it.
-	</para>
-</listitem>
-
-<listitem>
-	<para>
-		<command>--encrypted</command> &mdash; Specifies that this RAID device should be encrypted.  
-	</para>
-</listitem>
-
-<listitem>
-	<para>
-		<command>--passphrase=</command> &mdash; Specifies the passphrase to use when encrypting this RAID device. Without the above <command>--encrypted</command> option, this option does nothing. If no passphrase is specified, the default system-wide one is used, or the installer will stop and prompt if there is no default. 
-	</para>
-</listitem>
-<listitem>
-	<para>
-		<command>--escrowcert=<replaceable>URL_of_X.509_certificate</replaceable></command> &mdash; Store the data encryption key for this device in a file in <filename>/</filename> (root), encrypted using the X.509 certificate from the URL specified with <replaceable>URL_of_X.509_certificate</replaceable>. This option is only meaningful if <command>--encrypted</command> is specified. 
-	</para>
-</listitem>
-<listitem>
-	<para>
-		<command>--backuppassphrase=</command> &mdash; Add a randomly-generated passphrase to this device. Store the passphrase in a file in <filename>/</filename> (root), encrypted using the X.509 certificate specified with <command>--escrowcert</command>. This option is only meaningful if <command>--escrowcert</command> is specified. 
-	</para>
-</listitem>
-					</itemizedlist>
-					<para>
-						The following example shows how to create a RAID level 1 partition for <filename>/</filename>, and a RAID level 5 for <filename>/usr</filename>, assuming there are three SCSI disks on the system. It also creates three
-						swap partitions, one on each drive.
-					</para>
-<screen>part raid.01 --size=60 --ondisk=sda
-part raid.02 --size=60 --ondisk=sdb 
-part raid.03 --size=60 --ondisk=sdc
-</screen>
-<screen>part swap --size=128 --ondisk=sda  
-part swap --size=128 --ondisk=sdb  
-part swap --size=128 --ondisk=sdc
-</screen>
-<screen>part raid.11 --size=1 --grow --ondisk=sda  
-part raid.12 --size=1 --grow --ondisk=sdb  
-part raid.13 --size=1 --grow --ondisk=sdc
-</screen>
-<screen>raid / --level=1 --device=md0 raid.01 raid.02 raid.03  
-raid /usr --level=5 --device=md1 raid.11 raid.12 raid.13
-</screen>
-					<para>
-						For a detailed example of <command>raid</command> in action, refer to <xref linkend="s2-kickstart2-options-part-examples"/>.
-					</para>
-				</listitem>
-			</varlistentry>
-
-			<varlistentry>
-				<term>	<indexterm significance="normal">
-					<primary>kickstart file</primary>
-					<secondary><command>reboot</command>
-					</secondary>
-				</indexterm>
-<command>reboot</command> (optional) 	  </term>
-				<listitem>
-					<para>
-						Reboot after the installation is successfully completed (no arguments). Normally, kickstart displays a message and waits for the user to press a key before rebooting.
-					</para>
-
-					<para>
-						The <command>reboot</command> option is roughly equivalent to the <command>shutdown -r</command> command.
-					</para>
-
-					<note>
-						<title>Note</title>
-
-						<para>
-Use of the <command>reboot</command> option <emphasis>may</emphasis> result in an endless installation loop, depending on the installation media and method.
-						</para>
-
-						<para>
-The <command>reboot</command> option is the default completion method if no other methods are explicitly specified in the kickstart file.
-						</para>
-					</note>
-
-					<para>
-						For other completion methods, refer to the <command>halt</command>, <command>poweroff</command>, and <command>shutdown</command> kickstart options.
-					</para>
-				</listitem>
-			</varlistentry>
-
-			<varlistentry>
-				<term><command>repo</command> (optional)				<indexterm significance="normal">
-					<primary>kickstart file</primary>
-					<secondary><command>mediacheck</command>
-					</secondary>
-				</indexterm>
- 	  			</term>
-				<listitem>
-					<para>
-						Configures additional yum repositories that may be used as sources for package installation.  Multiple repo lines may be specified.
-					</para>
-					
-<screen>repo --name=<replaceable>&lt;repoid&gt;</replaceable> [--baseurl=<replaceable>&lt;url&gt;</replaceable>| --mirrorlist=<replaceable>&lt;url&gt;</replaceable>]
-</screen>
-					<itemizedlist>
-						
-<listitem>
-	<para>
-		  <command>--name=</command> &mdash; The repo id. This option is required.
-	</para>
-</listitem>
-						
-<listitem>
-	<para>
-		   <command>--baseurl=</command> &mdash; The URL for the repository. The variables that may be used in yum repo config files are not supported here. You may use one of either this option or --mirrorlist, not both.
-	</para>
-</listitem>
-						
-<listitem>
-	<para>
-		  <command>--mirrorlist=</command> &mdash; The URL pointing at a list of mirrors for the repository.  The variables that may be used in yum repo config files are not supported here.  You may use one of either this option or --baseurl, not both.
-	</para>
-	
-</listitem>
-
-					</itemizedlist>
-						
-				</listitem>
-			</varlistentry>
-			
-			<varlistentry>
-				<term><command>rootpw</command> (required) 	  </term>
-				<listitem>
-					<para>
-				<indexterm significance="normal">
-					<primary>kickstart file</primary>
-					<secondary><command>rootpw</command>
-					</secondary>
-				</indexterm>
-						Sets the system's root password to the <replaceable>&lt;password&gt;</replaceable> argument.
-					</para>
-<screen>rootpw [--iscrypted] <replaceable>&lt;password&gt;</replaceable></screen>
-					<itemizedlist>
-						
-<listitem>
-	<para>
-		<command>--iscrypted</command> &mdash; If this is present, the password argument is assumed to already be encrypted.
-	</para>
-</listitem>
-						
-					</itemizedlist>
-				</listitem>
-			</varlistentry>
-
-			<varlistentry>
-				<term><command>selinux</command> (optional) 	  </term>
-				<listitem>
-					<para>
-				<indexterm significance="normal">
-					<primary>kickstart file</primary>
-					<secondary><command>selinux</command>
-					</secondary>
-				</indexterm>
-						Sets the state of SELinux on the installed system. SELinux defaults to enforcing in anaconda.
-					</para>
-
-					<screen>selinux [--disabled|--enforcing|--permissive]</screen>
-
-					<itemizedlist>
-						
-<listitem>
-	<para>
-		<command>--enforcing</command> &mdash; Enables SELinux with the default targeted policy being enforced.
-	</para>
-
-	<note>
-		<title>Note</title>
-
-		<para>
-If the <command>selinux</command> option is not present in the kickstart file, SELinux is enabled and set to <command>--enforcing</command> by default.
-		</para>
-	</note>
-</listitem>
-						
-<listitem>
-	<para>
-		<command>--permissive</command> &mdash; Outputs warnings based on the SELinux policy, but does not actually enforce the policy.
-	</para>
-</listitem>
-						
-<listitem>
-	<para>
-		<command>--disabled</command> &mdash; Disables SELinux completely on the system.
-	</para>
-</listitem>
-						
-					</itemizedlist>
-					<para>
-						For complete information regarding SELinux for Fedora, refer to the <citetitle>Fedora &PRODVER; Security-Enhanced Linux User Guide</citetitle>.
-					</para>
-				</listitem>
-			</varlistentry>
-
-			<varlistentry>
-				<term><command>services</command> (optional) 	  </term>
-				<listitem>
-					<para>
-				<indexterm significance="normal">
-					<primary>kickstart file</primary>
-					<secondary><command>services</command>
-					</secondary>
-				</indexterm>
-						Modifies the default set of services that will run under the default runlevel.  The services listed in the disabled list will be disabled before the services listed in the enabled list are enabled.
-					</para>
-
-					
-					<itemizedlist>
-
-<listitem>
-	<para>
-		<command>--disabled</command> &mdash; Disable the services given in the comma separated list.
-	</para>
-</listitem>
-						
-<listitem>
-	<para>
-		<command>--enabled</command> &mdash; Enable the services given in the comma separated list.
-	</para>
-</listitem>
-						
-					</itemizedlist>
-					
-					<important>
-					<title>Do not include spaces in the list of services</title>
-					<para>
-					If you include spaces in the comma-separated list, kickstart will enable or disable only the services up to the first space. For example:
-					</para>
-					<para>
-					<command>services --disabled auditd, cups,smartd, nfslock</command>
-					</para>
-					<para>
-					will disable only the <application>auditd</application> service. To disable all four services, this entry should include no spaces between services:
-					</para>
-					<para>
-					<command>services --disabled auditd,cups,smartd,nfslock</command>
-					</para>
-					</important>
-					
-				</listitem>
-			</varlistentry>
-			
-			<varlistentry>
-				<term><command>shutdown</command> (optional) 	  </term>
-				<listitem>
-					<para>
-				<indexterm significance="normal">
-					<primary>kickstart file</primary>
-					<secondary><command>shutdown</command>
-					</secondary>
-				</indexterm>
-						Shut down the system after the installation has successfully completed. During a kickstart installation, if no completion method is specified, the <command>reboot</command> option is used as default.
-					</para>
-
-					<para>
-						The <command>shutdown</command> option is roughly equivalent to the <command>shutdown</command> command.
-					</para>
-
-					<para>
-						For other completion methods, refer to the <command>halt</command>, <command>poweroff</command>, and <command>reboot</command> kickstart options.
-					</para>
-				</listitem>
-			</varlistentry>
-
-			<varlistentry>
-				<term><command>skipx</command> (optional) 	  </term>
-				<listitem>
-						<para>
-			<indexterm significance="normal">
-					<primary>kickstart file</primary>
-					<secondary><command>skipx</command>
-					</secondary>
-				</indexterm>
-					If present, X is not configured on the installed system.
-					</para>
-				</listitem>
-			</varlistentry>
-
-			<varlistentry>
-				<term><command>text</command> (optional) 	  </term>
-				<listitem>
-					<para>
-					<indexterm significance="normal">
-					<primary>kickstart file</primary>
-					<secondary><command>text</command>
-					</secondary>
-				</indexterm>
-					Perform the kickstart installation in text mode. Kickstart installations are performed in graphical mode by default.
-					</para>
-					<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Kickstart-note-1.xml"/>
-					<!-- If you select text mode for a kickstart installation, you must ensure -->
-				</listitem>
-			</varlistentry>
-
-			<varlistentry>
-				<term><command>timezone</command> (required) 	  </term>
-				<listitem>
-					<para>
-				<indexterm significance="normal">
-					<primary>kickstart file</primary>
-					<secondary><command>timezone</command>
-					</secondary>
-				</indexterm>
-						Sets the system time zone to <replaceable>&lt;timezone&gt;</replaceable> which may be any of the time zones listed by <command>timeconfig</command>.
-					</para>
-<screen>timezone [--utc] <replaceable>&lt;timezone&gt;</replaceable></screen>
-					<itemizedlist>
-						
-<listitem>
-	<para>
-		<command>--utc</command> &mdash; If present, the system assumes the hardware clock is set to UTC (Greenwich Mean) time.
-	</para>
-</listitem>
-						
-					</itemizedlist>
-				</listitem>
-			</varlistentry>
-
-			<varlistentry>
-				<term><command>upgrade</command> (optional) 	  </term>
-				<listitem>
-					<para>
-				<indexterm significance="normal">
-					<primary>kickstart file</primary>
-					<secondary><command>upgrade</command>
-					</secondary>
-				</indexterm>
-						Tells the system to upgrade an existing system rather than install a fresh system. You must specify one of <command>cdrom</command>, <command>harddrive</command>, <command>nfs</command>, or
-						<command>url</command> (for FTP and HTTP) as the location of the installation tree. Refer to <command>install</command> for details.
-					</para>
-				</listitem>
-			</varlistentry>
-
-		
-			<varlistentry>
-				<term><command>user</command> (optional) 	  </term>
-				<listitem>
-					<para>
-				<indexterm significance="normal">
-					<primary>kickstart file</primary>
-					<secondary><command>user</command>
-					</secondary>
-				</indexterm>
-						Creates a new user on the system.
-					</para>
-					
-<screen>user --name=<replaceable>&lt;username&gt;</replaceable> [--groups=<replaceable>&lt;list&gt;</replaceable>] [--homedir=<replaceable>&lt;homedir&gt;</replaceable>] [--password=<replaceable>&lt;password&gt;</replaceable>] [--iscrypted] [--shell=<replaceable>&lt;shell&gt;</replaceable>] [--uid=<replaceable>&lt;uid&gt;</replaceable>]</screen>
-
-					
-					<itemizedlist>
-						
-<listitem>
-	<para>
-		<command>--name=</command> &mdash; Provides the name of the user. This option is required.
-	</para>
-</listitem>
-						
-<listitem>
-	<para>
-		<command>--groups=</command> &mdash; In addition to the default group, a comma separated list of group names the user should belong to. The groups must exist before the user account is created.
-	</para>
-</listitem>
-						
-<listitem>
-	<para>
-		<command>--homedir=</command> &mdash; The home directory for the user. If not provided, this defaults to /home/<replaceable>&lt;username&gt;</replaceable>.
-	</para>
-</listitem>
-						
-<listitem>
-	<para>
-		<command>--password=</command> &mdash; The new user's password. If not provided, the account will be locked by default.
-	</para>
-</listitem>
-						
-<listitem>
-	<para>
-		<command>--iscrypted=</command> &mdash; Is the password provided by --password already encrypted or not?
-	</para>
-</listitem>
-						
-<listitem>
-	<para>
-		<command>--shell=</command> &mdash; The user's login shell. If not provided, this defaults to the system default.
-	</para>
-</listitem>
-						
-<listitem>
-	<para>
-		<command>--uid=</command> &mdash; The user's UID. If not provided, this defaults to the next available non-system UID.
-	</para>
-</listitem>
-						
-					</itemizedlist>
-				</listitem>
-			</varlistentry>			
-			
-			<varlistentry>
-				<term><command>vnc</command> (optional) 	  </term>
-				<listitem>
-					<para>
-				<indexterm significance="normal">
-					<primary>kickstart file</primary>
-					<secondary><command>vnc</command>
-					</secondary>
-				</indexterm>
-						Allows the graphical installation to be viewed remotely via VNC.  This method is usually preferred over text mode, as there are some size and language limitations in text installs.  With no options, this command will start a VNC server on the machine with no password and will print out the command that needs to be run to connect a remote machine.
-					</para>
-					
-<screen>vnc [--host=<replaceable>&lt;hostname&gt;</replaceable>] [--port=<replaceable>&lt;port&gt;</replaceable>] [--password=<replaceable>&lt;password&gt;</replaceable>]</screen>
-
-					<itemizedlist>
-						
-<listitem>
-	<para>
-		<command>--host=</command> &mdash; Instead of starting a VNC server on the install machine, connect to the VNC viewer process listening on the given hostname.
-	</para>
-</listitem>
-						
-<listitem>
-	<para>
-		<command>--port=</command> &mdash; Provide a port that the remote VNC viewer process is listening on. If not provided, anaconda will use the VNC default.
-	</para>
-</listitem>
-						
-<listitem>
-	<para>
-		<command>--password=</command> &mdash; Set a password which must be provided to connect to the VNC session. This is optional, but recommended.
-	</para>
-</listitem>
-						
-					</itemizedlist>
-				</listitem>
-			</varlistentry>	
-			
-			<varlistentry>
-				<term><command>volgroup</command> (optional) 	  </term>
-				<listitem>
-					<para>
-				<indexterm significance="normal">
-					<primary>kickstart file</primary>
-					<secondary><command>volgroup</command>
-					</secondary>
-				</indexterm>
-						Use to create a Logical Volume Management (LVM) group with the syntax:
-					</para>
-<screen>volgroup <replaceable>&lt;name&gt;</replaceable> <replaceable>&lt;partition&gt;</replaceable> <replaceable>&lt;options&gt;</replaceable></screen>
-					<para>
-						The options are as follows:
-					</para>
-
-					<itemizedlist>
-						
-<listitem>
-	<para>
-		<command>--noformat</command> &mdash; Use an existing volume group and do not format it.
-	</para>
-</listitem>
-						
-<listitem>
-	<para>
-		<command>--useexisting</command> &mdash; Use an existing volume group and reformat it.
-	</para>
-</listitem>
-						
-<listitem>
-	<para>
-		<command>--pesize=</command> &mdash; Set the size of the physical extents.
-	</para>
-</listitem>
-						
-					</itemizedlist>
-
-					<para>
-						Create the partition first, create the logical volume group, and then create the logical volume. For example:
-					</para>
-<screen>part pv.01 --size 3000 
-volgroup myvg pv.01 
-logvol / --vgname=myvg --size=2000 --name=rootvol</screen>
-					<para>
-						For a detailed example of <command>volgroup</command> in action, refer to <xref linkend="s2-kickstart2-options-part-examples"/>.
-					</para>
-				</listitem>
-			</varlistentry>
-
-				<varlistentry>
-				<term><command>xconfig</command> (optional) 	  </term>
-				<listitem>
-					<para>
-					<indexterm significance="normal">
-					<primary>kickstart file</primary>
-					<secondary><command>xconfig</command>
-					</secondary>
-				</indexterm>
-					Configures the X Window System. If this option is not given, the user must configure X manually during the installation, if X was installed; this option should not be used if X is not installed on the final system.
-					</para>
-
-					<itemizedlist>
-
-<listitem>
-	<para>
-		<command>--driver</command> &mdash; Specify the X driver to use for the video hardware.
-	</para>
-</listitem>
-						
-<listitem>
-	<para>
-		<command>--videoram=</command> &mdash; Specifies the amount of video RAM the video card has.
-	</para>
-</listitem>
-						
-<listitem>
-	<para>
-		<command>--defaultdesktop=</command> &mdash; Specify either GNOME or KDE to set the default desktop (assumes that GNOME Desktop Environment and/or KDE Desktop Environment has been installed through <command>%packages</command>).
-	</para>
-</listitem>
-						
-<listitem>
-	<para>
-		<command>--startxonboot</command> &mdash; Use a graphical login on the installed system.
-	</para>
-</listitem>
-						
-<listitem>
-	<para>
-		<command>--resolution=</command> &mdash; Specify the default resolution for the X Window System on the installed system. Valid values are 640x480, 800x600, 1024x768, 1152x864, 1280x1024, 1400x1050, 1600x1200. Be sure to specify a resolution that is compatible with the video card and
-		monitor.
-	</para>
-</listitem>
-						
-<listitem>
-	<para>
-		<command>--depth=</command> &mdash; Specify the default color depth for the X Window System on the installed system. Valid values are 8, 16, 24, and 32. Be sure to specify a color depth that is compatible with the video card and monitor.
-	</para>
-</listitem>
-						
-					</itemizedlist>
-				</listitem>
-			</varlistentry>
-
-			<varlistentry>
-				<term><command>zerombr</command> (optional) 	  </term>
-				<listitem>
-					<para>
-				<indexterm significance="normal">
-					<primary>kickstart file</primary>
-					<secondary><command>zerombr</command>
-					</secondary>
-				</indexterm>
-						If <command>zerombr</command> is specified any invalid partition tables found on disks are initialized. This destroys all of the contents of disks with invalid partition tables.
-					</para>
-<!-- BZ#241666	 -->
-					
-		<para>Note that this command was previously specified as <command>zerombr yes</command>. This form is now deprecated; you should now simply specify <command>zerombr</command> in your kickstart file instead.</para>			
-				</listitem>
-			</varlistentry>
-
-			<varlistentry>
-				<term><command>zfcp</command> (optional) 	  </term>
-				<listitem>
-					<para>
-				<indexterm significance="normal">
-					<primary>kickstart file</primary>
-					<secondary><command>zfcp</command>
-					</secondary>
-				</indexterm>
-					Define a Fiber channel device (IBM System z).
-					</para>
-					
-<para><command>zfcp [--devnum=<replaceable>&lt;devnum&gt;</replaceable>] [--fcplun=<replaceable>&lt;fcplun&gt;</replaceable>] [--scsiid=<replaceable>&lt;scsiid&gt;</replaceable>] [--scsilun=<replaceable>&lt;scsilun&gt;</replaceable>] [--wwpn=<replaceable>&lt;wwpn&gt;</replaceable>]</command></para>
-
-					<!-- <variablelist>
-						<varlistentry>
-<term><command>- -devnum=</command></term>
-<listitem>
-	No further information is available at this time
-</listitem>
-						</varlistentry>
-
-						<varlistentry>
-<term><command>- -fcplun=</command></term>
-<listitem>
-	 No further information is available at this time
-</listitem>
-						</varlistentry>
-						
-						<varlistentry>
-<term><command>- -scsiid=</command></term>
-<listitem>
-	 No further information is available at this time
-</listitem>
-						</varlistentry>
-						
-						<varlistentry>
-<term><command>- -scsilun=</command></term>
-<listitem>
-	 No further information is available at this time
-</listitem>
-						</varlistentry>
-						
-						<varlistentry>
-<term><command>- -wwpn=</command></term>
-<listitem>
-	 No further information is available at this time
-</listitem>
-						</varlistentry>
-					</variablelist> -->
-				</listitem>
-			</varlistentry>	
-	
-			<varlistentry>
-				<term><command>%include</command> (optional)</term>
-				<listitem>
-					<para>
-				<indexterm significance="normal">
-					<primary>kickstart file</primary>
-					<secondary>include contents of another file</secondary>
-				</indexterm>
-				<indexterm significance="normal">
-					<primary>kickstart file</primary>
-					<secondary><command>%include</command>
-					</secondary>
-				</indexterm>
-						Use the <command>%include <replaceable>/path/to/file</replaceable></command> command to include the contents of another file in the kickstart file as though the contents were at the location of the <command>%include</command> command in the kickstart file.
-					</para>
-				</listitem>
-			</varlistentry>
-		</variablelist>
-		 
-		<section id="s2-kickstart2-options-part-examples">
-			<title>Advanced Partitioning Example</title>
-			<indexterm significance="normal">
-				<primary>kickstart file</primary>
-				<secondary>options</secondary>
-				<tertiary>partitioning examples</tertiary>
-			</indexterm>
-			<para>
-				The following is a single, integrated example showing the <command>clearpart</command>, <command>raid</command>, <command>part</command>, <command>volgroup</command>, and
-				<command>logvol</command> kickstart options in action:
-			</para>
-<screen>clearpart --drives=hda,hdc --initlabel  
-# Raid 1 IDE config 
-part raid.11    --size 1000     --asprimary     --ondrive=hda 
-part raid.12    --size 1000     --asprimary     --ondrive=hda 
-part raid.13    --size 2000     --asprimary     --ondrive=hda 
-part raid.14    --size 8000                     --ondrive=hda 
-part raid.15    --size 1 --grow                 --ondrive=hda             
-part raid.21    --size 1000     --asprimary     --ondrive=hdc 
-part raid.22    --size 1000     --asprimary     --ondrive=hdc 
-part raid.23    --size 2000     --asprimary     --ondrive=hdc 
-part raid.24    --size 8000                     --ondrive=hdc 
-part raid.25    --size 1 --grow                 --ondrive=hdc  
-
-# You can add --spares=x  
-raid /          --fstype ext3 --device md0 --level=RAID1 raid.11 raid.21 
-raid /safe      --fstype ext3 --device md1 --level=RAID1 raid.12 raid.22 
-raid swap       --fstype swap --device md2 --level=RAID1 raid.13 raid.23 
-raid /usr       --fstype ext3 --device md3 --level=RAID1 raid.14 raid.24 
-raid pv.01      --fstype ext3 --device md4 --level=RAID1 raid.15 raid.25  
-
-# LVM configuration so that we can resize /var and /usr/local later 
-volgroup sysvg pv.01     
-logvol /var             --vgname=sysvg  --size=8000     --name=var 
-logvol /var/freespace   --vgname=sysvg  --size=8000     --name=freespacetouse 
-logvol /usr/local       --vgname=sysvg  --size=1 --grow --name=usrlocal
-</screen>
-			<para>
-				This advanced example implements LVM over RAID, as well as the ability to resize various directories for future growth.
-			</para>
-		</section>
-	</section>
-	<section id="s1-kickstart2-packageselection">
-		<title>Package Selection</title>
-		<indexterm significance="normal">
-			<primary>kickstart file</primary>
-			<secondary>package selection specification</secondary>
-		</indexterm>
-		<para>
-			Use the <command>%packages</command> command to begin a kickstart file section that lists the packages you would like to install (this is for installations only, as package selection during upgrades is not supported).
-		</para>
-		 
-		<para>
-			Packages can be specified by group or by individual package name, including with globs using the asterisk. The installation program defines several groups that contain related packages. Refer to the <filename><replaceable>variant</replaceable>/repodata/comps-*.xml</filename> file on the first Fedora CD-ROM for a list of groups. Each group has an id, user visibility value, name, description, and package list. In the package list, the packages marked as mandatory are always installed if the group is selected, the packages marked default are selected by default if the group is selected, and the packages marked optional must be specifically selected even if the group is selected to be installed.
-		</para>
-		 
-		<para>
-			In most cases, it is only necessary to list the desired groups and not individual packages. Note that the <command>Core</command> and <command>Base</command> groups are always selected by default, so it is not necessary to specify them in the <command>%packages</command> section.
-		</para>
-		 
-		<para>
-			Here is an example <command>%packages</command> selection:
-		</para>
-<screen>%packages 
-@ X Window System 
-@ GNOME Desktop Environment 
-@ Graphical Internet 
-@ Sound and Video dhcp</screen>
-		<para>
-			As you can see, groups are specified, one to a line, starting with an <command>@</command> symbol, a space, and then the full group name as given in the <filename>comps.xml</filename> file. Groups can also be specified
-			using the id for the group, such as <computeroutput>gnome-desktop</computeroutput>. Specify individual packages with no additional characters (the <filename>dhcp</filename> line in the example above is an individual
-			package).
-		</para>
-		 
-		<para>
-			You can also specify which packages not to install from the default package list:
-		</para>
-<screen>-autofs</screen>
-		<para>
-			The following options are available for the <command>%packages</command> option:
-		</para>
-		 
-		<variablelist>
-			
-			<varlistentry>
-				<term><command>--nobase</command></term>
-				<listitem>
-					<para>
-						Do not install the @Base group. Use this option if you are trying to create a very small system.
-					</para>
-				</listitem>
-			</varlistentry>
-			
-			<varlistentry>
-				<term><command>--resolvedeps</command></term>
-				<listitem>
-					<para>
-						The --resolvedeps option has been deprecated. Dependencies are resolved automatically every time now.
-					</para>
-				</listitem>
-			</varlistentry>
-
-			<varlistentry>
-				<term><command>--ignoredeps</command></term>
-				<listitem>
-					<para>
-						The --ignoredeps option has been deprecated. Dependencies are resolved automatically every time now.
-					</para>
-				</listitem>
-			</varlistentry>
-
-			<varlistentry>
-				<term><command>--ignoremissing</command></term>
-				<listitem>
-					<para>
-						Ignore the missing packages and groups instead of halting the installation to ask if the installation should be aborted or continued. For example:
-					</para>
-<screen>%packages --ignoremissing</screen>
-				</listitem>
-			</varlistentry>
-		</variablelist>
-	</section>
-	<section id="s1-kickstart2-preinstallconfig">
-		<title>Pre-installation Script</title>
-		<indexterm significance="normal">
-			<primary>kickstart file</primary>
-			<secondary>pre-installation configuration</secondary>
-		</indexterm>
-		<indexterm significance="normal">
-			<primary>kickstart file</primary>
-			<secondary>%pre</secondary>
-		</indexterm>
-		<para>
-			You can add commands to run on the system immediately after the <filename>ks.cfg</filename> has been parsed. This section must be at the end of the kickstart file (after the commands) and must start with the
-			<command>%pre</command> command. You can access the network in the <command>%pre</command> section; however, <firstterm>name service</firstterm> has not been configured at this point, so only IP addresses work.
-		</para>
-		 
-		<note>
-			<title>Note</title>
-
-			<para>
-				Note that the pre-install script is not run in the change root environment.
-			</para>
-		</note>
-		 
-		<variablelist>
-			<varlistentry>
-				<term><command>--interpreter <replaceable>/usr/bin/python</replaceable></command></term>
-				<listitem>
-					<para>
-						Allows you to specify a different scripting language, such as Python. Replace <replaceable>/usr/bin/python</replaceable> with the scripting language of your choice.
-					</para>
-				</listitem>
-			</varlistentry>
-		</variablelist>
-		 
-		<section id="s2-kickstart2-prescript-example">
-			<title>Example</title>
-			 
-			<para>
-				Here is an example <command>%pre</command> section:
-			</para>
-<screen>%pre  
-#!/bin/sh  
-hds="" 
-mymedia=""  
-for file in /proc/ide/h* do   
-	mymedia=`cat $file/media`   
-	if [ $mymedia == "disk" ] ; then       
-		hds="$hds `basename $file`"   
-	fi 
-done  
-set $hds 
-numhd=`echo $#`  
-drive1=`echo $hds | cut -d' ' -f1` 
-drive2=`echo $hds | cut -d' ' -f2`  
-#Write out partition scheme based on whether there are 1 or 2 hard drives  
-if [ $numhd == "2" ] ; then   
-	#2 drives   
-	echo "#partitioning scheme generated in %pre for 2 drives" &gt; /tmp/part-include   
-	echo "clearpart --all" &gt;&gt; /tmp/part-include   
-	echo "part /boot --fstype ext3 --size 75 --ondisk hda" &gt;&gt; /tmp/part-include   
-	echo "part / --fstype ext3 --size 1 --grow --ondisk hda" &gt;&gt; /tmp/part-include   
-	echo "part swap --recommended --ondisk $drive1" &gt;&gt; /tmp/part-include   
-	echo "part /home --fstype ext3 --size 1 --grow --ondisk hdb" &gt;&gt; /tmp/part-include 
-else   
-	#1 drive   
-	echo "#partitioning scheme generated in %pre for 1 drive" &gt; /tmp/part-include   
-	echo "clearpart --all" &gt;&gt; /tmp/part-include   
-	echo "part /boot --fstype ext3 --size 75" &gt;&gt; /tmp/part-includ   
-	echo "part swap --recommended" &gt;&gt; /tmp/part-include   
-	echo "part / --fstype ext3 --size 2048" &gt;&gt; /tmp/part-include   
-	echo "part /home --fstype ext3 --size 2048 --grow" &gt;&gt; /tmp/part-include 
-fi
-</screen>
-			<para>
-				This script determines the number of hard drives in the system and writes a text file with a different partitioning scheme depending on whether it has one or two drives. Instead of having a set of partitioning commands in the kickstart file, include
-				the line:
-			</para>
-<screen>%include /tmp/part-include</screen>
-			<para>
-				The partitioning commands selected in the script are used.
-			</para>
-			 
-			<note>
-				<title>Note</title>
-
-				<para>
-					The pre-installation script section of kickstart <emphasis>cannot</emphasis> manage multiple install trees or source media. This information must be included for each created ks.cfg file, as the pre-installation script occurs during the second stage of the installation process.
-				</para>
-			</note>
-		</section>
-	</section>
-	<section id="s1-kickstart2-postinstallconfig">
-		<title>Post-installation Script</title>
-		<indexterm significance="normal">
-			<primary>kickstart file</primary>
-			<secondary>post-installation configuration</secondary>
-		</indexterm>
-		<indexterm significance="normal">
-			<primary>kickstart file</primary>
-			<secondary>%post</secondary>
-		</indexterm>
-		<para>
-			You have the option of adding commands to run on the system once the installation is complete. This section must be at the end of the kickstart file and must start with the <command>%post</command> command. This section is useful for functions such as installing additional software and configuring an additional nameserver.
-		</para>
-		 
-		<note>
-			<title>Note</title>
-
-			<para>
-				If you configured the network with static IP information, including a nameserver, you can access the network and resolve IP addresses in the <command>%post</command> section. If you configured the network for DHCP, the <filename>/etc/resolv.conf</filename> file has not been completed when the installation executes the <command>%post</command> section. You can access the network, but you can not resolve IP addresses. Thus, if you are using DHCP, you must specify IP addresses in the <command>%post</command> section.
-			</para>
-		</note>
-		 
-		<note>
-			<title>Note</title>
-
-			<para>
-				The post-install script is run in a chroot environment; therefore, performing tasks such as copying scripts or RPMs from the installation media do not work.
-			</para>
-		</note>
-		 
-		<variablelist>
-			<varlistentry>
-				<term><command>--nochroot</command></term>
-				<listitem>
-					<para>
-						Allows you to specify commands that you would like to run outside of the chroot environment.
-					</para>
-
-					<para>
-						The following example copies the file <filename>/etc/resolv.conf</filename> to the file system that was just installed.
-					</para>
-<screen>%post --nochroot cp /etc/resolv.conf /mnt/sysimage/etc/resolv.conf</screen>
-				</listitem>
-			</varlistentry>
-
-			<varlistentry>
-				<term><command>--interpreter <replaceable>/usr/bin/python</replaceable></command></term>
-				<listitem>
-					<para>
-						Allows you to specify a different scripting language, such as Python. Replace <replaceable>/usr/bin/python</replaceable> with the scripting language of your choice.
-					</para>
-				</listitem>
-			</varlistentry>
-		</variablelist>
-		 
-		<section id="s2-kickstart2-post-examples">
-			<title>Examples</title>
-			 
-			<para>
-				Register the system to a Red Hat Network Satellite:
-			</para>
-<screen>%post
-( # Note that in this example we run the entire %post section as a subshell for logging.
-wget -O- http://proxy-or-sat.example.com/pub/bootstrap_script | /bin/bash
-/usr/sbin/rhnreg_ks --activationkey=<replaceable>&lt;activationkey&gt;</replaceable>
-# End the subshell and capture any output to a post-install log file.
-) 1>/root/post_install.log 2>&amp;1
-</screen>
-			<para>
-				Run a script named <filename>runme</filename> from an NFS share:
-			</para>
-<screen>mkdir /mnt/temp 
-mount -o nolock 10.10.0.2:/usr/new-machines /mnt/temp open -s -w -- 
-/mnt/temp/runme 
-umount /mnt/temp
-</screen>
-			<note>
-				<title>Note</title>
-
-				<para>
-					NFS file locking is <emphasis>not</emphasis> supported while in kickstart mode, therefore <command>-o nolock</command> is required when mounting an NFS mount.
-				</para>
-			</note>
-			 
-		</section>
-	</section>
-	<section id="s1-kickstart2-putkickstarthere">
-		<title>Making the Kickstart File Available</title>
-		<indexterm significance="normal">
-			<primary>kickstart installations</primary>
-			<secondary>file locations</secondary>
-		</indexterm>
-		<para>
-			A kickstart file must be placed in one of the following locations:
-		</para>
-		 
-		<itemizedlist>
-			<listitem>
-				<para>
-					On a boot diskette
-				</para>
-			</listitem>
-
-			<listitem>
-				<para>
-					On a boot CD-ROM
-				</para>
-			</listitem>
-
-			<listitem>
-				<para>
-					On a network
-				</para>
-			</listitem>
-		</itemizedlist>
-		 
-		<para>
-			Normally a kickstart file is copied to the boot diskette, or made available on the network. The network-based approach is most commonly used, as most kickstart installations tend to be performed on networked computers.
-		</para>
-		 
-		<para>
-			Let us take a more in-depth look at where the kickstart file may be placed.
-		</para>
-		 
-		<section id="s2-kickstart2-boot-media">
-			<title>Creating Kickstart Boot Media</title>
-			<indexterm significance="normal">
-				<primary>kickstart installations</primary>
-				<secondary>diskette-based</secondary>
-			</indexterm>
-			<indexterm significance="normal">
-				<primary>kickstart file</primary>
-				<secondary>diskette-based</secondary>
-			</indexterm>
-			<para>
-				Diskette-based booting is no longer supported in Fedora. Installations must use CD-ROM or flash memory products for booting. However, the kickstart file may still reside on a diskette's top-level directory, and must be named
-				<filename>ks.cfg</filename>.
-			</para>
-			<indexterm significance="normal">
-				<primary>kickstart installations</primary>
-				<secondary>CD-ROM-based</secondary>
-			</indexterm>
-			<indexterm significance="normal">
-				<primary>kickstart file</primary>
-				<secondary>CD-ROM-based</secondary>
-			</indexterm>
-			<para>
-				To perform a CD-ROM-based kickstart installation, the kickstart file must be named <filename>ks.cfg</filename> and must be located in the boot CD-ROM's top-level directory. Since a CD-ROM is read-only, the file must be added to the directory used to create the image that is written to the CD-ROM. Refer to <xref linkend="sect-New_Users-Alternative_Boot_Methods"/> for instructions on creating boot media; however, before making the <filename>file.iso</filename> image file, copy the <filename>ks.cfg</filename> kickstart file to the <filename>isolinux/</filename> directory.
-			</para>
-			<indexterm significance="normal">
-				<primary>kickstart installations</primary>
-				<secondary>flash-based</secondary>
-			</indexterm>
-			<indexterm significance="normal">
-				<primary>kickstart file</primary>
-				<secondary>flash-based</secondary>
-			</indexterm>
-			<para>
-				To perform a pen-based flash memory kickstart installation, the kickstart file must be named <filename>ks.cfg</filename> and must be located in the flash memory's top-level directory. Create the boot image first, and then copy the
-				<filename>ks.cfg</filename> file.
-			</para>
-			<para>
-				Refer to <xref linkend="sect-New_Users-Alternative_Boot_Methods"/> for instructions on creating live USB media using the <filename>boot.iso</filename> image available for download from the same servers that host images of the Fedora installation disks &mdash; refer to <xref linkend="sect-Obtaining_Fedora-Downloading_Fedora"/>.
-			</para>
-			<note>
-				<title>Note</title>
-
-				<para>
-					Creation of USB flash memory pen drives for booting is possible, but is heavily dependent on system hardware BIOS settings. Refer to your hardware manufacturer to see if your system supports booting to alternate devices.
-				</para>
-			</note>
-		</section>
-		 
-		<section id="s2-kickstart2-networkbased">
-			<title>Making the Kickstart File Available on the Network</title>
-			<indexterm significance="normal">
-				<primary>kickstart installations</primary>
-				<secondary>network-based</secondary>
-			</indexterm>
-			<indexterm significance="normal">
-				<primary>kickstart file</primary>
-				<secondary>network-based</secondary>
-			</indexterm>
-			<para>
-				Network installations using kickstart are quite common, because system administrators can easily automate the installation on many networked computers quickly and painlessly. In general, the approach most commonly used is for the administrator to have both a BOOTP/DHCP server and an NFS server on the local network. The BOOTP/DHCP server is used to give the client system its networking information, while the actual files used during the installation are served by the NFS server. Often, these two servers run on the same physical machine, but they are not required to.
-			</para>
-			 
-			<para>
-				To perform a network-based kickstart installation, you must have a BOOTP/DHCP server on your network, and it must include configuration information for the machine on which you are attempting to install Fedora. The BOOTP/DHCP server provides the client with its networking information as well as the location of the kickstart file.
-			</para>
-			 
-			<para>
-				If a kickstart file is specified by the BOOTP/DHCP server, the client system attempts an NFS mount of the file's path, and copies the specified file to the client, using it as the kickstart file. The exact settings required vary depending on the BOOTP/DHCP server you use.
-			</para>
-			 
-			<para>
-				Here is an example of a line from the <filename>dhcpd.conf</filename> file for the DHCP server:
-			</para>
-<screen><filename>filename</filename> <replaceable>"/usr/new-machine/kickstart/"</replaceable>; next-server <replaceable>blarg.redhat.com;</replaceable></screen>
-			<para>
-				Note that you should replace the value after <computeroutput>filename</computeroutput> with the name of the kickstart file (or the directory in which the kickstart file resides) and the value after <computeroutput>next-server</computeroutput> with the NFS server name.
-			</para>
-			 
-			<para>
-				If the file name returned by the BOOTP/DHCP server ends with a slash ("/"), then it is interpreted as a path only. In this case, the client system mounts that path using NFS, and searches for a particular file. The file name the client searches for is:
-			</para>
-<screen><filename><replaceable>&lt;ip-addr&gt;</replaceable>-kickstart</filename></screen>
-			<para>
-				The <filename><replaceable>&lt;ip-addr&gt;</replaceable></filename> section of the file name should be replaced with the client's IP address in dotted decimal notation. For example, the file name for a computer with an IP address of 10.10.0.1 would be <filename>10.10.0.1-kickstart</filename>.
-			</para>
-			 
-			<para>
-				Note that if you do not specify a server name, then the client system attempts to use the server that answered the BOOTP/DHCP request as its NFS server. If you do not specify a path or file name, the client system tries to mount <filename>/kickstart</filename> from the BOOTP/DHCP server and tries to find the kickstart file using the same <filename><replaceable>&lt;ip-addr&gt;</replaceable>-kickstart</filename> file name as described above.
-			</para>
-		</section>
-	</section>
-	<section id="s1-kickstart2-install-tree">
-		<title>Making the Installation Tree Available</title>
-		<indexterm significance="normal">
-			<primary>kickstart installations</primary>
-			<secondary>installation tree</secondary>
-		</indexterm>
-		<para>
-			The kickstart installation must access an <firstterm>installation tree</firstterm>. An installation tree is a copy of the binary Fedora CD-ROMs with the same directory structure.
-		</para>
-		 
-		<para>
-			If you are performing a CD-based installation, insert the Fedora CD-ROM #1 into the computer before starting the kickstart installation.
-		</para>
-		 
-		<para>
-			If you are performing a hard drive installation, make sure the ISO images of the binary Fedora CD-ROMs are on a hard drive in the computer.
-		</para>
-		<indexterm significance="normal">
-			<primary>kickstart installations</primary>
-			<secondary>network-based</secondary>
-		</indexterm>
-		<indexterm significance="normal">
-			<primary>kickstart file</primary>
-			<secondary>network-based</secondary>
-		</indexterm>
-		<para>
-			If you are performing a network-based (NFS, FTP, or HTTP) installation, you must make the installation tree available over the network. Refer to <xref linkend="s1-steps-network-installs-x86"/> for details.
-		</para>
-	</section>
-	<section id="s1-kickstart2-startinginstall">
-		<title>Starting a Kickstart Installation</title>
-		<indexterm significance="normal">
-			<primary>kickstart installations</primary>
-			<secondary>starting</secondary>
-		</indexterm>
-		<indexterm significance="normal">
-			<primary>kickstart</primary>
-			<secondary>how the file is found</secondary>
-		</indexterm>
-		<xi:include href="Important-Kickstart_and_Firstboot.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> 
-		<para>
-			To begin a kickstart installation, you must boot the system from boot media you have made or the Fedora CD-ROM #1, and enter a special boot command at the boot prompt. The installation program looks for a kickstart file if the <command>ks</command> command line argument is passed to the kernel.
-		</para>
-		 
-		<variablelist>
-			<varlistentry>
-				<term>CD-ROM #1 and Diskette</term>
-				<listitem>
-					<para>
-				<indexterm significance="normal">
-					<primary>kickstart installations</primary>
-					<secondary>starting</secondary>
-					<tertiary>from CD-ROM #1 with a diskette</tertiary>
-				</indexterm>
-						The <userinput>linux ks=floppy</userinput> command also works if the <filename>ks.cfg</filename> file is located on a vfat or ext2 file system on a diskette and you boot from the Fedora CD-ROM #1.
-					</para>
-
-					<para>
-						An alternate boot command is to boot off the Fedora CD-ROM #1 and have the kickstart file on a vfat or ext2 file system on a diskette. To do so, enter the following command at the <prompt>boot:</prompt> prompt:
-					</para>
-<screen>linux ks=hd:fd0:/ks.cfg</screen>
-				</listitem>
-			</varlistentry>
-		</variablelist>
-		 
-		<variablelist>
-			<varlistentry>
-				<term>With Driver Disk</term>
-				<listitem>
-					<para>
-						If you need to use a driver disk with kickstart, specify the <userinput>dd</userinput> option as well. For example, to boot off a boot diskette and use a driver disk, enter the following command at the <prompt>boot:</prompt> prompt:
-					</para>
-<screen>linux ks=floppy dd</screen>
-				</listitem>
-			</varlistentry>
-
-			<varlistentry>
-				<term>Boot CD-ROM</term>
-				<listitem>
-					<para>
-				<indexterm significance="normal">
-					<primary>kickstart installations</primary>
-					<secondary>starting</secondary>
-					<tertiary>from a boot CD-ROM</tertiary>
-				</indexterm>
-						If the kickstart file is on a boot CD-ROM as described in <xref linkend="s2-kickstart2-boot-media"/>, insert the CD-ROM into the system, boot the system, and enter the following command at the <prompt>boot:</prompt> prompt (where <filename>ks.cfg</filename> is the name of the kickstart file):
-					</para>
-<screen>linux ks=cdrom:/ks.cfg</screen>
-				</listitem>
-			</varlistentry>
-		</variablelist>
-		 
-		<para>
-			Other options to start a kickstart installation are as follows:
-		</para>
-		 
-		<variablelist>
-			<varlistentry>
-				<term><command>askmethod</command></term>
-				<listitem>
-					<para>
-						Do not automatically use the CD-ROM as the install source if we detect a Fedora CD in your CD-ROM drive.
-					</para>
-				</listitem>
-			</varlistentry>
-			
-			<varlistentry>
-				<term><command>autostep</command></term>
-				<listitem>
-					<para>
-						Make kickstart non-interactive.
-					</para>
-				</listitem>
-			</varlistentry>
-				
-			<varlistentry>
-				<term><command>debug</command></term>
-				<listitem>
-					<para>
-						Start up pdb immediately.
-					</para>
-				</listitem>
-			</varlistentry>
-			
-			<varlistentry>
-				<term><command>dd</command></term>
-				<listitem>
-					<para>
-						Use a driver disk.
-					</para>
-				</listitem>
-			</varlistentry>
-			
-			<varlistentry>
-				<term><command>dhcpclass=<replaceable>&lt;class&gt;</replaceable></command></term>
-				<listitem>
-					<para>
-						Sends a custom DHCP vendor class identifier. ISC's dhcpcd can inspect this value using "option vendor-class-identifier". 
-					</para>
-				</listitem>
-			</varlistentry>
-			
-			<varlistentry>
-				<term><command>dns=<replaceable>&lt;dns&gt;</replaceable></command></term>
-				<listitem>
-					<para>
-						Comma separated list of nameservers to use for a network installation.
-					</para>
-				</listitem>
-			</varlistentry>
-			
-			<varlistentry>
-				<term><command>driverdisk</command></term>
-				<listitem>
-					<para>
-						Same as 'dd'.
-					</para>
-				</listitem>
-			</varlistentry>
-			
-			<varlistentry>
-				<term><command>expert</command></term>
-				<listitem>
-					<para>
-						Turns on special features:
-						<itemizedlist>
-<listitem>
-	<para>
-		allows partitioning of removable media
-	</para>
-</listitem>
-
-<listitem>
-	<para>
-		prompts for a driver disk
-	</para>
-</listitem>
-						</itemizedlist>		
-					</para>
-				</listitem>
-			</varlistentry>
-			
-			<varlistentry>
-				<term><command>gateway=<replaceable>&lt;gw&gt;</replaceable></command></term>
-				<listitem>
-					<para>
-						Gateway to use for a network installation.
-					</para>
-				</listitem>
-			</varlistentry>	
-			
-			<varlistentry>
-				<term><command>graphical</command></term>
-				<listitem>
-					<para>
-						Force graphical install. Required to have ftp/http use GUI.
-					</para>
-				</listitem>
-			</varlistentry>	
-			
-			<varlistentry>
-				<term><command>isa</command></term>
-				<listitem>
-					<para>
-						Prompt user for ISA devices configuration.
-					</para>
-				</listitem>
-			</varlistentry>	
-			
-			<varlistentry>
-				<term><command>ip=<replaceable>&lt;ip&gt;</replaceable></command></term>
-				<listitem>
-					<para>
-						IP to use for a network installation, use 'dhcp' for DHCP.
-					</para>
-				</listitem>
-			</varlistentry>	
-			
-			<varlistentry>
-				<term><command>keymap=<replaceable>&lt;keymap&gt;</replaceable></command></term>
-				<listitem>
-					<para>
-						Keyboard layout to use.  Valid values are those which can be used for the 'keyboard' kickstart command.
-					</para>
-				</listitem>
-			</varlistentry>	
-			
-			<varlistentry>
-				<term><command>ks=nfs:<replaceable>&lt;server&gt;</replaceable>:/<replaceable>&lt;path&gt;</replaceable></command></term>
-				<listitem>
-					<para>
-						The installation program looks for the kickstart file on the NFS server <replaceable>&lt;server&gt;</replaceable>, as file <replaceable>&lt;path&gt;</replaceable>. The installation program uses DHCP to configure the Ethernet card. For example, if your NFS server is server.example.com and the kickstart file is in the NFS share <filename>/mydir/ks.cfg</filename>, the correct boot command would be <command>ks=nfs:server.example.com:/mydir/ks.cfg</command>.
-					</para>
-				</listitem>
-			</varlistentry>
-
-			<varlistentry>
-				<term><command>ks=http://<replaceable>&lt;server&gt;</replaceable>/<replaceable>&lt;path&gt;</replaceable></command></term>
-				<listitem>
-					<para>
-						The installation program looks for the kickstart file on the HTTP server <replaceable>&lt;server&gt;</replaceable>, as file <replaceable>&lt;path&gt;</replaceable>. The installation program uses DHCP to configure the Ethernet card. For example, if your HTTP server is server.example.com and the kickstart file is in the HTTP directory <filename>/mydir/ks.cfg</filename>, the correct boot command would be <command>ks=http://server.example.com/mydir/ks.cfg</command>.
-					</para>
-				</listitem>
-			</varlistentry>
-
-			<varlistentry>
-				<term><command>ks=floppy</command></term>
-				<listitem>
-					<para>
-						The installation program looks for the file <filename>ks.cfg</filename> on a vfat or ext2 file system on the diskette in <filename>/dev/fd0</filename>.
-					</para>
-				</listitem>
-			</varlistentry>
-
-			<varlistentry>
-				<term><command>ks=floppy:/<replaceable>&lt;path&gt;</replaceable></command></term>
-				<listitem>
-					<para>
-						The installation program looks for the kickstart file on the diskette in <filename>/dev/fd0</filename>, as file <replaceable>&lt;path&gt;</replaceable>.
-					</para>
-				</listitem>
-			</varlistentry>
-
-			<varlistentry>
-				<term><command>ks=hd:<replaceable>&lt;device&gt;</replaceable>:/<replaceable>&lt;file&gt;</replaceable></command></term>
-				<listitem>
-					<para>
-						The installation program mounts the file system on <replaceable>&lt;device&gt;</replaceable> (which must be vfat or ext2), and looks for the kickstart configuration file as <replaceable>&lt;file&gt;</replaceable> in that file system (for example, <command>ks=hd:sda3:/mydir/ks.cfg</command>).
-					</para>
-				</listitem>
-			</varlistentry>
-			
-			<varlistentry>
-				<term><command>ks=bd:<replaceable>&lt;biosdev&gt;</replaceable>:/<replaceable>&lt;path&gt;</replaceable></command></term>
-				<listitem>
-					<para>
-						The installation program mounts the file system on the specified partition on the specified BIOS device <replaceable>&lt;biosdev&gt;</replaceable>, and looks for the kickstart configuration file specified in <replaceable>&lt;path&gt;</replaceable> (for example, <command>ks=bd:80p3:/mydir/ks.cfg</command>).     Note this does not work for BIOS RAID sets.
-					</para>
-				</listitem>
-			</varlistentry>
-
-			<varlistentry>
-				<term><command>ks=file:/<replaceable>&lt;file&gt;</replaceable></command></term>
-				<listitem>
-					<para>
-						The installation program tries to read the file <replaceable>&lt;file&gt;</replaceable> from the file system; no mounts are done. This is normally used if the kickstart file is already on the <filename>initrd</filename> image.
-					</para>
-				</listitem>
-			</varlistentry>
-
-			<varlistentry>
-				<term><command>ks=cdrom:/<replaceable>&lt;path&gt;</replaceable></command></term>
-				<listitem>
-					<para>
-						The installation program looks for the kickstart file on CD-ROM, as file <replaceable>&lt;path&gt;</replaceable>.
-					</para>
-				</listitem>
-			</varlistentry>
-
-			<varlistentry>
-				<term><command>ks</command></term>
-				<listitem>
-					<para>
-						If <command>ks</command> is used alone, the installation program configures the Ethernet card to use DHCP. The kickstart file is read from the "bootServer" from the DHCP response as if it is an NFS server sharing the kickstart file. By default, the bootServer is the same as the DHCP server. The name of the kickstart file is one of the following:
-					</para>
-
-					<itemizedlist>
-						<listitem>
-<para>
-	If DHCP is specified and the boot file begins with a <filename>/</filename>, the boot file provided by DHCP is looked for on the NFS server.
-</para>
-						</listitem>
-
-						<listitem>
-<para>
-	If DHCP is specified and the boot file begins with something other than a <computeroutput>/</computeroutput>, the boot file provided by DHCP is looked for in the <filename>/kickstart</filename> directory on the NFS server.
-</para>
-						</listitem>
-
-						<listitem>
-<para>
-	If DHCP did not specify a boot file, then the installation program tries to read the file <filename>/kickstart/1.2.3.4-kickstart</filename>, where <replaceable>1.2.3.4</replaceable> is the numeric IP address of the machine being installed.
-</para>
-						</listitem>
-					</itemizedlist>
-				</listitem>
-			</varlistentry>
-
-			<varlistentry>
-				<term><command>ksdevice=<replaceable>&lt;device&gt;</replaceable></command></term>
-				<listitem>
-					<para>
-						The installation program uses this network device to connect to the network. For example, consider a system connected to an NFS server through the eth1 device. To perform a kickstart installation on this system using a kickstart file from the NFS server, you would use the command <command>ks=nfs:<replaceable>&lt;server&gt;</replaceable>:/<replaceable>&lt;path&gt;</replaceable> ksdevice=eth1</command> at the <prompt>boot:</prompt> prompt.
-					</para>
-				</listitem>
-			</varlistentry>
-			
-			<varlistentry>
-				<term><command>kssendmac</command></term>
-				<listitem>
-					<para>
-						Adds HTTP headers to ks=http:// request that can be helpful for provisioning systems.  Includes MAC address of all nics in CGI environment variables of the form: "X-RHN-Provisioning-MAC-0: eth0 01:23:45:67:89:ab".
-					</para>
-				</listitem>
-			</varlistentry>	
-			
-			<varlistentry>
-				<term><command>lang=<replaceable>&lt;lang&gt;</replaceable></command></term>
-				<listitem>
-					<para>
-						Language to use for the installation.  This should be a language which is valid to be used with the 'lang' kickstart command.
-					</para>
-				</listitem>
-			</varlistentry>	
-			
-			<varlistentry>
-				<term><command>loglevel=<replaceable>&lt;level&gt;</replaceable></command></term>
-				<listitem>
-					<para>
-						Set the minimum level required for messages to be logged. Values for &lt;level&gt; are debug, info, warning, error, and critical.  The default value is info.
-					</para>
-				</listitem>
-			</varlistentry>	
-			
-			<varlistentry>
-				<term><command>lowres</command></term>
-				<listitem>
-					<para>
-						Force GUI installer to run at 640x480.
-					</para>
-				</listitem>
-			</varlistentry>	
-			
-			<varlistentry>
-				<term><command>mediacheck</command></term>
-				<listitem>
-					<para>
-						Activates loader code to give user option of testing integrity of install source (if an ISO-based method).
-					</para>
-				</listitem>
-			</varlistentry>	
-			
-			<varlistentry>
-				<term><command>method=cdrom</command></term>
-				<listitem>
-					<para>
-						Do a CDROM based installation.
-					</para>
-				</listitem>
-			</varlistentry>	
-			
-			<varlistentry>
-				<term><command>method=ftp://<replaceable>&lt;path&gt;</replaceable></command></term>
-				<listitem>
-					<para>
-						Use &lt;path&gt; for an FTP installation.
-					</para>
-				</listitem>
-			</varlistentry>	
-			
-			<varlistentry>
-				<term><command>method=hd:<replaceable>&lt;dev&gt;</replaceable>:<replaceable>&lt;path&gt;</replaceable></command></term>
-<!--	BZ#250941, above replaces below			
-				<term><command>method=hd://<replaceable>&lt;dev&gt;</replaceable>/<replaceable>&lt;path&gt;</replaceable></command></term>-->
-				<listitem>
-					<para>
-						Use &lt;path&gt; on &lt;dev&gt; for a hard drive installation.
-					</para>
-				</listitem>
-			</varlistentry>	
-			
-			<varlistentry>
-				<term><command>method=http://<replaceable>&lt;path&gt;</replaceable></command></term>
-				<listitem>
-					<para>
-						Use &lt;path&gt; for an HTTP installation.
-					</para>
-				</listitem>
-			</varlistentry>	
-			
-			<varlistentry>
-				<term><command>method=nfs:<replaceable>&lt;path&gt;</replaceable></command></term>
-				<listitem>
-					<para>
-						Use &lt;path&gt; for an NFS installation.
-					</para>
-				</listitem>
-			</varlistentry>	
-			
-			<varlistentry>
-				<term><command>netmask=<replaceable>&lt;nm&gt;</replaceable></command></term>
-				<listitem>
-					<para>
-						Netmask to use for a network installation.
-					</para>
-				</listitem>
-			</varlistentry>	
-			
-			<varlistentry>
-				<term><command>nofallback</command></term>
-				<listitem>
-					<para>
-						If GUI fails exit.
-					</para>
-				</listitem>
-			</varlistentry>	
-			
-			<varlistentry>
-				<term><command>nofb</command></term>
-				<listitem>
-					<para>
-						Do not load the VGA16 framebuffer required for doing text-mode installation in some languages.
-					</para>
-				</listitem>
-			</varlistentry>	
-			
-			
-			<varlistentry>
-				<term><command>nofirewire</command></term>
-				<listitem>
-					<para>
-						Do not load support for firewire devices.
-					</para>
-				</listitem>
-			</varlistentry>	
-			
-			<varlistentry>
-				<term><command>noipv6</command></term>
-				<listitem>
-					<para>
-						Disable IPv6 networking during installation.
-					</para>
-					<important>
-						<title>This option is not available during PXE installations</title>
-						<para>
-							During installations from a PXE server, IPv6 networking might become active before <application>anaconda</application> processes the Kickstart file. If so, this option will have no effect during installation.
-						</para>
-					</important>
-				</listitem>
-			</varlistentry>	
-						
-			<varlistentry>
-				<term><command>nomount</command></term>
-				<listitem>
-					<para>
-						Don't automatically mount any installed Linux partitions in rescue mode.
-					</para>
-				</listitem>
-			</varlistentry>	
-			
-			<varlistentry>
-				<term><command>nonet</command></term>
-				<listitem>
-					<para>
-						Do not auto-probe network devices.
-					</para>
-				</listitem>
-			</varlistentry>	
-			
-			<varlistentry>
-				<term><command>noparport</command></term>
-				<listitem>
-					<para>
-						Do not attempt to load support for parallel ports.
-					</para>
-				</listitem>
-			</varlistentry>	
-			
-			<varlistentry>
-				<term><command>nopass</command></term>
-				<listitem>
-					<para>
-						Don't pass keyboard/mouse info to stage 2 installer, good for testing keyboard and mouse config screens in stage2 installer during network installs.
-					</para>
-				</listitem>
-			</varlistentry>	
-			
-			<varlistentry>
-				<term><command>nopcmcia</command></term>
-				<listitem>
-					<para>
-						Ignore PCMCIA controller in system.
-					</para>
-				</listitem>
-			</varlistentry>	
-			
-			<varlistentry>
-				<term><command>noprobe</command></term>
-				<listitem>
-					<para>
-						Do not attempt to detect hw, prompts user instead.
-					</para>
-				</listitem>
-			</varlistentry>	
-			
-			<varlistentry>
-				<term><command>noshell</command></term>
-				<listitem>
-					<para>
-						Do not put a shell on tty2 during install.
-					</para>
-				</listitem>
-			</varlistentry>	
-			
-			<varlistentry>
-				<term><command>nostorage</command></term>
-				<listitem>
-					<para>
-						Do not auto-probe storage devices (SCSI, IDE, RAID).
-					</para>
-				</listitem>
-			</varlistentry>	
-			
-			<varlistentry>
-				<term><command>nousb</command></term>
-				<listitem>
-					<para>
-						Do not load USB support (helps if install hangs early sometimes).
-					</para>
-				</listitem>
-			</varlistentry>	
-			
-			<varlistentry>
-				<term><command>nousbstorage</command></term>
-				<listitem>
-					<para>
-						Do not load usbstorage module in loader.  May help with device ordering on SCSI systems.
-					</para>
-				</listitem>
-			</varlistentry>	
-			
-			
-			<varlistentry>
-				<term><command>rescue</command></term>
-				<listitem>
-					<para>
-						Run rescue environment.
-					</para>
-				</listitem>
-			</varlistentry>	
-			
-			<varlistentry>
-				<term><command>resolution=<replaceable>&lt;mode&gt;</replaceable></command></term>
-				<listitem>
-					<para>
-						Run installer in mode specified, '1024x768' for example.
-					</para>
-				</listitem>
-			</varlistentry>	
-			
-			<varlistentry>
-				<term><command>serial</command></term>
-				<listitem>
-					<para>
-						Turns on serial console support.
-					</para>
-				</listitem>
-			</varlistentry>
-			
-			<varlistentry>
-				<term><command>skipddc</command></term>
-				<listitem>
-					<para>
-						Skips DDC probe of monitor, may help if it's hanging system.
-					</para>
-				</listitem>
-			</varlistentry>
-			
-			<varlistentry>
-				<term><command>syslog=<replaceable>&lt;host&gt;</replaceable>[:<replaceable>&lt;port&gt;</replaceable>]</command></term>
-				<listitem>
-					<para>
-						Once installation is up and running, send log messages to the syslog process on <replaceable>&lt;host&gt;</replaceable>, and optionally, on port <replaceable>&lt;port&gt;</replaceable>. Requires the remote syslog process to accept connections (the -r option).
-					</para>
-				</listitem>
-			</varlistentry>
-			
-			<varlistentry>
-				<term><command>text</command></term>
-				<listitem>
-					<para>
-						Force text mode install.
-					</para>
-					<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Kickstart-note-1.xml"/>
-					<!-- If you select text mode for a kickstart installation, you must ensure -->
-				</listitem>
-			</varlistentry>
-			
-			<varlistentry>
-				<term><command>updates</command></term>
-				<listitem>
-					<para>
-						Prompt for floppy containing updates (bug fixes).
-					</para>
-				</listitem>
-			</varlistentry>
-			
-			<varlistentry>
-				<term><command>updates=ftp://<replaceable>&lt;path&gt;</replaceable></command></term>
-				<listitem>
-					<para>
-						Image containing updates over FTP.
-					</para>
-				</listitem>
-			</varlistentry>
-			
-			<varlistentry>
-				<term><command>updates=http://<replaceable>&lt;path&gt;</replaceable></command></term>
-				<listitem>
-					<para>
-						Image containing updates over HTTP.
-					</para>
-				</listitem>
-			</varlistentry>
-			
-			<varlistentry>
-				<term><command>upgradeany</command></term>
-				<listitem>
-					<para>
-						Don't require an /etc/redhat-release that matches the expected syntax to upgrade.
-					</para>
-				</listitem>
-			</varlistentry>
-			
-			<varlistentry>
-				<term><command>vnc</command></term>
-				<listitem>
-					<para>
-						 Enable vnc-based installation. You will need to connect to the machine using a vnc client application.
-					</para>
-				</listitem>
-			</varlistentry>
-			
-			<varlistentry>
-				<term><command>vncconnect=<replaceable>&lt;host&gt;</replaceable>[:<replaceable>&lt;port&gt;</replaceable>]</command></term>
-				<listitem>
-					<para>
-						 Once installation is up and running, connect to the vnc client named <replaceable>&lt;host&gt;</replaceable>, and optionally use port <replaceable>&lt;port&gt;</replaceable>.
-					 </para>
-
-					 <para>
-                				Requires 'vnc' option to be specified as well.
-					</para>
-				</listitem>
-			</varlistentry>
-			
-			<varlistentry>
-				<term><command>vncpassword=<replaceable>&lt;password&gt;</replaceable></command></term>
-				<listitem>
-					<para>
-						 Enable a password for the vnc connection. This will prevent someone from inadvertently connecting to the vnc-based installation.
-					 </para>
-
-					 <para>
-                				Requires 'vnc' option to be specified as well.
-					</para>
-				</listitem>
-			</varlistentry>
-		</variablelist>
-	</section>
-</chapter>
-
diff --git a/en-US/Ksconfig.xml b/en-US/Ksconfig.xml
deleted file mode 100644
index cbd46f3..0000000
--- a/en-US/Ksconfig.xml
+++ /dev/null
@@ -1,828 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<chapter id="ch-redhat-config-kickstart"><title><application>Kickstart Configurator</application></title>
-	<indexterm significance="normal">
-		<primary><application>Kickstart Configurator</application>
-		</primary>
-	</indexterm>
-	<indexterm significance="normal">
-		<primary><command>system-config-kickstart</command>
-		</primary>
-		<see><application>Kickstart Configurator</application>
-		</see>
-	</indexterm>
-
-	<para>
-		<application>Kickstart Configurator</application> allows you to create or modify a kickstart file using a graphical user interface, so that you do not have to remember the correct syntax of the file.
-	</para>
-	<para>
-		To use <application>Kickstart Configurator</application>, you must be running the X Window System. To start <application>Kickstart Configurator</application>, select <guimenu>Applications</guimenu> (the main menu on the panel) =&gt; <guimenu>System Tools</guimenu> =&gt; <guimenuitem>Kickstart</guimenuitem>, or type the command <command>/usr/sbin/system-config-kickstart</command>.
-	</para>
-	<indexterm significance="normal">
-		<primary><application>Kickstart Configurator</application>
-		</primary>
-		<secondary>preview</secondary>
-	</indexterm>
-	<para>
-		As you are creating a kickstart file, you can select <guimenuitem>File</guimenuitem> =&gt; <guimenuitem>Preview</guimenuitem> at any time to review your current selections.
-	</para>
-	<para>
-		To start with an existing kickstart file, select <guimenu>File</guimenu> =&gt; <guimenuitem>Open</guimenuitem> and select the existing file.
-	</para>
-	<section id="s1-redhat-config-kickstart-basic">
-		<title>Basic Configuration</title>
-		<indexterm significance="normal">
-			<primary><application>Kickstart Configurator</application>
-			</primary>
-			<secondary>basic options</secondary>
-		</indexterm>
-		<figure float="0" id="redhat-config-kickstart-basic-fig"><title>Basic Configuration</title>
-			<mediaobject>
-				<imageobject><imagedata fileref="images/ksconfig/ksconfig-basic.png" format="PNG"/></imageobject>
-				<textobject><para>
-						Basic Configuration
-					</para>
-				</textobject>
-			</mediaobject>
-		</figure>
-		<indexterm significance="normal">
-			<primary><application>Kickstart Configurator</application>
-			</primary>
-			<secondary>language</secondary>
-		</indexterm>
-		<para>
-			Choose the language to use during the installation and as the default language to be used after installation from the <guimenu>Default Language</guimenu> menu.
-		</para>
-		<indexterm significance="normal">
-			<primary><application>Kickstart Configurator</application>
-			</primary>
-			<secondary>keyboard</secondary>
-		</indexterm>
-		<para>
-			Select the system keyboard type from the <guimenu>Keyboard</guimenu> menu.
-		</para>
-		
-		<indexterm significance="normal">
-			<primary><application>Kickstart Configurator</application>
-			</primary>
-			<secondary>time zone</secondary>
-		</indexterm>
-		<para>
-			From the <guimenu>Time Zone</guimenu> menu, choose the time zone to use for the system. To configure the system to use UTC, select <guilabel>Use UTC clock</guilabel>.
-		</para>
-		<indexterm significance="normal">
-			<primary><application>Kickstart Configurator</application>
-			</primary>
-			<secondary>root password</secondary>
-		</indexterm>
-		<indexterm significance="normal">
-			<primary><application>Kickstart Configurator</application>
-			</primary>
-			<secondary>root password</secondary>
-			<tertiary>encrypt</tertiary>
-		</indexterm>
-		<para>
-			Enter the desired root password for the system in the <guilabel>Root Password</guilabel> text entry box. Type the same password in the <guilabel>Confirm Password</guilabel> text box. The second field is to make sure you do not mistype the password and then realize you do not know what it is after you have completed the installation. To save the password as an encrypted password in the file, select <guilabel>Encrypt root password</guilabel>. If the encryption option is selected, when the file is saved, the plain text password that you typed is encrypted and written to the kickstart file. Do not type an already encrypted password and select to encrypt it. Because a kickstart file is a plain text file that can be easily read, it is recommended that an encrypted password be used.
-		</para>
-		 
-		<para>
-			Choosing <guilabel>Target Architecture</guilabel> specifies which specific hardware architecture distribution is used during installation.
-		</para>
-		<indexterm significance="normal">
-			<primary><application>Kickstart Configurator</application>
-			</primary>
-			<secondary>reboot</secondary>
-		</indexterm>
-		<para>
-			Choosing <guilabel>Reboot system after installation</guilabel> reboots your system automatically after the installation is finished.
-		</para>
-		<indexterm significance="normal">
-			<primary><application>Kickstart Configurator</application>
-			</primary>
-			<secondary>text mode installation</secondary>
-		</indexterm>
-		<para>
-			Kickstart installations are performed in graphical mode by default. To override this default and use text mode instead, select the <guilabel>Perform installation in text mode</guilabel> option.
-		</para>
-		<indexterm significance="normal">
-			<primary><application>Kickstart Configurator</application>
-			</primary>
-			<secondary>interactive</secondary>
-		</indexterm>
-		<para>
-			You can perform a kickstart installation in interactive mode. This means that the installation program uses all the options pre-configured in the kickstart file, but it allows you to preview the options in each screen before continuing to the next screen. To continue to the next screen, click the <guibutton>Next</guibutton> button after you have approved the settings or change them before continuing the installation. To select this type of installation, select the <guilabel>Perform installation in interactive mode</guilabel> option.
-		</para>
-	</section>
-	<section id="s1-redhat-config-kickstart-install">
-		<title>Installation Method</title>
-		<indexterm significance="normal">
-			<primary><application>Kickstart Configurator</application>
-			</primary>
-			<secondary>installation method selection</secondary>
-		</indexterm>
-		<figure float="0" id="redhat-config-kickstart-install-fig"><title>Installation Method</title>
-			<mediaobject>
-				<imageobject><imagedata fileref="images/ksconfig/ksconfig-install.png" format="PNG"/></imageobject>
-				<textobject><para>
-						Kickstart Installation Method
-					</para>
-				</textobject>
-			</mediaobject>
-		</figure>
-		<para>
-			The <guilabel>Installation Method</guilabel> screen allows you to choose whether to perform a new installation or an upgrade. If you choose upgrade, the <guilabel>Partition Information</guilabel> and <guilabel>Package Selection</guilabel> options are disabled. They are not supported for kickstart upgrades.
-		</para>
-		 
-		<para>
-			Choose the type of kickstart installation or upgrade from the following options:
-		</para>
-		 
-		<itemizedlist>
-			<listitem>
-				<para>
-					<guilabel>CD-ROM</guilabel> &mdash; Choose this option to install or upgrade from the Fedora CD-ROMs.
-				</para>
-			</listitem>
-
-			<listitem>
-				<para>
-					<guilabel>NFS</guilabel> &mdash; Choose this option to install or upgrade from an NFS shared directory. In the text field for the the NFS server, enter a fully-qualified domain name or IP address. For the NFS directory, enter the name of the NFS directory that contains the <filename><replaceable>variant</replaceable></filename> directory of the installation tree. For example, if the NFS server contains the directory <filename>/mirrors/redhat/i386/Server/</filename>, enter <filename>/mirrors/redhat/i386/</filename> for the NFS directory.
-				</para>
-			</listitem>
-
-			<listitem>
-				<para>
-					<guilabel>FTP</guilabel> &mdash; Choose this option to install or upgrade from an FTP server. In the FTP server text field, enter a fully-qualified domain name or IP address. For the FTP directory, enter the name of the FTP directory that contains the <filename><replaceable>variant</replaceable></filename> directory. For example, if the FTP server contains the directory <filename>/mirrors/redhat/i386/Server/</filename>, enter <filename>/mirrors/redhat/i386/Server/</filename> for the FTP directory. If the FTP server requires a username and password, specify them as well.
-				</para>
-			</listitem>
-
-			<listitem>
-				<para>
-					<guilabel>HTTP</guilabel> &mdash; Choose this option to install or upgrade from an HTTP server. In the text field for the HTTP server, enter the fully-qualified domain name or IP address. For the HTTP directory, enter the name of the HTTP directory that contains the <filename><replaceable>variant</replaceable></filename> directory. For example, if the HTTP server contains the directory <filename>/mirrors/redhat/i386/Server/</filename>, enter <filename>/mirrors/redhat/i386/Server/</filename> for the HTTP directory.
-				</para>
-			</listitem>
-
-			<listitem>
-				<para>
-					<guilabel>Hard Drive</guilabel> &mdash; Choose this option to install or upgrade from a hard drive. Hard drive installations require the use of ISO (or CD-ROM) images. Be sure to verify that the ISO images are intact before you start the installation. To verify them, use an <command>md5sum</command> program as well as the <command>linux mediacheck</command> boot option as discussed in <xref linkend="sn-boot-mediacheck"/>. Enter the hard drive partition that contains the ISO images (for example, <filename>/dev/hda1</filename>) in the <guilabel>Hard Drive Partition</guilabel> text box. Enter the directory that contains the ISO images in the <guilabel>Hard Drive Directory</guilabel> text box.
-				</para>
-			</listitem>
-		</itemizedlist>
-	</section>
-	<section id="s1-redhat-config-kickstart-bootloader">
-		<title>Boot Loader Options</title>
-		<figure float="0" id="redhat-config-kickstart-bootloader-fig"><title>Boot Loader Options</title>
-			<indexterm significance="normal">
-				<primary><application>Kickstart Configurator</application>
-				</primary>
-				<secondary>boot loader options</secondary>
-			</indexterm>
-			<mediaobject>
-				<imageobject><imagedata fileref="images/ksconfig/ksconfig-bootloader.png" format="PNG"/></imageobject>
-				<textobject><para>
-						Boot Loader Options
-					</para>
-				</textobject>
-			</mediaobject>
-		</figure>
-		<indexterm significance="normal">
-			<primary><application>Kickstart Configurator</application>
-			</primary>
-			<secondary>boot loader</secondary>
-		</indexterm>
-		<para>
-			Please note that this screen will be disabled if you have specified a target architecture other than x86 / x86_64.
-		</para>
-		<para>
-			GRUB is the default boot loader for Fedora on x86 / x86_64 architectures. If you do not want to install a boot loader, select <guilabel>Do not install a boot loader</guilabel>. If you choose not to install a boot loader, make sure you create a boot diskette or have another way to boot your system, such as a third-party boot loader.
-		</para>
-		 
-		<para>
-			You must choose where to install the boot loader (the Master Boot Record or the first sector of the <filename>/boot</filename> partition). Install the boot loader on the MBR if you plan to use it as your boot loader.
-		</para>
-		 
-		<para>
-			To pass any special parameters to the kernel to be used when the system boots, enter them in the <guilabel>Kernel parameters</guilabel> text field. For example, if you have an IDE CD-ROM Writer, you can tell the kernel to use the SCSI emulation driver that must be loaded before using <command>cdrecord</command> by configuring <userinput>hdd=ide-scsi</userinput> as a kernel parameter (where <userinput>hdd</userinput> is the CD-ROM
-			device).
-		</para>
-		 
-		<para>
-			You can password protect the GRUB boot loader by configuring a GRUB password. Select <guilabel>Use GRUB password</guilabel>, and enter a password in the <guilabel>Password</guilabel> field. Type the same password in the <guilabel>Confirm Password</guilabel> text field. To save the password as an encrypted password in the file, select <guilabel>Encrypt GRUB password</guilabel>. If the encryption option is selected, when the file is saved, the plain text password that you typed is encrypted and written to the kickstart file. If the password you typed was already encrypted, unselect the encryption option.
-		</para>
-		 
-		<para>
-			If <guilabel>Upgrade an existing installation</guilabel> is selected on the <guilabel>Installation Method</guilabel> page, select <guilabel>Upgrade existing boot loader</guilabel> to upgrade the existing boot loader configuration, while preserving the old entries.
-		</para>
-<!--		
-		<note>
-			<title>Note</title>
-			<para>
-				The <guilabel>Upgrade existing boot loader</guilabel> option does not function at the time of General Availability of Red Hat Enterprise Linux 5. This issue is being addressed, and the functionality will be made available in an errata release.
-			</para>
-		</note>-->
-		
-	</section>
-	<section id="s1-redhat-config-kickstart-partitions">
-		<title>Partition Information</title>
-		<indexterm significance="normal">
-			<primary><application>Kickstart Configurator</application>
-			</primary>
-			<secondary>partitioning</secondary>
-		</indexterm>
-		<figure float="0" id="redhat-config-kickstart-partitions-fig"><title>Partition Information</title>
-			<mediaobject>
-				<imageobject><imagedata fileref="images/ksconfig/ksconfig-partitions.png" format="PNG"/></imageobject>
-				<textobject><para>
-						Kickstart Partition Information
-					</para>
-				</textobject>
-			</mediaobject>
-		</figure>
-		<para>
-			Select whether or not to clear the Master Boot Record (MBR). Choose to remove all existing partitions, remove all existing Linux partitions, or preserve existing partitions.
-		</para>
-		 
-		<para>
-			To initialize the disk label to the default for the architecture of the system (for example, <command>msdos</command> for x86 and <command>gpt</command> for Itanium), select <guilabel>Initialize the disk label</guilabel> if you are installing on a brand new hard drive.
-		</para>
-		
-		<note>
-			<para>
-				Although <command>anaconda</command> and <command>kickstart</command> support Logical Volume Management (LVM), at present there is no mechanism for configuring this using the <application>Kickstart Configurator</application>. 
-			</para>
-		</note>
-		 
-		<section id="s2-redhat-config-kickstart-create-part">
-			<title>Creating Partitions</title>
-			 
-			<para>
-				To create a partition, click the <guibutton>Add</guibutton> button. The <guilabel>Partition Options</guilabel> window shown in <xref linkend="redhat-config-kickstart-add-part-fig"/> appears. Choose the mount point, file system type, and partition size for the new partition. Optionally, you can also choose from the following:
-			</para>
-			 
-			<itemizedlist>
-				<listitem>
-					<para>
-						In the <guilabel>Additional Size Options</guilabel> section, choose to make the partition a fixed size, up to a chosen size, or fill the remaining space on the hard drive. If you selected swap as the file system type, you can select to have the installation program create the swap partition with the recommended size instead of specifying a size.
-					</para>
-				</listitem>
-
-				<listitem>
-					<para>
-						Force the partition to be created as a primary partition.
-					</para>
-				</listitem>
-
-				<listitem>
-					<para>
-						Create the partition on a specific hard drive. For example, to make the partition on the first IDE hard disk (<filename>/dev/hda</filename>), specify <userinput>hda</userinput> as the drive. Do not include <filename>/dev</filename> in the drive name.
-					</para>
-				</listitem>
-
-				<listitem>
-					<para>
-						Use an existing partition. For example, to make the partition on the first partition on the first IDE hard disk (<filename>/dev/hda1</filename>), specify <userinput>hda1</userinput> as the partition. Do not include <filename>/dev</filename> in the partition name.
-					</para>
-				</listitem>
-
-				<listitem>
-					<para>
-						Format the partition as the chosen file system type.
-					</para>
-				</listitem>
-			</itemizedlist>
-			<figure float="0" id="redhat-config-kickstart-add-part-fig"><title>Creating Partitions</title>
-				<mediaobject>
-					<imageobject><imagedata fileref="images/ksconfig/ksconfig-part-options.png" format="PNG"/></imageobject>
-					<textobject><para>
-							Creating Partitions for Kickstart
-						</para>
-					</textobject>
-				</mediaobject>
-			</figure>
-			<para>
-				To edit an existing partition, select the partition from the list and click the <guibutton>Edit</guibutton> button. The same <guilabel>Partition Options</guilabel> window appears as when you chose to add a partition as shown in <xref linkend="redhat-config-kickstart-add-part-fig"/>, except it reflects the values for the selected partition. Modify the partition options and click <guibutton>OK</guibutton>.
-			</para>
-			 
-			<para>
-				To delete an existing partition, select the partition from the list and click the <guibutton>Delete</guibutton> button.
-			</para>
-			 
-			<section id="s3-redhat-config-kickstart-raid">
-				<title>Creating Software RAID Partitions</title>
-				<indexterm significance="normal">
-					<primary><application>Kickstart Configurator</application>
-					</primary>
-					<secondary>partitioning</secondary>
-					<tertiary>software RAID</tertiary>
-				</indexterm>
-				<indexterm significance="normal">
-					<primary>RAID</primary>
-					<secondary>kickstart installations</secondary>
-					<tertiary>Kickstart Configurator</tertiary>
-				</indexterm>
-				<para>
-					To create a software RAID partition, use the following steps:
-				</para>
-				 
-				<orderedlist inheritnum="ignore" continuation="restarts">
-					<listitem>
-						<para>
-							Click the <guibutton>RAID</guibutton> button.
-						</para>
-					</listitem>
-
-					<listitem>
-						<para>
-							Select <guilabel>Create a software RAID partition</guilabel>.
-						</para>
-					</listitem>
-
-					<listitem>
-						<para>
-							Configure the partitions as previously described, except select <guilabel>Software RAID</guilabel> as the file system type. Also, you must specify a hard drive on which to make the partition or specify an existing partition to use.
-						</para>
-					</listitem>
-				</orderedlist>
-				<figure float="0" id="fig-kickstart-raid"><title>Creating a Software RAID Partition</title>
-					<mediaobject>
-						<imageobject><imagedata fileref="images/ksconfig/ksconfig-raid-new.png" format="PNG"/></imageobject>
-						<textobject><para>
-								Software RAID Partition
-							</para>
-						</textobject>
-					</mediaobject>
-				</figure>
-				<para>
-					Repeat these steps to create as many partitions as needed for your RAID setup. All of your partitions do not have to be RAID partitions.
-				</para>
-				 
-				<para>
-					After creating all the partitions needed to form a RAID device, follow these steps:
-				</para>
-				 
-				<orderedlist inheritnum="ignore" continuation="restarts">
-					<listitem>
-						<para>
-							Click the <guibutton>RAID</guibutton> button.
-						</para>
-					</listitem>
-
-					<listitem>
-						<para>
-							Select <guilabel>Create a RAID device</guilabel>.
-						</para>
-					</listitem>
-
-					<listitem>
-						<para>
-							Select a mount point, file system type, RAID device name, RAID level, RAID members, number of spares for the software RAID device, and whether to format the RAID device.
-						</para>
-						<figure float="0" id="fig-redhat-config-kickstart-md0"><title>Creating a Software RAID Device</title>
-							<mediaobject>
-								<imageobject><imagedata fileref="images/ksconfig/ksconfig-raid-device.png" format="PNG"/></imageobject>
-								<textobject><para>
-										Software RAID Device
-									</para>
-								</textobject>
-							</mediaobject>
-						</figure>
-					</listitem>
-
-					<listitem>
-						<para>
-							Click <guibutton>OK</guibutton> to add the device to the list.
-						</para>
-					</listitem>
-				</orderedlist>
-			</section>
-		</section>
-	</section>
-	<section id="s1-redhat-config-kickstart-network">
-		<title>Network Configuration</title>
-		<indexterm significance="normal">
-			<primary><application>Kickstart Configurator</application>
-			</primary>
-			<secondary>network configuration</secondary>
-		</indexterm>
-		<figure float="0" id="redhat-config-kickstart-network-fig"><title>Network Configuration</title>
-			<mediaobject>
-				<imageobject><imagedata fileref="images/ksconfig/ksconfig-network.png" format="PNG"/></imageobject>
-				<textobject><para>
-						Network Configuration for Kickstart
-					</para>
-				</textobject>
-			</mediaobject>
-		</figure>
-		<para>
-			If the system to be installed via kickstart does not have an Ethernet card, do not configure one on the <guilabel>Network Configuration</guilabel> page.
-		</para>
-		 
-		<para>
-			Networking is only required if you choose a networking-based installation method (NFS, FTP, or HTTP). Networking can always be configured after installation with the <application>Network Administration Tool</application> (<command>system-config-network</command>). Refer to the Red Hat Enterprise Linux Deployment Guide for details.
-		</para>
-		 
-		<para>
-			For each Ethernet card on the system, click <guibutton>Add Network Device</guibutton> and select the network device and network type for the device. Select <guilabel>eth0</guilabel> to configure the first Ethernet card, <guilabel>eth1</guilabel> for the second Ethernet card, and so on.
-		</para>
-	</section>
-	<section id="s1-redhat-config-kickstart-auth">
-		<title>Authentication</title>
-		<indexterm significance="normal">
-			<primary><application>Kickstart Configurator</application>
-			</primary>
-			<secondary>authentication options</secondary>
-		</indexterm>
-		<figure float="0" id="redhat-config-kickstart-auth-fig"><title>Authentication</title>
-			<mediaobject>
-				<imageobject><imagedata fileref="images/ksconfig/ksconfig-auth.png" format="PNG"/></imageobject>
-				<textobject><para>
-						Authentication for Kickstart
-					</para>
-				</textobject>
-			</mediaobject>
-		</figure>
-		<para>
-			In the <guilabel>Authentication</guilabel> section, select whether to use shadow passwords and MD5 encryption for user passwords. These options are highly recommended and chosen by default.
-		</para>
-		 
-		<para>
-			The <guilabel>Authentication Configuration</guilabel> options allow you to configure the following methods of authentication:
-		</para>
-		 
-		<itemizedlist>
-			<listitem>
-				<para>
-					NIS
-				</para>
-			</listitem>
-
-			<listitem>
-				<para>
-					LDAP
-				</para>
-			</listitem>
-
-			<listitem>
-				<para>
-					Kerberos 5
-				</para>
-			</listitem>
-
-			<listitem>
-				<para>
-					Hesiod
-				</para>
-			</listitem>
-
-			<listitem>
-				<para>
-					SMB
-				</para>
-			</listitem>
-
-			<listitem>
-				<para>
-					Name Switch Cache
-				</para>
-			</listitem>
-		</itemizedlist>
-		 
-		<para>
-			These methods are not enabled by default. To enable one or more of these methods, click the appropriate tab, click the checkbox next to <guilabel>Enable</guilabel>, and enter the appropriate information for the authentication method.
-			Refer to the Red Hat Enterprise Linux Deployment Guide for more information about the options.
-		</para>
-	</section>
-	<section id="s1-redhat-config-kickstart-firewall">
-		<title>Firewall Configuration</title>
-		<indexterm significance="normal">
-			<primary><application>Kickstart Configurator</application>
-			</primary>
-			<secondary>firewall configuration</secondary>
-		</indexterm>
-		<para>
-			The <guilabel>Firewall Configuration</guilabel> window is similar to the screen in the installation program and the <application>Security Level Configuration Tool</application>.
-		</para>
-		<figure float="0" id="redhat-config-kickstart-firewall-fig"><title>Firewall Configuration</title>
-			<mediaobject>
-				<imageobject><imagedata fileref="images/ksconfig/ksconfig-firewall.png" format="PNG"/></imageobject>
-				<textobject><para>
-						Firewall Configuration for Kickstart
-					</para>
-				</textobject>
-			</mediaobject>
-		</figure>
-		<para>
-			If <guilabel>Disable firewall</guilabel> is selected, the system allows complete access to any active services and ports. No connections to the system are refused or denied.
-		</para>
-		 
-		<para>
-			Selecting <guilabel>Enable firewall</guilabel> configures the system to reject incoming connections that are not in response to outbound requests, such as DNS replies or DHCP requests. If access to services running on this machine is required, you can choose to allow specific services through the firewall.
-		</para>
-		 
-		<para>
-			Only devices configured in the <guilabel>Network Configuration</guilabel> section are listed as available <guilabel>Trusted devices</guilabel>. Connections from any devices selected in the list are accepted by the system. For example, if <guilabel>eth1</guilabel> only receives connections from internal system, you might want to allow connections from it.
-		</para>
-		 
-		<para>
-			If a service is selected in the <guilabel>Trusted services</guilabel> list, connections for the service are accepted and processed by the system.
-		</para>
-		 
-		<para>
-			In the <guilabel>Other ports</guilabel> text field, list any additional ports that should be opened for remote access. Use the following format: <userinput>port:protocol</userinput>. For example, to allow IMAP access through the firewall, specify <userinput>imap:tcp</userinput>. Numeric ports can also be specified explicitly; to allow UDP packets on port 1234 through the firewall, enter <userinput>1234:udp</userinput>. To specify
-			multiple ports, separate them with commas.
-		</para>
-		 
-		<section id="s2-redhat-config-kickstart-firewall-selinux">
-			<title>SELinux Configuration</title>
-			<indexterm significance="normal">
-				<primary><application>Kickstart Configurator</application>
-				</primary>
-				<secondary>SELinux configuration</secondary>
-			</indexterm>
-			<para>
-				Kickstart can set SELinux to <command>enforcing</command>, <command>permissive</command> or <command>disabled</command> mode. Finer grained configuration is not possible at this time.
-			</para>
-		</section>
-	</section>
-	<section id="s1-redhat-config-kickstart-xconfig">
-		<title>Display Configuration</title>
-		<indexterm significance="normal">
-			<primary><application>Kickstart Configurator</application>
-			</primary>
-			<secondary>Display configuration</secondary>
-		</indexterm>
-		<para>
-			If you are installing the X Window System, you can configure it during the kickstart installation by checking the <guilabel>Configure the X Window System</guilabel> option on the <guilabel>Display Configuration</guilabel> window as shown in <xref linkend="xconfig-fig"/>. If this option is not chosen, the X configuration options are disabled and the <command>skipx</command> option is written to the kickstart file.
-		</para>
-		<figure float="0" id="xconfig-fig"><title>X Configuration</title>
-			<mediaobject>
-				<imageobject><imagedata fileref="images/ksconfig/ksconfig-xconfig.png" format="PNG"/></imageobject>
-				<textobject><para>
-						X Configuration for Kickstart
-					</para>
-				</textobject>
-			</mediaobject>
-		</figure>
-		<para>
-			Also select whether to start the <application>Setup Agent</application> the first time the system is rebooted. It is disabled by default, but the setting can be changed to enabled or enabled in reconfiguration mode. Reconfiguration mode enables the language, mouse, keyboard, root password, security level, time zone, and networking configuration options in addition to the default ones.
-		</para>
-		 
-<!--		<section id="s2-redhat-config-kickstart-xconfig-general">
-			<title>General</title>
-			 
-			<para>
-				The first step in configuring X is to choose the default color depth and resolution. Select them from their respective pulldown menus. Be sure to specify a color depth and resolution that is compatible with the video card and monitor for the system.
-			</para>
-			<figure float="0" id="xconfig-general-fig"><title>X Configuration - General</title>
-				<mediaobject>
-					<imageobject><imagedata fileref="images/ksconfig/ksconfig-xconfig-general.png" format="PNG"/></imageobject>
-					<textobject><para>
-							X Configuration for Kickstart
-						</para>
-					</textobject>
-				</mediaobject>
-			</figure>
-			<para>
-				If you are installing both the GNOME and KDE desktops, you must choose which desktop should be the default. If only one desktop is to be installed, be sure to choose it. Once the system is installed, users can choose which desktop they want to be their default.
-			</para>
-			 
-			<para>
-				Next, choose whether to start the X Window System when the system is booted. This option starts the system in runlevel 5 with the graphical login screen. After the system is installed, this can be changed by modifying the <filename>/etc/inittab</filename> configuration file.
-			</para>
-			 
-			<para>
-				Also select whether to start the <application>Setup Agent</application> the first time the system is rebooted. It is disabled by default, but the setting can be changed to enabled or enabled in reconfiguration mode. Reconfiguration mode enables the language, mouse, keyboard, root password, security level, time zone, and networking configuration options in addition to the default ones.
-			</para>
-		</section>
-		 
-		<section id="s2-redhat-config-kickstart-xconfig-videocard">
-			<title>Video Card</title>
-			 
-			<para>
-				<guilabel>Probe for video card driver</guilabel> is selected by default. Accept this default to have the installation program probe for the video card during installation. Probing works for most modern video cards. If this option is selected and the installation program cannot successfully probe the video card, the installation program stops at the video card configuration screen. To continue the installation process, select the driver for your video card from the list and click <guibutton>Next</guibutton>.
-			</para>
-			 
-			<para>
-				Alternatively, you can select the video card driver from the list on the <guilabel>Video Card</guilabel> tab as shown in <xref linkend="xconfig-videocard-fig"/>. Specify the amount of video RAM the selected video card has from the <guilabel>Video Card RAM</guilabel> pulldown menu. These values are used by the installation program to configure the X Window System.
-			</para>
-			<figure float="0" id="xconfig-videocard-fig"><title>X Configuration - Video Card</title>
-				<mediaobject>
-					<imageobject><imagedata fileref="images/ksconfig/ksconfig-xconfig-videocard.png" format="PNG"/></imageobject>
-					<textobject><para>
-							X Configuration for Kickstart
-						</para>
-					</textobject>
-				</mediaobject>
-			</figure>
-		</section>
-		 
-		<section id="s2-redhat-config-kickstart-xconfig-monitor">
-			<title>Monitor</title>
-			 
-			<para>
-				After configuring the video card, click on the <guilabel>Monitor</guilabel> tab as shown in <xref linkend="xconfig-monitor-fig"/>.
-			</para>
-			<figure float="0" id="xconfig-monitor-fig"><title>X Configuration - Monitor</title>
-				<mediaobject>
-					<imageobject><imagedata fileref="images/ksconfig/ksconfig-xconfig-monitor.png" format="PNG"/></imageobject>
-					<textobject><para>
-							X Configuration for Kickstart
-						</para>
-					</textobject>
-				</mediaobject>
-			</figure>
-			<para>
-				<guilabel>Probe for monitor</guilabel> is selected by default. Accept this default to have the installation program probe for the monitor during installation. Probing works for most modern monitors. If this option is selected and the installation program cannot successfully probe the monitor, the installation program stops at the monitor configuration screen. To continue the installation process, select your monitor from the list and click
-				<guibutton>Next</guibutton>.
-			</para>
-			 
-			<para>
-				Alternatively, you can select your monitor from the list. You can also specify the horizontal and vertical sync rates instead of selecting a specific monitor by checking the <guilabel>Specify hsync and vsync instead of monitor</guilabel> option. This option is useful if the monitor for the system is not listed. Notice that when this option is enabled, the monitor list is disabled.
-			</para>
-		</section> -->
-	</section>
-	<section id="s1-redhat-config-kickstart-pkgs">
-		<title>Package Selection</title>
-		<indexterm significance="normal">
-			<primary><application>Kickstart Configurator</application>
-			</primary>
-			<secondary>package selection</secondary>
-		</indexterm>
-		<figure float="0" id="redhat-config-kickstart-pkgs-fig"><title>Package Selection</title>
-			<mediaobject>
-				<imageobject><imagedata fileref="images/ksconfig/ksconfig-pkgs.png" format="PNG"/></imageobject>
-				<textobject><para>
-						Package Selection for Kickstart
-					</para>
-				</textobject>
-			</mediaobject>
-		</figure>
-		<para>
-			The <guilabel>Package Selection</guilabel> window allows you to choose which package groups to install.
-		</para>
-		 
-		<para>
-			Package resolution is carried out automatically.
-		</para>
-		 
-		<para>
-			Currently, <application>Kickstart Configurator </application> does not allow you to select individual packages. To install individual packages, modify the <command>%packages</command> section of the kickstart file after you save it. Refer to <xref linkend="s1-kickstart2-packageselection"/> for details.
-		</para>
-	</section>
-	<section id="s1-redhat-config-kickstart-prescript">
-		<title>Pre-Installation Script</title>
-		<indexterm significance="normal">
-			<primary><application>Kickstart Configurator</application>
-			</primary>
-			<secondary>%pre script</secondary>
-		</indexterm>
-		<figure float="0" id="redhat-config-kickstart-prescript-fig"><title>Pre-Installation Script</title>
-			<mediaobject>
-				<imageobject><imagedata fileref="images/ksconfig/ksconfig-prescript.png" format="PNG"/></imageobject>
-				<textobject><para>
-						Pre-Installation Script for Kickstart
-					</para>
-				</textobject>
-			</mediaobject>
-		</figure>
-		<para>
-			You can add commands to run on the system immediately after the kickstart file has been parsed and before the installation begins. If you have configured the network in the kickstart file, the network is enabled before this section is processed. To include a pre-installation script, type it in the text area.
-		</para>
-		 
-		<para>
-			To specify a scripting language to use to execute the script, select the <guilabel>Use an interpreter</guilabel> option and enter the interpreter in the text box beside it. For example, <userinput>/usr/bin/python2.4</userinput> can be specified for a Python script. This option corresponds to using <command>%pre --interpreter <replaceable>/usr/bin/python2.4</replaceable></command> in your kickstart file.
-		</para>
-		
-		<para>
-			Many of the commands that are available in the pre-installation environment are provided by a version of <application>busybox</application> called <application>busybox-anaconda</application>. <application>Busybox</application>-supplied commands do not provide all features, but supply only the most commonly used features. The following list of available commands include commands provided by <application>busybox</application>:
-		</para>
-		
-		<para><command>addgroup</command>, <command>adduser</command>, <command>adjtimex</command>, <command>ar</command>, <command>arping</command>, <command>ash</command>, <command>awk</command>, <command>basename</command>, <command>bbconfig</command>, <command>bunzip2</command>, <command>busybox</command>, <command>bzcat</command>, <command>cal</command>, <command>cat</command>, <command>catv</command>, <command>chattr</command>, <command>chgrp</command>, <command>chmod</command>, <command>chown</command>, <command>chroot</command>, <command>chvt</command>, <command>cksum</command>, <command>clear</command>, <command>cmp</command>, <command>comm</command>, <command>cp</command>, <command>cpio</command>, <command>crond</command>, <command>crontab</command>, <command>cut</command>, <command>date</command>, <command>dc</command>, <command>dd</command>, <command>deallocvt</command>, <command>delgroup</command>, <command>deluser</command>, <command>devfsd</command>, <command>df</co
 mmand>, <command>diff</command>, <command>dirname</command>, <command>dmesg</command>, <command>dnsd</command>, <command>dos2unix</command>, <command>dpkg</command>, <command>dpkg-deb</command>, <command>du</command>, <command>dumpkmap</command>, <command>dumpleases</command>, <command>e2fsck</command>, <command>e2label</command>, <command>echo</command>, <command>ed</command>, <command>egrep</command>, <command>eject</command>, <command>env</command>, <command>ether-wake</command>, <command>expr</command>, <command>fakeidentd</command>, <command>false</command>, <command>fbset</command>, <command>fdflush</command>, <command>fdformat</command>, <command>fdisk</command>, <command>fgrep</command>, <command>find</command>, <command>findfs</command>, <command>fold</command>, <command>free</command>, <command>freeramdisk</command>, <command>fsck</command>, <command>fsck.ext2</command>, <command>fsck.ext3</command>, <command>fsck.ext4</command>, <command>fsck.minix</command>, <com
 mand>ftpget</command>, <command>ftpput</command>, <command>fuser</command>, <command>getopt</command>, <command>getty</command>, <command>grep</command>, <command>gunzip</command>, <command>gzip</command>, <command>hdparm</command>, <command>head</command>, <command>hexdump</command>, <command>hostid</command>, <command>hostname</command>, <command>httpd</command>, <command>hush</command>, <command>hwclock</command>, <command>id</command>, <command>ifconfig</command>, <command>ifdown</command>, <command>ifup</command>, <command>inetd</command>, <command>insmod</command>, <command>install</command>, <command>ip</command>, <command>ipaddr</command>, <command>ipcalc</command>, <command>ipcrm</command>, <command>ipcs</command>, <command>iplink</command>, <command>iproute</command>, <command>iptunnel</command>, <command>kill</command>, <command>killall</command>, <command>lash</command>, <command>last</command>, <command>length</command>, <command>less</command>, <command>linux32
 </command>, <command>linux64</command>, <command>ln</command>, <command>load_policy</command>, <command>loadfont</command>, <command>loadkmap</command>, <command>login</command>, <command>logname</command>, <command>losetup</command>, <command>ls</command>, <command>lsattr</command>, <command>lsmod</command>, <command>lzmacat</command>, <command>makedevs</command>, <command>md5sum</command>, <command>mdev</command>, <command>mesg</command>, <command>mkdir</command>, <command>mke2fs</command>, <command>mkfifo</command>, <command>mkfs.ext2</command>, <command>mkfs.ext3</command>, <command>mkfs.ext4</command>, <command>mkfs.minix</command>, <command>mknod</command>, <command>mkswap</command>, <command>mktemp</command>, <command>modprobe</command>, <command>more</command>, <command>mount</command>, <command>mountpoint</command>, <command>msh</command>, <command>mt</command>, <command>mv</command>, <command>nameif</command>, <command>nc</command>, <command>netstat</command>, <com
 mand>nice</command>, <command>nohup</command>, <command>nslookup</command>, <command>od</command>, <command>openvt</command>, <command>passwd</command>, <command>patch</command>, <command>pidof</command>, <command>ping</command>, <command>ping6</command>, <command>pipe_progress</command>, <command>pivot_root</command>, <command>printenv</command>, <command>printf</command>, <command>ps</command>, <command>pwd</command>, <command>rdate</command>, <command>readlink</command>, <command>readprofile</command>, <command>realpath</command>, <command>renice</command>, <command>reset</command>, <command>rm</command>, <command>rmdir</command>, <command>rmmod</command>, <command>route</command>, <command>rpm</command>, <command>rpm2cpio</command>, <command>run-parts</command>, <command>runlevel</command>, <command>rx</command>, <command>sed</command>, <command>seq</command>, <command>setarch</command>, <command>setconsole</command>, <command>setkeycodes</command>, <command>setlogcons</
 command>, <command>setsid</command>, <command>sh</command>, <command>sha1sum</command>, <command>sleep</command>, <command>sort</command>, <command>start-stop-daemon</command>, <command>stat</command>, <command>strings</command>, <command>stty</command>, <command>su</command>, <command>sulogin</command>, <command>sum</command>, <command>swapoff</command>, <command>swapon</command>, <command>switch_root</command>, <command>sync</command>, <command>sysctl</command>, <command>tail</command>, <command>tar</command>, <command>tee</command>, <command>telnet</command>, <command>telnetd</command>, <command>test</command>, <command>tftp</command>, <command>time</command>, <command>top</command>, <command>touch</command>, <command>tr</command>, <command>traceroute</command>, <command>true</command>, <command>tty</command>, <command>tune2fs</command>, <command>udhcpc</command>, <command>udhcpd</command>, <command>umount</command>, <command>uname</command>, <command>uncompress</command>
 , <command>uniq</command>, <command>unix2dos</command>, <command>unlzma</command>, <command>unzip</command>, <command>uptime</command>, <command>usleep</command>, <command>uudecode</command>, <command>uuencode</command>, <command>vconfig</command>, <command>vi</command>, <command>vlock</command>, <command>watch</command>, <command>watchdog</command>, <command>wc</command>, <command>wget</command>, <command>which</command>, <command>who</command>, <command>whoami</command>, <command>xargs</command>, <command>yes</command>, <command>zcat</command>, <command>zcip</command></para>
-
-		<para>For a description of any of these commands, run:</para>
-		
-		<para><command>busybox <replaceable>command</replaceable> --help</command></para>
-		
-		<para>
-			In addition to the aforementioned commands, the following commands are provided in their full featured versions:
-		</para>
-<!-- above replaces below: BZ#221934
-		<para>
-			Some of the previous commands are provided by <application>busybox</application> and some are provided in their full featured versions. In addition to the commands above the following commands are provided in their full featured versions:
-		</para>
-		-->
-		<para><command>anaconda</command>, <command>bash</command>, <command>bzip2</command>, <command>jmacs</command>, <command>ftp</command>, <command>head</command>, <command>joe</command>, <command>kudzu-probe</command>, <command>list-harddrives</command>, <command>loadkeys</command>, <command>mtools</command>, <command>mbchk</command>, <command>mtools</command>, <command>mini-wm</command>, <command>mtools</command>, <command>jpico</command>, <command>pump</command>, <command>python</command>, <command>python2.4</command>, <command>raidstart</command>, <command>raidstop</command>, <command>rcp</command>, <command>rlogin</command>, <command>rsync</command>, <command>setxkbmap</command>, <command>sftp</command>, <command>shred</command>, <command>ssh</command>, <command>syslinux</command>, <command>syslogd</command>, <command>tac</command>, <command>termidx</command>, <command>vncconfig</command>, <command>vncpasswd</command>, <command>xkbcomp</command>, <command>Xorg</command>,
  <command>Xvnc</command>, <command>zcat</command></para>
-		 
-		<warning>
-			<title>Warning</title>
-
-			<para>
-				Do not include the <command>%pre</command> command. It is added for you.
-			</para>
-		</warning>
-		
-		<note>
-			<para>
-				The pre-installation script is run after the source media is mounted and stage 2 of the bootloader has been loaded. For this reason it is not possible to change the source media in the pre-installation script.
-			</para>
-		</note>
-	</section>
-	<section id="s1-redhat-config-kickstart-postinstall">
-		<title>Post-Installation Script</title>
-		<indexterm significance="normal">
-			<primary><application>Kickstart Configurator</application>
-			</primary>
-			<secondary>%post script</secondary>
-		</indexterm>
-		<figure float="0" id="redhat-config-kickstart-postinstall-fig"><title>Post-Installation Script</title>
-			<mediaobject>
-				<imageobject><imagedata fileref="images/ksconfig/ksconfig-postscript.png" format="PNG"/></imageobject>
-				<textobject><para>
-						Post-Installation Script for Kickstart
-					</para>
-				</textobject>
-			</mediaobject>
-		</figure>
-		<para>
-			You can also add commands to execute on the system after the installation is completed. If the network is properly configured in the kickstart file, the network is enabled, and the script can include commands to access resources on the network. To include a post-installation script, type it in the text area.
-		</para>
-		 
-		<warning>
-			<title>Warning</title>
-
-			<para>
-				Do not include the <command>%post</command> command. It is added for you.
-			</para>
-		</warning>
-		 
-		<para>
-			For example, to change the message of the day for the newly installed system, add the following command to the <command>%post</command> section:
-		</para>
-<screen>
-<command>echo "Hackers will be punished" &gt; /etc/motd</command>
-</screen>
-		<note><title>Note</title>
-			<para>
-				More examples can be found in <xref linkend="s2-kickstart2-post-examples"/>.
-			</para>
-		</note>
-		<section id="s2-redhat-config-kickstart-nochroot">
-			<title>Chroot Environment</title>
-			 
-			<para>
-				To run the post-installation script outside of the chroot environment, click the checkbox next to this option on the top of the <guilabel>Post-Installation</guilabel> window. This is equivalent to using the <command>--nochroot</command> option in the <command>%post</command> section.
-			</para>
-			 
-			<para>
-				To make changes to the newly installed file system, within the post-installation section, but outside of the chroot environment, you must prepend the directory name with <filename>/mnt/sysimage/</filename>.
-			</para>
-			 
-			<para>
-				For example, if you select <guilabel>Run outside of the chroot environment</guilabel>, the previous example must be changed to the following:
-			</para>
-<screen>
-<command>echo "Hackers will be punished" &gt; /mnt/sysimage/etc/motd</command>
-</screen>
-		</section>
-		 
-		<section id="s2-redhat-config-kickstart-interpreter">
-			<title>Use an Interpreter</title>
-			 
-			<para>
-				To specify a scripting language to use to execute the script, select the <guilabel>Use an interpreter</guilabel> option and enter the interpreter in the text box beside it. For example, <userinput>/usr/bin/python2.2</userinput> can be specified for a Python script. This option corresponds to using <command>%post --interpreter <replaceable>/usr/bin/python2.2</replaceable></command> in your kickstart
-				file.
-			</para>
-		</section>
-	</section>
-	<section id="s1-redhat-config-kickstart-savefile">
-		<title>Saving the File</title>
-		<indexterm significance="normal">
-			<primary><application>Kickstart Configurator</application>
-			</primary>
-			<secondary>saving</secondary>
-		</indexterm>
-		<para>
-			To review the contents of the kickstart file after you have finished choosing your kickstart options, select <guimenuitem>File</guimenuitem> =&gt; <guimenuitem>Preview</guimenuitem> from the pull-down menu.
-		</para>
-		<figure float="0" id="redhat-config-kickstart-preview"><title>Preview</title>
-			<mediaobject>
-				<imageobject><imagedata fileref="images/ksconfig/ksconfig-confirm.png" format="PNG"/></imageobject>
-				<textobject><para>
-						Preview
-					</para>
-				</textobject>
-			</mediaobject>
-		</figure>
-		<para>
-			To save the kickstart file, click the <guibutton>Save to File</guibutton> button in the preview window. To save the file without previewing it, select <guimenuitem>File</guimenuitem> =&gt; <guimenuitem>Save File</guimenuitem> or press <keycombo><keycap>Ctrl</keycap><keycap>S</keycap>
-			</keycombo>
-			. A dialog box appears. Select where to save the file.
-		</para>
-		 
-		<para>
-			After saving the file, refer to <xref linkend="s1-kickstart2-startinginstall"/> for information on how to start the kickstart installation.
-		</para>
-	</section>
-</chapter>
diff --git a/en-US/Language_Selection-x86.xml b/en-US/Language_Selection-x86.xml
deleted file mode 100644
index e5f3a12..0000000
--- a/en-US/Language_Selection-x86.xml
+++ /dev/null
@@ -1,44 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<section id="s1-langselection-x86">
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" 
-	href="Language_Selection_common-title.xml"/>
-	<!-- Title: Language Selection -->
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" 
-	href="Language_Selection_common-indexterm.xml"/>
-
-	<para>
-		Using your mouse, select a language to use for the installation (refer to <xref linkend="fig-langselection-x86"/>).
-	</para>
-
-	 
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" 
-	href="Language_Selection_common-para-1.xml"/>
-	<!-- The language you select here will become the default language... -->
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" 
-	href="Language_Selection_common-para-3.xml"/>
-	<!-- To add support for additional languages, customize... -->
-	
-	<figure float="0" id="fig-langselection-x86"><title>Language Selection</title>
-		<mediaobject>
-			<imageobject><imagedata fileref="images/langselection/lang.png" format="PNG"/></imageobject>
-			<textobject><para>
-
-					Language selection screen.
-				</para>
-			</textobject>
-		</mediaobject>
-	</figure>
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" 
-	href="Language_Selection_common-para-2.xml"/>
-	<!-- Once you have selected the appropriate language... -->
-		
-</section>
-
-
-
diff --git a/en-US/Language_Selection_common-indexterm.xml b/en-US/Language_Selection_common-indexterm.xml
deleted file mode 100644
index 594f05a..0000000
--- a/en-US/Language_Selection_common-indexterm.xml
+++ /dev/null
@@ -1,8 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE indexterm PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<indexterm significance="normal">
-	<primary>language</primary>
-	<secondary>selecting</secondary>
-</indexterm>
\ No newline at end of file
diff --git a/en-US/Language_Selection_common-para-1.xml b/en-US/Language_Selection_common-para-1.xml
deleted file mode 100644
index d016ce9..0000000
--- a/en-US/Language_Selection_common-para-1.xml
+++ /dev/null
@@ -1,7 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<para>
-	The language you select here will become the default language for the operating system once it is installed. Selecting the appropriate language also helps target your time zone configuration later in the installation. The installation program tries to define the appropriate time zone based on what you specify on this screen. 
-</para>
\ No newline at end of file
diff --git a/en-US/Language_Selection_common-para-2.xml b/en-US/Language_Selection_common-para-2.xml
deleted file mode 100644
index e6e9859..0000000
--- a/en-US/Language_Selection_common-para-2.xml
+++ /dev/null
@@ -1,7 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<para>
-	Once you select the appropriate language, click <guibutton>Next</guibutton> to continue.
-</para>
\ No newline at end of file
diff --git a/en-US/Language_Selection_common-para-3.xml b/en-US/Language_Selection_common-para-3.xml
deleted file mode 100644
index 6c27fce..0000000
--- a/en-US/Language_Selection_common-para-3.xml
+++ /dev/null
@@ -1,9 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-    <para>
-      To add support for additional languages, customize the
-      installation at the package selection stage. For more information,
-      refer to <xref linkend="sn-lang-packages"/>.
-    </para>
diff --git a/en-US/Language_Selection_common-title.xml b/en-US/Language_Selection_common-title.xml
deleted file mode 100644
index 5e94d8e..0000000
--- a/en-US/Language_Selection_common-title.xml
+++ /dev/null
@@ -1,5 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE title PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<title>Language Selection</title>
\ No newline at end of file
diff --git a/en-US/Making_Fedora_Media.xml b/en-US/Making_Fedora_Media.xml
deleted file mode 100644
index 790ab0a..0000000
--- a/en-US/Making_Fedora_Media.xml
+++ /dev/null
@@ -1,77 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
-"http://www.docbook.org/xml/4.4/docbookx.dtd" [
-]>
-
-<chapter  id="sn-making-media">
-    <title>Making Fedora Media</title>
-    <indexterm>
-	<primary>CD/DVD media</primary>
-	<secondary>making</secondary>
-	<seealso>ISO images</seealso>
-      </indexterm>
-      <indexterm>
-	<primary>USB flash media</primary>
-	<secondary>making</secondary>
-      </indexterm>
-    <para>
-	Use any of the methods described in this section to turn the ISO image file that you downloaded into a bootable DVD, CD, or USB device.
-    </para>
-    <section id="sn-making-disc-media">
-      <title>Making CD or DVD Discs</title>
-      <para>
-	You can make a CD or DVD from a distribution image file, a live image file, or a minimal boot media image file using the CD or DVD burning software on your computer.
-      </para>
-      
-<!-- this text is from Burn_the_image_file_to_CD.xml in the Fedora Installation Quick Start Guide -->
-	<para>
-		The exact series of steps that produces a CD from an image file varies greatly from computer to computer, depending on the operating system and disc burning software installed. Use this procedure as a general guide. You might be able to omit certain steps on your computer, or might have to perform some of the steps in a different order from the order described here.
-	</para>
-	<para>
-		Make sure that your disc burning software is capable of burning discs from image files. Although this is true of most disc burning software, exceptions exist.
-	</para>
-	<para>
-		In particular, note that the CD burning feature built into Windows XP and Windows Vista cannot burn CDs from images and that earlier Windows operating systems did not have any CD burning capability installed by default. Therefore, if your computer has a Windows operating system prior to Windows&nbsp;7 installed on it, you need a separate piece of software for this task. Examples of popular CD burning software for Windows that you might already have on your computer include <application>Nero Burning ROM</application> and <application>Roxio Creator</application>. If you use a Windows operating system on your computer and do not have disc burning software installed (or you are not sure that the software can burn discs from image files) <application>InfraRecorder</application> is a suitable alternative available from <ulink url="http://www.infrarecorder.org/"></ulink>, and is free and open-source. 
-	</para>
-	<para>
-		The <application>Disk Utility</application> software installed by default with Mac OS&nbsp;X on Apple computers has the capability to burn CDs from images built into it already. Most widely-used CD burning software for Linux, such as <application>Brasero</application> and <application>K3b</application>, also includes this capability.
-	</para>
-	<procedure>
-		<step>
-			<para>
-				Insert a blank, writeable CD into your computer's CD or DVD burner. On some computers, a window opens and displays various options when you insert the disc. If you see a window like this, look for an option to launch your chosen disc burning program. If you do not see an option like this, close the window and launch the program manually.
-			</para>
-		</step>
-		<step>
-			<para>
-				Launch your disc burning program. On some computers, you can do this by right-clicking (or control-clicking) on the image file and selecting a menu option with a label like <guilabel>Copy image to CD</guilabel>, or <guilabel>Copy CD or DVD image</guilabel>. Other computers might provide you with a menu option to launch your chosen disc burning program, either directly or with an option like <guimenuitem>Open With</guimenuitem>. If none of these options are available on your computer, launch the program from an icon on your desktop, in a menu of applications such as the <guimenu>Start</guimenu> menu on Windows operating systems, or in the Mac <filename>Applications</filename> folder.
-			</para>
-		</step>
-		<step>
-			<para>
-				In your disc burning program, select the option to burn a CD from an image file. For example, in <application>Nero Burning ROM</application>, this option is called <guimenuitem>Burn Image</guimenuitem> and is located on the <guimenu>File</guimenu> menu.
-			</para>
-			<para>
-				Note that you can skip this step when using certain CD burning software; for example, <application>Disk Utility</application> on Mac OS&nbsp;X does not require it.
-			</para>
-		</step>
-		<step>
-			<para>
-				Browse to the ISO CD image file that you downloaded previously and select it for burning.
-			</para>
-		</step>
-		<step>
-			<para>
-				Click the button that starts the burning process.
-			</para>
-		</step>
-	</procedure>
-<!-- end of text from Burn_the_image_file_to_CD.xml in the Fedora Installation Quick Start Guide -->
-
-	<para>
-		For more detail, including step-by-step instructions for various popular disc burning applications, refer to <citetitle>Making Fedora Discs</citetitle> available from <ulink url="http://docs.fedoraproject.org/readme-burning-isos/">http://docs.fedoraproject.org/readme-burning-isos/</ulink>
-	</para>
-    </section>
-
-<xi:include href="Making_USB_media.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include>    
-</chapter>
diff --git a/en-US/Making_USB_media.xml b/en-US/Making_USB_media.xml
deleted file mode 100644
index 31ecb48..0000000
--- a/en-US/Making_USB_media.xml
+++ /dev/null
@@ -1,282 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
-"http://www.docbook.org/xml/4.4/docbookx.dtd" [
-]>
-
-<section id="Making_USB_Media">
-	<title>Making USB Media</title>
-	<important>
-		<title>Btrfs</title>
-		<para>
-			The <application>GRUB</application> bootloader does not support the Btrfs file system. You cannot create bootable USB media on media formatted as Btrfs. 
-		</para>
-	</important>
-	<important>
-		<title>Unusual USB Media</title>
-		<para>
-			In a few cases with oddly formatted or partitioned USB media, image writing may fail.
-		</para>
-	</important>
-	<para>
-		USB media often comes in the form of flash devices sometimes called <firstterm>pen drives</firstterm>, <firstterm>thumb disks</firstterm>, or <firstterm>keys</firstterm>; or as an externally connected hard disk device.  Almost all media of this type is formatted as a vfat file system.  You can create bootable USB media on media formatted as ext2, ext3, or vfat.
-	</para>
-	<para>
-		  You can transfer a distribution image file, a live image file, or a minimal boot media image file to USB media. Make sure that sufficient free space is available on the device. You require around 4&nbsp;GB for a distribution DVD image, around 700&nbsp;MB for a live image or around 200&nbsp;MB for a minimal boot media image.
-	</para>
-	
-	<section id="Making_USB_Media-Windows">
-		<title>Making Fedora USB Media on a Windows Operating System</title>
-		<xi:include href="Note_Nondestructive_Method.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include>
-		<para>
-			The most straightforward way to place a Fedora image on USB media using a Windows operating system is to transfer the Fedora live image to the USB device with the <application>LiveUSB Creator</application> tool.
-		</para>
-		<para>
-			Note that the <application>dd</application> tool discussed in <xref linkend="Making_USB_Media-UNIX_Linux"/> is also available for Windows. Follow the instructions in that section to use an implementation of <application>dd</application> for Windows operating systems. The instructions in this section assume that you will use <application>LiveUSB Creator</application>.
-		</para>
-		<procedure>
-			<step>
-				<para>
-					Download the <application>LiveUSB Creator</application> program for Windows from <ulink url="http://fedorahosted.org/liveusb-creator"/>.
-				</para>
-			</step>
-			<step>
-				<para>
-					<application>LiveUSB Creator</application> can create live USB media either from an image file that you downloaded previously, as described in <xref linkend="sn-which-files"/>, or it can download an image file from the Internet. Either: 
-				</para>
-				<itemizedlist>
-					<listitem>
-						<para>
-							click the <guibutton>Browse</guibutton> button under the <guilabel>Use existing LiveCD</guilabel> label, browse to the location where you previously downloaded a Fedora Live ISO file, and select that file.
-						</para>
-					</listitem>
-					<listitem>
-						<para>
-							select a Fedora Live ISO file from the drop-down menu that <application>LiveUSB Creator</application> presents under the <guilabel>Download Fedora</guilabel> label. Note that image files are large and that it is probably impractical to use <application>LiveUSB Creator</application> to download an image file if you do not have a broadband connection to the Internet. 
-						</para>
-					</listitem>
-				</itemizedlist>
-			</step>
-			<step>
-				<para>
-					Click <guibutton>Create Live USB</guibutton>.
-				</para>
-			</step>
-		</procedure>
-	</section>
-	<section id="Making_USB_Media-UNIX_Linux">
-		<title>Making Fedora USB Media in UNIX, Linux, and Similar Operating Systems</title>
-		<para>
-			A graphical tool is available to create Fedora USB media on systems that run Fedora, Red Hat Enterprise Linux, or operating systems derived from either of these. To create Fedora USB media on other UNIX or Linux operating systems (including Mac&nbsp;OS&nbsp;X), use the command-line method described in <xref linkend="Making_USB_Media-UNIX_Linux-RHEL_Fedora-dd"/>.
-		</para>
-		<section id="Making_USB_Media-UNIX_Linux-RHEL_Fedora">
-			<title>Creating Fedora USB Media in Fedora, Red Hat Enterprise Linux, and similar Linux distributions</title>
-			<para>
-				Graphical and command-line tools are available to create Fedora USB media on computers that run Fedora, Red Hat Enterprise Linux, and Linux distributions derived from Red Hat Enterprise Linux. The graphical tool and the works only with the Fedora live image. To create Fedora USB media from the distribution image or minimal boot media image, use the command-line method described in <xref linkend="Making_USB_Media-UNIX_Linux-RHEL_Fedora-dd"/>.
-			</para>
-			<section id="Making_USB_Media-UNIX_Linux-RHEL_Fedora-graphical">
-				<title>Making Fedora USB Media with a graphical tool</title>
-				<xi:include href="Important-Enable_EPEL.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include>
-				<xi:include href="Note_Nondestructive_Method.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include>
-				<procedure>
-					<step>
-						<para>
-							Install the <package>liveusb-creator</package> on your system with your graphical package manager, or the following command:
-						</para>
-<screen><![CDATA[su -c 'yum -y install liveusb-creator']]></screen>
-					</step>
-					<step>
-						<para>
-							Plug in your USB media.
-						</para>
-					</step>
-					<step>
-						<para>
-							Launch <application>LiveUSB Creator</application>, either from a menu or by entering <command>liveusb-creator</command> on the command line. Enter the root password for your system when <application>LiveUSB Creator</application> prompts you for it.
-						</para>
-					</step>
-					<step>
-						<para>
-							<application>LiveUSB Creator</application> can create live USB media either from an image file that you downloaded previously, as described in <xref linkend="sn-which-files"/>, or it can download an image file from the Internet. Either: 
-						</para>
-						<itemizedlist>
-							<listitem>
-								<para>
-									click the <guibutton>Browse</guibutton> button under the <guilabel>Use existing LiveCD</guilabel> label, browse to the location where you previously downloaded a Fedora Live ISO file, and select that file.
-								</para>
-							</listitem>
-							<listitem>
-								<para>
-									select a Fedora Live ISO file from the drop-down menu that <application>LiveUSB Creator</application> presents under the <guilabel>Download Fedora</guilabel> label. Note that image files are large and that it is probably impractical to use <application>LiveUSB Creator</application> to download an image file if you do not have a broadband connection to the Internet. 
-								</para>
-							</listitem>
-						</itemizedlist>
-					</step>
-					<step>
-						<para>
-							Click <guibutton>Create Live USB</guibutton>.
-						</para>
-					</step>
-				</procedure>
-			</section>
-			<section id="Making_USB_Media-UNIX_Linux-RHEL_Fedora-livecd-tools">
-				<title>Making Fedora USB Media with <application>livecd-tools</application></title>
-				<xi:include href="Important-Enable_EPEL.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include>
-				<xi:include href="Note_Nondestructive_Method.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include>
-				<procedure>
-					<step>
-						<para>
-							Install the <package>livecd-tools</package> package on your system with your graphical package manager, or the following command:
-						</para>
-<screen><![CDATA[su -c 'yum -y install livecd-tools']]></screen>
-					</step>
-					<step>
-						<para>
-							Plug in your USB media.
-						</para>
-					</step>
-					<step>
-						<para>
-							Find the device name for your USB media.  If the media has a volume name, look up the name in <filename class="directory">/dev/disk/by-label</filename>, or use the <command>findfs</command>:
-						</para>
-<screen><![CDATA[su -c 'findfs LABEL="]]><replaceable>MyLabel</replaceable><![CDATA["']]></screen>
-						<para>
-							If the media does not have a volume name, or you do not know it, consult the <filename>/var/log/messages</filename> log for details:
-						</para>
-<screen><![CDATA[su -c 'less /var/log/messages']]></screen>
-					</step>
-					<step>
-						<para>
-							Use the <command>livecd-iso-to-disk</command> command to write the ISO image to the media:
-						</para>
-<screen><![CDATA[su -c 'livecd-iso-to-disk ]]><replaceable>the_image.iso</replaceable><![CDATA[ /dev/]]><replaceable>sdX1</replaceable><![CDATA[']]></screen>
-						<para>
-							Replace <replaceable>sdX1</replaceable> with the device name for the partition on the USB media.  Most flash drives and external hard disks use only one partition.  If you have changed this behavior or have oddly partitioned media, you may need to consult other sources of help.
-						</para>
-					</step>
-				</procedure>
-			</section>
-			<section id="Making_USB_Media-UNIX_Linux-RHEL_Fedora-dd">
-				<title>Making Fedora USB Media with <application>dd</application></title>
-				<xi:include href="DU-Preparing_a_driver_update_disk_ppc_x86-warning-1.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include>
-				<xi:include href="Procedure-dd_Image_to_USB.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include>
-			</section>
-		</section>
-		<section id="Making_USB_Media-UNIX_Linux-other">
-			<title>Making Fedora USB Media in other Linux Distributions</title>
-			<para>
-				To create Fedora USB media on a computer that uses a Linux distribution other than Fedora, Red Hat Enterprise Linux, and those derived from Red Hat Enterprise Linux, use one of the command-line procedures detailed in this section. 
-			</para>
-			<section id="Making_USB_Media-UNIX_Linux-other_livecd-tools">
-				<title>Making Fedora USB Media with <application>livecd-tools</application></title>
-				<xi:include href="Note_Nondestructive_Method.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include>
-				<para>
-					This method works only with the Fedora live image, and only on Linux operating systems. 
-				</para>
-				<procedure>
-					<step>
-						<para>
-							Download a live ISO file for Fedora as shown in <xref linkend="sn-which-files"/>
-						</para>
-					</step>
-					<step>
-						<para>
-							Plug in your USB media.
-						</para>
-					</step>
-					<step>
-						<para>
-							Find the device name for your USB media.  If the media has a volume name, look up the name in <filename class="directory">/dev/disk/by-label</filename>, or use the <command>findfs</command>:
-						</para>
-<screen><![CDATA[su -c 'findfs LABEL="]]><replaceable>MyLabel</replaceable><![CDATA["']]></screen>
-						<para>
-							If the media does not have a volume name, or you do not know it, consult the <filename>/var/log/messages</filename> log for details:
-						</para>
-<screen><![CDATA[su -c 'less /var/log/messages']]></screen>
-					</step>
-					<step>
-						<para>
-							Many Linux distributions automatically <firstterm>mount</firstterm> USB media devices when you connect the device to your computer. If this is the case, unmount the device. The specific method to do this varies widely between Linux distributions and desktops. Some common methods include:
-						</para>
-						<itemizedlist>
-							<listitem>
-								<para>
-									select <guilabel>File &gt; Unmount</guilabel> if the operating system presents you with a window that displays the contents of the device.
-								</para>
-							</listitem>
-							<listitem>
-								<para>
-									right-click on an icon of the device and click <guilabel>Unmount</guilabel>.
-								</para>
-							</listitem>
-							<listitem>
-								<para>
-									click on an icon that represents ejecting the media &mdash; commonly, an upward-pointing triangle.
-								</para>
-							</listitem>
-						</itemizedlist>
-					</step>
-					<step>
-						<para>
-							At a command line, type <command>su -</command> to become root, and enter the root password when your system prompts you. 
-						</para>
-					</step>
-					<step>
-						<para>
-							Create a <firstterm>mount point</firstterm> for the live image that you downloaded. For example, to use <filename>/tmp/livecd</filename> as the mount point, type <command>mkdir /tmp/livecd</command> and press <keycap>Enter</keycap>.
-						</para>
-					</step>
-					<step>
-						<para>
-							Mount the live image with the following command: <command>mount -o loop <replaceable>/path/to/image/file/imagefile.iso</replaceable> <replaceable>/path/to/mount/point</replaceable></command>, where <replaceable>/path/to/image/file</replaceable> is the location of the image file that you downloaded, <filename>imagefile.iso</filename> is the image file, and <replaceable>/path/to/mount/point</replaceable> is the mount point that you just created.
-						</para>
-					</step>
-					<step>
-						<para>
-							Change directory to the <filename>LiveOS</filename> directory of the image that you just mounted. mount point where you just mounted the Fedora live image. For example, <command>cd /tmp/livecd/LiveOS</command>.
-						</para>
-					</step>
-					<step>
-						<para>
-							Run the following command: <command>./livecd-iso-to-disk <replaceable>/path/to/image/file/imagefile.iso</replaceable> <replaceable>device</replaceable></command>, where <filename><replaceable>/path/to/image/file</replaceable></filename> is the location of the image file that you downloaded, <filename><replaceable>imagefile.iso</replaceable></filename> is the image file, and <filename><replaceable>device</replaceable></filename> is the USB media device.
-						</para>
-						
-					</step>
-				</procedure>
-				<example>
-					<title>Mounting a Fedora live image file and using livecd-iso-to-disk to create live USB media</title>
-					<para>
-						You have downloaded a Fedora live image, <filename>Fedora-&PRODVER;-i686-Live.iso</filename>, to a folder named <filename>Downloads</filename> in your home directory. You have a USB flash drive plugged into your computer, named <filename>/dev/sdc1</filename>
-					</para>
-					<para>
-						Become root:
-					</para>
-<screen>su -</screen>
-					<para>
-						Make a mount point for the image:
-					</para>
-<screen>mkdir /mnt/livecd</screen>
-					<para>
-						Mount the image:
-					</para>
-<screen>mount -o loop /home/<replaceable>Username</replaceable>/Downloads/Fedora-&PRODVER;-i686-Live.iso /mnt/livecd</screen>
-					<para>
-						Change into the <filename>LiveOS</filename> directory of the live CD image:
-					</para>
-<screen>cd /mnt/livecd/LiveOS</screen>
-					<para>
-						Run <application>livecd-iso-to-disk</application> to transfer the live image to your flash drive and make the flash drive bootable:
-					</para>
-<screen>./livecd-iso-to-disk /home/<replaceable>Username</replaceable>/Downloads/Fedora-&PRODVER;-i686-Live.iso /dev/sdc1</screen>
-				</example>
-			</section>
-			<section id="Making_USB_Media-UNIX_Linux-other-dd">
-				<title>Making Fedora USB Media with <application>dd</application></title>
-				<xi:include href="DU-Preparing_a_driver_update_disk_ppc_x86-warning-1.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include>
-				<para>
-					Use this method for the distribution image, the minimal boot media image, or on systems with a UNIX operating system (including Mac&nbsp;OX&nbsp;X).
-				</para>
-				<xi:include href="Procedure-dd_Image_to_USB.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include>
-			</section>
-		</section>
-	</section>  
-</section>
diff --git a/en-US/Netboot_DHCP.xml b/en-US/Netboot_DHCP.xml
deleted file mode 100644
index 7f94507..0000000
--- a/en-US/Netboot_DHCP.xml
+++ /dev/null
@@ -1,37 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-	<section>
-		<title>Configuring the DHCP Server</title>
-<indexterm significance="normal">
-	<primary>DHCP</primary>
-	<secondary>PXE installations</secondary>
-</indexterm>
-
-<indexterm significance="normal">
-	<primary>DHCP</primary>
-	<secondary>diskless environment</secondary>
-</indexterm>
-
-<indexterm significance="normal">
-	<primary>PXE installations</primary>
-	<secondary>DHCP configuration</secondary>
-</indexterm>
-
-<indexterm significance="normal">
-	<primary>diskless environment</primary>
-	<secondary>DHCP configuration</secondary>
-</indexterm>
-
-<para>
-	If a DHCP server does not already exist on the network, configure one. Refer to the Red Hat Enterprise Linux Deployment Guide for details. Make sure the configuration file contains the following so that PXE booting is enabled for systems which support it:
-</para>
-
-
-<programlisting>allow booting; allow bootp; class "pxeclients" {    match if substring(option vendor-class-identifier, 0, 9) = "PXEClient";    next-server <replaceable>&lt;server-ip&gt;</replaceable>; filename "linux-install/pxelinux.0"; }</programlisting>
-
-
-<para>
-	where the next-server <replaceable>&lt;server-ip&gt;</replaceable> should be replaced with the IP address of the <command>tftp</command> server.
-</para>
-</section>
\ No newline at end of file
diff --git a/en-US/Netboot_TFTP.xml b/en-US/Netboot_TFTP.xml
deleted file mode 100644
index 58f2a72..0000000
--- a/en-US/Netboot_TFTP.xml
+++ /dev/null
@@ -1,27 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-	<section>
-		<title>Starting the <command>tftp</command> Server</title>
-<indexterm significance="normal">
-	<primary><command>tftp</command>
-	</primary>
-</indexterm>
-
-<para>
-	On the DHCP server, verify that the <filename>tftp-server</filename> package is installed with the command <command>rpm -q tftp-server</command>. <!-- If it is not installed, install it via Red Hat Network or the &PROD; CD-ROMs. <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="note_Installing_Packages.xml"/> -->
-</para>
-
-<para>
-	<command>tftp</command> is an xinetd-based service; start it with the following commands:
-</para>
-
-<screen>
-<command>/sbin/chkconfig --level 345 xinetd on </command>
-<command>/sbin/chkconfig --level 345 tftp on</command>
-</screen>
-
-<para>
-	These commands configure the <command>tftp</command> and <command>xinetd</command> services to immediately turn on and also configure them to start at boot time in runlevels 3, 4, and 5.
-</para>
-</section>
diff --git a/en-US/Netconfig_common-figure-2.xml b/en-US/Netconfig_common-figure-2.xml
deleted file mode 100644
index 8d55bbb..0000000
--- a/en-US/Netconfig_common-figure-2.xml
+++ /dev/null
@@ -1,16 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
- "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
-]>
-
-<figure float="0" >
-	<title>Enable Network Interface</title>
-	<mediaobject>
-		<imageobject><imagedata fileref="images/netconfig/net-edit.png" format="PNG"/></imageobject>
-		<textobject><para>
-				Enable Network Interface
-			</para>
-		</textobject>
-	</mediaobject>
-</figure>
-
diff --git a/en-US/Netconfig_common-para-7.xml b/en-US/Netconfig_common-para-7.xml
deleted file mode 100644
index 44ee0ab..0000000
--- a/en-US/Netconfig_common-para-7.xml
+++ /dev/null
@@ -1,9 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
- "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
-]>
-
-<para>
-	Use this dialog to configure the network interfaces through which the system will connect to networked storage devices. 
-</para>
-
diff --git a/en-US/Netconfig_common-para-8.xml b/en-US/Netconfig_common-para-8.xml
deleted file mode 100644
index e74b401..0000000
--- a/en-US/Netconfig_common-para-8.xml
+++ /dev/null
@@ -1,9 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
- "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
-]>
-
-<para>
-	If your network does not have DHCP enabled, or if you need to override the DHCP settings, select the network interface that you plan to use from the <guilabel>Interfaces</guilabel> menu. Clear the checkbox for <guilabel>Use dynamic IP configuration (DHCP)</guilabel>. You can now enter an IPv4 address and netmask for this system in the form <replaceable>address</replaceable>&nbsp;/&nbsp;<replaceable>netmask</replaceable>, along with the gateway address and nameserver address for your network. 
-</para>
-
diff --git a/en-US/Netconfig_common-para-9.xml b/en-US/Netconfig_common-para-9.xml
deleted file mode 100644
index bfda3d4..0000000
--- a/en-US/Netconfig_common-para-9.xml
+++ /dev/null
@@ -1,9 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
- "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
-]>
-
-<para>
-	Click <guilabel>OK</guilabel> to accept these settings and continue.
-</para>
-
diff --git a/en-US/Netconfig_common-title-2.xml b/en-US/Netconfig_common-title-2.xml
deleted file mode 100644
index b374ddc..0000000
--- a/en-US/Netconfig_common-title-2.xml
+++ /dev/null
@@ -1,7 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
- "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
-]>
-
-<title>Enable Network Interfaces</title>
-
diff --git a/en-US/Note-Multiple_NICs_and_PXE.xml b/en-US/Note-Multiple_NICs_and_PXE.xml
deleted file mode 100644
index 53242be..0000000
--- a/en-US/Note-Multiple_NICs_and_PXE.xml
+++ /dev/null
@@ -1,21 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
- "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd">
-
-<note>
-	<title>Note â€” Multiple NICs and PXE installation </title>
-	<para>
-		Some servers with multiple network interfaces might not assign eth0 to the first network interface as the firmware interface knows it, which can cause the installer to try to use a different network interface from the one that was used by PXE. To change this behavior, use the following in <filename>pxelinux.cfg/*</filename> config files: 
-	</para>
-<programlisting>IPAPPEND 2
-APPEND ksdevice=bootif</programlisting>
-	<para>
-	These configuration options above cause the installer to use the same network interface the firmware interface and PXE use. You can also use the following option: 
-	</para>
-<programlisting>ksdevice=link</programlisting>
-	<para>
-		This option causes the installer to use the first network device it finds that is linked to a network switch. 
-	</para>
-</note>
-
-
diff --git a/en-US/Note_Aborting_Installation.xml b/en-US/Note_Aborting_Installation.xml
deleted file mode 100644
index 38bed17..0000000
--- a/en-US/Note_Aborting_Installation.xml
+++ /dev/null
@@ -1,11 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
- "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd">
-
-<note>
-<title>Note â€” Aborting the Installation</title>
-      <para>
-	    To abort the installation, either press <keycombo><keycap>Ctrl </keycap><keycap>Alt</keycap><keycap>Del</keycap></keycombo> or power off your computer with the power switch. You may abort the installation process without consequence at any time prior to selecting <guibutton>Write changes to disk</guibutton> on the <guilabel>Write partitioning to disk</guilabel> screen. Fedora makes no permanent changes to your computer until that point. Please be aware that stopping the installation after partitioning has begun can leave your computer unusable.
-      </para>
-</note>
-
diff --git a/en-US/Note_Nondestructive_Method.xml b/en-US/Note_Nondestructive_Method.xml
deleted file mode 100644
index a7ddfe1..0000000
--- a/en-US/Note_Nondestructive_Method.xml
+++ /dev/null
@@ -1,11 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-<!DOCTYPE note PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
- "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
-]>
-
-<note>
-	<title>Note â€” This Method Is Not Destructive</title>
-	<para>
-		This method is not destructive, so existing data on the media is not harmed. Nevertheless, it is always a good idea to back up important data before performing sensitive disk operations.
-	</para>
-</note>
diff --git a/en-US/Other_Disk_Devices-common-note-1.xml b/en-US/Other_Disk_Devices-common-note-1.xml
deleted file mode 100644
index 8912d4d..0000000
--- a/en-US/Other_Disk_Devices-common-note-1.xml
+++ /dev/null
@@ -1,10 +0,0 @@
-<!DOCTYPE note PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
- "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd">
-
-
-<note>
-	<title>Post-installation Usage</title>
-	<para>
-		You can connect and configure external FireWire and USB hard disks after installation.  Most such devices are recognized by the kernel and available for use at that time.
-	</para>
-</note>
diff --git a/en-US/Other_Disk_Devices-common-para-1.xml b/en-US/Other_Disk_Devices-common-para-1.xml
deleted file mode 100644
index e688028..0000000
--- a/en-US/Other_Disk_Devices-common-para-1.xml
+++ /dev/null
@@ -1,7 +0,0 @@
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
- "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd">
-
-
-<para>
-	RAID, or Redundant Array of Independent Disks, allows a group, or array, of drives to act as a single device. Configure any RAID functions provided by the mainboard of your computer, or attached controller cards, before you begin the installation process. Each active RAID array appears as one drive within Fedora.
-</para>
diff --git a/en-US/Other_Disk_Devices-common-para-2.xml b/en-US/Other_Disk_Devices-common-para-2.xml
deleted file mode 100644
index fac0cb8..0000000
--- a/en-US/Other_Disk_Devices-common-para-2.xml
+++ /dev/null
@@ -1,8 +0,0 @@
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
- "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd">
-
-
-<para>
-	On systems with more than one hard drive you may configure Fedora to operate several of the drives as a Linux RAID array without requiring any additional hardware.
-</para>
-
diff --git a/en-US/Other_Disk_Devices-common-para-3.xml b/en-US/Other_Disk_Devices-common-para-3.xml
deleted file mode 100644
index a8fc7cf..0000000
--- a/en-US/Other_Disk_Devices-common-para-3.xml
+++ /dev/null
@@ -1,7 +0,0 @@
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
- "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd">
-
-
-<para>
-	Some FireWire and USB hard disks may not be recognized by the Fedora installation system.  If configuration of these disks at installation time is not vital, disconnect them to avoid any confusion.
-</para>
diff --git a/en-US/Other_Disk_Devices-common-title-1.xml b/en-US/Other_Disk_Devices-common-title-1.xml
deleted file mode 100644
index 6daaf58..0000000
--- a/en-US/Other_Disk_Devices-common-title-1.xml
+++ /dev/null
@@ -1,7 +0,0 @@
-<!DOCTYPE title PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
- "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd">
-
-
-<title>
-	RAID and Other Disk Devices
-</title>
diff --git a/en-US/Other_Disk_Devices-common-title-2.xml b/en-US/Other_Disk_Devices-common-title-2.xml
deleted file mode 100644
index c3e1260..0000000
--- a/en-US/Other_Disk_Devices-common-title-2.xml
+++ /dev/null
@@ -1,7 +0,0 @@
-<!DOCTYPE title PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
- "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd">
-
-
-<title>
-	Hardware RAID
-</title>
diff --git a/en-US/Other_Disk_Devices-common-title-3.xml b/en-US/Other_Disk_Devices-common-title-3.xml
deleted file mode 100644
index 34aa71d..0000000
--- a/en-US/Other_Disk_Devices-common-title-3.xml
+++ /dev/null
@@ -1,7 +0,0 @@
-<!DOCTYPE title PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
- "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd">
-
-
-<title>
-	Software RAID
-</title>
diff --git a/en-US/Other_Disk_Devices-common-title-4.xml b/en-US/Other_Disk_Devices-common-title-4.xml
deleted file mode 100644
index b7024cb..0000000
--- a/en-US/Other_Disk_Devices-common-title-4.xml
+++ /dev/null
@@ -1,7 +0,0 @@
-<!DOCTYPE title PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
- "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd">
-
-
-<title>
-	FireWire and USB Disks
-</title>
diff --git a/en-US/Other_Disk_Devices-x86.xml b/en-US/Other_Disk_Devices-x86.xml
deleted file mode 100644
index 0b1bbad..0000000
--- a/en-US/Other_Disk_Devices-x86.xml
+++ /dev/null
@@ -1,57 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-
-<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
- "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd">
-
-<section id="sn-partitioning-raid-x86">
-
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Other_Disk_Devices-common-title-1.xml"/>
-	<!-- RAID and Other Disk Devices -->
-    
-    	<!-- Index terms -->
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Disk_Partitioning_Setup_common-indexterm-6.xml"/>
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Disk_Partitioning_Setup_common-indexterm-7.xml"/>
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Disk_Partitioning_Setup_common-indexterm-8.xml"/>
-	<!-- End Index terms -->
-
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Systems_with_Intel_BIOS_RAID.xml"/>
-	
-	<section id="sn-partitioning-raid-hw-x86">
-	
-		<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Other_Disk_Devices-common-title-2.xml"/>
-		<!-- Hardware RAID -->
-		
-		<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Other_Disk_Devices-common-para-1.xml"/>
-		<!-- RAID, or Redundant Array of Independent Disks, allows a group, or array, of drives... -->
-		
-		<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Other_Disk_Devices-common-para-2.xml"/>
-		<!-- On systems with more than one hard drive you may configure Fedora... -->
-
-	</section>
-    
-    
-	<section id="sn-partitioning-raid-sw-x86">
-	
-		<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Other_Disk_Devices-common-title-3.xml"/>
-		<!-- Software RAID -->
-		
-		<para>
-			You can use the Fedora installation program to create Linux software RAID arrays, where RAID functions are controlled by the operating system rather than dedicated hardware.  These functions are explained in detail in <xref linkend="s1-diskpartitioning-x86"/>.
-		</para>
-	
-	</section>
-	
-	<section id="sn-partitioning-fw-usb-x86">
-		
-		<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Other_Disk_Devices-common-title-4.xml"/>
-		<!-- FireWire and USB Disks -->
-		
-		<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Other_Disk_Devices-common-para-3.xml"/>
-		<!-- Some FireWire and USB hard disks may not be recognized by the Red Hat Enterprise Linux installation system. -->
-		
-		<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Other_Disk_Devices-common-note-1.xml"/>
-		<!-- Post-installation Usage -->
-		
-	</section>
-</section>
-
diff --git a/en-US/Package_Selection-x86.xml b/en-US/Package_Selection-x86.xml
deleted file mode 100644
index 41e8416..0000000
--- a/en-US/Package_Selection-x86.xml
+++ /dev/null
@@ -1,90 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<section id="s1-pkgselection-x86">
-
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Package_Selection_common-title-1.xml"/>
-	<!-- Package Group Selection -->
-	
-	<!-- Begin Index terms -->
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Package_Selection_common-indexterm-1.xml"/>
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Package_Selection_common-indexterm-2.xml"/>
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Package_Selection_common-indexterm-3.xml"/>
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Package_Selection_common-indexterm-4.xml"/>
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Package_Selection_common-indexterm-5.xml"/>
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Package_Selection_common-indexterm-6.xml"/>
-	<!-- End Index terms -->
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Package_Selection_common-para-1.xml"/>
-	<!-- Now that you have made most of the choices.. -->
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Package_Selection_common-para-2.xml"/>
-	<!-- The Package Installation Defaults screen... -->
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Package_Selection_common-note-1.xml"/>
-	<!-- Installing from a Live Image -->
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Package_Selection_common-note-2.xml"/>
-	<!-- Installing in text mode -->
-
-	<figure float="0" id="fig-pkgselection-group-x86"><title>Package Group Selection</title>
-		<mediaobject>
-			<imageobject><imagedata fileref="images/pkgselection/pkg-group.png" format="PNG"/></imageobject>
-			<textobject>
-				<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Package_Selection_common-imagecap-1.xml"/>
-				<!-- Choose which package groups you want to install. -->
-			</textobject>
-		</mediaobject>
-	</figure>
-
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Package_Selection_common-para-7.xml"/>
-	<!-- By default, the Fedora Installation process loads... -->
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Package_Selection_common-list-1.xml"/>
-	<!-- Office and Productivity
-	Software Development
-	Web server -->
-	
-	<para>
-		If you choose to accept the current package list, skip ahead to <xref linkend="s1-installpkgs-x86"/>.
-	</para>
-
-	<para>
-		To select a component, click on the checkbox beside it (refer to <xref linkend="fig-pkgselection-group-x86"/>).
-	</para>
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Package_Selection_common-para-3.xml"/>
-	<!-- To customize your package set further, select... -->
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Package_Selection_Repositories-x86.xml"/>
-	<!-- You can define additional repositories to increase the software... -->
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Package_Selection_Customizing-x86.xml"/>
-	<!-- Select Customize now to specify the software packages for your final... -->
-	
-<!-- 	<note>
-		<title>Note</title>
-		
-		<para>
-			Users of Itanium systems who want support for developing or running 32-bit applications are encouraged to select the <guilabel>Compatibility Arch Support</guilabel> and
-			<guilabel>Compatibility Arch Development Support</guilabel> packages to install architecure specific support for their systems.
-		</para>
-	</note> -->
-<!--	BZ#250601, above replaces below:	
-		<para>
-			Users of AMD64, <trademark class="registered">Intel</trademark> 64, and Itanium systems who want support for developing or running 32-bit applications are encouraged to select the <guilabel>Compatibility Arch Support</guilabel> and
-			<guilabel>Compatibility Arch Development Support</guilabel> packages to install architecure specific support for their systems.
-		</para>-->
-
-	
-
-	
-	
-<!--	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Package_Selection_common-para-5.xml"/> -->
-	<!-- Select each component you wish to install. Selecting... -->
-	
-<!-- 	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Package_Selection_common-para-6.xml"/> -->
-	<!-- Once a package group has been selected, click on... -->
-	
-</section>
diff --git a/en-US/Package_Selection_Customizing-x86.xml b/en-US/Package_Selection_Customizing-x86.xml
deleted file mode 100644
index e3ec488..0000000
--- a/en-US/Package_Selection_Customizing-x86.xml
+++ /dev/null
@@ -1,186 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-
-<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
- "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
-]>
-
-  <section id="sn-package-selection-x86">
-    <title>Customizing the Software Selection</title>
-    <para>
-      Select <guilabel>Customize now</guilabel> to specify the software
-      packages for your final system in more detail. This option causes
-      the installation process to display an additional customization
-      screen when you select <guibutton>Next</guibutton>.
-    </para>
-    <note>
-      <title>Installing Support for Additional Languages</title>
-
-      <para>
-      Select <guilabel>Customize now</guilabel> to install support for
-	additional languages. Refer to <xref
-	  linkend="sn-lang-packages"/> for more information on
-	configuring language support.
-      </para>
-    </note>
-
-	<figure float="0" id="fig-pkgselection-details-x86"><title>Package Group Details</title>
-		<mediaobject>
-			<imageobject><imagedata fileref="images/pkgselection/pkg-group-details.png" format="PNG"/></imageobject>
-			<textobject>
-				<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Package_Selection_common-imagecap-2.xml"/>
-				<!-- Choose to add or remove optional packages from this package group. -->
-			</textobject>
-		</mediaobject>
-	</figure>
-
-
-    <para>
-      Fedora divides the included software into
-      <indexterm>
-        <primary>package groups</primary>
-      </indexterm> <firstterm>package groups</firstterm>. For ease of
-      use, the package selection screen displays these groups as
-      categories.
-    </para>
-
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Package_Selection_common-para-4.xml"/>
-	<!-- You can select package groups, which group components... -->
-
-    <para>
-      To view the package groups for a category, select the category
-      from the list on the left. The list on the right displays the
-      package groups for the currently selected category.
-    </para>
-
-    <para>
-      To specify a package group for installation, select the check box
-      next to the group. The box at the bottom of the screen displays
-      the details of the package group that is currently highlighted.
-      <emphasis>None</emphasis> of the packages from a group will be
-      installed unless the check box for that group is selected.
-    </para>
-
-    <para>
-      If you select a package group, Fedora automatically installs the
-      base and mandatory packages for that group. To change which
-      optional packages within a selected group will be installed,
-      select the <guibutton>Optional Packages</guibutton> button under
-      the description of the group. Then use the check box next to an
-      individual package name to change its selection.
-    </para>
-    <para>
-      After you choose the desired packages, select
-      <guilabel>Next</guilabel> to proceed. Fedora checks your selection,
-      and automatically adds any extra packages required to use the
-      software you select. When you have finished selecting packages, click
-		<guilabel>Close</guilabel> to save your optional package selections and 
-		return to the main package 
-		selection screen.
-    </para>
-    <section id="sn-changing-selection">
-      <title>Changing Your Mind</title>
-      <para>
-	The packages that you select are not permanent. After you boot
-	your system, use the <application>Add/Remove Software</application> tool to
-	either install new software or remove installed packages. To run
-	this tool, from the main menu, select <menuchoice>
-	  <guimenu>System</guimenu>
-	  <guisubmenu>Administration</guisubmenu>
-	  <guimenuitem>Add/Remove Software</guimenuitem>
-	</menuchoice>. The Fedora software management system downloads
-	the latest packages from network servers, rather than using
-	those on the installation discs.
-      </para>
-    </section>
-    <section id="sn-lang-packages">
-      <title>Additional Language Support</title>
-
-      <para>
-	Your Fedora system automatically supports the language that you
-	selected at the start of the installation process. To include
-	support for additional languages, select the package group for
-	those languages from the <guilabel>Languages</guilabel>
-	category.
-      </para>
-
-    </section>
-    <section id="sn-mandatory-services">
-      <title>Core Network Services</title>
-
-      <para>
-	All Fedora installations include the following network
-	services:
-      </para>
-
-      <itemizedlist>
-	<listitem>
-	  <para>
-	    centralized logging through syslog
-	  </para>
-	</listitem>
-	<listitem>
-	  <para>
-	    email through SMTP (Simple Mail Transfer Protocol)
-	  </para>
-	</listitem>
-	<listitem>
-	  <para>
-	    network file sharing through NFS (Network File System)
-	  </para>
-	</listitem>
-	<listitem>
-	  <para>
-	    remote access through SSH (Secure SHell)
-	  </para>
-	</listitem>
-	<listitem>
-	  <para>
-	    resource advertising through mDNS (multicast DNS)
-	  </para>
-	</listitem>
-      </itemizedlist>
-
-      <para>
-	The default installation also provides:
-      </para>
-
-      <itemizedlist>
-	<listitem>
-	  <para>
-	    network file transfer through HTTP (HyperText Transfer
-	    Protocol)
-	  </para>
-	</listitem>
-	<listitem>
-	  <para>
-	    printing through CUPS (Common UNIX Printing System)
-	  </para>
-	</listitem>
-	<listitem>
-	  <para>
-	    remote desktop access through VNC (Virtual Network
-	    Computing)
-	  </para>
-	</listitem>
-      </itemizedlist>
-
-      <para>
-	Some automated processes on your Fedora system use the email
-	service to send reports and messages to the system
-	administrator. By default, the email, logging, and printing
-	services do not accept connections from other systems. Fedora
-	installs the NFS sharing, HTTP, and VNC components without
-	enabling those services.
-      </para>
-
-      <para>
-	You may configure your Fedora system after installation to offer
-	email, file sharing, logging, printing and remote desktop access
-	services. The SSH service is enabled by default. You may use NFS
-	to access files on other systems without enabling the NFS
-	sharing service.
-      </para>
-    </section>
-  </section>
-
-
diff --git a/en-US/Package_Selection_Repositories-x86.xml b/en-US/Package_Selection_Repositories-x86.xml
deleted file mode 100644
index 3912665..0000000
--- a/en-US/Package_Selection_Repositories-x86.xml
+++ /dev/null
@@ -1,108 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-
-<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
- "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
-]>
-
-  <section id="sn-additional-repos">
-    <title>Installing from Additional Repositories</title>
-    <para>
-      You can define additional <firstterm>repositories</firstterm> to
-      increase the software available to your system during
-      installation. A repository is a network location that stores
-      software packages along with <firstterm>metadata</firstterm> that
-      describes them. Many of the software packages used in Fedora
-      require other software to be installed.  The installer uses the
-      metadata to ensure that these requirements are met for every piece
-      of software you select for installation.
-    </para>
-    
-    <para>The basic options are:</para>
-    <itemizedlist>
-    <listitem>
-    <para>
-      The <guilabel>Installation Repo</guilabel> repository is automatically selected for
-      you. This represents the collection of software available on your installation CD or DVD.
-      </para> 
-    </listitem>
-    <listitem>
-      <para>The <guilabel>Fedora &PRODVER; - i386</guilabel> repository contains the complete collection of software that was released as Fedora &PRODVER;, with the various pieces of software in their versions that were current at the time of release. If you are installing from the Fedora &PRODVER; DVD or <emphasis>set</emphasis> of CDs, this option does not offer you anything extra. However, if you are installing from a Fedora Live CD, this option provides access to far more software than is included on the disk. Note that the computer must have access to the internet to use this option.
-    </para>
-    </listitem>
-    <listitem>
-      <para>The <guilabel>Fedora &PRODVER; - i386 - Updates</guilabel> repository contains the complete collection of software that was released as Fedora &PRODVER;, with the various pieces of software in their most current stable versions. This option not only installs the software that you select, but makes sure that it is fully updated as well. Note that the computer must have access to the internet to use this option.
-    </para>
-    </listitem>
-    
-    </itemizedlist>
-    
-	<figure float="0" id="fig-pkgselection-repos-x86"><title>Adding a software repository</title>
-		<mediaobject>
-			<imageobject><imagedata fileref="images/pkgselection/pkg-group-repos.png" format="PNG"/></imageobject>
-			<textobject>
-				<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Package_Selection_common-imagecap-3.xml"/>
-				<!-- Enter the details of additional software repositories. -->
-			</textobject>
-		</mediaobject>
-	</figure>
-
-
-    <para>
-      To include software from <firstterm>repositories</firstterm> other
-      than the Fedora package collection, select <guilabel>Add additional
-      software repositories</guilabel>.  You may provide the location
-      of a repository of third-party software.  Depending on the
-      configuration of that repository, you may be able to select
-      non-Fedora software during installation.
-    </para>
-    <para>
-      To edit an existing software repository location, select the
-      repository in the list and then select <guilabel>Modify
-      repository</guilabel>.
-    </para>
-    <note>
-      <title>Network Access Required</title>
-      <para>
-	If you change the repository information during a non-network
-	installation, such as from a Fedora DVD, the installer prompts
-	you for network configuration information.
-      </para>
-    </note>
-    <para>
-      If you select <guilabel>Add additional software
-	repositories</guilabel>, the <guilabel>Edit repository</guilabel>
-      dialog appears. Provide a <guilabel>Repository name</guilabel> and
-      the <guilabel>Repository URL</guilabel> for its location.
-    </para>
-    <note>
-      <title>Fedora Software Mirrors</title>
-      <para>To find a Fedora software mirror near you, refer to <ulink
-	  url="http://fedoraproject.org/wiki/Mirrors"/>.</para>
-    </note>
-    <para>Once you have located a mirror, to determine the URL to use,
-      find the directory on the mirror that
-      <emphasis>contains</emphasis> a directory named <filename
-	class="directory">repodata</filename>.  For instance, the
-      "Everything" repository for Fedora is typically located in a
-      directory tree
-      <filename>releases/&PRODVER;/Everything/<replaceable>arch</replaceable>/os</filename>, 
-      where <replaceable>arch</replaceable> is a system architecture
-      name.</para>
-    <para>
-      Once you provide information for an additional repository, the
-      installer reads the package metadata over the network.  Software
-      that is specially marked is then included in the package group
-      selection system.  See <xref linkend="sn-package-selection-x86"/> for
-      more information on selecting packages.
-    </para>
-    <note>
-      <title>Backtracking Removes Repository Metadata</title>
-      <para>
-	If you choose <guilabel>Back</guilabel> from the package
-	selection screen, any extra repository data you may have entered
-	is lost.  This allows you to effectively cancel extra
-	repositories.  Currently there is no way to cancel only a single
-	repository once entered.
-      </para>
-    </note>
-  </section>
diff --git a/en-US/Package_Selection_common-imagecap-1.xml b/en-US/Package_Selection_common-imagecap-1.xml
deleted file mode 100644
index 72fcd39..0000000
--- a/en-US/Package_Selection_common-imagecap-1.xml
+++ /dev/null
@@ -1,10 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<para>
-	Choose which package groups you want to install.
-</para>
\ No newline at end of file
diff --git a/en-US/Package_Selection_common-imagecap-2.xml b/en-US/Package_Selection_common-imagecap-2.xml
deleted file mode 100644
index ca0a421..0000000
--- a/en-US/Package_Selection_common-imagecap-2.xml
+++ /dev/null
@@ -1,7 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<para>
-	Choose to add or remove optional packages from this package group.
-</para>
\ No newline at end of file
diff --git a/en-US/Package_Selection_common-imagecap-3.xml b/en-US/Package_Selection_common-imagecap-3.xml
deleted file mode 100644
index 4fb429b..0000000
--- a/en-US/Package_Selection_common-imagecap-3.xml
+++ /dev/null
@@ -1,7 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<para>
-	Enter the details of additional software repositories.
-</para>
\ No newline at end of file
diff --git a/en-US/Package_Selection_common-indexterm-1.xml b/en-US/Package_Selection_common-indexterm-1.xml
deleted file mode 100644
index af05f68..0000000
--- a/en-US/Package_Selection_common-indexterm-1.xml
+++ /dev/null
@@ -1,11 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE indexterm PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<indexterm significance="normal">
-	<primary>packages</primary>
-	<secondary>installing</secondary>
-</indexterm>
\ No newline at end of file
diff --git a/en-US/Package_Selection_common-indexterm-2.xml b/en-US/Package_Selection_common-indexterm-2.xml
deleted file mode 100644
index 216a277..0000000
--- a/en-US/Package_Selection_common-indexterm-2.xml
+++ /dev/null
@@ -1,11 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE indexterm PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<indexterm significance="normal">
-	<primary>packages</primary>
-	<secondary>selecting</secondary>
-</indexterm>
\ No newline at end of file
diff --git a/en-US/Package_Selection_common-indexterm-3.xml b/en-US/Package_Selection_common-indexterm-3.xml
deleted file mode 100644
index bf131dc..0000000
--- a/en-US/Package_Selection_common-indexterm-3.xml
+++ /dev/null
@@ -1,11 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE indexterm PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<indexterm significance="normal">
-	<primary>selecting</primary>
-	<secondary>packages</secondary>
-</indexterm>
\ No newline at end of file
diff --git a/en-US/Package_Selection_common-indexterm-4.xml b/en-US/Package_Selection_common-indexterm-4.xml
deleted file mode 100644
index a20792c..0000000
--- a/en-US/Package_Selection_common-indexterm-4.xml
+++ /dev/null
@@ -1,10 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE indexterm PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<indexterm significance="normal">
-	<primary>installing packages</primary>
-</indexterm>
\ No newline at end of file
diff --git a/en-US/Package_Selection_common-indexterm-5.xml b/en-US/Package_Selection_common-indexterm-5.xml
deleted file mode 100644
index 1a2dbef..0000000
--- a/en-US/Package_Selection_common-indexterm-5.xml
+++ /dev/null
@@ -1,11 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE indexterm PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<indexterm significance="normal">
-	<primary>packages</primary>
-	<secondary>groups</secondary>
-</indexterm>
\ No newline at end of file
diff --git a/en-US/Package_Selection_common-indexterm-6.xml b/en-US/Package_Selection_common-indexterm-6.xml
deleted file mode 100644
index c33346c..0000000
--- a/en-US/Package_Selection_common-indexterm-6.xml
+++ /dev/null
@@ -1,12 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE indexterm PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<indexterm significance="normal">
-	<primary>packages</primary>
-	<secondary>groups</secondary>
-	<tertiary>selecting</tertiary>
-</indexterm>
\ No newline at end of file
diff --git a/en-US/Package_Selection_common-list-1.xml b/en-US/Package_Selection_common-list-1.xml
deleted file mode 100644
index b1677a8..0000000
--- a/en-US/Package_Selection_common-list-1.xml
+++ /dev/null
@@ -1,37 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-
-<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
- "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
-]>
-
-  <variablelist>
-    <varlistentry>
-      <term>Office and Productivity</term>
-      <listitem>
-	<para>
-	  This option provides the OpenOffice.org productivity suite,
-	  the Planner project management application, graphical tools
-	  such as the GIMP, and multimedia applications.
-	</para>
-      </listitem>
-    </varlistentry>
-
-    <varlistentry>
-      <term>Software Development</term>
-      <listitem>
-	<para>
-	  This option provides the necessary tools to compile software
-	  on your Fedora system.
-	</para>
-      </listitem>
-    </varlistentry>
-
-    <varlistentry>
-      <term>Web server</term>
-      <listitem>
-	<para>
-	  This option provides the Apache Web server.
-	</para>
-      </listitem>
-    </varlistentry>
-  </variablelist>
diff --git a/en-US/Package_Selection_common-note-1.xml b/en-US/Package_Selection_common-note-1.xml
deleted file mode 100644
index 781b590..0000000
--- a/en-US/Package_Selection_common-note-1.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-
-<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
- "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
-]>
-
-  <important>
-    <title>Installing from a Live Image</title>
-    <para>If you install from a Fedora Live image, you cannot make
-      package selections.  This installation method transfers a copy of
-      the Live image rather than installing packages from a repository.
-      To change the package selection, complete the installation, then
-      use the <application>Add/Remove Software</application> application
-      to make desired changes.</para>
-  </important>
diff --git a/en-US/Package_Selection_common-note-2.xml b/en-US/Package_Selection_common-note-2.xml
deleted file mode 100644
index 0597cea..0000000
--- a/en-US/Package_Selection_common-note-2.xml
+++ /dev/null
@@ -1,14 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-
-<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
- "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
-]>
-
-  <important>
-    <title>Installing in text mode</title>
-    <para>If you install Fedora in text mode, you cannot make
-      package selections. The installer automatically selects packages only from the base and core groups. These packages are sufficient to ensure that the system is operational at the end of the installation process, ready to install updates and new packages. 
-      To change the package selection, complete the installation, then
-      use the <application>Add/Remove Software</application> application
-      to make desired changes.</para>
-  </important>
diff --git a/en-US/Package_Selection_common-para-1.xml b/en-US/Package_Selection_common-para-1.xml
deleted file mode 100644
index 75d6ff5..0000000
--- a/en-US/Package_Selection_common-para-1.xml
+++ /dev/null
@@ -1,10 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<para>
-	Now that you have made most of the choices for your installation, you are ready to confirm the default package selection or customize packages for your system.
-</para>
\ No newline at end of file
diff --git a/en-US/Package_Selection_common-para-2.xml b/en-US/Package_Selection_common-para-2.xml
deleted file mode 100644
index 732a41e..0000000
--- a/en-US/Package_Selection_common-para-2.xml
+++ /dev/null
@@ -1,7 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<para>
-	The <guilabel>Package Installation Defaults</guilabel> screen appears and details the default package set for your Fedora installation. This screen varies depending on the version of Fedora you are installing.
-</para>
\ No newline at end of file
diff --git a/en-US/Package_Selection_common-para-3.xml b/en-US/Package_Selection_common-para-3.xml
deleted file mode 100644
index cd769ef..0000000
--- a/en-US/Package_Selection_common-para-3.xml
+++ /dev/null
@@ -1,10 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<para>
-	To customize your package set further, select the <guilabel>Customize now</guilabel> option on the screen. Clicking <guibutton>Next</guibutton> takes you to the <guilabel>Package Group Selection</guilabel> screen.
-</para>
\ No newline at end of file
diff --git a/en-US/Package_Selection_common-para-4.xml b/en-US/Package_Selection_common-para-4.xml
deleted file mode 100644
index 9fefe98..0000000
--- a/en-US/Package_Selection_common-para-4.xml
+++ /dev/null
@@ -1,10 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<para>
-	You can select package groups, which group components together according to function (for example, <guilabel>X Window System</guilabel> and <guilabel>Editors</guilabel>), individual packages, or a combination of the two.
-</para>
\ No newline at end of file
diff --git a/en-US/Package_Selection_common-para-7.xml b/en-US/Package_Selection_common-para-7.xml
deleted file mode 100644
index b17de01..0000000
--- a/en-US/Package_Selection_common-para-7.xml
+++ /dev/null
@@ -1,11 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-
-<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
- "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
-]>
-
-  <para>
-    By default, the Fedora installation process loads a selection of
-    software that is suitable for a desktop system. To include or remove
-    software for common tasks, select the relevant items from the list:
-  </para>
diff --git a/en-US/Package_Selection_common-title-1.xml b/en-US/Package_Selection_common-title-1.xml
deleted file mode 100644
index 1a2676c..0000000
--- a/en-US/Package_Selection_common-title-1.xml
+++ /dev/null
@@ -1,8 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE title PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<title>Package Group Selection</title>
\ No newline at end of file
diff --git a/en-US/Partitions-x86.xml b/en-US/Partitions-x86.xml
deleted file mode 100644
index c8ca77a..0000000
--- a/en-US/Partitions-x86.xml
+++ /dev/null
@@ -1,1080 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE appendix PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<appendix id="ch-partitions-x86">
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Partitions_common-title.xml"/>
-	<!-- An Introduction to Disk Partitions -->
-	
-	<!-- Begin Index Terms -->
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Partitions_common-indexterm-1.xml"/>
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Partitions_common-indexterm-2.xml"/>
-	<!-- End Index Terms -->
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Partitions_common-note-1.xml"/>
-	<!-- This appendix is not necessarily applicable to non-x86-based architectures -->
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Partitions_common-para-1.xml"/>
-	<!-- Disk partitions are a standard part of the personal computer -->
-
-	<para>
-		If you are reasonably comfortable with disk partitions, you could skip ahead to <xref linkend="s2-partitions-make-room-x86"/>, for more information on the process of freeing up disk space to prepare for a Fedora installation. This section also discusses the partition naming scheme used by Linux systems, sharing disk space with other operating systems, and related topics.
-	</para>
-	
-	<section id="s1-partitions-concepts-x86">
-		<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Partitions_common-title-2.xml"/>
-		<!-- Hard Disk Basic Concepts -->
-		
-		<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Partitions_common-indexterm-3.xml"/>
-		<!-- Index Term -->
-		
-		<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Partitions_common-para-2.xml"/>
-		<!-- Hard disks perform a very simple function... -->
-		 
-		<para>
-			When discussing issues such as disk partitioning, it is important to know a bit about the underlying hardware. Unfortunately, it is easy to become bogged down in details. Therefore, this appendix uses a simplified diagram of a disk drive to help explain what is really happening when a disk drive is partitioned. <xref linkend="fig-partitions-unused-drive-x86"/>, shows a brand-new, unused disk drive.
-		</para>
-		<figure float="0" id="fig-partitions-unused-drive-x86"><title>An Unused Disk Drive</title>
-			<mediaobject>
-				<imageobject><imagedata fileref="images/partitions/unused-drive.png" format="PNG"/></imageobject>
-				<textobject>
-					<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Partitions_common-imagecap-1.xml"/>
-					<!-- "Image of an unused disk drive." -->
-				</textobject>
-			</mediaobject>
-		</figure>
-		
-		<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Partitions_common-para-3.xml"/>
-		<!-- Not much to look at, is it? But if we are... -->
-		 
-		<section id="s2-partitions-filesystem-x86">
-			
-			<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Partitions_common-title-3.xml"/>
-			<!-- It is Not What You Write, it is How You Write It -->
-			
-			<!-- Begin Index Terms -->
-			<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Partitions_common-indexterm-4.xml"/>
-			<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Partitions_common-indexterm-5.xml"/>
-			<!-- End Index Terms -->
-			
-			<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Partitions_common-para-4.xml"/>
-			<!-- Experienced computer users probably got this one on the first try. -->
-			
-			<figure float="0" id="fig-partitions-formatted-drive-x86"><title>Disk Drive with a File System</title>
-				<mediaobject>
-					<imageobject><imagedata fileref="images/partitions/formatted-drive.png" format="PNG"/></imageobject>
-					<textobject>
-						<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Partitions_common-imagecap-2.xml"/>
-						<!-- "Image of a formatted disk drive." -->
-					</textobject>
-				</mediaobject>
-			</figure>
-			<para>
-				As <xref linkend="fig-partitions-formatted-drive-x86"/>, implies, the order imposed by a file system involves some trade-offs:
-			</para>
-			 
-			<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Partitions_common-itemizedlist-1.xml"/>
-			<!-- A small percentage... etc -->
-			 
-			<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Partitions_common-para-5.xml"/>
-			<!-- Given that file systems make things like directories and files possible... -->
-			 
-			<para>
-				It is also worth noting that there is no single, universal file system. As <xref linkend="fig-partitions-other-formatted-d-x86"/>, shows, a disk drive may have one of many different file systems written on it. As you might guess, different file systems tend to be incompatible; that is, an operating system that supports one file system (or a handful of related file system types) may not support another. This last statement is not a hard-and-fast rule, however. For example, Fedora supports a wide variety of file systems (including many commonly used by other operating systems), making data interchange between different file systems easy.
-			</para>
-			<figure float="0" id="fig-partitions-other-formatted-d-x86"><title>Disk Drive with a Different File System</title>
-				<mediaobject>
-					<imageobject><imagedata fileref="images/partitions/other-formatted-drive.png" format="PNG"/></imageobject>
-					<textobject>
-						<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Partitions_common-imagecap-3.xml"/>
-						<!-- "Image of a disk drive with a different file system." -->
-					</textobject>
-				</mediaobject>
-			</figure>
-			
-			<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Partitions_common-para-6.xml"/>
-			<!-- Of course, writing a file system to disk is only the beginning... -->
-			
-			<figure float="0" id="fig-partitions-used-formatted-dr-x86"><title>Disk Drive with Data Written to It</title>
-				<mediaobject>
-					<imageobject><imagedata fileref="images/partitions/used-formatted-drive.png" format="PNG"/></imageobject>
-					<textobject>
-						<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Partitions_common-imagecap-4.xml"/>
-						<!-- "Image of a disk drive with data written to it." -->
-					</textobject>
-				</mediaobject>
-			</figure>
-			<para>
-				As <xref linkend="fig-partitions-used-formatted-dr-x86"/>, shows, some of the previously-empty blocks are now holding data. However, by just looking at this picture, we cannot determine exactly how many files reside on this drive. There may only be one
-				file or many, as all files use at least one block and some files use multiple blocks. Another important point to note is that the used blocks do not have to form a contiguous region; used and unused blocks may be interspersed. This is known as
-				<firstterm>fragmentation</firstterm>. Fragmentation can play a part when attempting to resize an existing partition.
-			</para>
-			 
-			<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Partitions_common-para-7.xml"/>
-			<!-- As with most computer-related technologies, disk drives changed over time -->
-		</section>
-		 
-		<section id="s2-partitions-partitioning-x86">
-			
-			<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Partitions_common-title-4.xml"/>
-			<!-- Partitions: Turning One Drive Into Many -->
-			
-			<!-- Begin Index Terms -->
-			<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Partitions_common-indexterm-6.xml"/>
-			<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Partitions_common-indexterm-7.xml"/>
-			<!-- End Index Terms -->
-			
-			<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Partitions_common-para-8.xml"/>
-			<!-- As disk drive capacities soared, some people began to wonder ... -->
-			
-			<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Partitions_common-para-9.xml"/>
-			<!-- The solution to this problem was to divide disks -->
-			 
-			<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Partitions_complete-note-1.xml"/>
-			<!-- Note: While the diagrams in this chapter.. -->
-			
-			<figure float="0" id="fig-partitions-unused-partitione-x86"><title>Disk Drive with Partition Table</title>
-				<mediaobject>
-					<imageobject><imagedata fileref="images/partitions/unused-partitioned-drive.png" format="PNG"/></imageobject>
-					<textobject>
-						<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Partitions_common-imagecap-5.xml"/>
-						<!-- "Image of an unused disk drive with a partition table."-->
-					</textobject>
-				</mediaobject>
-			</figure>
-			
-			<!-- Begin Index Terms -->
-			<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Partitions_common-indexterm-8.xml"/>
-			<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Partitions_common-indexterm-9.xml"/>
-			<!-- End Index Terms -->
-			
-			<para>
-				As <xref linkend="fig-partitions-unused-partitione-x86"/> shows, the partition table is divided into four sections or four <firstterm>primary</firstterm> partitions. A primary partition is a partition on a hard drive that can contain only one logical drive
-				(or section). Each section can hold the information necessary to define a single partition, meaning that the partition table can define no more than four partitions.
-			</para>
-			 
-			<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Partitions_common-para-10.xml"/>
-			<!-- Each partition table entry contains several important characteristics... -->
-			 
-			<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Partitions_common-itemizedlist-2.xml"/>
-			<!-- The points on the disk where the partition starts and ends, etc.. -->
-			 
-			<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Partitions_common-para-11.xml"/>
-			<!-- Let us take a closer look at each of these characteristics. -->
-			 
-			<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Partitions_common-para-12.xml"/>
-			<!-- The partition's type can be a bit confusing. -->
-			
-			<para>
-				By this point, you might be wondering how all this additional complexity is normally used. Refer to <xref linkend="fig-partitions-dos-single-part-x86"/>, for an example.
-			</para>
-			<figure float="0" id="fig-partitions-dos-single-part-x86"><title>Disk Drive With Single Partition</title>
-				<mediaobject>
-					<imageobject><imagedata fileref="images/partitions/dos-single-partition.png" format="PNG"/></imageobject>
-					<textobject>
-						<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Partitions_common-imagecap-6.xml"/>
-						<!-- Image of a disk drive with a single partition.-->
-					</textobject>
-				</mediaobject>
-			</figure>
-			
-			<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Partitions_common-para-13.xml"/>
-			<!-- In many cases, there is only a single partition spanning -->
-			 
-			<para>
-				We have labeled this partition as being of the "DOS" type. Although it is only one of several possible partition types listed in <xref linkend="tb-partitions-types-x86"/>, it is adequate for the purposes of this discussion.
-			</para>
-			 
-			<para>
-				<xref linkend="tb-partitions-types-x86"/>, contains a listing of some popular (and obscure) partition types, along with their hexadecimal numeric values.
-			</para>
-			
-			<!-- Begin Index Terms -->
-			<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Partitions_common-indexterm-11.xml"/>
-			<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Partitions_common-indexterm-10.xml"/>
-			<!-- End Index Terms -->
-			
-			<table id="tb-partitions-types-x86">
-				
-				<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Partitions_common-table-title-1.xml"/>
-				<!-- Partition Types -->
-				 
-				<tgroup cols="4">
-					<colspec colnum="1" colwidth="2*"></colspec>
-					 
-					<colspec colnum="2" colwidth="1*"></colspec>
-					 
-					<colspec colnum="3" colwidth="2*"></colspec>
-					 
-					<colspec colnum="4" colwidth="1*"></colspec>
-					<thead><row>
-							<entry>
-								Partition Type
-							</entry>
-							 
-							<entry>
-								Value
-							</entry>
-							 
-							<entry>
-								Partition Type
-							</entry>
-							 
-							<entry>
-								Value
-							</entry>
-						</row>
-					</thead>
-					<tbody>
-						<row>
-							<entry>
-								Empty
-							</entry>
-							 
-							<entry>
-								00
-							</entry>
-							 
-							<entry>
-								Novell Netware 386
-							</entry>
-							 
-							<entry>
-								65
-							</entry>
-						</row>
-						 
-						<row>
-							<entry>
-								DOS 12-bit FAT
-							</entry>
-							 
-							<entry>
-								01
-							</entry>
-							 
-							<entry>
-								PIC/IX
-							</entry>
-							 
-							<entry>
-								75
-							</entry>
-						</row>
-						 
-						<row>
-							<entry>
-								XENIX root
-							</entry>
-							 
-							<entry>
-								02
-							</entry>
-							 
-							<entry>
-								Old MINIX
-							</entry>
-							 
-							<entry>
-								80
-							</entry>
-						</row>
-						 
-						<row>
-							<entry>
-								XENIX usr
-							</entry>
-							 
-							<entry>
-								03
-							</entry>
-							 
-							<entry>
-								Linux/MINUX
-							</entry>
-							 
-							<entry>
-								81
-							</entry>
-						</row>
-						 
-						<row>
-							<entry>
-								DOS 16-bit &lt;=32M
-							</entry>
-							 
-							<entry>
-								04
-							</entry>
-							 
-							<entry>
-								Linux swap
-							</entry>
-							 
-							<entry>
-								82
-							</entry>
-						</row>
-						 
-						<row>
-							<entry>
-								Extended
-							</entry>
-							 
-							<entry>
-								05
-							</entry>
-							 
-							<entry>
-								Linux native
-							</entry>
-							 
-							<entry>
-								83
-							</entry>
-						</row>
-						 
-						<row>
-							<entry>
-								DOS 16-bit &gt;=32
-							</entry>
-							 
-							<entry>
-								06
-							</entry>
-							 
-							<entry>
-								Linux extended
-							</entry>
-							 
-							<entry>
-								85
-							</entry>
-						</row>
-						 
-						<row>
-							<entry>
-								OS/2 HPFS
-							</entry>
-							 
-							<entry>
-								07
-							</entry>
-							 
-							<entry>
-								Amoeba
-							</entry>
-							 
-							<entry>
-								93
-							</entry>
-						</row>
-						 
-						<row>
-							<entry>
-								AIX
-							</entry>
-							 
-							<entry>
-								08
-							</entry>
-							 
-							<entry>
-								Amoeba BBT
-							</entry>
-							 
-							<entry>
-								94
-							</entry>
-						</row>
-						 
-						<row>
-							<entry>
-								AIX bootable
-							</entry>
-							 
-							<entry>
-								09
-							</entry>
-							 
-							<entry>
-								BSD/386
-							</entry>
-							 
-							<entry>
-								a5
-							</entry>
-						</row>
-						 
-						<row>
-							<entry>
-								OS/2 Boot Manager
-							</entry>
-							 
-							<entry>
-								0a
-							</entry>
-							 
-							<entry>
-								OpenBSD
-							</entry>
-							 
-							<entry>
-								a6
-							</entry>
-						</row>
-						 
-						<row>
-							<entry>
-								Win95 FAT32
-							</entry>
-							 
-							<entry>
-								0b
-							</entry>
-							 
-							<entry>
-								NEXTSTEP
-							</entry>
-							 
-							<entry>
-								a7
-							</entry>
-						</row>
-						 
-						<row>
-							<entry>
-								Win95 FAT32 (LBA)
-							</entry>
-							 
-							<entry>
-								0c
-							</entry>
-							 
-							<entry>
-								BSDI fs
-							</entry>
-							 
-							<entry>
-								b7
-							</entry>
-						</row>
-						 
-						<row>
-							<entry>
-								Win95 FAT16 (LBA)
-							</entry>
-							 
-							<entry>
-								0e
-							</entry>
-							 
-							<entry>
-								BSDI swap
-							</entry>
-							 
-							<entry>
-								b8
-							</entry>
-						</row>
-						 
-						<row>
-							<entry>
-								Win95 Extended (LBA)
-							</entry>
-							 
-							<entry>
-								0f
-							</entry>
-							 
-							<entry>
-								Syrinx
-							</entry>
-							 
-							<entry>
-								c7
-							</entry>
-						</row>
-						 
-						<row>
-							<entry>
-								Venix 80286
-							</entry>
-							 
-							<entry>
-								40
-							</entry>
-							 
-							<entry>
-								CP/M
-							</entry>
-							 
-							<entry>
-								db
-							</entry>
-						</row>
-						 
-						<row>
-							<entry>
-								Novell
-							</entry>
-							 
-							<entry>
-								51
-							</entry>
-							 
-							<entry>
-								DOS access
-							</entry>
-							 
-							<entry>
-								e1
-							</entry>
-						</row>
-						 
-						<row>
-							<entry>
-								PPC PReP Boot
-							</entry>
-							 
-							<entry>
-								41
-							</entry>
-							 
-							<entry>
-								DOS R/O
-							</entry>
-							 
-							<entry>
-								e3
-							</entry>
-						</row>
-						 
-						<row>
-							<entry>
-								GNU HURD
-							</entry>
-							 
-							<entry>
-								63
-							</entry>
-							 
-							<entry>
-								DOS secondary
-							</entry>
-							 
-							<entry>
-								f2
-							</entry>
-						</row>
-						 
-						<row>
-							<entry>
-								Novell Netware 286
-							</entry>
-							 
-							<entry>
-								64
-							</entry>
-							 
-							<entry>
-								BBT
-							</entry>
-							 
-							<entry>
-								ff
-							</entry>
-						</row>
-					</tbody>
-				</tgroup>
-				<!-- Table -->
-				
-			</table>
-			 
-			<para></para>
-			 
-			<para></para>
-			 
-			<para></para>
-			 
-			<para></para>
-			 
-			<para></para>
-		</section>
-		 
-		<section id="s2-partitions-overview-extended-x86">
-			
-			<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Partitions_common-title-5.xml"/>
-			<!--Partitions within Partitions - An Overview of Extended Partitions -->
-			
-			<!-- Begin Index Terms -->
-			<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Partitions_common-indexterm-12.xml"/>
-			<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Partitions_common-indexterm-13.xml"/>
-			<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Partitions_common-indexterm-14.xml"/>
-			<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Partitions_common-indexterm-15.xml"/>
-			<!-- End Index Terms -->
-			
-			<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Partitions_common-para-14.xml"/>
-			<!-- Of course, over time it became obvious that four partitions would not be enough. -->
-			 
-			<para>
-				Enter the extended partition. As you may have noticed in <xref linkend="tb-partitions-types-x86"/>, there is an "Extended" partition type. It is this partition type that is at the heart of extended partitions.
-			</para>
-			 
-			<para>
-				When a partition is created and its type is set to "Extended," an extended partition table is created. In essence, the extended partition is like a disk drive in its own right &mdash; it has a partition table that points to one or more partitions (now
-				called <firstterm>logical partitions</firstterm>, as opposed to the four <firstterm>primary partitions</firstterm>) contained entirely within the extended partition itself. <xref linkend="fig-partitions-extended-part-x86"/>, shows a disk drive with one
-				primary partition and one extended partition containing two logical partitions (along with some unpartitioned free space).
-			</para>
-			<figure float="0" id="fig-partitions-extended-part-x86"><title>Disk Drive With Extended Partition</title>
-				<mediaobject>
-					<imageobject><imagedata fileref="images/partitions//extended-partitions.png" format="PNG"/></imageobject>
-					<textobject>
-						<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Partitions_common-imagecap-7.xml"/>
-						<!-- Image of a disk drive with an extended partition. -->
-					</textobject>
-				</mediaobject>
-			</figure>
-			
-			<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Partitions_common-para-15.xml"/>
-			<!-- As this figure implies, there is a difference between primary and logical partitions  -->
-			 
-			<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Partitions_common-para-16.xml"/>
-			<!-- Now that we have discussed partitions in general -->
-		</section>
-		 
-		<section id="s2-partitions-make-room-x86">
-			<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Partitions_common-title-6.xml"/>
-			<!-- Making Room For Red Hat Enterprise Linux -->
-			
-			<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Partitions_common-indexterm-16.xml"/>
-			
-			<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Partitions_common-para-17.xml"/>
-			<!-- The following list presents some possible scenarios -->
-			 
-			<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Partitions_common-itemizedlist-3.xml"/>
-			<!-- Unpartitioned free space is available, etc.. -->
-			
-			<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Partitions_common-para-18.xml"/>
-			<!-- Let us look at each scenario in order. -->
-			 
-			<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Partitions_common-note-3.xml"/>
-			<!-- Keep in mind that the following illustrations are simplified -->
-			 
-			<section id="s3-partitions-free-space-x86">
-				<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Partitions_common-title-7.xml"/>
-				<!-- Using Unpartitioned Free Space -->
-				
-				<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Partitions_common-indexterm-17.xml"/>
-					
-				<para>
-					In this situation, the partitions already defined do not span the entire hard disk, leaving unallocated space that is not part of any defined partition. <xref linkend="fig-partitions-unpart-space-x86"/>, shows what this might look like.
-				</para>
-				<figure float="0" id="fig-partitions-unpart-space-x86"><title>Disk Drive with Unpartitioned Free Space</title>
-					<mediaobject>
-						<imageobject><imagedata fileref="images/partitions/unpart-space.png" format="PNG"/></imageobject>
-						<textobject>
-							<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Partitions_common-imagecap-8.xml"/>
-							<!--Image of a disk drive with unpartitioned free space, where 1 represents... -->
-						</textobject>
-					</mediaobject>
-				</figure>
-				<para>
-					In <xref linkend="fig-partitions-unpart-space-x86"/>, <wordasword>1</wordasword> represents an undefined partition with unallocated space and <wordasword>2</wordasword> represents a defined partition with allocated space.
-				</para>
-				 
-				<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Partitions_common-para-19.xml"/>
-				<!-- If you think about it, an unused hard disk also falls into this category. -->
-				 
-				<para>
-					In any case, you can create the necessary partitions from the unused space. Unfortunately, this scenario, although very simple, is not very likely (unless you have just purchased a new disk just for Fedora). Most pre-installed operating systems are configured to take up all available space on a disk drive (refer to <xref linkend="s3-partitions-active-part-x86"/>).
-				</para>
-				 
-				<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Partitions_common-para-20.xml"/>
-				<!-- Next, we will discuss a slightly more common situation.-->
-			</section>
-			 
-			<section id="s3-partitions-unused-part-x86">
-				
-				<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Partitions_common-title-8.xml"/>
-				<!--Using Space from an Unused Partition -->
-				
-				<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Partitions_common-indexterm-18.xml"/>
-				
-				<para>
-					In this case, maybe you have one or more partitions that you do not use any longer. Perhaps you have dabbled with another operating system in the past, and the partition(s) you dedicated to it never seem to be used anymore.
-					<xref linkend="fig-partitions-unused-partition-x86"/>, illustrates such a situation.
-				</para>
-				<figure float="0" id="fig-partitions-unused-partition-x86"><title>Disk Drive With an Unused Partition</title>
-					<mediaobject>
-						<imageobject><imagedata fileref="images/partitions/unused-partition.png" format="PNG"/></imageobject>
-						<textobject>
-							<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Partitions_common-imagecap-9.xml"/>
-							<!-- Image of a disk drive with an unused partition, where 1 represents... -->
-						</textobject>
-					</mediaobject>
-				</figure>
-				<para>
-					In <xref linkend="fig-partitions-unused-partition-x86"/>, <wordasword>1</wordasword> represents an unused partition and <wordasword>2</wordasword> represents reallocating an unused partition for Linux.
-				</para>
-				 
-				<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Partitions_common-para-21.xml"/>
-				<!-- If you find yourself in this situation, you can use the space... -->
-			</section>
-			 
-			<section id="s3-partitions-active-part-x86">
-				
-				<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Partitions_common-title-9.xml"/>
-				<!-- Using Free Space from an Active Partition -->
-				
-				<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Partitions_common-indexterm-19.xml"/>
-				
-				<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Partitions_common-para-22.xml"/>
-				<!-- This is the most common situation. It is also, unfortunately, the hardest to handle... -->
-				 
-				<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Partitions_common-para-23.xml"/>
-				<!-- Aside from adding a new hard drive to your system, you have two choices -->
-				 
-				<variablelist>
-					<varlistentry>
-				
-				<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Partitions_common-term-1.xml"/>
-				<!-- Destructive Repartitioning -->
-						<listitem>
-							<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Partitions_common-para-24.xml"/>
-							<!-- Basically, you delete the single large partition... -->
-
-							<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Partitions_common-caution-1.xml"/>
-
-							<para>
-								After creating a smaller partition for your existing operating system, you can reinstall any software, restore your data, and start your Fedora installation. <xref linkend="fig-partitions-dstrct-reprt-x86"/> shows this being done.
-							</para>
-							<figure float="0" id="fig-partitions-dstrct-reprt-x86">
-								<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Partitions_common-title-10.xml"/>
-							<!--Disk Drive Being Destructively Repartitioned -->
-								<mediaobject>
-									<imageobject><imagedata fileref="images/partitions/dstrct-reprt.png" format="PNG"/></imageobject>
-									<textobject><xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Partitions_common-imagecap-10.xml"/>
-										<!--Image of a disk drive being destructively repartitioned, where 1 represents.. -->
-									</textobject>
-								</mediaobject>
-							</figure>
-							<para>
-								In <xref linkend="fig-partitions-dstrct-reprt-x86"/>, <wordasword>1</wordasword> represents before and <wordasword>2</wordasword> represents after.
-							</para>
-
-							<warning>
-								<title>Warning</title>
-
-								<para>
-									As <xref linkend="fig-partitions-dstrct-reprt-x86"/>, shows, any data present in the original partition is lost without proper backup!
-								</para>
-							</warning>
-						</listitem>
-					</varlistentry>
-
-					<varlistentry>
-						<term>						<indexterm significance="normal">
-							<primary>partitioning</primary>
-							<secondary>non-destructive</secondary>
-						</indexterm>
-<emphasis>Non-Destructive Repartitioning</emphasis></term>
-						<listitem>
-							<para>
-								Here, you run a program that does the seemingly impossible: it makes a big partition smaller without losing any of the files stored in that partition. Many people have found this method to be reliable and trouble-free. What software should you use
-								to perform this feat? There are several disk management software products on the market. Do some research to find the one that is best for your situation.
-							</para>
-
-							<para>
-								While the process of non-destructive repartitioning is rather straightforward, there are a number of steps involved:
-							</para>
-
-							<itemizedlist>
-								<listitem>
-									<para>
-										Compress and backup existing data
-									</para>
-								</listitem>
-
-								<listitem>
-									<para>
-										Resize the existing partition
-									</para>
-								</listitem>
-
-								<listitem>
-									<para>
-										Create new partition(s)
-									</para>
-								</listitem>
-							</itemizedlist>
-						</listitem>
-					</varlistentry>
-				</variablelist>
-				 
-				<para>
-					Next we will look at each step in a bit more detail.
-				</para>
-				 
-				<section id="s4-partitions-compress-data-x86">
-					<title>Compress existing data</title>
-					 
-					<para>
-						As <xref linkend="fig-partitions-compression-x86"/>, shows, the first step is to compress the data in your existing partition. The reason for doing this is to rearrange the data such that it maximizes the available free space at the "end" of the
-						partition.
-					</para>
-					<figure float="0" id="fig-partitions-compression-x86"><title>Disk Drive Being Compressed</title>
-						<mediaobject>
-							<imageobject><imagedata fileref="images/partitions/compression.png" format="PNG"/></imageobject>
-							<textobject><para>
-									Image of a disk drive being compressed, where <wordasword>1</wordasword> represents before and <wordasword>2</wordasword> represents after.
-								</para>
-							</textobject>
-						</mediaobject>
-					</figure>
-					<para>
-						In <xref linkend="fig-partitions-compression-x86"/>, <wordasword>1</wordasword> represents before and <wordasword>2</wordasword> represents after.
-					</para>
-					 
-					<para>
-						This step is crucial. Without it, the location of your data could prevent the partition from being resized to the extent desired. Note also that, for one reason or another, some data cannot be moved. If this is the case (and it severely restricts the
-						size of your new partition(s)), you may be forced to destructively repartition your disk.
-					</para>
-				</section>
-				 
-				<section id="s4-partitions-resize-x86">
-					<title>Resize the existing partition</title>
-					 
-					<para>
-						<xref linkend="fig-partitions-part-resize-x86"/>, shows the actual resizing process. While the actual result of the resizing operation varies depending on the software used, in most cases the newly freed space is used to create an unformatted partition
-						of the same type as the original partition.
-					</para>
-					<figure float="0" id="fig-partitions-part-resize-x86"><title>Disk Drive with Partition Resized</title>
-						<mediaobject>
-							<imageobject><imagedata fileref="images/partitions/part-resize.png" format="PNG"/></imageobject>
-							<textobject><para>
-									Image of a disk drive with a resized partition, where <wordasword>1</wordasword> represents before and <wordasword>2</wordasword> represents after.
-								</para>
-							</textobject>
-						</mediaobject>
-					</figure>
-					<para>
-						In <xref linkend="fig-partitions-part-resize-x86"/>, <wordasword>1</wordasword> represents before and <wordasword>2</wordasword> represents after.
-					</para>
-					 
-					<para>
-						It is important to understand what the resizing software you use does with the newly freed space, so that you can take the appropriate steps. In the case we have illustrated, it would be best to delete the new DOS partition and create the appropriate
-						Linux partition(s).
-					</para>
-				</section>
-				 
-				<section id="s4-partitions-create-new-x86">
-					<title>Create new partition(s)</title>
-					 
-					<para>
-						As the previous step implied, it may or may not be necessary to create new partitions. However, unless your resizing software is Linux-aware, it is likely that you must delete the partition that was created during the resizing process.
-						<xref linkend="fig-partitions-nondestruct-fin-x86"/>, shows this being done.
-					</para>
-					<figure float="0" id="fig-partitions-nondestruct-fin-x86"><title>Disk Drive with Final Partition Configuration</title>
-						<mediaobject>
-							<imageobject><imagedata fileref="images/partitions/nondestruct-fin.png" format="PNG"/></imageobject>
-							<textobject><para>
-									Image of a disk drive with final partition configuration, where <wordasword>1</wordasword> represents before and <wordasword>2</wordasword> represents after.
-								</para>
-							</textobject>
-						</mediaobject>
-					</figure>
-					<para>
-						In <xref linkend="fig-partitions-nondestruct-fin-x86"/>, <wordasword>1</wordasword> represents before and <wordasword>2</wordasword> represents after.
-					</para>
-					 
-					<note>
-						<title>Note</title>
-
-						<para>
-							The following information is specific to x86-based computers only.
-						</para>
-					</note>
-					<indexterm significance="normal">
-						<primary>parted partitioning utility</primary>
-					</indexterm>
-					<para>
-						As a convenience to our customers, we provide the <command>parted</command> utility. This is a freely available program that can resize partitions.
-					</para>
-					 
-					<para>
-						If you decide to repartition your hard drive with <command>parted</command>, it is important that you be familiar with disk storage and that you perform a backup of your computer data. You should make two copies of all the important
-						data on your computer. These copies should be to removable media (such as tape, CD-ROM, or diskettes), and you should make sure they are readable before proceeding.
-					</para>
-					 
-					<para>
-						Should you decide to use <command>parted</command>, be aware that after <command>parted</command> runs you are left with <emphasis>two</emphasis> partitions: the one you resized, and the one <command>parted</command> created out of the newly freed space. If your goal is to use that space to install Fedora, you should delete the newly created partition, either by using the partitioning utility under your current operating system or while setting up partitions during installation.
-					</para>
-				</section>
-			</section>
-		</section>
-		 
-		<section id="s2-partitions-part-name-x86">
-			<title>Partition Naming Scheme</title>
-			<indexterm significance="normal">
-				<primary>partitioning</primary>
-				<secondary>numbering partitions</secondary>
-			</indexterm>
-			<indexterm significance="normal">
-				<primary>partitioning</primary>
-				<secondary>naming partitions</secondary>
-			</indexterm>
-			<para>
-				Linux refers to disk partitions using a combination of letters and numbers which may be confusing, particularly if you are used to the "C drive" way of referring to hard disks and their partitions. In the DOS/Windows world, partitions are named using
-				the following method:
-			</para>
-			 
-			<itemizedlist mark="bullet">
-				<listitem>
-					<para>
-						Each partition's type is checked to determine if it can be read by DOS/Windows.
-					</para>
-				</listitem>
-
-				<listitem>
-					<para>
-						If the partition's type is compatible, it is assigned a "drive letter." The drive letters start with a "C" and move on to the following letters, depending on the number of partitions to be labeled.
-					</para>
-				</listitem>
-
-				<listitem>
-					<para>
-						The drive letter can then be used to refer to that partition as well as the file system contained on that partition.
-					</para>
-				</listitem>
-			</itemizedlist>
-			 
-			<para>
-				Fedora uses a naming scheme that is more flexible and conveys more information than the approach used by other operating systems. The naming scheme is file-based, with file names in the form of
-				<filename>/dev/<replaceable>xxyN</replaceable></filename>.
-			</para>
-			 
-			<para>
-				Here is how to decipher the partition naming scheme:
-			</para>
-			 
-			<variablelist>
-				<varlistentry>
-					<term><filename>/dev/</filename></term>
-					<listitem>
-						<para>
-							This is the name of the directory in which all device files reside. Since partitions reside on hard disks, and hard disks are devices, the files representing all possible partitions reside in <filename>/dev/</filename>.
-						</para>
-					</listitem>
-				</varlistentry>
-
-				<varlistentry>
-					<term><filename><replaceable>xx</replaceable></filename></term>
-					<listitem>
-						<para>
-							The first two letters of the partition name indicate the type of device on which the partition resides, usually either <filename>hd</filename> (for IDE disks) or <filename>sd</filename> (for SCSI disks).
-						</para>
-					</listitem>
-				</varlistentry>
-
-				<varlistentry>
-					<term><filename><replaceable>y</replaceable></filename></term>
-					<listitem>
-						<para>
-							This letter indicates which device the partition is on. For example, <filename>/dev/hda</filename> (the first IDE hard disk) or <filename>/dev/sdb</filename> (the second SCSI disk).
-						</para>
-					</listitem>
-				</varlistentry>
-
-				<varlistentry>
-					<term><filename><replaceable>N</replaceable></filename></term>
-					<listitem>
-						<para>
-							The final number denotes the partition. The first four (primary or extended) partitions are numbered <filename>1</filename> through <filename>4</filename>. Logical partitions start at
-							<filename>5</filename>. So, for example, <filename>/dev/hda3</filename> is the third primary or extended partition on the first IDE hard disk, and <filename>/dev/sdb6</filename> is the second logical
-							partition on the second SCSI hard disk.
-						</para>
-					</listitem>
-				</varlistentry>
-			</variablelist>
-			 
-			<note>
-				<title>Note</title>
-
-				<para>
-					There is no part of this naming convention that is based on partition type; unlike DOS/Windows, <emphasis>all</emphasis> partitions can be identified under Fedora. Of course, this does not mean that Fedora can access data on every type of partition, but in many cases it is possible to access data on a partition dedicated to another operating system.
-				</para>
-			</note>
-			 
-			<para>
-				Keep this information in mind; it makes things easier to understand when you are setting up the partitions Fedora requires.
-			</para>
-		</section>
-		 
-		<section id="s2-partitions-other-os-x86">
-			<title>Disk Partitions and Other Operating Systems</title>
-			<indexterm significance="normal">
-				<primary>partitioning</primary>
-				<secondary>other operating systems</secondary>
-			</indexterm>
-			<para>
-				If your Fedora partitions are sharing a hard disk with partitions used by other operating systems, most of the time you will have no problems. However, there are certain combinations of Linux and other operating systems that require
-				extra care.
-			</para>
-		</section>
-		 
-		<section id="s2-partitions-mt-points-x86">
-			<title>Disk Partitions and Mount Points</title>
-			<indexterm significance="normal">
-				<primary>partitioning</primary>
-				<secondary>mount points and</secondary>
-			</indexterm>
-			<indexterm significance="normal">
-				<primary>mount points</primary>
-				<secondary>partitions and</secondary>
-			</indexterm>
-			<para>
-				One area that many people new to Linux find confusing is the matter of how partitions are used and accessed by the Linux operating system. In DOS/Windows, it is relatively simple: Each partition gets a "drive letter." You then use the correct drive
-				letter to refer to files and directories on its corresponding partition.
-			</para>
-			 
-			<para>
-				This is entirely different from how Linux deals with partitions and, for that matter, with disk storage in general. The main difference is that each partition is used to form part of the storage necessary to support a single set of files and
-				directories. This is done by associating a partition with a directory through a process known as <firstterm>mounting</firstterm>. Mounting a partition makes its storage available starting at the specified directory (known as a <firstterm>mount
-				point</firstterm>).
-			</para>
-			 
-			<para>
-				For example, if partition <filename>/dev/hda5</filename> is mounted on <filename>/usr/</filename>, that would mean that all files and directories under <filename>/usr/</filename> physically reside on
-				<filename>/dev/hda5</filename>. So the file <filename>/usr/share/doc/FAQ/txt/Linux-FAQ</filename> would be stored on <filename>/dev/hda5</filename>, while the file
-				<filename>/etc/gdm/custom.conf</filename> would not.
-			</para>
-			 
-			<para>
-				Continuing our example, it is also possible that one or more directories below <filename>/usr/</filename> would be mount points for other partitions. For instance, a partition (say, <filename>/dev/hda7</filename>) could
-				be mounted on <filename>/usr/local/</filename>, meaning that <filename>/usr/local/man/whatis</filename> would then reside on <filename>/dev/hda7</filename> rather than
-				<filename>/dev/hda5</filename>.
-			</para>
-		</section>
-		 
-		<section id="s2-partitions-how-many-x86">
-			<title>How Many Partitions?</title>
-			<indexterm significance="normal">
-				<primary>partitioning</primary>
-				<secondary>how many partitions</secondary>
-			</indexterm>
-			<para>
-				At this point in the process of preparing to install Fedora, you must give some consideration to the number and size of the partitions to be used by your new operating system. The question of "how many partitions" continues to spark debate within the Linux community and, without any end to the debate in sight, it is safe to say that there are probably as many partition layouts as there are people debating the issue.
-			</para>
-			 
-			<para>
-				Keeping this in mind, we recommend that, unless you have a reason for doing otherwise, you should at least create the following partitions: <filename>swap</filename>, <filename>/boot/</filename> (or a <filename>/boot/efi/</filename> partition for Itanium systems), a <filename>/var/</filename> partition for Itanium systems, and <filename>/</filename> (root).
-			</para>
-			 
-			<para>
-				For more information, refer to <xref linkend="s2-diskpartrecommend-x86"/>.
-			</para>
-		</section>
-	</section>
-</appendix>
diff --git a/en-US/Partitions_common-caution-1.xml b/en-US/Partitions_common-caution-1.xml
deleted file mode 100644
index fbcaee6..0000000
--- a/en-US/Partitions_common-caution-1.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE caution PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<warning>
-	<title>Warning</title>
-	
-	<para>
-		If there was an operating system of some type installed on that partition, it needs to be reinstalled as well. Be aware that some computers sold with pre-installed operating systems may not include the CD-ROM media to reinstall the original
-		operating system. The best time to notice if this applies to your system is <emphasis>before</emphasis> you destroy your original partition and its operating system installation.
-	</para>
-							</warning>
\ No newline at end of file
diff --git a/en-US/Partitions_common-imagecap-1.xml b/en-US/Partitions_common-imagecap-1.xml
deleted file mode 100644
index 2f57e59..0000000
--- a/en-US/Partitions_common-imagecap-1.xml
+++ /dev/null
@@ -1,9 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-<para>
-	Image of an unused disk drive.
-</para>
\ No newline at end of file
diff --git a/en-US/Partitions_common-imagecap-10.xml b/en-US/Partitions_common-imagecap-10.xml
deleted file mode 100644
index 0fb476d..0000000
--- a/en-US/Partitions_common-imagecap-10.xml
+++ /dev/null
@@ -1,10 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<para>
-	Image of a disk drive being destructively repartitioned, where <wordasword>1</wordasword> represents before and <wordasword>2</wordasword> represents after.
-									</para>
\ No newline at end of file
diff --git a/en-US/Partitions_common-imagecap-2.xml b/en-US/Partitions_common-imagecap-2.xml
deleted file mode 100644
index 045dcb7..0000000
--- a/en-US/Partitions_common-imagecap-2.xml
+++ /dev/null
@@ -1,9 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-<para>
-	Image of a formatted disk drive.
-</para>
\ No newline at end of file
diff --git a/en-US/Partitions_common-imagecap-3.xml b/en-US/Partitions_common-imagecap-3.xml
deleted file mode 100644
index 4e0c06d..0000000
--- a/en-US/Partitions_common-imagecap-3.xml
+++ /dev/null
@@ -1,9 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-<para>
-	Image of a disk drive with a different file system.
-</para>
\ No newline at end of file
diff --git a/en-US/Partitions_common-imagecap-4.xml b/en-US/Partitions_common-imagecap-4.xml
deleted file mode 100644
index 251d12a..0000000
--- a/en-US/Partitions_common-imagecap-4.xml
+++ /dev/null
@@ -1,9 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-<para>
-	Image of a disk drive with data written to it.
-</para>
\ No newline at end of file
diff --git a/en-US/Partitions_common-imagecap-5.xml b/en-US/Partitions_common-imagecap-5.xml
deleted file mode 100644
index aaeee3a..0000000
--- a/en-US/Partitions_common-imagecap-5.xml
+++ /dev/null
@@ -1,9 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-<para>
-	Image of an unused disk drive with a partition table.
-</para>
\ No newline at end of file
diff --git a/en-US/Partitions_common-imagecap-6.xml b/en-US/Partitions_common-imagecap-6.xml
deleted file mode 100644
index da8e6b6..0000000
--- a/en-US/Partitions_common-imagecap-6.xml
+++ /dev/null
@@ -1,9 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-<para>
-	Image of a disk drive with a single partition.
-</para>
\ No newline at end of file
diff --git a/en-US/Partitions_common-imagecap-7.xml b/en-US/Partitions_common-imagecap-7.xml
deleted file mode 100644
index 4cfd999..0000000
--- a/en-US/Partitions_common-imagecap-7.xml
+++ /dev/null
@@ -1,9 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-<para>
-	Image of a disk drive with an extended partition.
-</para>
\ No newline at end of file
diff --git a/en-US/Partitions_common-imagecap-8.xml b/en-US/Partitions_common-imagecap-8.xml
deleted file mode 100644
index 204fbfe..0000000
--- a/en-US/Partitions_common-imagecap-8.xml
+++ /dev/null
@@ -1,9 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-<para>
-	Image of a disk drive with unpartitioned free space, where <wordasword>1</wordasword> represents an undefined partition with unallocated space and <wordasword>2</wordasword> represents a defined partition with allocated space.
-</para>
\ No newline at end of file
diff --git a/en-US/Partitions_common-imagecap-9.xml b/en-US/Partitions_common-imagecap-9.xml
deleted file mode 100644
index fda16f1..0000000
--- a/en-US/Partitions_common-imagecap-9.xml
+++ /dev/null
@@ -1,9 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-<para>
-	Image of a disk drive with an unused partition, where <wordasword>1</wordasword> represents an unused partition and <wordasword>2</wordasword> represents reallocating an unused partition for Linux.
-</para>
\ No newline at end of file
diff --git a/en-US/Partitions_common-indexterm-1.xml b/en-US/Partitions_common-indexterm-1.xml
deleted file mode 100644
index 076aba6..0000000
--- a/en-US/Partitions_common-indexterm-1.xml
+++ /dev/null
@@ -1,11 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE indexterm PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<indexterm significance="normal">
-	<primary>partitioning</primary>
-	<secondary>basic concepts</secondary>
-</indexterm>
\ No newline at end of file
diff --git a/en-US/Partitions_common-indexterm-10.xml b/en-US/Partitions_common-indexterm-10.xml
deleted file mode 100644
index 100abad..0000000
--- a/en-US/Partitions_common-indexterm-10.xml
+++ /dev/null
@@ -1,11 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE indexterm PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<indexterm significance="normal">
-	<primary>hard disk</primary>
-	<secondary>partition types</secondary>
-</indexterm>
\ No newline at end of file
diff --git a/en-US/Partitions_common-indexterm-11.xml b/en-US/Partitions_common-indexterm-11.xml
deleted file mode 100644
index b684c8f..0000000
--- a/en-US/Partitions_common-indexterm-11.xml
+++ /dev/null
@@ -1,11 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE indexterm PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<indexterm significance="normal">
-	<primary>partitioning</primary>
-	<secondary>types of partitions</secondary>
-</indexterm>
diff --git a/en-US/Partitions_common-indexterm-12.xml b/en-US/Partitions_common-indexterm-12.xml
deleted file mode 100644
index c5b93a1..0000000
--- a/en-US/Partitions_common-indexterm-12.xml
+++ /dev/null
@@ -1,11 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE indexterm PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<indexterm significance="normal">
-	<primary>hard disk</primary>
-	<secondary>extended partitions</secondary>
-</indexterm>
\ No newline at end of file
diff --git a/en-US/Partitions_common-indexterm-13.xml b/en-US/Partitions_common-indexterm-13.xml
deleted file mode 100644
index 421a3fd..0000000
--- a/en-US/Partitions_common-indexterm-13.xml
+++ /dev/null
@@ -1,10 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE indexterm PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<indexterm significance="normal">
-	<primary>extended partitions</primary>
-</indexterm>
\ No newline at end of file
diff --git a/en-US/Partitions_common-indexterm-14.xml b/en-US/Partitions_common-indexterm-14.xml
deleted file mode 100644
index a2ce6c7..0000000
--- a/en-US/Partitions_common-indexterm-14.xml
+++ /dev/null
@@ -1,11 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE indexterm PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<indexterm significance="normal">
-	<primary>partition</primary>
-	<secondary>extended</secondary>
-</indexterm>
\ No newline at end of file
diff --git a/en-US/Partitions_common-indexterm-15.xml b/en-US/Partitions_common-indexterm-15.xml
deleted file mode 100644
index 6e6e98d..0000000
--- a/en-US/Partitions_common-indexterm-15.xml
+++ /dev/null
@@ -1,11 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE indexterm PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<indexterm significance="normal">
-	<primary>partitioning</primary>
-	<secondary>extended partitions</secondary>
-</indexterm>
\ No newline at end of file
diff --git a/en-US/Partitions_common-indexterm-16.xml b/en-US/Partitions_common-indexterm-16.xml
deleted file mode 100644
index 87683ba..0000000
--- a/en-US/Partitions_common-indexterm-16.xml
+++ /dev/null
@@ -1,11 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE indexterm PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<indexterm significance="normal">
-	<primary>partitioning</primary>
-	<secondary>making room for partitions</secondary>
-</indexterm>
\ No newline at end of file
diff --git a/en-US/Partitions_common-indexterm-17.xml b/en-US/Partitions_common-indexterm-17.xml
deleted file mode 100644
index dfa68d4..0000000
--- a/en-US/Partitions_common-indexterm-17.xml
+++ /dev/null
@@ -1,11 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE indexterm PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<indexterm significance="normal">
-	<primary>partitioning</primary>
-	<secondary>using free space</secondary>
-</indexterm>
\ No newline at end of file
diff --git a/en-US/Partitions_common-indexterm-18.xml b/en-US/Partitions_common-indexterm-18.xml
deleted file mode 100644
index 89b4f2b..0000000
--- a/en-US/Partitions_common-indexterm-18.xml
+++ /dev/null
@@ -1,11 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE indexterm PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<indexterm significance="normal">
-	<primary>partitioning</primary>
-	<secondary>using unused partition</secondary>
-</indexterm>
\ No newline at end of file
diff --git a/en-US/Partitions_common-indexterm-19.xml b/en-US/Partitions_common-indexterm-19.xml
deleted file mode 100644
index 0f87791..0000000
--- a/en-US/Partitions_common-indexterm-19.xml
+++ /dev/null
@@ -1,11 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE indexterm PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<indexterm significance="normal">
-	<primary>partitioning</primary>
-	<secondary>using in-use partition</secondary>
-</indexterm>
\ No newline at end of file
diff --git a/en-US/Partitions_common-indexterm-2.xml b/en-US/Partitions_common-indexterm-2.xml
deleted file mode 100644
index 2986469..0000000
--- a/en-US/Partitions_common-indexterm-2.xml
+++ /dev/null
@@ -1,11 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE indexterm PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<indexterm significance="normal">
-	<primary>hard disk</primary>
-	<secondary>partitioning of</secondary>
-</indexterm>
\ No newline at end of file
diff --git a/en-US/Partitions_common-indexterm-3.xml b/en-US/Partitions_common-indexterm-3.xml
deleted file mode 100644
index 7b6ee63..0000000
--- a/en-US/Partitions_common-indexterm-3.xml
+++ /dev/null
@@ -1,11 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE indexterm PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<indexterm significance="normal">
-	<primary>hard disk</primary>
-	<secondary>basic concepts</secondary>
-</indexterm>
\ No newline at end of file
diff --git a/en-US/Partitions_common-indexterm-4.xml b/en-US/Partitions_common-indexterm-4.xml
deleted file mode 100644
index bd8ab08..0000000
--- a/en-US/Partitions_common-indexterm-4.xml
+++ /dev/null
@@ -1,11 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE indexterm PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<indexterm significance="normal">
-	<primary>hard disk</primary>
-	<secondary>file system formats</secondary>
-</indexterm>
\ No newline at end of file
diff --git a/en-US/Partitions_common-indexterm-5.xml b/en-US/Partitions_common-indexterm-5.xml
deleted file mode 100644
index 6793843..0000000
--- a/en-US/Partitions_common-indexterm-5.xml
+++ /dev/null
@@ -1,11 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE indexterm PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<indexterm significance="normal">
-	<primary>file system</primary>
-	<secondary>formats, overview of</secondary>
-</indexterm>
\ No newline at end of file
diff --git a/en-US/Partitions_common-indexterm-6.xml b/en-US/Partitions_common-indexterm-6.xml
deleted file mode 100644
index b4423ec..0000000
--- a/en-US/Partitions_common-indexterm-6.xml
+++ /dev/null
@@ -1,11 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE indexterm PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<indexterm significance="normal">
-	<primary>hard disk</primary>
-	<secondary>partition introduction</secondary>
-</indexterm>
diff --git a/en-US/Partitions_common-indexterm-7.xml b/en-US/Partitions_common-indexterm-7.xml
deleted file mode 100644
index 440a855..0000000
--- a/en-US/Partitions_common-indexterm-7.xml
+++ /dev/null
@@ -1,11 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE indexterm PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<indexterm significance="normal">
-	<primary>partitioning</primary>
-	<secondary>introduction to</secondary>
-</indexterm>
\ No newline at end of file
diff --git a/en-US/Partitions_common-indexterm-8.xml b/en-US/Partitions_common-indexterm-8.xml
deleted file mode 100644
index b51153a..0000000
--- a/en-US/Partitions_common-indexterm-8.xml
+++ /dev/null
@@ -1,11 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE indexterm PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<indexterm significance="normal">
-	<primary>partitioning</primary>
-	<secondary>how many partitions</secondary>
-</indexterm>
diff --git a/en-US/Partitions_common-indexterm-9.xml b/en-US/Partitions_common-indexterm-9.xml
deleted file mode 100644
index 3a4d3bb..0000000
--- a/en-US/Partitions_common-indexterm-9.xml
+++ /dev/null
@@ -1,11 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE indexterm PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<indexterm significance="normal">
-	<primary>partitioning</primary>
-	<secondary>primary partitions</secondary>
-</indexterm>
\ No newline at end of file
diff --git a/en-US/Partitions_common-itemizedlist-1.xml b/en-US/Partitions_common-itemizedlist-1.xml
deleted file mode 100644
index 75792d0..0000000
--- a/en-US/Partitions_common-itemizedlist-1.xml
+++ /dev/null
@@ -1,24 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE itemizedlist PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<itemizedlist mark="bullet">
-	<listitem>
-		<para>
-			A small percentage of the drive's available space is used to store file system-related data and can be considered as overhead.
-		</para>
-	</listitem>
-
-	<listitem>
-		<para>
-			A file system splits the remaining space into small, consistently-sized segments. For Linux, these segments are known as <firstterm>blocks</firstterm>. <footnote>
-			<para>
-				Blocks really <emphasis>are</emphasis> consistently sized, unlike our illustrations. Keep in mind, also, that an average disk drive contains thousands of blocks. But for the purposes of this discussion, please ignore these minor discrepancies.
-			</para>
-			</footnote>
-		</para>
-	</listitem>
-</itemizedlist>
\ No newline at end of file
diff --git a/en-US/Partitions_common-itemizedlist-2.xml b/en-US/Partitions_common-itemizedlist-2.xml
deleted file mode 100644
index b1aea0e..0000000
--- a/en-US/Partitions_common-itemizedlist-2.xml
+++ /dev/null
@@ -1,26 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE itemizedlist PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<itemizedlist mark="bullet">
-	<listitem>
-		<para>
-			The points on the disk where the partition starts and ends
-		</para>
-	</listitem>
-	
-	<listitem>
-		<para>
-			Whether the partition is "active"
-		</para>
-	</listitem>
-	
-	<listitem>
-		<para>
-			The partition's type
-		</para>
-	</listitem>
-</itemizedlist>
\ No newline at end of file
diff --git a/en-US/Partitions_common-itemizedlist-3.xml b/en-US/Partitions_common-itemizedlist-3.xml
deleted file mode 100644
index 22f09d5..0000000
--- a/en-US/Partitions_common-itemizedlist-3.xml
+++ /dev/null
@@ -1,26 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE itemizedlist PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<itemizedlist mark="bullet">
-	<listitem>
-		<para>
-			Unpartitioned free space is available
-		</para>
-	</listitem>
-	
-	<listitem>
-		<para>
-			An unused partition is available
-		</para>
-	</listitem>
-	
-	<listitem>
-		<para>
-			Free space in an actively used partition is available
-		</para>
-	</listitem>
-</itemizedlist>
\ No newline at end of file
diff --git a/en-US/Partitions_common-note-1.xml b/en-US/Partitions_common-note-1.xml
deleted file mode 100644
index c49ba0c..0000000
--- a/en-US/Partitions_common-note-1.xml
+++ /dev/null
@@ -1,14 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE note PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<note>
-	<title>Note</title>
-
-	<para>
-		This appendix is not necessarily applicable to non-x86-based architectures. However, the general concepts mentioned here may apply.
-	</para>
-</note>
\ No newline at end of file
diff --git a/en-US/Partitions_common-note-3.xml b/en-US/Partitions_common-note-3.xml
deleted file mode 100644
index f29b44c..0000000
--- a/en-US/Partitions_common-note-3.xml
+++ /dev/null
@@ -1,11 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE note PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<note>
-	<title>Note</title>
-
-<para>
-	Keep in mind that the following illustrations are simplified in the interest of clarity and do not reflect the exact partition layout that you encounter when actually installing Fedora.
-</para>
-</note>
\ No newline at end of file
diff --git a/en-US/Partitions_common-para-1.xml b/en-US/Partitions_common-para-1.xml
deleted file mode 100644
index d4184af..0000000
--- a/en-US/Partitions_common-para-1.xml
+++ /dev/null
@@ -1,10 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<para>
-	This appendix is not necessarily applicable to non-x86-based architectures. However, the general concepts mentioned here may apply.
-</para>
\ No newline at end of file
diff --git a/en-US/Partitions_common-para-10.xml b/en-US/Partitions_common-para-10.xml
deleted file mode 100644
index e19fc91..0000000
--- a/en-US/Partitions_common-para-10.xml
+++ /dev/null
@@ -1,10 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<para>
-	Each partition table entry contains several important characteristics of the partition:
-</para>
\ No newline at end of file
diff --git a/en-US/Partitions_common-para-11.xml b/en-US/Partitions_common-para-11.xml
deleted file mode 100644
index f2ac2d8..0000000
--- a/en-US/Partitions_common-para-11.xml
+++ /dev/null
@@ -1,11 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<para>
-	Let us take a closer look at each of these characteristics. The starting and ending points actually define the partition's size and location on the disk. The "active" flag is used by some operating systems' boot loaders. In other words, the operating
-	system in the partition that is marked "active" is booted.
-</para>
\ No newline at end of file
diff --git a/en-US/Partitions_common-para-12.xml b/en-US/Partitions_common-para-12.xml
deleted file mode 100644
index 71b9c05..0000000
--- a/en-US/Partitions_common-para-12.xml
+++ /dev/null
@@ -1,11 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<para>
-	The partition's type can be a bit confusing. The type is a number that identifies the partition's anticipated usage. If that statement sounds a bit vague, that is because the meaning of the partition type is a bit vague. Some operating systems use the
-	partition type to denote a specific file system type, to flag the partition as being associated with a particular operating system, to indicate that the partition contains a bootable operating system, or some combination of the three.
-</para>
\ No newline at end of file
diff --git a/en-US/Partitions_common-para-13.xml b/en-US/Partitions_common-para-13.xml
deleted file mode 100644
index 76633a8..0000000
--- a/en-US/Partitions_common-para-13.xml
+++ /dev/null
@@ -1,10 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<para>
-	In many cases, there is only a single partition spanning the entire disk, essentially duplicating the method used before partitions. The partition table has only one entry used, and it points to the start of the partition.
-</para>
\ No newline at end of file
diff --git a/en-US/Partitions_common-para-14.xml b/en-US/Partitions_common-para-14.xml
deleted file mode 100644
index 5746d7f..0000000
--- a/en-US/Partitions_common-para-14.xml
+++ /dev/null
@@ -1,11 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<para>
-	Of course, over time it became obvious that four partitions would not be enough. As disk drives continued to grow, it became more and more likely that a person could configure four reasonably-sized partitions and still have disk space left over. There
-	needed to be some way of creating more partitions.
-</para>
\ No newline at end of file
diff --git a/en-US/Partitions_common-para-15.xml b/en-US/Partitions_common-para-15.xml
deleted file mode 100644
index 50ff6f9..0000000
--- a/en-US/Partitions_common-para-15.xml
+++ /dev/null
@@ -1,10 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<para>
-	As this figure implies, there is a difference between primary and logical partitions &mdash; there can only be four primary partitions, but there is no fixed limit to the number of logical partitions that can exist. However, due to the way in which partitions are accessed in Linux, you should avoid defining more than 12 logical partitions on a single disk drive.
-</para>
\ No newline at end of file
diff --git a/en-US/Partitions_common-para-16.xml b/en-US/Partitions_common-para-16.xml
deleted file mode 100644
index fee1a54..0000000
--- a/en-US/Partitions_common-para-16.xml
+++ /dev/null
@@ -1,8 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-]>
-
-<para>
-	Now that we have discussed partitions in general, let us review how to use this knowledge to install Fedora.
-</para>
\ No newline at end of file
diff --git a/en-US/Partitions_common-para-17.xml b/en-US/Partitions_common-para-17.xml
deleted file mode 100644
index 48ed516..0000000
--- a/en-US/Partitions_common-para-17.xml
+++ /dev/null
@@ -1,10 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<para>
-	The following list presents some possible scenarios you may face when attempting to repartition your hard disk:
-</para>
\ No newline at end of file
diff --git a/en-US/Partitions_common-para-18.xml b/en-US/Partitions_common-para-18.xml
deleted file mode 100644
index 8ffd957..0000000
--- a/en-US/Partitions_common-para-18.xml
+++ /dev/null
@@ -1,10 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<para>
-	Let us look at each scenario in order.
-</para>
\ No newline at end of file
diff --git a/en-US/Partitions_common-para-19.xml b/en-US/Partitions_common-para-19.xml
deleted file mode 100644
index ccdaabc..0000000
--- a/en-US/Partitions_common-para-19.xml
+++ /dev/null
@@ -1,10 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<para>
-	If you think about it, an unused hard disk also falls into this category. The only difference is that <emphasis>all</emphasis> the space is not part of any defined partition.
-</para>
\ No newline at end of file
diff --git a/en-US/Partitions_common-para-2.xml b/en-US/Partitions_common-para-2.xml
deleted file mode 100644
index ba5396f..0000000
--- a/en-US/Partitions_common-para-2.xml
+++ /dev/null
@@ -1,10 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<para>
-	Hard disks perform a very simple function &mdash; they store data and reliably retrieve it on command.
-</para>
\ No newline at end of file
diff --git a/en-US/Partitions_common-para-20.xml b/en-US/Partitions_common-para-20.xml
deleted file mode 100644
index 458ceea..0000000
--- a/en-US/Partitions_common-para-20.xml
+++ /dev/null
@@ -1,10 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<para>
-	Next, we will discuss a slightly more common situation.
-</para>
\ No newline at end of file
diff --git a/en-US/Partitions_common-para-21.xml b/en-US/Partitions_common-para-21.xml
deleted file mode 100644
index 33ff356..0000000
--- a/en-US/Partitions_common-para-21.xml
+++ /dev/null
@@ -1,11 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<para>
-	If you find yourself in this situation, you can use the space allocated to the unused partition. You first must delete the partition and then create the appropriate Linux partition(s) in its place. You can delete the unused partition and manually
-	create new partitions during the installation process.
-</para>
\ No newline at end of file
diff --git a/en-US/Partitions_common-para-22.xml b/en-US/Partitions_common-para-22.xml
deleted file mode 100644
index 27aa8e8..0000000
--- a/en-US/Partitions_common-para-22.xml
+++ /dev/null
@@ -1,11 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<para>
-	This is the most common situation. It is also, unfortunately, the hardest to handle. The main problem is that, even if you have enough free space, it is presently allocated to a partition that is already in use. If you purchased a computer with
-	pre-installed software, the hard disk most likely has one massive partition holding the operating system and data.
-</para>
\ No newline at end of file
diff --git a/en-US/Partitions_common-para-23.xml b/en-US/Partitions_common-para-23.xml
deleted file mode 100644
index fd940bc..0000000
--- a/en-US/Partitions_common-para-23.xml
+++ /dev/null
@@ -1,10 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<para>
-	Aside from adding a new hard drive to your system, you have two choices:
-</para>
\ No newline at end of file
diff --git a/en-US/Partitions_common-para-24.xml b/en-US/Partitions_common-para-24.xml
deleted file mode 100644
index b8be00f..0000000
--- a/en-US/Partitions_common-para-24.xml
+++ /dev/null
@@ -1,11 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<para>
-	Basically, you delete the single large partition and create several smaller ones. As you might imagine, any data you had in the original partition is destroyed. This means that making a complete backup is necessary. For your own sake, make two
-	backups, use verification (if available in your backup software), and try to read data from your backup <emphasis>before</emphasis> you delete the partition.
-</para>
\ No newline at end of file
diff --git a/en-US/Partitions_common-para-3.xml b/en-US/Partitions_common-para-3.xml
deleted file mode 100644
index df3c8be..0000000
--- a/en-US/Partitions_common-para-3.xml
+++ /dev/null
@@ -1,10 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<para>
-	Not much to look at, is it? But if we are talking about disk drives on a basic level, it is adequate. Say that we would like to store some data on this drive. As things stand now, it will not work. There is something we need to do first.
-</para>
\ No newline at end of file
diff --git a/en-US/Partitions_common-para-4.xml b/en-US/Partitions_common-para-4.xml
deleted file mode 100644
index 6c5e2fe..0000000
--- a/en-US/Partitions_common-para-4.xml
+++ /dev/null
@@ -1,11 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<para>
-	Experienced computer users probably got this one on the first try. We need to <firstterm>format</firstterm> the drive. Formatting (usually known as "making a <firstterm>file system</firstterm>") writes information to the drive, creating order out of
-	the empty space in an unformatted drive.
-</para>
\ No newline at end of file
diff --git a/en-US/Partitions_common-para-5.xml b/en-US/Partitions_common-para-5.xml
deleted file mode 100644
index 6bec429..0000000
--- a/en-US/Partitions_common-para-5.xml
+++ /dev/null
@@ -1,10 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<para>
-	Given that file systems make things like directories and files possible, these trade-offs are usually seen as a small price to pay.
-</para>
\ No newline at end of file
diff --git a/en-US/Partitions_common-para-6.xml b/en-US/Partitions_common-para-6.xml
deleted file mode 100644
index 6e506df..0000000
--- a/en-US/Partitions_common-para-6.xml
+++ /dev/null
@@ -1,10 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<para>
-	Of course, writing a file system to disk is only the beginning. The goal of this process is to actually <emphasis>store</emphasis> and <emphasis>retrieve</emphasis> data. Let us take a look at our drive after some files have been written to it.
-</para>
\ No newline at end of file
diff --git a/en-US/Partitions_common-para-7.xml b/en-US/Partitions_common-para-7.xml
deleted file mode 100644
index fcfbad2..0000000
--- a/en-US/Partitions_common-para-7.xml
+++ /dev/null
@@ -1,10 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<para>
-	As with most computer-related technologies, disk drives changed over time after their introduction. In particular, they got bigger. Not larger in physical size, but bigger in their capacity to store information. And, this additional capacity drove a fundamental change in the way disk drives were used.
-</para>
\ No newline at end of file
diff --git a/en-US/Partitions_common-para-8.xml b/en-US/Partitions_common-para-8.xml
deleted file mode 100644
index 18144fd..0000000
--- a/en-US/Partitions_common-para-8.xml
+++ /dev/null
@@ -1,10 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<para>
-	As disk drive capacities soared, some people began to wonder if having all of that formatted space in one big chunk was such a great idea. This line of thinking was driven by several issues, some philosophical, some technical. On the philosophical side, above a certain size, it seemed that the additional space provided by a larger drive created more clutter. On the technical side, some file systems were never designed to support anything above a certain capacity. Or the file systems <emphasis>could</emphasis> support larger drives with a greater capacity, but the overhead imposed by the file system to track files became excessive.
-</para>
\ No newline at end of file
diff --git a/en-US/Partitions_common-para-9.xml b/en-US/Partitions_common-para-9.xml
deleted file mode 100644
index 2545def..0000000
--- a/en-US/Partitions_common-para-9.xml
+++ /dev/null
@@ -1,10 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<para>
-	The solution to this problem was to divide disks into <firstterm>partitions</firstterm>. Each partition can be accessed as if it was a separate disk. This is done through the addition of a <firstterm>partition table</firstterm>.
-</para>
\ No newline at end of file
diff --git a/en-US/Partitions_common-table-title-1.xml b/en-US/Partitions_common-table-title-1.xml
deleted file mode 100644
index fe05457..0000000
--- a/en-US/Partitions_common-table-title-1.xml
+++ /dev/null
@@ -1,8 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE title PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<title>Partition Types</title>
\ No newline at end of file
diff --git a/en-US/Partitions_common-term-1.xml b/en-US/Partitions_common-term-1.xml
deleted file mode 100644
index c7b451b..0000000
--- a/en-US/Partitions_common-term-1.xml
+++ /dev/null
@@ -1,12 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE term PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<term>						<indexterm significance="normal">
-		<primary>partitioning</primary>
-		<secondary>destructive</secondary>
-	</indexterm>
-<emphasis>Destructive Repartitioning</emphasis></term>
\ No newline at end of file
diff --git a/en-US/Partitions_common-title-10.xml b/en-US/Partitions_common-title-10.xml
deleted file mode 100644
index 6232af3..0000000
--- a/en-US/Partitions_common-title-10.xml
+++ /dev/null
@@ -1,8 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE title PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<title>Disk Drive Being Destructively Repartitioned</title>
\ No newline at end of file
diff --git a/en-US/Partitions_common-title-2.xml b/en-US/Partitions_common-title-2.xml
deleted file mode 100644
index cc27ae7..0000000
--- a/en-US/Partitions_common-title-2.xml
+++ /dev/null
@@ -1,8 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE title PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<title>Hard Disk Basic Concepts</title>
\ No newline at end of file
diff --git a/en-US/Partitions_common-title-3.xml b/en-US/Partitions_common-title-3.xml
deleted file mode 100644
index 1013cca..0000000
--- a/en-US/Partitions_common-title-3.xml
+++ /dev/null
@@ -1,8 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE title PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<title>It is Not What You Write, it is How You Write It</title>
\ No newline at end of file
diff --git a/en-US/Partitions_common-title-4.xml b/en-US/Partitions_common-title-4.xml
deleted file mode 100644
index afb506b..0000000
--- a/en-US/Partitions_common-title-4.xml
+++ /dev/null
@@ -1,8 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE title PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<title>Partitions: Turning One Drive Into Many</title>
\ No newline at end of file
diff --git a/en-US/Partitions_common-title-5.xml b/en-US/Partitions_common-title-5.xml
deleted file mode 100644
index 20cfc3f..0000000
--- a/en-US/Partitions_common-title-5.xml
+++ /dev/null
@@ -1,8 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE title PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<title>Partitions within Partitions &mdash; An Overview of Extended Partitions</title>
\ No newline at end of file
diff --git a/en-US/Partitions_common-title-6.xml b/en-US/Partitions_common-title-6.xml
deleted file mode 100644
index c84103c..0000000
--- a/en-US/Partitions_common-title-6.xml
+++ /dev/null
@@ -1,5 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE title PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<title>Making Room For Fedora</title>
\ No newline at end of file
diff --git a/en-US/Partitions_common-title-7.xml b/en-US/Partitions_common-title-7.xml
deleted file mode 100644
index 16168c3..0000000
--- a/en-US/Partitions_common-title-7.xml
+++ /dev/null
@@ -1,8 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE title PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<title>Using Unpartitioned Free Space</title>
\ No newline at end of file
diff --git a/en-US/Partitions_common-title-8.xml b/en-US/Partitions_common-title-8.xml
deleted file mode 100644
index 42281e3..0000000
--- a/en-US/Partitions_common-title-8.xml
+++ /dev/null
@@ -1,8 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE title PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<title>Using Space from an Unused Partition</title>
\ No newline at end of file
diff --git a/en-US/Partitions_common-title-9.xml b/en-US/Partitions_common-title-9.xml
deleted file mode 100644
index 688d027..0000000
--- a/en-US/Partitions_common-title-9.xml
+++ /dev/null
@@ -1,8 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE title PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<title>Using Free Space from an Active Partition</title>
\ No newline at end of file
diff --git a/en-US/Partitions_common-title.xml b/en-US/Partitions_common-title.xml
deleted file mode 100644
index b13122d..0000000
--- a/en-US/Partitions_common-title.xml
+++ /dev/null
@@ -1,8 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE title PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<title>An Introduction to Disk Partitions</title>
\ No newline at end of file
diff --git a/en-US/Partitions_complete-note-1.xml b/en-US/Partitions_complete-note-1.xml
deleted file mode 100644
index c686f55..0000000
--- a/en-US/Partitions_complete-note-1.xml
+++ /dev/null
@@ -1,14 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE note PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<note>
-	<title>Note</title>
-
-	<para>
-		While the diagrams in this chapter show the partition table as being separate from the actual disk drive, this is not entirely accurate. In reality, the partition table is stored at the very start of the disk, before any file system or user data. But for clarity, they are separate in our diagrams.
-	</para>
-</note>
\ No newline at end of file
diff --git a/en-US/Preface.xml b/en-US/Preface.xml
deleted file mode 100644
index 0c4f452..0000000
--- a/en-US/Preface.xml
+++ /dev/null
@@ -1,13 +0,0 @@
-<?xml version='1.0'?>
-<!DOCTYPE preface PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
-]>
-
-<preface id="Installation-Guide-Preface">
-	<title>Preface</title>
-	<xi:include href="Common_Content/Conventions.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
-	<xi:include href="Feedback.xml" xmlns:xi="http://www.w3.org/2001/XInclude">
-		<xi:fallback xmlns:xi="http://www.w3.org/2001/XInclude">
-			<xi:include href="Common_Content/Feedback.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
-		</xi:fallback>
-	</xi:include>
-</preface>
diff --git a/en-US/Prepare_To_Install-common-Boot_Media.xml b/en-US/Prepare_To_Install-common-Boot_Media.xml
deleted file mode 100644
index 04acbc8..0000000
--- a/en-US/Prepare_To_Install-common-Boot_Media.xml
+++ /dev/null
@@ -1,8 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
-
-]>
-
-<para>
-	Ensure that you have boot media available on CD, DVD, or a USB storage device such as a flash drive. 
-</para>
\ No newline at end of file
diff --git a/en-US/Procedure-dd_Image_to_USB.xml b/en-US/Procedure-dd_Image_to_USB.xml
deleted file mode 100644
index 8e08ca9..0000000
--- a/en-US/Procedure-dd_Image_to_USB.xml
+++ /dev/null
@@ -1,30 +0,0 @@
-<?xml version='1.0' encoding='utf-8' ?>
-<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
-]>
-
-<procedure>
-	<step>
-		<para>
-			Plug in your USB media.
-		</para>
-	</step>
-	<step>
-		<para>
-			Find the device name for your USB media.  If the media has a volume name, look up the name in <filename class="directory">/dev/disk/by-label</filename>, or use the <command>findfs</command>:
-		</para>
-<screen><command>su -c 'findfs LABEL="<replaceable>MyLabel</replaceable>"'</command></screen>
-		<para>
-			If the media does not have a volume name, or you do not know it, consult the <filename>/var/log/messages</filename> log for details:
-		</para>
-<screen><command>su -c 'less /var/log/messages'</command></screen>
-	</step>
-	<step>
-		<para>
-			Use the <command>dd</command> command to write the ISO image to the media:
-		</para>
-<screen><command>su -c 'dd if=<replaceable>/path/to/image/file/imagefile.iso</replaceable> of=<replaceable>device</replaceable>'</command></screen>
-		<para>
-		where <filename><replaceable>/path/to/image/file</replaceable></filename> is the location of the image file that you downloaded and <filename><replaceable>device</replaceable></filename> is the USB media device.
-		</para>
-	</step>
-</procedure>
diff --git a/en-US/Rescue_Mode.xml b/en-US/Rescue_Mode.xml
deleted file mode 100644
index c14ec9c..0000000
--- a/en-US/Rescue_Mode.xml
+++ /dev/null
@@ -1,400 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<chapter id="ap-rescuemode"><title>Basic System Recovery</title>
-	<indexterm significance="normal">
-		<primary>system recovery</primary>
-	</indexterm>
-
-	<para>
-		When things go wrong, there are ways to fix problems. However, these methods require that you understand the system well. This chapter describes how to boot into rescue mode, single-user mode, and emergency mode, where you can use your own knowledge to
-		repair the system.
-	</para>
-	<section id="s1-rescuemode-common-problems">
-		<title>Common Problems</title>
-		<indexterm significance="normal">
-			<primary>system recovery</primary>
-			<secondary>common problems</secondary>
-		</indexterm>
-		<para>
-			You might need to boot into one of these recovery modes for any of the following reasons:
-		</para>
-		 
-		<itemizedlist>
-			<listitem>
-				<para>
-					You are unable to boot normally into Fedora (runlevel 3 or 5).
-				</para>
-			</listitem>
-
-			<listitem>
-				<para>
-					You are having hardware or software problems, and you want to get a few important files off of your system's hard drive.
-				</para>
-			</listitem>
-
-			<listitem>
-				<para>
-					You forgot the root password.
-				</para>
-			</listitem>
-		</itemizedlist>
-		 
-		<section id="s2-rescuemode-whatis-unable-boot">
-			<title>Unable to Boot into Fedora</title>
-			<indexterm significance="normal">
-				<primary>system recovery</primary>
-				<secondary>common problems</secondary>
-				<tertiary>unable to boot into Fedora</tertiary>
-			</indexterm>
-			<indexterm significance="normal">
-				<primary>Master Boot Record</primary>
-			</indexterm>
-			<para>
-				This problem is often caused by the installation of another operating system after you have installed Fedora. Some other operating systems assume that you have no other operating system(s) on your computer. They overwrite the Master
-				Boot Record (MBR) that originally contained the GRUB boot loader. If the boot loader is overwritten in this manner, you cannot boot Fedora unless you can get into rescue mode and reconfigure the boot loader.
-			</para>
-			 
-			<para>
-				Another common problem occurs when using a partitioning tool to resize a partition or create a new partition from free space after installation, and it changes the order of your partitions. If the partition number of your
-				<filename>/</filename> partition changes, the boot loader might not be able to find it to mount the partition. To fix this problem, boot in rescue mode and modify the <filename>/boot/grub/grub.conf</filename> file.
-			</para>
-			 
-			<para>
-				For instructions on how to reinstall the GRUB boot loader from a rescue environment, refer to <xref linkend="s2-rescuemode-boot-reinstall-bootloader"/>.
-			</para>
-		</section>
-		 
-		<section id="s2-rescuemode-hardware-troubles">
-			<title>Hardware/Software Problems</title>
-			<indexterm significance="normal">
-				<primary>system recovery</primary>
-				<secondary>common problems</secondary>
-				<tertiary>hardware/software problems</tertiary>
-			</indexterm>
-			<para>
-				This category includes a wide variety of different situations. Two examples include failing hard drives and specifying an invalid root device or kernel in the boot loader configuration file. If either of these occur, you might not be able to reboot
-				into Fedora. However, if you boot into one of the system recovery modes, you might be able to resolve the problem or at least get copies of your most important files.
-			</para>
-		</section>
-		 
-		<section id="s2-rescuemode-root-password">
-			<title>Root Password</title>
-			<indexterm significance="normal">
-				<primary>system recovery</primary>
-				<secondary>common problems</secondary>
-				<tertiary>forgetting the root password</tertiary>
-			</indexterm>
-			<para>
-				What can you do if you forget your root password? To reset it to a different password, boot into rescue mode or single-user mode, and use the <command>passwd</command> command to reset the root password.
-			</para>
-		</section>
-	</section>
-	<section id="s1-rescuemode-boot">
-		<title>Booting into Rescue Mode</title>
-		<indexterm significance="normal">
-			<primary>rescue mode</primary>
-			<secondary>definition of</secondary>
-		</indexterm>
-		<para>
-			Rescue mode provides the ability to boot a small Fedora environment entirely from CD-ROM, or some other boot method, instead of the system's hard drive.
-		</para>
-		 
-		<para>
-			As the name implies, rescue mode is provided to rescue you from something. During normal operation, your Fedora system uses files located on your system's hard drive to do everything &mdash; run programs, store your files, and more.
-		</para>
-		 
-		<para>
-			However, there may be times when you are unable to get Fedora running completely enough to access files on your system's hard drive. Using rescue mode, you can access the files stored on your system's hard drive, even if you cannot
-			actually run Fedora from that hard drive.
-		</para>
-		<indexterm significance="normal">
-			<primary>booting</primary>
-			<secondary>rescue mode</secondary>
-		</indexterm>
-		<para>
-			To boot into rescue mode, you must be able to boot the system using one of the following methods<footnote id="boot-media">
-			<para>
-				Refer to the earlier sections of this guide for more details.
-			</para>
-			</footnote>:
-		</para>
-		 
-		<itemizedlist>
-			<listitem>
-				<para>
-					By booting the system from an installation boot CD-ROM or DVD.
-				</para>
-			</listitem>
-
-			<listitem>
-				<para>
-					By booting the system from other installation boot media, such as USB flash devices.
-				</para>
-			</listitem>
-
-			<listitem>
-				<para>
-					By booting the system from the Fedora CD-ROM #1 or DVD.
-				</para>
-			</listitem>
-		</itemizedlist>
-		 
-		<para>
-			Once you have booted using one of the described methods, add the keyword <userinput>rescue</userinput> as a kernel parameter. For example, for an x86 system, type the following command at the installation boot prompt:
-		</para>
-<screen>
-<userinput>linux rescue</userinput>
-</screen>
-		<para>
-			You are prompted to answer a few basic questions, including which language to use. It also prompts you to select where a valid rescue image is located. Select from <guilabel>Local CD-ROM</guilabel>, <guilabel>Hard
-			Drive</guilabel>, <guilabel>NFS image</guilabel>, <guilabel>FTP</guilabel>, or <guilabel>HTTP</guilabel>. The location selected must contain a valid installation tree, and the installation tree must be for
-			the same version of Fedora as the Fedora disk from which you booted. If you used a boot CD-ROM or other media to start rescue mode, the installation tree must be from the same tree from which the media was created. For more information about how to setup an installation tree on a hard drive, NFS server, FTP server, or HTTP server, refer to the earlier section of this guide.
-		</para>
-		 
-		<para>
-			If you select a rescue image that does not require a network connection, you are asked whether or not you want to establish a network connection. A network connection is useful if you need to backup files to a different computer or install some RPM
-			packages from a shared network location, for example.
-		</para>
-		 
-		<para>
-			The following message is displayed:
-		</para>
-<blockquote><para>The rescue environment will now attempt to find your Linux installation and mount it under the directory /mnt/sysimage.  You can then make any changes required to your system.  If you want to proceed with this step choose 'Continue'. You can also choose to mount your file systems read-only instead of read-write by choosing 'Read-only'.  If for some reason this process fails you can choose 'Skip' and this step will be skipped and you will go directly to a command shell.</para></blockquote>
-
-		<para>
-			If you select <guibutton>Continue</guibutton>, it attempts to mount your file system under the directory <filename>/mnt/sysimage/</filename>. If it fails to mount a partition, it notifies you. If you select
-			<guibutton>Read-Only</guibutton>, it attempts to mount your file system under the directory <filename>/mnt/sysimage/</filename>, but in read-only mode. If you select <guibutton>Skip</guibutton>, your file
-			system is not mounted. Choose <guibutton>Skip</guibutton> if you think your file system is corrupted.
-		</para>
-		 
-		<para>
-			Once you have your system in rescue mode, a prompt appears on VC (virtual console) 1 and VC 2 (use the <keycap>Ctrl</keycap>-<keycap>Alt</keycap>-<keycap>F1</keycap> key combination to access VC 1 and
-			<keycap>Ctrl</keycap>-<keycap>Alt</keycap>-<keycap>F2</keycap> to access VC 2):
-		</para>
-<screen>
-<prompt>sh-3.00b#</prompt>
-</screen>
-		<para>
-			If you selected <guibutton>Continue</guibutton> to mount your partitions automatically and they were mounted successfully, you are in single-user mode.
-		</para>
-		 
-		<para>
-			Even if your file system is mounted, the default root partition while in rescue mode is a temporary root partition, not the root partition of the file system used during normal user mode (runlevel 3 or 5). If you selected to mount your file system and
-			it mounted successfully, you can change the root partition of the rescue mode environment to the root partition of your file system by executing the following command:
-		</para>
-<screen>
-<command>chroot /mnt/sysimage</command>
-</screen>
-		<para>
-			This is useful if you need to run commands such as <command>rpm</command> that require your root partition to be mounted as <filename>/</filename>. To exit the <command>chroot</command> environment, type
-			<command>exit</command> to return to the prompt.
-		</para>
-		 
-		<para>
-			If you selected <guibutton>Skip</guibutton>, you can still try to mount a partition or LVM2 logical volume manually inside rescue mode by creating a directory such as <filename><replaceable>/foo</replaceable></filename>,
-			and typing the following command:
-		</para>
-<screen>
-<command>mount -t ext4 <replaceable>/dev/mapper/VolGroup00-LogVol02 /foo</replaceable></command>
-</screen>
-		<para>
-			In the above command, <filename><replaceable>/foo</replaceable></filename> is a directory that you have created and <command><replaceable>/dev/mapper/VolGroup00-LogVol02</replaceable></command> is the LVM2 logical volume
-			you want to mount. If the partition is of type <command>ext2</command> or <command>ext3</command> replace <command>ext4</command> with <command>ext2</command> or <command>ext3</command> respectively.
-		</para>
-		 
-		<para>
-			If you do not know the names of all physical partitions, use the following command to list them:
-		</para>
-<screen>
-<command>fdisk -l</command>
-</screen>
-		<para>
-			If you do not know the names of all LVM2 physical volumes, volume groups, or logical volumes, use the following commands to list them:
-		</para>
-<screen>
-<command>pvdisplay</command>
-</screen>
-<screen>
-<command>vgdisplay</command>
-</screen>
-<screen>
-<command>lvdisplay</command>
-</screen>
-		<indexterm significance="normal">
-			<primary>rescue mode</primary>
-			<secondary>utilities available</secondary>
-		</indexterm>
-		<para>
-			From the prompt, you can run many useful commands, such as:
-		</para>
-		 
-		<itemizedlist>
-			<listitem>
-				<para>
-					<command>ssh</command>, <command>scp</command>, and <command>ping</command> if the network is started
-				</para>
-			</listitem>
-
-			<listitem>
-				<para>
-					<command>dump</command> and <command>restore</command> for users with tape drives
-				</para>
-			</listitem>
-
-			<listitem>
-				<para>
-					<command>parted</command> and <command>fdisk</command> for managing partitions
-				</para>
-			</listitem>
-
-			<listitem>
-				<para>
-					<command>rpm</command> for installing or upgrading software
-				</para>
-			</listitem>
-
-			<listitem>
-				<para>
-					<command>joe</command> for editing configuration files
-				</para>
-
-				<note>
-					<title>Note</title>
-
-					<para>
-						If you try to start other popular editors such as <command>emacs</command>, <command>pico</command>, or <command>vi</command>, the <command>joe</command> editor is started.
-					</para>
-				</note>
-			</listitem>
-		</itemizedlist>
-		 
-		<section id="s2-rescuemode-boot-reinstall-bootloader">
-			<title>Reinstalling the Boot Loader</title>
-			<indexterm significance="normal">
-				<primary>system recovery</primary>
-				<secondary>common problems</secondary>
-				<tertiary>reinstalling the boot loader</tertiary>
-			</indexterm>
-			<indexterm significance="normal">
-				<primary>Master Boot Record</primary>
-				<secondary>reinstalling</secondary>
-			</indexterm>
-			<para>
-				In many cases, the GRUB boot loader can mistakenly be deleted, corrupted, or replaced by other operating systems.
-			</para>
-			 
-			<para>
-				The following steps detail the process on how GRUB is reinstalled on the master boot record:
-			</para>
-			 
-			<itemizedlist>
-				<listitem>
-					<para>
-						Boot the system from an installation boot medium.
-					</para>
-				</listitem>
-
-				<listitem>
-					<para>
-						Type <command>linux rescue</command> at the installation boot prompt to enter the rescue environment.
-					</para>
-				</listitem>
-
-				<listitem>
-					<para>
-						Type <command>chroot /mnt/sysimage</command> to mount the root partition.
-					</para>
-				</listitem>
-
-				<listitem>
-					<para>
-						Type <command>/sbin/grub-install <replaceable>bootpart</replaceable></command> to reinstall the GRUB boot loader, where <replaceable>bootpart</replaceable> is the boot partition (typically, /dev/sda). 
-					</para>
-				</listitem>
-
-				<listitem>
-					<para>
-						Review the <filename>/boot/grub/grub.conf</filename> file, as additional entries may be needed for GRUB to control additional operating systems.
-					</para>
-				</listitem>
-
-				<listitem>
-					<para>
-						Reboot the system.
-					</para>
-				</listitem>
-			</itemizedlist>
-		</section>
-	</section>
-	<section id="s1-rescuemode-booting-single">
-		<title>Booting into Single-User Mode</title>
-		<indexterm significance="normal">
-			<primary>booting</primary>
-			<secondary>single-user mode</secondary>
-		</indexterm>
-		<indexterm significance="normal">
-			<primary>single-user mode</primary>
-		</indexterm>
-		<indexterm significance="normal">
-			<primary>runlevel 1</primary>
-		</indexterm>
-		<para>
-			One of the advantages of single-user mode is that you do not need a boot CD-ROM; however, it does not give you the option to mount the file systems as read-only or not mount them at all.
-		</para>
-		 
-		<para>
-			If your system boots, but does not allow you to log in when it has completed booting, try single-user mode.
-		</para>
-		 
-		<para>
-			In single-user mode, your computer boots to runlevel 1. Your local file systems are mounted, but your network is not activated. You have a usable system maintenance shell. Unlike rescue mode, single-user mode automatically tries to mount your file
-			system. <emphasis>Do not use single-user mode if your file system cannot be mounted successfully.</emphasis> You cannot use single-user mode if the runlevel 1 configuration on your system is corrupted.
-		</para>
-		 
-		<para>
-			On an x86 system using GRUB, use the following steps to boot into single-user mode:
-		</para>
-		 
-		<orderedlist inheritnum="ignore" continuation="restarts">
-			<listitem>
-				<para>
-					At the GRUB splash screen at boot time, press any key to enter the GRUB interactive menu.
-				</para>
-			</listitem>
-
-			<listitem>
-				<para>
-					Select <guilabel>Fedora</guilabel> with the version of the kernel that you wish to boot and type <command>a</command> to append the line.
-				</para>
-			</listitem>
-
-			<listitem>
-				<para>
-					Go to the end of the line and type <userinput>single</userinput> as a separate word (press the <keycap>Spacebar</keycap> and then type <userinput>single</userinput>). Press
-					<keycap>Enter</keycap> to exit edit mode.
-				</para>
-			</listitem>
-		</orderedlist>
-	</section>
-	<section id="s1-rescuemode-booting-emergency">
-		<title>Booting into Emergency Mode</title>
-		<indexterm significance="normal">
-			<primary>booting</primary>
-			<secondary>emergency mode</secondary>
-		</indexterm>
-		<indexterm significance="normal">
-			<primary>emergency mode</primary>
-		</indexterm>
-		<para>
-			In emergency mode, you are booted into the most minimal environment possible. The root file system is mounted read-only and almost nothing is set up. The main advantage of emergency mode over single-user mode is that the
-			<command>init</command> files are not loaded. If <command>init</command> is corrupted or not working, you can still mount file systems to recover data that could be lost during a re-installation.
-		</para>
-		 
-		<para>
-			To boot into emergency mode, use the same method as described for single-user mode in <xref linkend="s1-rescuemode-booting-single"/> with one exception, replace the keyword <userinput>single</userinput> with the keyword
-			<userinput>emergency</userinput>.
-		</para>
-	</section>
-</chapter>
diff --git a/en-US/Revision_History.xml b/en-US/Revision_History.xml
deleted file mode 100644
index 441a05d..0000000
--- a/en-US/Revision_History.xml
+++ /dev/null
@@ -1,26 +0,0 @@
-<?xml version='1.0'?>
-<!DOCTYPE appendix PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
-]>
-
-<appendix id="appe-Publican-Revision_History">
-	<title>Revision History</title>
-	<simpara>
-		<revhistory>
-			<revision>
-				<revnumber>13.0.1</revnumber>
-				<date>Fri Apr 30 2010</date>
-				<author>
-				    <firstname>Ruediger</firstname>
-				    <surname>Landmann</surname>
-				    <email>r.landmann at redhat.com</email>
-				</author>
-				<revdescription>
-					<simplelist>
-						<member>Update for F13</member>
-					</simplelist>
-				</revdescription>
-			</revision>
-		</revhistory>
-	</simpara>
-</appendix>
-
diff --git a/en-US/Specialized_Storage_Devices-x86.xml b/en-US/Specialized_Storage_Devices-x86.xml
deleted file mode 100644
index c3bca66..0000000
--- a/en-US/Specialized_Storage_Devices-x86.xml
+++ /dev/null
@@ -1,52 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-
-<section id="sect-Storage_Device_Selection_Screen-x86">
-
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Specialized_Storage_Devices_common-title.xml"/>
-	<!-- Storage Device Selection Screen -->
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Specialized_Storage_Devices_common-para-1.xml"/>
-	<!-- The storage devices selection screen displays all storage devices to which anaconda has access. -->
-		
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Specialized_Storage_Devices_common-figure-1.xml"/>
-	<!-- Select storage devices -->
-		
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Specialized_Storage_Devices_common-para-2.xml"/>
-	<!-- Devices are grouped under the following tabs: -->
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Specialized_Storage_Devices_common-variablelist-1.xml"/>
-	<!-- Basic Devices Basic storage devices directly connected to -->
-
-	<para>
-		If you do need to configure iSCSI or FCoE storage, click <guibutton>Add Advanced Target</guibutton> and refer to <xref linkend="s1-advanced-storage-x86"/>.
-	</para>
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Specialized_Storage_Devices_common-para-3.xml"/>
-	<!-- The storage devices selection screen also contains a Search tab -->
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Specialized_Storage_Devices_common-figure-2.xml"/>
-	<!-- The Storage Devices Search Tab -->
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Specialized_Storage_Devices_common-para-4.xml"/>
-	<!-- Each tab presents a list of devices detected by anaconda, with information about the device to help you to identify it. -->
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Specialized_Storage_Devices_common-figure-3.xml"/>
-	<!-- Selecting Columns -->
-		
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Specialized_Storage_Devices_common-para-5.xml"/>
-	<!-- Each device is presented on a separate row, with a checkbox to its left. -->
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Specialized_Storage_Devices_common-para-6.xml"/>
-	<!-- Note that the devices that you select here are not automatically wiped by the installation process. -->
-	
-	<para>
-		If you selected only one storage device, click <guibutton>Next</guibutton> and proceed to <xref linkend="sn-initialize-hdd-x86"/>. If you selected two or more storage devices, click <guibutton>Next</guibutton> and proceed to <xref linkend="Assign_Storage_Devices-x86"/>.
-	</para>
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Disk_Partitioning_Advanced_Storage-x86.xml"/>
-	<!-- Advanced Storage Options -->
-	
-</section>
diff --git a/en-US/Specialized_Storage_Devices_common-figure-1.xml b/en-US/Specialized_Storage_Devices_common-figure-1.xml
deleted file mode 100644
index 1666633..0000000
--- a/en-US/Specialized_Storage_Devices_common-figure-1.xml
+++ /dev/null
@@ -1,14 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE figure PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<figure float="0"><title>Select storage devices</title>
-	<mediaobject>
-		<imageobject><imagedata fileref="images/storagedevices/selectstoragedevices.png" format="PNG"/></imageobject>
-		<textobject><para>
-				Screen to select available storage devices, with tabs for basic devices, firmware RAID, multipath devices, and other SAN devices.
-			</para>
-		</textobject>
-	</mediaobject>
-</figure>
-	
\ No newline at end of file
diff --git a/en-US/Specialized_Storage_Devices_common-figure-2.xml b/en-US/Specialized_Storage_Devices_common-figure-2.xml
deleted file mode 100644
index 1553eb5..0000000
--- a/en-US/Specialized_Storage_Devices_common-figure-2.xml
+++ /dev/null
@@ -1,14 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE figure PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<figure float="0"><title>The Storage Devices Search Tab</title>
-	<mediaobject>
-		<imageobject><imagedata fileref="images/storagedevices/searchstoragedevices.png" format="PNG"/></imageobject>
-		<textobject><para>
-				The tab contains a drop-down menu to select between searching by port, target, and LUN (with corresponding text boxes for these values) and searching by WWID (with a corresponding text box for this value).
-			</para>
-		</textobject>
-	</mediaobject>
-</figure>
-	
\ No newline at end of file
diff --git a/en-US/Specialized_Storage_Devices_common-figure-3.xml b/en-US/Specialized_Storage_Devices_common-figure-3.xml
deleted file mode 100644
index c3a3159..0000000
--- a/en-US/Specialized_Storage_Devices_common-figure-3.xml
+++ /dev/null
@@ -1,14 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE figure PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<figure float="0"><title>Selecting Columns</title>
-	<mediaobject>
-		<imageobject><imagedata fileref="images/storagedevices/storagedevicescolumns.png" format="PNG"/></imageobject>
-		<textobject><para>
-				The drop-down menu in its expanded state
-			</para>
-		</textobject>
-	</mediaobject>
-</figure>
-	
\ No newline at end of file
diff --git a/en-US/Specialized_Storage_Devices_common-para-1.xml b/en-US/Specialized_Storage_Devices_common-para-1.xml
deleted file mode 100644
index d64007b..0000000
--- a/en-US/Specialized_Storage_Devices_common-para-1.xml
+++ /dev/null
@@ -1,7 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<para>
-	The storage devices selection screen displays all storage devices to which <application>anaconda</application> has access.
-</para>
diff --git a/en-US/Specialized_Storage_Devices_common-para-2.xml b/en-US/Specialized_Storage_Devices_common-para-2.xml
deleted file mode 100644
index 1a778a9..0000000
--- a/en-US/Specialized_Storage_Devices_common-para-2.xml
+++ /dev/null
@@ -1,7 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<para>
-	Devices are grouped under the following tabs:
-</para>
diff --git a/en-US/Specialized_Storage_Devices_common-para-3.xml b/en-US/Specialized_Storage_Devices_common-para-3.xml
deleted file mode 100644
index aa0b418..0000000
--- a/en-US/Specialized_Storage_Devices_common-para-3.xml
+++ /dev/null
@@ -1,7 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<para>
-	The storage devices selection screen also contains a <guilabel>Search</guilabel> tab that allows you to filter storage devices either by their <firstterm>World Wide Identifier</firstterm> (WWID) or by the port, target, or <firstterm>logical unit number</firstterm> (LUN) at which they are accessed.
-</para>
diff --git a/en-US/Specialized_Storage_Devices_common-para-4.xml b/en-US/Specialized_Storage_Devices_common-para-4.xml
deleted file mode 100644
index 9c248c3..0000000
--- a/en-US/Specialized_Storage_Devices_common-para-4.xml
+++ /dev/null
@@ -1,7 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<para>
-	Each tab presents a list of devices detected by <application>anaconda</application>, with information about the device to help you to identify it. A small drop-down menu marked with an icon is located to the right of the column headings. This menu allows you to select the types of data presented on each device. For example, the menu on the <guilabel>Multipath Devices</guilabel> tab allows you to specify any of <guimenuitem>WWID</guimenuitem>, <guimenuitem>Capacity</guimenuitem>, <guimenuitem>Vendor</guimenuitem>, <guimenuitem>Interconnect</guimenuitem>, and <guimenuitem>Paths</guimenuitem> to include among the details presented for each device. Reducing or expanding the amount of information presented might help you to identify particular devices.
-</para>
diff --git a/en-US/Specialized_Storage_Devices_common-para-5.xml b/en-US/Specialized_Storage_Devices_common-para-5.xml
deleted file mode 100644
index 13b93d6..0000000
--- a/en-US/Specialized_Storage_Devices_common-para-5.xml
+++ /dev/null
@@ -1,7 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<para>
-	Each device is presented on a separate row, with a checkbox to its left. Click the checkbox to make a device available during the installation process, or click the <firstterm>radio button</firstterm> at the left of the column headings to select or deselect all the devices listed in a particular screen. Later in the installation process, you can choose to install Fedora onto any of the devices selected here, and can choose to automatically mount any of the other devices selected here as part of the installed system. 
-</para>
diff --git a/en-US/Specialized_Storage_Devices_common-para-6.xml b/en-US/Specialized_Storage_Devices_common-para-6.xml
deleted file mode 100644
index 85a5674..0000000
--- a/en-US/Specialized_Storage_Devices_common-para-6.xml
+++ /dev/null
@@ -1,7 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<para>
-	Note that the devices that you select here are not automatically wiped by the installation process. Selecting a device on this screen does not, in itself, place data stored on the device at risk. Note also that any devices that you do not select here to form part of the installed system can be added to the system after installation by modifying the <filename>/etc/fstab</filename> file.
-</para>
diff --git a/en-US/Specialized_Storage_Devices_common-title.xml b/en-US/Specialized_Storage_Devices_common-title.xml
deleted file mode 100644
index 0bd2b72..0000000
--- a/en-US/Specialized_Storage_Devices_common-title.xml
+++ /dev/null
@@ -1,8 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE title PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-
-<title>
-	The Storage Devices Selection Screen
-</title>
diff --git a/en-US/Specialized_Storage_Devices_common-variablelist-1.xml b/en-US/Specialized_Storage_Devices_common-variablelist-1.xml
deleted file mode 100644
index bd5e021..0000000
--- a/en-US/Specialized_Storage_Devices_common-variablelist-1.xml
+++ /dev/null
@@ -1,38 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE variablelist PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<variablelist>
-	<varlistentry>
-		<term>Basic Devices</term>
-		<listitem>
-			<para>
-				Basic storage devices directly connected to the local system, such as hard disk drives and solid-state drives.
-			</para>
-		</listitem>
-	</varlistentry>
-	<varlistentry>
-		<term>Firmware RAID</term>
-		<listitem>
-			<para>
-				Storage devices attached to a firmware RAID controller.
-			</para>
-		</listitem>
-	</varlistentry>
-	<varlistentry>
-		<term>Multipath Devices</term>
-		<listitem>
-			<para>
-				Storage devices accessible through more than one path, such as through multiple SCSI controllers or Fiber Channel ports on the same system.
-			</para>
-		</listitem>
-	</varlistentry>
-	<varlistentry>
-		<term>Other SAN Devices</term>
-		<listitem>
-			<para>
-				Any other devices available on a storage area network (SAN).
-			</para>
-		</listitem>
-	</varlistentry>
-</variablelist>
diff --git a/en-US/Steps-x86.xml b/en-US/Steps-x86.xml
deleted file mode 100644
index 218feef..0000000
--- a/en-US/Steps-x86.xml
+++ /dev/null
@@ -1,29 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<chapter id="ch-steps-x86">
-	<title>Steps to Get You Started</title>
-
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Steps_Upgrade-common.xml"/>
-	<!-- Upgrade or Install? -->
-		
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Steps_Hardware-x86.xml"/>
-	<!-- Is Your Hardware Compatible? -->
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Other_Disk_Devices-x86.xml"/>
-	<!-- RAID and Other Disk Devices -->
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Steps_Diskspace-x86.xml"/>
-	<!-- Do You Have Enough Disk Space? -->
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Steps_Cdrom-x86.xml"/>
-	<!-- Can You Install Using the CD-ROM or DVD? -->
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Steps_Network_Install-x86.xml"/>
-	<!-- Preparing for a Network Installation -->
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Steps_Hd_Install-x86.xml"/> 
-	<!-- Preparing for a Hard Drive Installation -->
-	
-</chapter>
diff --git a/en-US/Steps_Cdrom-x86.xml b/en-US/Steps_Cdrom-x86.xml
deleted file mode 100644
index 52f6098..0000000
--- a/en-US/Steps_Cdrom-x86.xml
+++ /dev/null
@@ -1,114 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<section>
-	<title>Can You Install Using the CD-ROM or DVD?</title>
-	<indexterm significance="normal">
-		<primary>steps</primary>
-		<secondary>installing with CD-ROM or DVD</secondary>
-	</indexterm>
-	<indexterm significance="normal">
-		<primary>installation</primary>
-		<secondary>can you install with a CD-ROM or DVD</secondary>
-	</indexterm>
-	<para>
-		There are several methods that can be used to install Fedora.
-	</para>
-
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Steps_Cdrom_x86_ppc_preamble.xml"/>
-	 
-	<para>
-		Your BIOS may need to be changed to allow booting from your DVD/CD-ROM drive. For more information about changing your BIOS, refer to <xref linkend="s2-x86-starting-booting"/>.
-	</para>
-	 
-	<section id="sect-New_Users-Alternative_Boot_Methods">
-		<title>Alternative Boot Methods</title>
-		<indexterm significance="normal">
-			<primary>boot methods</primary>
-			<secondary>boot CD-ROM</secondary>
-		</indexterm>
-		<variablelist>
-			<varlistentry>
-				<term>Boot DVD/CD-ROM</term>
-				<listitem>
-					<para>
-				<indexterm significance="normal">
-					<primary>boot CD-ROM</primary>
-				</indexterm>
-						If you can boot using the DVD/CD-ROM drive, you can create your own CD-ROM to boot the installation program. This may be useful, for example, if you are performing an installation over a network or from a hard drive. Refer to
-						<xref linkend="s2-steps-make-cd"/> for further instructions.
-					</para>
-				</listitem>
-			</varlistentry>
-			<varlistentry>
-				<term>USB pen drive</term>
-				<listitem>
-					<para>
-				<indexterm significance="normal">
-					<primary>USB pen drive</primary>
-					<secondary>boot methods</secondary>
-				</indexterm>
-				<indexterm significance="normal">
-					<primary>boot methods</primary>
-					<secondary>USB pen drive</secondary>
-				</indexterm>
-						If you cannot boot from the DVD/CD-ROM drive, but you can boot using a USB device, such as a USB pen drive, the following alternative boot method is available:
-					</para>
-					<para>
-						Your BIOS must support booting from a USB device in order for this boot method to work.
-					</para>
-					<para>
-						Install the <package>livecd-tools</package> package on your system with your graphical package manager, or the following command:
-					</para>
-<screen><![CDATA[su -c 'yum -y install livecd-tools']]></screen>
-					<para>
-						Download the <filename>boot.iso</filename> image file as described in <xref linkend="sn-which-files"/> and 
-						use the <application>livecd-iso-to-disk</application> script to copy it to your USB device:
-					</para>
-<screen>livecd-iso-to-disk <replaceable>/path/to/image/file/boot.iso</replaceable> <replaceable>device</replaceable></screen>
-					<para>
-						Where <filename><replaceable>/path/to/image/file</replaceable></filename> is the location of <filename>boot.iso</filename> and <filename><replaceable>device</replaceable></filename> is the USB media device. For example:
-					</para>
-<screen>livecd-iso-to-disk '/home/username/Downloads/boot.iso' /dev/sdc1</screen>
-					<para>
-						If you use Red Hat Enterprise Linux or a Linux distribution derived from it, you can obtain the <package>livecd-tools</package> package from the <firstterm>Extra Packages for Enterprise Linux</firstterm> (EPEL) repository. Refer to <ulink url="http://fedoraproject.org/wiki/EPEL/FAQ#howtouse"></ulink> for details.
-					</para>
-					<para>
-						To create bootable USB media from the <filename>boot.iso</filename> file on a computer that uses Microsoft Windows or a Linux distribution other than Fedora, Red Hat Enterprise Linux, or those derived from Red Hat Enterprise Linux, you will need to find a tool that works for your chosen operating system. 
-					</para>
-					<para>
-						<application>UNetbootin</application> is a free and open-source graphical tool that can create live USB media from live image files on computers that use a wide range of different Linux distributions or Microsoft Windows. Refer to the documentation accompanying <application>UNetbootin</application> for a complete description of the tool and instructions on how to use it. 
-					</para>
-				</listitem>
-			</varlistentry>
-		</variablelist>
-	</section>
-	 
-	<section id="s2-steps-make-cd">
-		<title>Making an Installation Boot CD-ROM</title>
-		<indexterm significance="normal">
-			<primary>CD-ROM</primary>
-			<secondary>boot CD-ROM, creating</secondary>
-		</indexterm>
-		<indexterm significance="normal">
-			<primary>boot CD-ROM</primary>
-			<secondary>creating</secondary>
-		</indexterm>
-		<indexterm significance="normal">
-			<primary><filename>boot.iso</filename></primary>
-		</indexterm>
-		
-		<para>
-			The <filename>boot.iso</filename> image file is available for download from the same servers that host images of the Fedora installation disks &mdash; refer to <xref linkend="sect-Obtaining_Fedora-Downloading_Fedora"/>. This file is an image of a disc that you can burn to a CD and use to boot the installation program. To use this boot CD, your computer must be able to boot from its CD-ROM drive, and its BIOS settings must be configured to do so. 
-		</para>
-		
-		<important>
-			<title>Choose an option to burn a CD from an image</title>
-			<para>
-				When you burn the <filename>boot.iso</filename> image, make sure that you select the option to <literal>burn an image file to disc</literal> in your CD burning software. The exact wording of this option varies, depending on the software that you use, but should contain the word "image". Note that not all CD burning software includes this option. In particular, the CD burning software built into Microsoft Windows XP and Windows Vista does not offer this capability. There are many programs available that add this capability to Windows operating systems;  <application>Infrarecorder</application> is a free and open-source example available from <ulink url="http://www.infrarecorder.org/">http://www.infrarecorder.org/</ulink>.
-			</para>
-		</important>
-		
-	</section>
-</section>
diff --git a/en-US/Steps_Cdrom_x86_ppc_preamble.xml b/en-US/Steps_Cdrom_x86_ppc_preamble.xml
deleted file mode 100644
index f69cee4..0000000
--- a/en-US/Steps_Cdrom_x86_ppc_preamble.xml
+++ /dev/null
@@ -1,7 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>	
-
-<para>
-	Installing from a CD-ROM or DVD requires that you have <!-- purchased a Fedora product, you have -->a Fedora &PRODVER; CD-ROM or DVD, and you have a DVD/CD-ROM drive on a system that supports booting from it. 
-</para>
\ No newline at end of file
diff --git a/en-US/Steps_Diskspace-x86.xml b/en-US/Steps_Diskspace-x86.xml
deleted file mode 100644
index 2abccb4..0000000
--- a/en-US/Steps_Diskspace-x86.xml
+++ /dev/null
@@ -1,39 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-	  
-<section id="Disk_Space-x86">
-	<title>Do You Have Enough Disk Space?</title>
-	<indexterm significance="normal">
-		<primary>steps</primary>
-		<secondary>disk space</secondary>
-	</indexterm>
-	<indexterm significance="normal">
-		<primary>disk space</primary>
-	</indexterm>
-	<indexterm significance="normal">
-		<primary>installation</primary>
-		<secondary>disk space</secondary>
-	</indexterm>
-
-	<para>
-		Nearly every modern-day operating system (OS) uses <firstterm>disk partitions</firstterm>, and Fedora is no exception. When you install Fedora, you may have to work with disk partitions. If you have not worked with disk partitions before (or need a quick review of the basic concepts), refer to <xref linkend="ch-partitions-x86"/> before proceeding.
-	</para>
-	
-	<para>
-		The disk space used by Fedora must be separate from the disk space used by other OSes you may have installed on your system, such as Windows, OS/2, or even a different version of Linux. For x86, AMD64, and <trademark class="registered">Intel</trademark> 64 systems, at least two partitions (<filename>/</filename> and <filename>swap</filename>) must be dedicated to Fedora. <!-- (RHEL) For Itanium systems, at least three partitions (<filename>/</filename>, <filename>/boot/efi/</filename>, and <filename>swap</filename>) must be dedicated to Fedora. -->
-	</para>
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Steps_Diskspace_x86_ppc_oneline_paragraph.xml"/>
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Steps_Diskspace_x86_ppc_Itemized_List.xml"/>
-	
-	<para>
-		To gain a better sense of how much space you really need, refer to the recommended partitioning sizes discussed in <xref linkend="s2-diskpartrecommend-x86"/>.
-	</para>
-	
-	<para>
-		If you are not sure that you meet these conditions, or if you want to know how to create free disk space for your Fedora installation, refer to <xref linkend="ch-partitions-x86"/>.
-	</para>
-	
-</section>
\ No newline at end of file
diff --git a/en-US/Steps_Diskspace_x86_ppc_Itemized_List.xml b/en-US/Steps_Diskspace_x86_ppc_Itemized_List.xml
deleted file mode 100644
index a02029c..0000000
--- a/en-US/Steps_Diskspace_x86_ppc_Itemized_List.xml
+++ /dev/null
@@ -1,23 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE itemizedlist PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<!-- This is a list that appears in the x86 and ppc diskspace section of the install guide -->
-
-<itemizedlist>
-	<listitem>
-		<para>
-			have enough <emphasis>unpartitioned<footnote>
-			<para>
-				Unpartitioned disk space means that available disk space on the hard drive(s) you are installing to has not been divided into sections for data. When you partition a disk, each partition behaves like a separate disk drive.
-			</para>
-			</footnote></emphasis> disk space for the installation of Fedora, or
-		</para>
-	</listitem>
-
-	<listitem>
-		<para>
-			have one or more partitions that may be deleted, thereby freeing up enough disk space to install Fedora.
-		</para>
-	</listitem>
-</itemizedlist>
\ No newline at end of file
diff --git a/en-US/Steps_Diskspace_x86_ppc_oneline_paragraph.xml b/en-US/Steps_Diskspace_x86_ppc_oneline_paragraph.xml
deleted file mode 100644
index 90de039..0000000
--- a/en-US/Steps_Diskspace_x86_ppc_oneline_paragraph.xml
+++ /dev/null
@@ -1,9 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-	  
-	  
-	  
-]>
-<para>
-	Before you start the installation process, you must
-</para>
diff --git a/en-US/Steps_Hardware-x86.xml b/en-US/Steps_Hardware-x86.xml
deleted file mode 100644
index 6bd0d55..0000000
--- a/en-US/Steps_Hardware-x86.xml
+++ /dev/null
@@ -1,29 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<section id="sn-Is_Your_Hardware_Compatible-x86">
-	<title>Is Your Hardware Compatible?</title>
-	<indexterm significance="normal">
-		<primary>steps</primary>
-		<secondary>hardware compatibility</secondary>
-	</indexterm>
-	<indexterm significance="normal">
-		<primary>hardware</primary>
-		<secondary>compatibility</secondary>
-	</indexterm>
-	<para>
-		Hardware compatibility is particularly important if you have an older system or a system that you built yourself. Fedora &PRODVER; should be compatible with most hardware in systems that were factory built within the last two years. However,
-		hardware specifications change almost daily, so it is difficult to guarantee that your hardware is 100% compatible.
-	</para>
-	 
-	<para>
-		The most recent list of supported hardware can be found <!-- (RHEL) at: <ulink url="http://hardware.redhat.com/hcl/">http://hardware.redhat.com/hcl/</ulink> --> in the Release Notes for Fedora &PRODVER;, available at <ulink url="http://docs.fedoraproject.org/release-notes">http://docs.fedoraproject.org/release-notes</ulink> .  
-	</para>
-	<para>
-		At the end of a successful Fedora installation process, the installation program offers you the option to provide details of your hardware configuration anonymously to the Fedora Project (refer to <xref linkend="sn-smolt"/>). You can view the statistics gathered by this method at <ulink url="http://smolt.fedoraproject.org/static/stats/devices.html"></ulink>. Viewing the list of hardware that makes up systems on which other people have successfully installed Fedora might help you determine how suitable your hardware is. 
-	</para>
-	<xi:include href="Trouble_During_x86_ppc-para-3.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
-	<xi:include href="Trouble_During_x86_ppc-screen-1.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
-
-</section>
diff --git a/en-US/Steps_Hd_Install-x86.xml b/en-US/Steps_Hd_Install-x86.xml
deleted file mode 100644
index 7bb3214..0000000
--- a/en-US/Steps_Hd_Install-x86.xml
+++ /dev/null
@@ -1,82 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<section>
-	<title>Preparing for a Hard Drive Installation</title>
-	<indexterm significance="normal">
-		<primary>hard drive installation</primary>
-		<secondary>preparing for</secondary>
-	</indexterm>
-	<indexterm significance="normal">
-		<primary>installation</primary>
-		<secondary>hard drive</secondary>
-	</indexterm>
-
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Steps_Hd_Install_x86_ppc_note_1.xml"/>
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Steps_Hd_Install_x86_ppc_para_1.xml"/>
-	<!-- Hard drive installations require the use of the ISO (or CD-ROM) images. -->
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Prepare_To_Install-common-Boot_Media.xml"/>
-	<!-- Ensure that you have boot media available on CD, DVD, or a USB storage device... -->
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Steps_Hd_Install_x86_ppc_s390_para_1.xml"/>
-	<!-- To prepare your system for a hard drive installation, you must set the system up -->
-	
-	<itemizedlist>
-		<listitem>
-			<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Steps_Hd_Install_x86_ppc_s390_listitem_1.xml"/>
-			<!-- Using a set of CD-ROMs - Create CD-ROM ISO image files from each -->
-			
-			<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Steps_Hd_Install_x86_ppc_s390_listitem_1a.xml"/>
-			<!-- screen -->
-		</listitem>
-		
-		<listitem>
-			<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Steps_Hd_Install_x86_ppc_s390_listitem_2.xml"/>
-			<!-- Using ISO images - transfer these images to the system to be installed -->
-			
-			<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Beginning_Installation_Hard_Disk_common-para-5.xml"/>
-			<!-- The ISO files must be located on a hard drive that... -->
-
-			<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Steps_Hd_Install_x86_ppc_s390_listitem_2b.xml"/>
-			<!-- Verifying that ISO images are intact before you attempt an installation, -->
-			
-		</listitem>
-	</itemizedlist>
-
-	<indexterm significance="normal">
-		<primary>installation media</primary>
-		<secondary>testing</secondary>
-	</indexterm>
-	<indexterm significance="normal">
-		<primary>boot options</primary>
-		<secondary><command moreinfo="none">linux mediacheck</command>
-		</secondary>
-	</indexterm>
-	<indexterm significance="normal">
-		<primary>troubleshooting</primary>
-		<secondary>CD-ROM failure</secondary>
-		<tertiary>CD-ROM verification</tertiary>
-	</indexterm>
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Steps_Hd_Install_x86_note_1.xml"/>
-	<!-- The $PROD; installation program has the ability to test the integrity -->
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Steps_Hd_Install_x86_ppc_s390_para_2.xml"/>
-	<!-- Additionally, if a file called updates.img exists in the  -->
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Beginning_Installation_Hard_Disk_common-para-6.xml"/>
-	<!-- To extract the install.img from the iso follow... -->
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Beginning_Installation_Hard_Disk_common-screen-1.xml"/>
-	<!-- mount -t iso9660 /path/to/Fedora10/iso /mnt/point... -->
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Beginning_Installation_Hard_Disk_common-para-8.xml"/>
-	<!-- Before you begin installation from a hard drive, check... -->
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Beginning_Installation_Hard_Disk_common-note-1.xml"/>
-	<!-- Cannot install from LVM partitions -->
-
-</section>
\ No newline at end of file
diff --git a/en-US/Steps_Hd_Install_x86_note_1.xml b/en-US/Steps_Hd_Install_x86_note_1.xml
deleted file mode 100644
index cfbc26c..0000000
--- a/en-US/Steps_Hd_Install_x86_note_1.xml
+++ /dev/null
@@ -1,19 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE note PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<note><title>Note</title>
-
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Steps_Hd_Install_x86_ppc_note_para_1.xml"/>
-	<!-- The $PROD; installation program has the ability to test the integrity -->
-	
-	<screen>
-<userinput>linux mediacheck</userinput>
-</screen>
-
-
-
-</note>
\ No newline at end of file
diff --git a/en-US/Steps_Hd_Install_x86_ppc_note_1.xml b/en-US/Steps_Hd_Install_x86_ppc_note_1.xml
deleted file mode 100644
index 5cad27d..0000000
--- a/en-US/Steps_Hd_Install_x86_ppc_note_1.xml
+++ /dev/null
@@ -1,14 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE note PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-<!ENTITY % RH_ENTITIES SYSTEM "./Common_Config/rh-entities.ent">
-%RH_ENTITIES;
-
-]>
-
-<note>
-	<title>Note</title>
-
-	<para>
-		Hard drive installations only work from ext2, ext3, or FAT file systems. If you have a file system other than those listed here, such as reiserfs, you will not be able to perform a hard drive installation.
-	</para>
-</note>
\ No newline at end of file
diff --git a/en-US/Steps_Hd_Install_x86_ppc_note_para_1.xml b/en-US/Steps_Hd_Install_x86_ppc_note_para_1.xml
deleted file mode 100644
index cd410f5..0000000
--- a/en-US/Steps_Hd_Install_x86_ppc_note_para_1.xml
+++ /dev/null
@@ -1,9 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<!-- This is in the Step_Network_Install-ppc.xml file as well, so as to say yaboot in place of boot, and remove the Itanium reference -->
-
-<para>
-	The Fedora installation program has the ability to test the integrity of the installation media. It works with the CD / DVD, hard drive ISO, and NFS ISO installation methods. We recommend that you test all installation media before starting the installation process, and before reporting any installation-related bugs (many of the bugs reported are actually due to improperly-burned CDs). To use this test, type the following command at the <prompt>boot:</prompt> prompt<!-- (RHEL) (prepend with <command>elilo</command> for Itanium systems)-->:
-</para>
\ No newline at end of file
diff --git a/en-US/Steps_Hd_Install_x86_ppc_para_1.xml b/en-US/Steps_Hd_Install_x86_ppc_para_1.xml
deleted file mode 100644
index 6bc52a8..0000000
--- a/en-US/Steps_Hd_Install_x86_ppc_para_1.xml
+++ /dev/null
@@ -1,7 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<para>
-	Hard drive installations require the use of the ISO (or DVD/CD-ROM) images. An ISO image is a file containing an exact copy of a DVD/CD-ROM image. <!-- Because Fedora has so many packages included with its distribution, there are several ISO images available. -->After placing the required ISO images (the binary Fedora DVD/CD-ROMs) in a directory, choose to install from the hard drive. You can then point the installation program at that directory to perform the installation.
-</para>
\ No newline at end of file
diff --git a/en-US/Steps_Hd_Install_x86_ppc_s390_listitem_1.xml b/en-US/Steps_Hd_Install_x86_ppc_s390_listitem_1.xml
deleted file mode 100644
index 1c50cd7..0000000
--- a/en-US/Steps_Hd_Install_x86_ppc_s390_listitem_1.xml
+++ /dev/null
@@ -1,7 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<para>
-	Using a set of CD-ROMs, or a DVD &mdash; Create ISO image files from each installation CD-ROM, or from the DVD. For each CD-ROM (once for the DVD), execute the following command on a Linux system:
-</para>
\ No newline at end of file
diff --git a/en-US/Steps_Hd_Install_x86_ppc_s390_listitem_1a.xml b/en-US/Steps_Hd_Install_x86_ppc_s390_listitem_1a.xml
deleted file mode 100644
index d6db5b4..0000000
--- a/en-US/Steps_Hd_Install_x86_ppc_s390_listitem_1a.xml
+++ /dev/null
@@ -1,6 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<screen><command>dd if=/dev/cdrom of=/tmp/<replaceable>file-name</replaceable>.iso</command>
-</screen>
diff --git a/en-US/Steps_Hd_Install_x86_ppc_s390_listitem_2.xml b/en-US/Steps_Hd_Install_x86_ppc_s390_listitem_2.xml
deleted file mode 100644
index f0d9a17..0000000
--- a/en-US/Steps_Hd_Install_x86_ppc_s390_listitem_2.xml
+++ /dev/null
@@ -1,10 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-	  
-	  
-	  
-]>
-
-<para>
-	Using ISO images &mdash; transfer these images to the system to be installed.
-</para>
\ No newline at end of file
diff --git a/en-US/Steps_Hd_Install_x86_ppc_s390_listitem_2b.xml b/en-US/Steps_Hd_Install_x86_ppc_s390_listitem_2b.xml
deleted file mode 100644
index 5d1a203..0000000
--- a/en-US/Steps_Hd_Install_x86_ppc_s390_listitem_2b.xml
+++ /dev/null
@@ -1,10 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<para>
-	Verifying that ISO images are intact before you attempt an installation, helps to avoid problems. To verify the ISO images are intact prior to performing an installation, use an <command>md5sum</command> program (many <command>md5sum</command> programs are available for various operating systems). An <command>md5sum</command> program should be available on the same Linux machine as the ISO images.
-</para>
\ No newline at end of file
diff --git a/en-US/Steps_Hd_Install_x86_ppc_s390_para_1.xml b/en-US/Steps_Hd_Install_x86_ppc_s390_para_1.xml
deleted file mode 100644
index 7e0c2d3..0000000
--- a/en-US/Steps_Hd_Install_x86_ppc_s390_para_1.xml
+++ /dev/null
@@ -1,12 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<para>
-	To prepare your system for a hard drive installation, you must set the system up in one of the following ways:
-</para>
-	 
-	
\ No newline at end of file
diff --git a/en-US/Steps_Hd_Install_x86_ppc_s390_para_2.xml b/en-US/Steps_Hd_Install_x86_ppc_s390_para_2.xml
deleted file mode 100644
index ccf22f8..0000000
--- a/en-US/Steps_Hd_Install_x86_ppc_s390_para_2.xml
+++ /dev/null
@@ -1,7 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<para>
-	Additionally, if a file called <filename>updates.img</filename> exists in the location from which you install, it is used for updates to <filename>anaconda</filename>, the installation program. Refer to the file <filename>install-methods.txt</filename> in the <filename>anaconda</filename> RPM package for detailed information on the various ways to install Fedora, as well as how to apply the installation program updates.
-</para>
\ No newline at end of file
diff --git a/en-US/Steps_Network_Install-x86.xml b/en-US/Steps_Network_Install-x86.xml
deleted file mode 100644
index 838ba57..0000000
--- a/en-US/Steps_Network_Install-x86.xml
+++ /dev/null
@@ -1,73 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<section id="s1-steps-network-installs-x86">
-	<title>Preparing for a Network Installation</title>
-	<indexterm significance="normal">
-		<primary>network installation</primary>
-		<secondary>preparing for</secondary>
-	</indexterm>
-	<indexterm significance="normal">
-		<primary>installation</primary>
-		<secondary>network</secondary>
-	</indexterm>
-	<indexterm significance="normal">
-		<primary>installation</primary>
-		<secondary>FTP</secondary>
-	</indexterm>
-	<indexterm significance="normal">
-		<primary>installation</primary>
-		<secondary>NFS</secondary>
-	</indexterm>
-	<indexterm significance="normal">
-		<primary>installation</primary>
-		<secondary>HTTP</secondary>
-	</indexterm>
-	<indexterm significance="normal">
-		<primary>FTP</primary>
-		<secondary>installation</secondary>
-	</indexterm>
-	<indexterm significance="normal">
-		<primary>NFS</primary>
-		<secondary>installation</secondary>
-	</indexterm>
-	<indexterm significance="normal">
-		<primary>HTTP</primary>
-		<secondary>installation</secondary>
-	</indexterm>
-	
-	
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Steps_Network_Install_x86_ppc_note.xml"/>
-	<!-- Make sure an installation CD (or any other type of CD) is not in your hosting -->
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Prepare_To_Install-common-Boot_Media.xml"/>
-	<!-- Ensure that you have boot media available on CD, DVD, or a USB storage device... -->
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Steps_Network_Install_x86_ppc_s390_para_1.xml"/>
-	<!-- The Fedora installation media must be available for either a network installation  -->
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Steps_Network_Install_x86_ppc_s390_para_2.xml"/>
-	<!-- The NFS, FTP, or HTTP server to be used for installation over the network -->
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Steps_Network_Install_x86_ppc_note_2.xml"/>
-	<!-- The Red Hat Enterprise Linux installation program has the ability -->
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Steps_Network_Install_x86_ppc_s390_note_1.xml"/>
-	<!-- In the following examples, the directory on the installation staging server -->
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Steps_Network_Install_x86_ppc_s390_para_3.xml"/>
-	<!-- To copy the files from the installation CD-ROMs to a Linux machine -->
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Steps_Network_Install_x86_ppc_s390_itemized_list_1.xml"/>
-	<!--Create an iso image from the installation disk(s) using the following command: -->
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Steps_Network_Install_x86_ppc_s390_section_1.xml"/>
-	<!-- Preparing for FTP and HTTP installation -->
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Steps_Network_Install_x86_ppc_s390_section_2.xml"/>
-	<!-- Preparing for an NFS install -->
-	
-	
-</section>
\ No newline at end of file
diff --git a/en-US/Steps_Network_Install_x86_ppc_note.xml b/en-US/Steps_Network_Install_x86_ppc_note.xml
deleted file mode 100644
index ad40219..0000000
--- a/en-US/Steps_Network_Install_x86_ppc_note.xml
+++ /dev/null
@@ -1,14 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE note PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<note>
-	<title>Note</title>
-	
-	<para>
-		Make sure an installation CD (or any other type of CD) is not in your system's CD/DVD drive if you are performing a network-based installation. Having a CD in the drive may cause unexpected errors.
-	</para>
-</note>
\ No newline at end of file
diff --git a/en-US/Steps_Network_Install_x86_ppc_note_2.xml b/en-US/Steps_Network_Install_x86_ppc_note_2.xml
deleted file mode 100644
index c43a8d8..0000000
--- a/en-US/Steps_Network_Install_x86_ppc_note_2.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE note PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>	
-
-<!-- Note that this has been replaced in the ppc file with an inline version that says yaboot in place of boot, and does not have the Itanium phrase -->
-<note>
-	<title>Note</title>
-
-<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Steps_Hd_Install_x86_ppc_note_para_1.xml"/>
-	<!-- The Fedora installation program has the ability to test the integrity... -->
-	
-<screen>
-<userinput>linux mediacheck</userinput>
-</screen>
-</note>
\ No newline at end of file
diff --git a/en-US/Steps_Network_Install_x86_ppc_s390_itemized_list_1.xml b/en-US/Steps_Network_Install_x86_ppc_s390_itemized_list_1.xml
deleted file mode 100644
index 01f3ff7..0000000
--- a/en-US/Steps_Network_Install_x86_ppc_s390_itemized_list_1.xml
+++ /dev/null
@@ -1,60 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE itemizedlist PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<itemizedlist>
-	<listitem>
-
-		<para>
-			Create an iso image from the installation disk(s) using the following command (for DVDs):
-			
-			
-		</para>
-		
-		<para>
-			<command>
-				dd if=/dev/<replaceable>dvd</replaceable> of=<replaceable>/location/of/disk/space/</replaceable>f&PRODVER;.iso
-			</command>
-		</para>
-		
-		<para>
-			where <replaceable>dvd</replaceable> refers to your DVD drive device.
-				</para>
-				
-		<para>For instructions on how to prepare a network installation using CD-ROMs, refer to the instructions on the <filename>README-en</filename> file in <filename>disk1</filename>.</para>
-<!--		above replaces below, BZ#240455
-		<itemizedlist>
-			<listitem>
-				<para>
-					For DVD:
-				</para>
-				
-				<para>
-					<command>
-						dd if=/dev/<replaceable>dvd</replaceable> of=<replaceable>/location/of/disk/space/</replaceable>RHEL5.iso
-					</command>
-				</para>
-				
-				<para>
-					where <replaceable>dvd</replaceable> refers to your DVD drive device.
-				</para>
-			</listitem>
-			
-			<listitem>
-				<para>
-					For CD-ROMs:
-				</para>
-				
-				<para>
-					<command>
-						dd if=/dev/<replaceable>cdrom</replaceable> of=<replaceable>/location/of/disk/space/</replaceable>disk<replaceable>X</replaceable>.iso
-					</command>
-				</para>
-				
-				<para>
-					where <replaceable>cdrom</replaceable> refers to your CD drive device, and <replaceable>X</replaceable> is the number of the disk that you are copying, beginning with 1 for the first disk, and so on.
-				</para>
-			</listitem>
-		</itemizedlist>-->
-	</listitem>
-</itemizedlist>
\ No newline at end of file
diff --git a/en-US/Steps_Network_Install_x86_ppc_s390_note_1.xml b/en-US/Steps_Network_Install_x86_ppc_s390_note_1.xml
deleted file mode 100644
index e192ad9..0000000
--- a/en-US/Steps_Network_Install_x86_ppc_s390_note_1.xml
+++ /dev/null
@@ -1,11 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE note PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>	
-
-<note>
-	<title>Note</title>
-
-	<para>
-		In the following examples, the directory on the installation staging server that will contain the installation files will be specified as <filename><replaceable>/location/of/disk/space</replaceable></filename>. The directory that will be made publicly available via FTP, NFS, or HTTP will be specified as <replaceable>/publicly/available/directory</replaceable>. For example, <filename><replaceable>/location/of/disk/space</replaceable></filename> may be a directory you create called <filename>/var/isos</filename>. <filename><replaceable>/publicly/available/directory</replaceable></filename> might be <filename>/var/www/html/f&PRODVER;</filename>, for an HTTP install.
-	</para>
-</note>
\ No newline at end of file
diff --git a/en-US/Steps_Network_Install_x86_ppc_s390_para_1.xml b/en-US/Steps_Network_Install_x86_ppc_s390_para_1.xml
deleted file mode 100644
index 678e5ce..0000000
--- a/en-US/Steps_Network_Install_x86_ppc_s390_para_1.xml
+++ /dev/null
@@ -1,7 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<para>
-	The Fedora installation media must be available for either a network installation (via NFS, FTP, or HTTP) or installation via local storage. Use the following steps if you are performing an NFS, FTP, or HTTP installation.
-</para>
\ No newline at end of file
diff --git a/en-US/Steps_Network_Install_x86_ppc_s390_para_2.xml b/en-US/Steps_Network_Install_x86_ppc_s390_para_2.xml
deleted file mode 100644
index 84d7952..0000000
--- a/en-US/Steps_Network_Install_x86_ppc_s390_para_2.xml
+++ /dev/null
@@ -1,10 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<para>
-	The NFS, FTP, or HTTP server to be used for installation over the network must be a separate machine which can provide the complete contents of the installation DVD-ROM or the installation CD-ROMs.
-</para>
\ No newline at end of file
diff --git a/en-US/Steps_Network_Install_x86_ppc_s390_para_3.xml b/en-US/Steps_Network_Install_x86_ppc_s390_para_3.xml
deleted file mode 100644
index be6dafc..0000000
--- a/en-US/Steps_Network_Install_x86_ppc_s390_para_3.xml
+++ /dev/null
@@ -1,10 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<para>
-	To copy the files from the installation DVD or CD-ROMs to a Linux machine which acts as an installation staging server, perform the following steps:
-</para>
\ No newline at end of file
diff --git a/en-US/Steps_Network_Install_x86_ppc_s390_section_1.xml b/en-US/Steps_Network_Install_x86_ppc_s390_section_1.xml
deleted file mode 100644
index 640b498..0000000
--- a/en-US/Steps_Network_Install_x86_ppc_s390_section_1.xml
+++ /dev/null
@@ -1,58 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<section>
-	<title>Preparing for FTP and HTTP installation</title>
-	
-	<para>
-		Extract the files from the iso image of the installation DVD or the iso images of the installation CDs and place them in a directory that is shared over FTP or HTTP. 
-	</para>
-	<!-- 
-	<itemizedlist>
-		<listitem>
-			<para>
-				For DVD:
-			</para>
-			
-			<para>
-				<command>
-					mount -o loop <replaceable>/location/of/disk/space/</replaceable>f&PRODVER;.iso <replaceable>/publicly/available/directory</replaceable>/
-				</command>
-			</para>
-			
-			<para>
-				In this case <replaceable>/publicly/available/directory</replaceable> will be a directory that is shared via FTP or HTTP.
-			</para>
-			
-		</listitem>
-		
-		<listitem>
-			<para>
-				For CDROMs:
-			</para>
-			
-			<para>
-				<command>
-					mount -o loop <replaceable>/location/of/disk/space/</replaceable>disk<replaceable>X</replaceable>.iso <replaceable>/publicly/available/directory/</replaceable>disk<replaceable>X</replaceable>/
-				</command>
-			</para>
-			
-			<para>
-				Again, <replaceable>/publicly/available/directory</replaceable> will be a directory that is shared via FTP or HTTP. Do the above for each of the CDROM iso images, for example:
-			</para>
-			<example>
-			<title>Making a Fedora installation CD available on a HTTP server</title>
-			<para>
-				<command>
-					mount -o loop /var/isos/Fedora-&PRODVER;-i386-disk1.iso /var/www/html/f&PRODVER;-install/disk1/
-				</command>
-			</para>
-			</example>
-		</listitem>
-	</itemizedlist> -->
-	
-	<para>
-		Next, make sure that the  <!--<filename><replaceable>/publicly/available/directory</replaceable></filename>--> directory is shared via FTP or HTTP, and verify client access. You can check to see whether the directory is accessible from the server itself, and then from another machine on the same subnet that you will be installing to.
-	</para>
-</section>
\ No newline at end of file
diff --git a/en-US/Steps_Network_Install_x86_ppc_s390_section_2.xml b/en-US/Steps_Network_Install_x86_ppc_s390_section_2.xml
deleted file mode 100644
index a25f74b..0000000
--- a/en-US/Steps_Network_Install_x86_ppc_s390_section_2.xml
+++ /dev/null
@@ -1,71 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<section>
-	<title>Preparing for an NFS install</title>
-	
-	<para>
-		For NFS installation it is not necessary to mount the iso image. It is sufficient to make the iso image itself available via NFS. You can do this by moving the iso image or images to the NFS exported directory:
-	</para>
-	
-	<itemizedlist>
-			
-		<listitem>
-			<para>
-				For DVD:
-			</para>
-<screen><command>mv <replaceable>/location/of/disk/space/</replaceable>f&PRODVER;.iso <replaceable>/publicly/available/directory/</replaceable>
-</command></screen>
-		</listitem>
-		
-		<listitem>
-			<para>
-				For CDROMs:
-			</para>
-<screen><command>mv <replaceable>/location/of/disk/space/</replaceable>f&PRODVER;-disk*.iso <replaceable>/publicly/available/directory/</replaceable>
-</command></screen>
-		</listitem>
-	</itemizedlist>
-	<para>
-		In addition the <filename>install.img</filename> file from within the ISO files must be copied to a directory named <filename class="directory">images</filename>
-	</para>
-	<para>
-		Additionally, if a file called <filename>updates.img</filename> exists in the location from which you install, it is used for updates to <application>anaconda</application>, the installation program. Refer to the file <filename>install-methods.txt</filename> in the <application>anaconda</application> RPM package for detailed information on the various ways to install Fedora, as well as how to apply the installation program updates. 
-	</para>	
-	<para>
-		To extract the <filename>install.img</filename> from the ISO follow the procedure:
-	</para>
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Beginning_Installation_Hard_Disk_common-screen-1.xml"/>
-	<!-- <para>
-		<command>
-			mount -o loop <replaceable>/location/of/disk/space/</replaceable>RHEL5.iso <replaceable>/export/directory</replaceable>
-		</command>
-	</para>
-
-	<para>
-		This will make the files from the DVD available for sharing from <filename><replaceable>/export/directory</replaceable></filename> via HTTP, FTP, or NFS.
-	</para> -->
-		
-	<para>
-		Ensure that the <filename><replaceable>/publicly/available/directory</replaceable></filename> directory is exported via NFS via an entry in <filename>/etc/exports</filename>. 
-	</para>
-		
-	<para>
-		To export to a specific system:
-	</para>
-<screen><command><replaceable>/publicly/available/directory</replaceable> <replaceable>client.ip.address</replaceable>
-</command></screen>
-	<para>
-		To export to all systems use an entry such as:
-	</para>
-<screen><command><replaceable>/publicly/available/directory</replaceable> *
-</command></screen>
-	<para>
-		Start the NFS daemon (on a Fedora system, use <command>/sbin/service nfs start</command>). If NFS is already running, reload the configuration file (on a Fedora system use <command>/sbin/service nfs reload</command>).
-	</para>
-	
-	<!-- (RHEL) <para>
-		Be sure to test the NFS share following the directions in the &PROD; Deployment Guide.
-	</para> -->
-</section>
diff --git a/en-US/Steps_Upgrade-common.xml b/en-US/Steps_Upgrade-common.xml
deleted file mode 100644
index 01d8ff6..0000000
--- a/en-US/Steps_Upgrade-common.xml
+++ /dev/null
@@ -1,11 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<section>
-	<title>Upgrade or Install?</title>
-	
-	<para>
-		For information to help you determine whether to perform an upgrade or an installation refer to <xref linkend="ch-upgrade-x86"/>.
-	</para>
-</section>
\ No newline at end of file
diff --git a/en-US/Storage_Devices-x86.xml b/en-US/Storage_Devices-x86.xml
deleted file mode 100644
index 20ea612..0000000
--- a/en-US/Storage_Devices-x86.xml
+++ /dev/null
@@ -1,33 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-
-<section id="Storage_Devices-x86">
-
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Storage_Devices_common-title.xml"/>
-	<!-- Storage Devices -->
-	
-	<!-- Index terms -->
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Storage_Devices_common-indexterm-1.xml"/>
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Storage_Devices_common-indexterm-2.xml"/>
-	<!-- End Index terms -->
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Storage_Devices_common-para-1.xml"/>
-	<!-- You can install Red Hat Enterprise Linux on a large variety of storage devices... -->
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Storage_Devices_common-figure-1.xml"/>
-	<!-- Storage devices -->
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Storage_Devices_common-variablelist-1.xml"/>
-	<!-- Basic Storage Devices -->
-	
-	<para>
-		If you select <guimenuitem>Basic Storage Devices</guimenuitem> and have only one storage device attached to your system, <application>anaconda</application> automatically detects the local storage attached to the system and does not require further input from you. Proceed to <xref linkend="sn-initialize-hdd-x86"/>. 
-	</para>
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Specialized_Storage_Devices-x86.xml"/>
-	<!-- Specialized Storage Devices -->
-
-</section>
-
diff --git a/en-US/Storage_Devices_common-figure-1.xml b/en-US/Storage_Devices_common-figure-1.xml
deleted file mode 100644
index b879c91..0000000
--- a/en-US/Storage_Devices_common-figure-1.xml
+++ /dev/null
@@ -1,14 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE figure PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-
-<figure float="0"><title>Storage devices</title>
-	<mediaobject>
-		<imageobject><imagedata fileref="images/storagedevices/storagedevices.png" format="PNG"/></imageobject>
-		<textobject><para>
-				Screen to select basic or specialized storage devices
-			</para>
-		</textobject>
-	</mediaobject>
-</figure>
diff --git a/en-US/Storage_Devices_common-indexterm-1.xml b/en-US/Storage_Devices_common-indexterm-1.xml
deleted file mode 100644
index 648f345..0000000
--- a/en-US/Storage_Devices_common-indexterm-1.xml
+++ /dev/null
@@ -1,12 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE indexterm PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<indexterm significance="normal">
-	<primary>storage devices</primary>
-	<secondary>basic storage devices</secondary>
-</indexterm>
-
diff --git a/en-US/Storage_Devices_common-indexterm-2.xml b/en-US/Storage_Devices_common-indexterm-2.xml
deleted file mode 100644
index 739d776..0000000
--- a/en-US/Storage_Devices_common-indexterm-2.xml
+++ /dev/null
@@ -1,12 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE indexterm PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<indexterm significance="normal">
-	<primary>storage devices</primary>
-	<secondary>specialized storage devices</secondary>
-</indexterm>
-
diff --git a/en-US/Storage_Devices_common-para-1.xml b/en-US/Storage_Devices_common-para-1.xml
deleted file mode 100644
index c00430a..0000000
--- a/en-US/Storage_Devices_common-para-1.xml
+++ /dev/null
@@ -1,8 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-
-<para>
-	You can install Fedora on a large variety of storage devices. This screen allows you to select either basic or specialized storage devices.
-</para>
diff --git a/en-US/Storage_Devices_common-title.xml b/en-US/Storage_Devices_common-title.xml
deleted file mode 100644
index 4a1bee1..0000000
--- a/en-US/Storage_Devices_common-title.xml
+++ /dev/null
@@ -1,6 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE title PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<title>Storage Devices</title>
-
diff --git a/en-US/Storage_Devices_common-variablelist-1.xml b/en-US/Storage_Devices_common-variablelist-1.xml
deleted file mode 100644
index 74d804a..0000000
--- a/en-US/Storage_Devices_common-variablelist-1.xml
+++ /dev/null
@@ -1,55 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<variablelist>
-	<varlistentry>
-		<term>Basic Storage Devices</term>
-		<listitem>
-			<para>
-				Select <guimenuitem>Basic Storage Devices</guimenuitem> to install Fedora on the following storage devices:
-			</para>
-			<itemizedlist>
-				<listitem>
-					<para>
-						hard drives or solid-state drives connected directly to the local system.
-					</para>
-				</listitem>
-			</itemizedlist>
-		</listitem>
-	</varlistentry>
-	<varlistentry>
-		<term>Specialized Storage Devices</term>
-		<listitem>
-			<para>
-				Select <guimenuitem>Specialized Storage Devices</guimenuitem> to install Fedora on the following storage devices:
-			</para>
-			<itemizedlist>
-				<listitem>
-					<para>
-						<firstterm>Storage area networks</firstterm> (SANs) 
-					</para>
-				</listitem>
-				<listitem>
-					<para>
-						<firstterm>Direct access storage devices</firstterm> (DASDs)
-					</para>
-				</listitem>
-				<listitem>
-					<para>
-						Firmware RAID devices
-					</para>
-				</listitem>
-				<listitem>
-					<para>
-						Multipath devices
-					</para>
-				</listitem>
-			</itemizedlist>
-			<para>
-				Use the <guimenuitem>Specialized Storage Devices</guimenuitem> option to configure <firstterm>Internet Small Computer System Interface</firstterm> (iSCSI) and <firstterm>FCoE</firstterm> (Fiber Channel over Ethernet) connections.
-			</para>
-		</listitem>
-	</varlistentry>
-</variablelist>
-
diff --git a/en-US/Swap_Partrecommend.xml b/en-US/Swap_Partrecommend.xml
deleted file mode 100644
index bec246e..0000000
--- a/en-US/Swap_Partrecommend.xml
+++ /dev/null
@@ -1,59 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE listitem PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-<listitem>
-	<para>
-		A swap partition (at least 256 MB) &mdash; swap partitions are used to support virtual memory. In other words, data is written to a swap partition when there is not enough RAM to store the data your system is processing.
-	</para>
-
-		<para>In years past, the recommended amount of swap space increased linearly with the amount of RAM in the system. But because the amount of memory in modern systems has increased into the hundreds of gigabytes, it is now recognized that the amount of swap space that a system needs is a function of the memory workload running on that system. However, given that swap space is usually designated at install time, and that it can be difficult to determine beforehand the memory workload of a system, we recommend determining system swap using the following table.</para>
-		<table
-			id="table-Recommended_System_Swap_Space"
-			frame="all">
-			<title>Recommended System Swap Space</title>
-			<tgroup
-				cols="2"
-				align="left"
-				colsep="1"
-				rowsep="1">
-				<colspec
-					colnum="1"
-					colname="col1"/>
-				<colspec
-					colnum="2"
-					colname="col2"/>
-				<thead>
-					<row>
-						<entry>Amount of RAM in the System</entry>
-						<entry>Recommended Amount of Swap Space</entry>
-					</row>
-				</thead>
-				<tbody>
-					<row>
-						<entry>4GB of RAM or less</entry>
-						<entry>a minimum of 2GB of swap space</entry>
-					</row>
-					<row>
-						<entry>4GB to 16GB of RAM</entry>
-						<entry>a minimum of 4GB of swap space</entry>
-					</row>
-					<row>
-						<entry>16GB to 64GB of RAM</entry>
-						<entry>a minimum of 8GB of swap space</entry>
-					</row>
-					<row>
-						<entry>64GB to 256GB of RAM</entry>
-						<entry>a minimum of 16GB of swap space</entry>
-					</row>
-					<row>
-						<entry>256GB to 512GB of RAM</entry>
-						<entry>a minimum of 32GB of swap space</entry>
-					</row>
-				</tbody>
-			</tgroup>
-		</table>
-		<para>
-			Note that you can obtain better performance by distributing swap space over multiple storage devices, particularly on systems with fast drives, controllers, and interfaces.
-		</para>
-
-</listitem>
diff --git a/en-US/System_Requirements_Table.xml b/en-US/System_Requirements_Table.xml
deleted file mode 100644
index f01fc7e..0000000
--- a/en-US/System_Requirements_Table.xml
+++ /dev/null
@@ -1,148 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<chapter id="ch-ent-table">
-	<title>System Specifications List</title>
-
-<!-- Index terms -->
-<indexterm significance="normal">
-	<primary>hardware</primary>
-	<secondary>configuration</secondary>
-</indexterm>
-
-<indexterm significance="normal">
-	<primary>configuration</primary>
-	<secondary>hardware</secondary>
-</indexterm>
-<!-- End index terms -->
-
-<para>
-	The installation program automatically detects and installs your computer's hardware. Although you should make sure that your hardware meets the minimum requirements to install Fedora (refer to <xref linkend="sn-Is_Your_Hardware_Compatible-x86"/>) you do not usually need to supply the installation program with any specific details about your system.
-</para>
-
-<para>
-	However, when performing certain types of installation, some specific details might be useful or even essential.
-</para>
-
-<itemizedlist>
-	<listitem>
-		<para>
-			If you plan to use a customized partition layout, record:
-		</para>
-		<itemizedlist>
-			<listitem>
-				<para>
-					The model numbers, sizes, types, and interfaces of the hard drives attached to the system. For example, Seagate ST3320613AS 320 GB on SATA0, Western Digital WD7500AAKS 750 GB on SATA1. This will allow you to identify specific hard drives during the partitioning process. 
-				</para>
-			</listitem>
-		</itemizedlist>
-	</listitem>
-	
-	<listitem>
-		<para>
-			If you are installing Fedora as an additional operating system on an existing system, record:
-		</para>
-		<itemizedlist>
-			<listitem>
-				<para>
-					The mount points of the existing partitions on the system. For example, <filename>/boot</filename> on <filename>sda1</filename>, <filename>/</filename> on <filename>sda2</filename>, and <filename>/home</filename> on <filename>sdb1</filename>. This will allow you to identify specific partitions during the partitioning process. 
-				</para>
-			</listitem>
-		</itemizedlist>		
-	</listitem>
-	
-	<listitem>
-		<para>
-			If you plan to install from an image on a local hard drive:
-		</para>
-		<itemizedlist>
-			<listitem>
-				<para>
-					The hard drive and directory that holds the image &ndash; see <xref linkend="table-Location_of_ISO_images" /> for examples.
-				</para>
-			</listitem>
-		</itemizedlist>		
-	</listitem>
-	
-	<listitem>
-		<para>
-			If you plan to install from a network location, or install on an iSCSI target:
-		</para>
-		<itemizedlist>
-			<listitem>
-				<para>
-					The make and model numbers of the network adapters on your system. For example, Netgear GA311. This will allow you to identify adapters when manually configuring the network.
-				</para>
-			</listitem>						
-			<listitem>
-				<para>
-					IP, DHCP, and BOOTP addresses 
-				</para>
-			</listitem>
-	
-			<listitem>
-				<para>
-					Netmask
-				</para>
-			</listitem>
-	
-			<listitem>
-				<para>
-					Gateway IP address
-				</para>
-			</listitem>
-	
-			<listitem>
-				<para>
-					One or more name server IP addresses (DNS)
-				</para>
-			</listitem>		
-		</itemizedlist>
-		<para>
-			If any of these networking requirements or terms are unfamiliar to you, contact your network administrator for assistance.
-		</para>
-	</listitem>
-
-	<listitem>
-		<para>
-			If you plan to install from a network location:
-		</para>
-		<itemizedlist>
-			<listitem>
-				<para>
-					The location of the image on an FTP server, HTTP (web) server, or NFS server &ndash; see <xref linkend="s1-begininstall-url-x86"/> and <xref linkend="s1-begininstall-nfs-x86"/> for examples.
-				</para>
-			</listitem>
-		</itemizedlist>		
-	</listitem>
-
-	<listitem>
-		<para>
-			If you plan to install on an iSCSI target:
-		</para>
-		<itemizedlist>
-			<listitem>
-				<para>
-					The location of the iSCSI target. Depending on your network, you might also need a CHAP username and password, and perhaps a reverse CHAP username and password &ndash; see <xref linkend="s1-advanced-storage-x86"/>.
-				</para>
-			</listitem>
-		</itemizedlist>		
-	</listitem>
-	
-	<listitem>
-		<para>
-			If your computer is part of a domain:
-		</para>
-		<itemizedlist>
-			<listitem>
-				<para>
-					You should verify that the domain name will be supplied by the DHCP server. If not, you will need to input the domain name manually during installation.
-				</para>
-			</listitem>
-		</itemizedlist>		
-	</listitem>
-	
-</itemizedlist>
-
-</chapter>
diff --git a/en-US/Systems_with_Intel_BIOS_RAID.xml b/en-US/Systems_with_Intel_BIOS_RAID.xml
deleted file mode 100644
index 77c02a0..0000000
--- a/en-US/Systems_with_Intel_BIOS_RAID.xml
+++ /dev/null
@@ -1,14 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-
-<!DOCTYPE important PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
- "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd">
-
-<important>
-	<title>Important â€” Systems with Intel BIOS RAID sets</title>
-	<para>
-		Fedora&nbsp;&PRODVER; uses <application>mdraid</application> instead of <application>dmraid</application> for installation onto Intel BIOS RAID sets. These sets are detected automatically, and devices with Intel ISW metadata are recognized as mdraid instead of dmraid. Note that the device node names of any such devices under <application>mdraid</application> are different from their device node names under <application>dmraid</application>. Therefore, special precautions are necessary when you migrate systems with Intel BIOS RAID sets from operating systems or versions of operating systems that use <application>dmraid</application>.
-	</para>
-	<para>
-		Local modifications to <filename>/etc/fstab</filename>, <filename>/etc/crypttab</filename> or other configuration files which refer to devices by their device node names will not work in Fedora&nbsp;&PRODVER;. Before migrating these files, you must therefore edit them to replace device node paths with device UUIDs instead. You can find the UUIDs of devices with the <command>blkid</command> command. 
-	</para>
-</important>
diff --git a/en-US/Time_Zone-x86.xml b/en-US/Time_Zone-x86.xml
deleted file mode 100644
index 1bf478c..0000000
--- a/en-US/Time_Zone-x86.xml
+++ /dev/null
@@ -1,53 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<section id="s1-timezone-x86">
-
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Time_Zone_common-title.xml"/>
-	<!-- Time Zone -->
-	
-	<!-- Begin Index Terms -->
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Time_Zone_common-indexterm-1.xml"/>
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Time_Zone_common-indexterm-2.xml"/>
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Time_Zone_common-indexterm-3.xml"/>
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Time_Zone_common-indexterm-4.xml"/>
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Time_Zone_common-indexterm-5.xml"/>
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Time_Zone_common-indexterm-6.xml"/>
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Time_Zone_common-indexterm-7.xml"/>
-	<!-- End Index Terms -->
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Time_Zone_common-para-4.xml"/>
-	<!-- Specify a time zone even if you plan to use NTP...  -->
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Time_Zone_common-para-1.xml"/>
-	<!-- Set your time zone by selecting the city closest  -->
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Time_Zone_common-para-4.xml"/>
-	<!-- Specify a time zone even if you plan to use NTP...  -->
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Time_Zone_common-para-2.xml"/>
-	<!-- From here there are two ways for you to select your time zone: -->
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Time_Zone_common-itemizedlist-1.xml"/>
-	<!-- Using your mouse, click on the interactive map to select a specific city -->
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Time_Zone_common-figure-1.xml"/>
-	<!-- Time zone configuration screen. -->
-	
-	<!-- <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Time_Zone_common-para-3.xml"/> -->
-	<!-- Select System Clock uses UTC if you know that your system is set to UTC. --> 
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Time_Zone_common-para-5.xml"/>
-	<!-- If Fedora is the only operating system on your computer, -->
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Time_Zone_common-note-1.xml"/>
-	<!-- Windows and the System Clock -->
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Time_Zone_common-tip-1.xml"/>
-	<!-- To change your time zone configuration after you have completed the installation, -->
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Time_Zone_common-para-6.xml"/>
-	<!-- Select Next to proceed -->
-	
-</section>
\ No newline at end of file
diff --git a/en-US/Time_Zone_common-figure-1.xml b/en-US/Time_Zone_common-figure-1.xml
deleted file mode 100644
index d12cffa..0000000
--- a/en-US/Time_Zone_common-figure-1.xml
+++ /dev/null
@@ -1,13 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE figure PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<figure float="0"><title>Configuring the Time Zone</title>
-	<mediaobject>
-		<imageobject><imagedata fileref="images/timezone/timezone.png" format="PNG"/></imageobject>
-		<textobject><para>
-				Time zone configuration screen.
-			</para>
-		</textobject>
-	</mediaobject>
-</figure>
\ No newline at end of file
diff --git a/en-US/Time_Zone_common-indexterm-1.xml b/en-US/Time_Zone_common-indexterm-1.xml
deleted file mode 100644
index 17e1516..0000000
--- a/en-US/Time_Zone_common-indexterm-1.xml
+++ /dev/null
@@ -1,8 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE indexterm PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<indexterm significance="normal">
-	<primary>time zone</primary>
-	<secondary>configuration</secondary>
-</indexterm>
\ No newline at end of file
diff --git a/en-US/Time_Zone_common-indexterm-2.xml b/en-US/Time_Zone_common-indexterm-2.xml
deleted file mode 100644
index fcfbef0..0000000
--- a/en-US/Time_Zone_common-indexterm-2.xml
+++ /dev/null
@@ -1,10 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE indexterm PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<indexterm significance="normal">
-	<primary>clock</primary>
-</indexterm>
\ No newline at end of file
diff --git a/en-US/Time_Zone_common-indexterm-3.xml b/en-US/Time_Zone_common-indexterm-3.xml
deleted file mode 100644
index 65eee3a..0000000
--- a/en-US/Time_Zone_common-indexterm-3.xml
+++ /dev/null
@@ -1,11 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE indexterm PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<indexterm significance="normal">
-	<primary>configuration</primary>
-	<secondary>time</secondary>
-</indexterm>
\ No newline at end of file
diff --git a/en-US/Time_Zone_common-indexterm-4.xml b/en-US/Time_Zone_common-indexterm-4.xml
deleted file mode 100644
index a6ef3dd..0000000
--- a/en-US/Time_Zone_common-indexterm-4.xml
+++ /dev/null
@@ -1,11 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE indexterm PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<indexterm significance="normal">
-	<primary>configuration</primary>
-	<secondary>clock</secondary>
-</indexterm>
\ No newline at end of file
diff --git a/en-US/Time_Zone_common-indexterm-5.xml b/en-US/Time_Zone_common-indexterm-5.xml
deleted file mode 100644
index a6ef3dd..0000000
--- a/en-US/Time_Zone_common-indexterm-5.xml
+++ /dev/null
@@ -1,11 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE indexterm PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<indexterm significance="normal">
-	<primary>configuration</primary>
-	<secondary>clock</secondary>
-</indexterm>
\ No newline at end of file
diff --git a/en-US/Time_Zone_common-indexterm-6.xml b/en-US/Time_Zone_common-indexterm-6.xml
deleted file mode 100644
index efa3188..0000000
--- a/en-US/Time_Zone_common-indexterm-6.xml
+++ /dev/null
@@ -1,11 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE indexterm PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<indexterm significance="normal">
-	<primary>configuration</primary>
-	<secondary>time zone</secondary>
-</indexterm>
\ No newline at end of file
diff --git a/en-US/Time_Zone_common-indexterm-7.xml b/en-US/Time_Zone_common-indexterm-7.xml
deleted file mode 100644
index 2df7368..0000000
--- a/en-US/Time_Zone_common-indexterm-7.xml
+++ /dev/null
@@ -1,8 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
- "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
-]>
-
-<indexterm significance="normal">
-    <primary>NTP (Network Time Protocol)</primary>
-    </indexterm>
diff --git a/en-US/Time_Zone_common-itemizedlist-1.xml b/en-US/Time_Zone_common-itemizedlist-1.xml
deleted file mode 100644
index 5f74d5a..0000000
--- a/en-US/Time_Zone_common-itemizedlist-1.xml
+++ /dev/null
@@ -1,20 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE itemizedlist PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<itemizedlist>
-	<listitem>
-		<para>
-			Using your mouse, click on the interactive map to select a specific city (represented by a yellow dot). A red <guilabel>X</guilabel> appears indicating your selection.
-		</para>
-	</listitem>
-	
-	<listitem>
-		<para>
-			You can also scroll through the list at the bottom of the screen to select your time zone. Using your mouse, click on a location to highlight your selection.
-		</para>
-	</listitem>
-</itemizedlist>
\ No newline at end of file
diff --git a/en-US/Time_Zone_common-note-1.xml b/en-US/Time_Zone_common-note-1.xml
deleted file mode 100644
index 9862521..0000000
--- a/en-US/Time_Zone_common-note-1.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
- "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
-]>
-
-    <warning>
-      <title>Windows and the System Clock</title>
-
-      <para>
-        Do not enable the <guilabel>System clock uses UTC</guilabel>
-	option if your machine also runs Microsoft Windows. Microsoft
-	operating systems change the BIOS clock to match local time
-	rather than UTC. This may cause unexpected behavior under Fedora.
-      </para>
-    </warning>
diff --git a/en-US/Time_Zone_common-para-1.xml b/en-US/Time_Zone_common-para-1.xml
deleted file mode 100644
index b1bec59..0000000
--- a/en-US/Time_Zone_common-para-1.xml
+++ /dev/null
@@ -1,10 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<para>
-	Set your time zone by selecting the city closest to your computer's physical location. Click on the map to zoom in to a particular geographical region of the world.
-</para>
\ No newline at end of file
diff --git a/en-US/Time_Zone_common-para-2.xml b/en-US/Time_Zone_common-para-2.xml
deleted file mode 100644
index ec87f69..0000000
--- a/en-US/Time_Zone_common-para-2.xml
+++ /dev/null
@@ -1,10 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<para>
-	From here there are two ways for you to select your time zone:
-</para>
\ No newline at end of file
diff --git a/en-US/Time_Zone_common-para-4.xml b/en-US/Time_Zone_common-para-4.xml
deleted file mode 100644
index df49536..0000000
--- a/en-US/Time_Zone_common-para-4.xml
+++ /dev/null
@@ -1,10 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
- "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
-]>
-
-  <para>
-    Specify a time zone even if you plan to
-    use NTP (Network Time Protocol) to maintain the accuracy of
-    the system clock.
-  </para>
diff --git a/en-US/Time_Zone_common-para-5.xml b/en-US/Time_Zone_common-para-5.xml
deleted file mode 100644
index 727f1e6..0000000
--- a/en-US/Time_Zone_common-para-5.xml
+++ /dev/null
@@ -1,13 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
- "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
-]>
-
-<para>
-      If Fedora is the only operating system on your computer, select
-      <guilabel>System clock uses UTC</guilabel>. The system clock is a
-      piece of hardware on your computer system. Fedora uses the timezone
-      setting to determine the offset between the local time and UTC on
-      the system clock. This behavior is standard for UNIX-like
-      operating systems.
-</para>
\ No newline at end of file
diff --git a/en-US/Time_Zone_common-para-6.xml b/en-US/Time_Zone_common-para-6.xml
deleted file mode 100644
index 89f1d2b..0000000
--- a/en-US/Time_Zone_common-para-6.xml
+++ /dev/null
@@ -1,8 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
- "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
-]>
-
-    <para>
-      Select <guibutton>Next</guibutton> to proceed.
-    </para>
\ No newline at end of file
diff --git a/en-US/Time_Zone_common-tip-1.xml b/en-US/Time_Zone_common-tip-1.xml
deleted file mode 100644
index 9d7b33e..0000000
--- a/en-US/Time_Zone_common-tip-1.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE tip PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<note><title>Note</title>
-	<para>
-		To change your time zone configuration after you have completed the installation, use the <application>Time and Date Properties Tool</application>.
-	</para>
-	<para>
-		Type the <command>system-config-date</command> command in a shell prompt to launch the <application>Time and Date Properties Tool</application>. If you are not root, it prompts you for the root password to continue.
-	</para>
-</note>
\ No newline at end of file
diff --git a/en-US/Time_Zone_common-title.xml b/en-US/Time_Zone_common-title.xml
deleted file mode 100644
index fed8ad5..0000000
--- a/en-US/Time_Zone_common-title.xml
+++ /dev/null
@@ -1,5 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE title PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<title>Time Zone Configuration</title>
\ No newline at end of file
diff --git a/en-US/Trouble-x86.xml b/en-US/Trouble-x86.xml
deleted file mode 100644
index bb84dc1..0000000
--- a/en-US/Trouble-x86.xml
+++ /dev/null
@@ -1,313 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE appendix PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<chapter id="ch-trouble-x86">
-	
-	<title>Troubleshooting Installation on an <trademark class="registered">Intel</trademark> or AMD System</title>
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Trouble_common-indexterm-1.xml"/>
-	<!-- Index term -->
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Trouble_common-indexterm-2.xml"/>
-	<!-- Index term -->
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Trouble_common-indexterm-3.xml"/>
-	<!-- Index term -->
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Trouble_common-indexterm-4.xml"/>
-	<!-- Index term -->
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Trouble_common-indexterm-5.xml"/>
-	<!-- Index term -->
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Trouble_common-indexterm-6.xml"/>
-	<!-- Index term -->
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Trouble_common-indexterm-7.xml"/>
-	<!-- Index term -->
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Trouble_common-indexterm-8.xml"/>
-	<!-- Index term -->
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Trouble_common-para-1.xml"/>
-	<!-- This appendix discusses some common installation problems and their solutions. -->
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Trouble_common-para-2.xml"/>
-	<!-- For debugging purposes, anaconda logs installation actions into files in the /tmp directory. -->
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Trouble_common-variablelist-1.xml"/>
-	<!-- /tmp/anaconda.log General anaconda messages -->
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Trouble_common-para-3.xml"/>
-	<!-- If the installation fails, the messages from these files are consolidated into /tmp/anacdump.txt -->
-
-	<section>
-	<!-- Problems with Booting -->
-		
-		<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Trouble_No_Boot-title-1.xml"/>
-		<!-- You are Unable to Boot... -->
-		
-		<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Trouble_No_Boot-indexterm-1.xml"/>
-		<!-- Indexterm -->
-		
-		<section>
-			<title>Are You Unable to Boot With Your RAID Card?</title>
-			<indexterm significance="normal">
-				<primary>troubleshooting</primary>
-				<secondary>booting</secondary>
-				<tertiary>RAID cards</tertiary>
-			</indexterm>
-			<indexterm significance="normal">
-				<primary>RAID</primary>
-				<secondary>trouble booting from drive attached to RAID card</secondary>
-			</indexterm>
-			<para>
-				If you have performed an installation and cannot boot your system properly, you may need to reinstall and create your partitions differently.
-			</para>
-			
-			<para>
-				Some BIOSes do not support booting from RAID cards. At the end of an installation, a text-based screen showing the boot loader prompt (for example,
-				<prompt moreinfo="none">GRUB:</prompt>
-				) and a flashing cursor may be all that appears. If this is the case, you must repartition your system.
-			</para>
-			
-			<para>
-				Whether you choose automatic or manual partitioning, you must install your <filename moreinfo="none">/boot</filename> partition outside of the RAID array, such as on a separate hard drive. An internal hard drive is necessary to use for partition
-				creation with problematic RAID cards.
-			</para>
-			
-			<para>
-				You must also install your preferred boot loader (GRUB or LILO) on the MBR of a drive that is outside of the RAID array. This should be the same drive that hosts the <filename moreinfo="none">/boot/</filename> partition.
-			</para>
-			
-			<para>
-				Once these changes have been made, you should be able to finish your installation and boot the system properly.
-			</para>
-		</section>
-		
-		<section>
-			<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Trouble_No_Boot-Sig11-title-1.xml"/>
-			<!-- Is Your System Displaying Signal 11 Errors? -->
-			
-			<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Trouble_No_Boot-Sig11-indexterm-1.xml"/>
-			<!-- Index terms -->
-			
-			<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Trouble_No_Boot-Sig11-para-1.xml"/>
-			<!-- A signal 11 error, commonly know as a segmentation fault, means -->
-			
-			<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Trouble_No_Boot-Sig11-para-2.xml"/>
-			<!-- If you receive a fatal signal 11 error during your installation, --> 
-			
-			<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Trouble_No_Boot-Sig11-para-3.xml"/>
-			<!-- Ensure that you have the latest installation updates and images from Red Hat. -->
-			
-			
-			
-			<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Trouble_No_Boot-Sig11-para-7.xml"/>
-			<!-- Another option is to perform a media check on your installation CD-ROMs. -->
-			
-			<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Trouble_No_Boot-Sig11-screen-2.xml"/>
-			<!-- linux media check -->
-			
-			<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Trouble_No_Boot-Sig11-para-8.xml"/>
-			<!-- For more information concerning signal 11 errors, refer to: -->
-			
-			<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Trouble_No_Boot-Sig11-screen-3.xml"/>		
-			<!-- http://www.bitwizard.nl/sig11/ -->
-		</section>
-	</section>
-	
-	<!-- Trouble Beginning the Installation
-		Problems with Booting into the Graphical Installation
-		-->
-	<section>
-		<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Trouble_Begin_x86_ppc_title-1.xml"/>
-		<!-- Trouble Beginning the Installation -->
-		
-		<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Trouble_Begin_x86_ppc_indexterm-1.xml"/>
-		<!-- Indexterm -->
-		
-		<section>
-			<!-- Problems with Booting into the Graphical Installation -->
-			
-			<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Trouble_Begin_GUI-title.xml"/>
-			<!-- Problems with Booting into the Graphical Installation -->
-			
-			<!-- Begin Indexterms -->
-			<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Trouble_Begin_GUI-indexterm-1.xml"/>
-			<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Trouble_Begin_GUI-indexterm-2.xml"/>
-			<!-- End of index terms -->
-						
-			<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Trouble_Begin_GUI-para-1.xml"/>
-			<!-- There are some video cards that have trouble booting -->
-			
-			<para>
-				One possible solution is to use only a basic video driver during installation. You can do this either by selecting <guilabel>Install system with basic video driver</guilabel> on the boot menu, or using the <command moreinfo="none">xdriver=vesa</command> boot option at the boot prompt. Alternatively, you can force the installer to use a specific screen resolution with the <command moreinfo="none">resolution=</command> boot option. This option may be most helpful for laptop users. Another solution to try is the <command>driver=</command> option to specify the driver that should be loaded for your video card. If this works, you should report it as a bug, because the installer failed to detect your video card automatically. Refer to <xref linkend="ap-admin-options"/> for more information on boot options.
-			</para>
-			
-			<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Trouble_Begin_GUI-note-1.xml"/>
-			<!-- To disable frame buffer support and allow the installation -->
-		</section>
-			
-	</section>
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Trouble_During-x86.xml"/> 
-	<!-- Trouble During the Installation
-	     No devices found to install Red Hat Enterprise Linux Error Message
-	     Saving Traceback Messages Without removeable media
-	     Trouble with Partition Tables
-	     Using Remaining Space
-	     Other Partitioning Problems
-	     Other Partitioning Problems for Itanium System Users
-	     Are You Seeing Python Errors?
-	     -->
-	
-	<section>
-		<!-- Trouble After -->
-	
-		<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Trouble_After_common-title-1.xml"/>
-		<!-- Title: Problems After Installation -->
-	
-		<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Trouble_After_common-indexterm-1.xml"/>
-		<!-- Index term -->
-	
-		<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="X86_Trouble_After_Grub.xml"/>
-		<!-- Trouble With the Graphical GRUB Screen on an x86-based System? -->
-	
-		<section id="Trouble_After_Booting-GUI">
-			<!-- Booting into a Graphical Environment -->
-			
-			<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Trouble_After_Booting_GUI_x86_ppc-title-1.xml"/>
-			<!-- Title: Booting into a Graphical Environment -->
-			
-			<!-- Begin Index Terms -->
-			<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Trouble_After_Booting_GUI-indexterm-1.xml"/>
-			<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Trouble_After_Booting_GUI-indexterm-2.xml"/>
-			<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Trouble_After_Booting_GUI-indexterm-3.xml"/>
-			<!-- End Index Terms -->
-			
-			<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Trouble_After_Booting_GUI-para-1.xml"/>
-			<!-- If you have installed the X Window System but are not seeing a graphical desktop environment -->
-			
-			<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Trouble_After_Booting_GUI-para-2.xml"/>
-			<!-- Once you enter this command and press Enter -->
-			
-			<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Trouble_After_Booting_GUI-para-3.xml"/>
-			<!-- Note, however, that this is just a one-time fix -->
-			
-			<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Trouble_After_Booting_GUI-para-4.xml"/>
-			<!-- To set up your system so that you can log in at a graphical login screen, -->
-			
-			<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Trouble_After_Booting_GUI-para-5.xml"/>
-			<!-- Open a shell prompt. If you are in your user account -->
-			
-			<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Trouble_After_Booting_GUI-para-6.xml"/>
-			<!-- Now, type gedit /etc/inittab to edit the file with -->
-			
-			<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Trouble_After_Booting_GUI-screen-1.xml"/>
-			<!--  Default runlevel. The runlevels used by RHS are: -->
-			
-			<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Trouble_After_Booting_GUI-para-7.xml"/>
-			<!-- To change from a console to a graphical login, -->
-			
-			<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Trouble_After_Booting_GUI-warning-1.xml"/>
-			<!-- Change only the number of the default runlevel from 3 to 5 -->
-			
-			<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Trouble_After_Booting_GUI-para-8.xml"/>
-			<!-- Your changed line should look like the following: -->
-			
-			<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Trouble_After_Booting_GUI-screen-2.xml"/>
-			<!-- id:5:initdefault: -->
-			
-			<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Trouble_After_Booting_GUI-para-9.xml"/>
-			<!-- When you are satisfied with your change, save and exit the file using the -->	
-			
-			<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Trouble_After_Booting_GUI-para-10.xml"/>
-			<!-- The next time you log in after rebooting your system -->
-			
-		</section>
-		
-		<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Trouble_After_Booting_X_Windows.xml"/>
-		<!-- Problems with the X Window System (GUI) -->
-			
-		<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Trouble_After_Booting_X_Server_Non_Root.xml"/>
-		<!-- Problems with the X Server Crashing and Non-Root Users -->
-		
-		<section>
-			<!-- Problems When You Try to Log In -->
-			
-			<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Trouble_After_Booting_Problems_Login-title-1.xml"/>
-			<!-- Title: Problems When You Try to Log In -->
-			
-			<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Trouble_After_Booting_Problems_Login-indexterm-1.xml"/>
-			<!-- Index term -->
-			
-			<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Trouble_After_Booting_Problems_Login-para-1.xml"/>
-			<!-- If you did not create a user account in the Setup Agent -->
-			
-			<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Trouble_After_Booting_Problems_Login-para-2.xml"/>
-			<!-- If you cannot remember your root password, boot your system as linux single -->
-			
-			<!-- (RHEL) <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Trouble_After_Booting_Problems_Login-para-3.xml"/> -->
-			<!-- Itanium users must enter boot commands with elilo followed by the boot command. -->
-			
-			<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Trouble_After_Booting_Problems_Login-para-4.xml"/>
-			<!-- If you are using an x86-based system and GRUB is your installed boot loader -->
-			
-			<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Trouble_After_Booting_Problems_Login-para-5.xml"/>
-			<!-- Choose the line that starts with <filename moreinfo="none">kernel -->	
-				
-			<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Trouble_After_Booting_Problems_Login-para-6.xml"/>
-			<!-- At the end of the kernel line, add: -->
-			
-			<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Trouble_After_Booting_Problems_Login-screen-1.xml"/>
-			<!-- single -->
-			
-			<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Trouble_After_Booting_Problems_Login-para-7.xml"/>
-			<!-- Press Enter to exit edit mode -->
-			
-			<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Trouble_After_Booting_Problems_Login-para-8.xml"/>
-			<!-- Once the boot loader screen has returned, type b to boot the system. -->
-			
-			<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Trouble_After_Booting_Problems_Login-para-9.xml"/>
-			<!-- Once you have booted into single user mode and have access to the -->
-			
-			<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Trouble_After_Booting_Problems_Login-para-10.xml"/>
-			<!-- If you cannot remember your user account password, you must become root. -->
-			
-			<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Trouble_After_Booting_Problems_Login-para-11.xml"/>
-			<!-- If the graphical login screen does not appear -->
-			
-			<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Trouble_After_Booting_Problems_Login-screen-2.xml"/>
-			<!-- http://hardware.redhat.com/hcl/ -->
-		</section>
-		
-		<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Trouble_After_Ram.xml"/>
-		<!-- Is Your RAM Not Being Recognized? -->
-		
-		<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Trouble_After_Booting_Problems-Printer.xml"/>
-		<!-- Your Printer Does Not Work -->
-		
-		<!-- <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Trouble_After_Sound.xml"/> -->
-		<!-- Problems with Sound Configuration -->
-		
-		<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Trouble_After_Booting_Problems-Apache.xml"/>
-		<!-- Apache-based httpd service/Sendmail Hangs During Startup -->
-		
-	<!--	<section id="s2-trouble-nvidia">
-			<title>Trouble with NVIDIA chipset</title>
-			<indexterm significance="normal">
-				<primary>troubleshooting</primary>
-				<secondary>after the installation</secondary>
-				<tertiary>NVIDIA</tertiary>
-			</indexterm>
-			<para>
-				If you have an NVIDIA chipset and have just updated your kernel, you may experience problems with the video card, such as not having any video output.
-			</para>
-			
-			<para>
-				If you experience a similar problem, you should download the latest kernel drivers available for your NVIDIA chipset. For more information, refer to:
-			</para>
-			<screen>
-<ulink url="http://www.nvidia.com/view.asp?IO=linux_display_archive">http://www.nvidia.com/view.asp?IO=linux_display_1.0-3123</ulink>
-			</screen>
-		</section> -->
-		
-		
-	</section>
-	
-</chapter>
diff --git a/en-US/Trouble_After_Booting_GUI-indexterm-1.xml b/en-US/Trouble_After_Booting_GUI-indexterm-1.xml
deleted file mode 100644
index 05eaab0..0000000
--- a/en-US/Trouble_After_Booting_GUI-indexterm-1.xml
+++ /dev/null
@@ -1,12 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE indexterm PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<indexterm significance="normal">
-	<primary>troubleshooting</primary>
-	<secondary>after the installation</secondary>
-	<tertiary>booting into a graphical environment</tertiary>
-</indexterm>
\ No newline at end of file
diff --git a/en-US/Trouble_After_Booting_GUI-indexterm-2.xml b/en-US/Trouble_After_Booting_GUI-indexterm-2.xml
deleted file mode 100644
index 3785b47..0000000
--- a/en-US/Trouble_After_Booting_GUI-indexterm-2.xml
+++ /dev/null
@@ -1,12 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE indexterm PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<indexterm significance="normal">
-	<primary>troubleshooting</primary>
-	<secondary>after the installation</secondary>
-	<tertiary>booting into the X Window System</tertiary>
-</indexterm>
\ No newline at end of file
diff --git a/en-US/Trouble_After_Booting_GUI-indexterm-3.xml b/en-US/Trouble_After_Booting_GUI-indexterm-3.xml
deleted file mode 100644
index 78149f4..0000000
--- a/en-US/Trouble_After_Booting_GUI-indexterm-3.xml
+++ /dev/null
@@ -1,12 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE indexterm PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<indexterm significance="normal">
-	<primary>troubleshooting</primary>
-	<secondary>after the installation</secondary>
-	<tertiary>booting into GNOME or KDE</tertiary>
-</indexterm>
\ No newline at end of file
diff --git a/en-US/Trouble_After_Booting_GUI-para-1.xml b/en-US/Trouble_After_Booting_GUI-para-1.xml
deleted file mode 100644
index c2a7d2d..0000000
--- a/en-US/Trouble_After_Booting_GUI-para-1.xml
+++ /dev/null
@@ -1,8 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<para>
-	If you have installed the X Window System but are not seeing a graphical desktop environment once you log into your system, you can start the X Window System graphical interface using the command
-	<command moreinfo="none">startx</command>.
-</para>
\ No newline at end of file
diff --git a/en-US/Trouble_After_Booting_GUI-para-10.xml b/en-US/Trouble_After_Booting_GUI-para-10.xml
deleted file mode 100644
index 92f2c89..0000000
--- a/en-US/Trouble_After_Booting_GUI-para-10.xml
+++ /dev/null
@@ -1,10 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<para>
-	The next time you log in after rebooting your system, you are presented with a graphical login prompt.
-</para>
\ No newline at end of file
diff --git a/en-US/Trouble_After_Booting_GUI-para-2.xml b/en-US/Trouble_After_Booting_GUI-para-2.xml
deleted file mode 100644
index dcc026f..0000000
--- a/en-US/Trouble_After_Booting_GUI-para-2.xml
+++ /dev/null
@@ -1,10 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<para>
-	Once you enter this command and press <keycap moreinfo="none">Enter</keycap>, the graphical desktop environment is displayed.
-</para>
\ No newline at end of file
diff --git a/en-US/Trouble_After_Booting_GUI-para-3.xml b/en-US/Trouble_After_Booting_GUI-para-3.xml
deleted file mode 100644
index 36efc1f..0000000
--- a/en-US/Trouble_After_Booting_GUI-para-3.xml
+++ /dev/null
@@ -1,10 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<para>
-	Note, however, that this is just a one-time fix and does not change the log in process for future log ins.
-</para>
\ No newline at end of file
diff --git a/en-US/Trouble_After_Booting_GUI-para-4.xml b/en-US/Trouble_After_Booting_GUI-para-4.xml
deleted file mode 100644
index d19b262..0000000
--- a/en-US/Trouble_After_Booting_GUI-para-4.xml
+++ /dev/null
@@ -1,11 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<para>
-	To set up your system so that you can log in at a graphical login screen, you must edit one file, <filename moreinfo="none">/etc/inittab</filename>, by changing just one number in the runlevel section. When you are finished, reboot the computer. The
-	next time you log in, you are presented with a graphical login prompt.
-</para>
\ No newline at end of file
diff --git a/en-US/Trouble_After_Booting_GUI-para-5.xml b/en-US/Trouble_After_Booting_GUI-para-5.xml
deleted file mode 100644
index 1326998..0000000
--- a/en-US/Trouble_After_Booting_GUI-para-5.xml
+++ /dev/null
@@ -1,10 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<para>
-	Open a shell prompt. If you are in your user account, become root by typing the <command moreinfo="none">su</command> command.
-</para>
\ No newline at end of file
diff --git a/en-US/Trouble_After_Booting_GUI-para-6.xml b/en-US/Trouble_After_Booting_GUI-para-6.xml
deleted file mode 100644
index 2b20c9a..0000000
--- a/en-US/Trouble_After_Booting_GUI-para-6.xml
+++ /dev/null
@@ -1,11 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<para>
-	Now, type <command moreinfo="none">gedit /etc/inittab</command> to edit the file with <application moreinfo="none">gedit</application>. The file <filename moreinfo="none">/etc/inittab</filename> opens. Within the first screen, a section of the file
-	which looks like the following appears:
-</para>
\ No newline at end of file
diff --git a/en-US/Trouble_After_Booting_GUI-para-7.xml b/en-US/Trouble_After_Booting_GUI-para-7.xml
deleted file mode 100644
index d393653..0000000
--- a/en-US/Trouble_After_Booting_GUI-para-7.xml
+++ /dev/null
@@ -1,11 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<para>
-	To change from a console to a graphical login, you should change the number in the line <computeroutput moreinfo="none">id:3:initdefault:</computeroutput> from a <computeroutput moreinfo="none">3</computeroutput> to a
-	<computeroutput moreinfo="none">5</computeroutput>.
-</para>
\ No newline at end of file
diff --git a/en-US/Trouble_After_Booting_GUI-para-8.xml b/en-US/Trouble_After_Booting_GUI-para-8.xml
deleted file mode 100644
index cc248bf..0000000
--- a/en-US/Trouble_After_Booting_GUI-para-8.xml
+++ /dev/null
@@ -1,10 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<para>
-	Your changed line should look like the following:
-</para>
\ No newline at end of file
diff --git a/en-US/Trouble_After_Booting_GUI-para-9.xml b/en-US/Trouble_After_Booting_GUI-para-9.xml
deleted file mode 100644
index 7e6f7c1..0000000
--- a/en-US/Trouble_After_Booting_GUI-para-9.xml
+++ /dev/null
@@ -1,13 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<para>
-	When you are satisfied with your change, save and exit the file using the
-	<keycombo moreinfo="none"><keycap moreinfo="none">Ctrl</keycap><keycap moreinfo="none">Q</keycap>
-	</keycombo>
-	keys. A window appears and asks if you would like to save the changes. Click <guibutton moreinfo="none">Save</guibutton>.
-</para>
\ No newline at end of file
diff --git a/en-US/Trouble_After_Booting_GUI-screen-1.xml b/en-US/Trouble_After_Booting_GUI-screen-1.xml
deleted file mode 100644
index 95265b0..0000000
--- a/en-US/Trouble_After_Booting_GUI-screen-1.xml
+++ /dev/null
@@ -1,14 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE screen PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<screen># Default runlevel. The runlevels used are: 
-#   0 - halt (Do NOT set initdefault to this) 
-#   1 - Single user mode 
-#   2 - Multiuser, without NFS (The same as 3, if you do not have networking) 
-#   3 - Full multiuser mode 
-#   4 - unused 
-#   5 - X11 
-#   6 - reboot (Do NOT set initdefault to this) 
-#  id:3:initdefault:
-</screen>
\ No newline at end of file
diff --git a/en-US/Trouble_After_Booting_GUI-screen-2.xml b/en-US/Trouble_After_Booting_GUI-screen-2.xml
deleted file mode 100644
index c1c733a..0000000
--- a/en-US/Trouble_After_Booting_GUI-screen-2.xml
+++ /dev/null
@@ -1,10 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE screen PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<screen>
-	<computeroutput moreinfo="none">	id:5:initdefault:       </computeroutput>
-</screen>
\ No newline at end of file
diff --git a/en-US/Trouble_After_Booting_GUI-warning-1.xml b/en-US/Trouble_After_Booting_GUI-warning-1.xml
deleted file mode 100644
index f405f06..0000000
--- a/en-US/Trouble_After_Booting_GUI-warning-1.xml
+++ /dev/null
@@ -1,14 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE warning PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<warning>
-	<title>Warning</title>
-	
-	<para>
-		Change <emphasis>only</emphasis> the number of the default runlevel from <filename moreinfo="none">3</filename> to <filename moreinfo="none">5</filename>.
-	</para>
-</warning>
\ No newline at end of file
diff --git a/en-US/Trouble_After_Booting_GUI_x86_ppc-title-1.xml b/en-US/Trouble_After_Booting_GUI_x86_ppc-title-1.xml
deleted file mode 100644
index 546d305..0000000
--- a/en-US/Trouble_After_Booting_GUI_x86_ppc-title-1.xml
+++ /dev/null
@@ -1,8 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE title PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<title>Booting into a Graphical Environment</title>
\ No newline at end of file
diff --git a/en-US/Trouble_After_Booting_Problems-Apache.xml b/en-US/Trouble_After_Booting_Problems-Apache.xml
deleted file mode 100644
index 0cda463..0000000
--- a/en-US/Trouble_After_Booting_Problems-Apache.xml
+++ /dev/null
@@ -1,24 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<section>
-	<title>Apache-based <command moreinfo="none">httpd</command> service/Sendmail Hangs During Startup</title>
-	<indexterm significance="normal">
-		<primary>troubleshooting</primary>
-		<secondary>after the       installation</secondary>
-		<tertiary>Apache-based <command moreinfo="none">httpd</command>       service hangs during startup</tertiary>
-	</indexterm>
-	<indexterm significance="normal">
-		<primary>troubleshooting</primary>
-		<secondary>after the installation</secondary>
-		<tertiary>Sendmail hangs during startup</tertiary>
-	</indexterm>
-	<para>
-		If you are having trouble with the Apache-based <command moreinfo="none">httpd</command> service or Sendmail hanging at startup, make sure the following line is in the <filename moreinfo="none">/etc/hosts</filename> file:
-	</para>
-	<screen>127.0.0.1  localhost.localdomain  localhost</screen>
-</section>
diff --git a/en-US/Trouble_After_Booting_Problems-Printer.xml b/en-US/Trouble_After_Booting_Problems-Printer.xml
deleted file mode 100644
index d3e7504..0000000
--- a/en-US/Trouble_After_Booting_Problems-Printer.xml
+++ /dev/null
@@ -1,22 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<section>
-	<title>Your Printer Does Not Work</title>
-	<indexterm significance="normal">
-		<primary>troubleshooting</primary>
-		<secondary>after the installation</secondary>
-		<tertiary>printers</tertiary>
-	</indexterm>
-	<para>
-		If you are not sure how to set up your printer or are having trouble getting it to work properly, try using the <application moreinfo="none">Printer Configuration Tool</application>.
-	</para>
-	
-	<para>
-		Type the <command moreinfo="none">system-config-printer</command> command at a shell prompt to launch the <application moreinfo="none">Printer Configuration Tool</application>. If you are not root, it prompts you for the root password to continue.
-	</para>
-</section>
diff --git a/en-US/Trouble_After_Booting_Problems_Login-indexterm-1.xml b/en-US/Trouble_After_Booting_Problems_Login-indexterm-1.xml
deleted file mode 100644
index 40a76a2..0000000
--- a/en-US/Trouble_After_Booting_Problems_Login-indexterm-1.xml
+++ /dev/null
@@ -1,12 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE indexterm PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<indexterm significance="normal">
-	<primary>troubleshooting</primary>
-	<secondary>after the installation</secondary>
-	<tertiary>logging in</tertiary>
-</indexterm>
\ No newline at end of file
diff --git a/en-US/Trouble_After_Booting_Problems_Login-para-1.xml b/en-US/Trouble_After_Booting_Problems_Login-para-1.xml
deleted file mode 100644
index 483ea83..0000000
--- a/en-US/Trouble_After_Booting_Problems_Login-para-1.xml
+++ /dev/null
@@ -1,7 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<para>
-	If you did not create a user account in the <application>firstboot</application> screens, switch to a console by pressing <keycombo><keycap>Ctrl</keycap><keycap>Alt</keycap><keycap>F2</keycap></keycombo>, log in as root and use the password you assigned to root.
-</para>
\ No newline at end of file
diff --git a/en-US/Trouble_After_Booting_Problems_Login-para-10.xml b/en-US/Trouble_After_Booting_Problems_Login-para-10.xml
deleted file mode 100644
index dd4d020..0000000
--- a/en-US/Trouble_After_Booting_Problems_Login-para-10.xml
+++ /dev/null
@@ -1,11 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<para>
-	If you cannot remember your user account password, you must become root. To become root, type <command moreinfo="none">su -</command> and enter your root password when prompted. Then, type <command moreinfo="none">passwd &lt;username&gt;</command>.
-	This allows you to enter a new password for the specified user account.
-</para>
\ No newline at end of file
diff --git a/en-US/Trouble_After_Booting_Problems_Login-para-11.xml b/en-US/Trouble_After_Booting_Problems_Login-para-11.xml
deleted file mode 100644
index fb113e8..0000000
--- a/en-US/Trouble_After_Booting_Problems_Login-para-11.xml
+++ /dev/null
@@ -1,7 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<para>
-	If the graphical login screen does not appear, check your hardware for compatibility issues. <!-- (RHEL) The <citetitle>Hardware Compatibility List</citetitle> can be found at:-->Linuxquestions.org maintains a Hardware Compatibility List at:
-</para>
\ No newline at end of file
diff --git a/en-US/Trouble_After_Booting_Problems_Login-para-2.xml b/en-US/Trouble_After_Booting_Problems_Login-para-2.xml
deleted file mode 100644
index 9b0c74a..0000000
--- a/en-US/Trouble_After_Booting_Problems_Login-para-2.xml
+++ /dev/null
@@ -1,10 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<para>
-	If you cannot remember your root password, boot your system as <command moreinfo="none">linux single</command>.
-</para>
\ No newline at end of file
diff --git a/en-US/Trouble_After_Booting_Problems_Login-para-4.xml b/en-US/Trouble_After_Booting_Problems_Login-para-4.xml
deleted file mode 100644
index b1fb9f3..0000000
--- a/en-US/Trouble_After_Booting_Problems_Login-para-4.xml
+++ /dev/null
@@ -1,11 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<para>
-	If you are using an x86-based system and GRUB is your installed boot loader, type <command moreinfo="none">e</command> for edit when the GRUB boot screen has loaded. You are presented with a list of items in the configuration file for the boot label you
-	have selected.
-</para>
\ No newline at end of file
diff --git a/en-US/Trouble_After_Booting_Problems_Login-para-5.xml b/en-US/Trouble_After_Booting_Problems_Login-para-5.xml
deleted file mode 100644
index 418a67d..0000000
--- a/en-US/Trouble_After_Booting_Problems_Login-para-5.xml
+++ /dev/null
@@ -1,10 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<para>
-	Choose the line that starts with <filename moreinfo="none">kernel</filename> and type <command moreinfo="none">e</command> to edit this boot entry.
-</para>
\ No newline at end of file
diff --git a/en-US/Trouble_After_Booting_Problems_Login-para-6.xml b/en-US/Trouble_After_Booting_Problems_Login-para-6.xml
deleted file mode 100644
index ba11fe9..0000000
--- a/en-US/Trouble_After_Booting_Problems_Login-para-6.xml
+++ /dev/null
@@ -1,10 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<para>
-	At the end of the <filename moreinfo="none">kernel</filename> line, add:
-</para>
\ No newline at end of file
diff --git a/en-US/Trouble_After_Booting_Problems_Login-para-7.xml b/en-US/Trouble_After_Booting_Problems_Login-para-7.xml
deleted file mode 100644
index ade775c..0000000
--- a/en-US/Trouble_After_Booting_Problems_Login-para-7.xml
+++ /dev/null
@@ -1,10 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<para>
-	Press <keycap moreinfo="none">Enter</keycap> to exit edit mode.
-</para>
\ No newline at end of file
diff --git a/en-US/Trouble_After_Booting_Problems_Login-para-8.xml b/en-US/Trouble_After_Booting_Problems_Login-para-8.xml
deleted file mode 100644
index 2d0fa57..0000000
--- a/en-US/Trouble_After_Booting_Problems_Login-para-8.xml
+++ /dev/null
@@ -1,10 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<para>
-	Once the boot loader screen has returned, type <command moreinfo="none">b</command> to boot the system.
-</para>
\ No newline at end of file
diff --git a/en-US/Trouble_After_Booting_Problems_Login-para-9.xml b/en-US/Trouble_After_Booting_Problems_Login-para-9.xml
deleted file mode 100644
index fc96d45..0000000
--- a/en-US/Trouble_After_Booting_Problems_Login-para-9.xml
+++ /dev/null
@@ -1,12 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<para>
-	Once you have booted into single user mode and have access to the
-	<prompt moreinfo="none">#</prompt>
-	prompt, you must type <command moreinfo="none">passwd root</command>, which allows you to enter a new password for root. At this point you can type <command moreinfo="none">shutdown -r now</command> to reboot the system with the new root password.
-</para>
\ No newline at end of file
diff --git a/en-US/Trouble_After_Booting_Problems_Login-screen-1.xml b/en-US/Trouble_After_Booting_Problems_Login-screen-1.xml
deleted file mode 100644
index 3165f77..0000000
--- a/en-US/Trouble_After_Booting_Problems_Login-screen-1.xml
+++ /dev/null
@@ -1,10 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE screen PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<screen>
-	<userinput moreinfo="none">single</userinput>
-</screen>
\ No newline at end of file
diff --git a/en-US/Trouble_After_Booting_Problems_Login-screen-2.xml b/en-US/Trouble_After_Booting_Problems_Login-screen-2.xml
deleted file mode 100644
index 76ee2ed..0000000
--- a/en-US/Trouble_After_Booting_Problems_Login-screen-2.xml
+++ /dev/null
@@ -1,12 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE screen PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<screen>
-	<ulink url="http://www.linuxquestions.org/hcl/index.php">http://www.linuxquestions.org/hcl/index.php</ulink>
-</screen>
-
-<!-- (RHEL)
-<screen>
-	<ulink url="http://hardware.redhat.com/hcl/">http://hardware.redhat.com/hcl/</ulink>
-</screen> -->
\ No newline at end of file
diff --git a/en-US/Trouble_After_Booting_Problems_Login-title-1.xml b/en-US/Trouble_After_Booting_Problems_Login-title-1.xml
deleted file mode 100644
index 7326b1a..0000000
--- a/en-US/Trouble_After_Booting_Problems_Login-title-1.xml
+++ /dev/null
@@ -1,8 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE title PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<title>Problems When You Try to Log In</title>
\ No newline at end of file
diff --git a/en-US/Trouble_After_Booting_X_Server_Non_Root.xml b/en-US/Trouble_After_Booting_X_Server_Non_Root.xml
deleted file mode 100644
index 3ca865a..0000000
--- a/en-US/Trouble_After_Booting_X_Server_Non_Root.xml
+++ /dev/null
@@ -1,32 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<section>
-	<title>Problems with the X Server Crashing and Non-Root Users</title>
-	<indexterm significance="normal">
-		<primary>troubleshooting</primary>
-		<secondary>after the installation</secondary>
-		<tertiary>X server crashes</tertiary>
-	</indexterm>
-	<para>
-		If you are having trouble with the X server crashing when anyone logs in, you may have a full file system (or, a lack of available hard drive space).
-	</para>
-	
-	<para>
-		To verify that this is the problem you are experiencing, run the following command:
-	</para>
-	<screen>df -h</screen>
-	<para>
-		The <command moreinfo="none">df</command> command should help you diagnose which partition is full. For additional information about <command moreinfo="none">df</command> and an explanation of the options available (such as the <option>-h</option>
-		option used in this example), refer to the <command moreinfo="none">df</command> man page by typing <command moreinfo="none">man df</command> at a shell prompt.
-	</para>
-	
-	<para>
-		A key indicator is 100% full or a percentage above 90% or 95% on a partition. The <filename moreinfo="none">/home/</filename> and <filename moreinfo="none">/tmp/</filename> partitions can sometimes fill up quickly with user files. You can make some room
-		on that partition by removing old files. After you free up some disk space, try running X as the user that was unsuccessful before.
-	</para>
-</section>
\ No newline at end of file
diff --git a/en-US/Trouble_After_Booting_X_Windows.xml b/en-US/Trouble_After_Booting_X_Windows.xml
deleted file mode 100644
index 334ce84..0000000
--- a/en-US/Trouble_After_Booting_X_Windows.xml
+++ /dev/null
@@ -1,26 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<section>
-	<title>Problems with the X Window System (GUI)</title>
-	<indexterm significance="normal">
-		<primary>troubleshooting</primary>
-		<secondary>after the installation</secondary>
-		<tertiary>X (X Window System)</tertiary>
-	</indexterm>
-	<para>
-		If you are having trouble getting X (the X Window System) to start, you may not have installed it during your installation.
-	</para>
-	
-	<para>
-		If you want X, you can either install the packages from the Fedora installation media or perform an upgrade.
-	</para>
-	
-	<para>
-		If you elect to upgrade, select the X Window System packages, and choose GNOME, KDE, or both, during the upgrade package selection process.
-	</para>
-	<para>
-		Refer to <xref linkend="sn-switching-to-gui-login"/> for more detail on installing a desktop environment. 
-	</para>
-</section>
\ No newline at end of file
diff --git a/en-US/Trouble_After_Ram.xml b/en-US/Trouble_After_Ram.xml
deleted file mode 100644
index e44473e..0000000
--- a/en-US/Trouble_After_Ram.xml
+++ /dev/null
@@ -1,89 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<section id="s2-trouble-ram">
-	<title>Is Your RAM Not Being Recognized?</title>
-	<indexterm significance="normal">
-		<primary>troubleshooting</primary>
-		<secondary>after the installation</secondary>
-		<tertiary>RAM not recognized</tertiary>
-	</indexterm>
-	<para>
-		Sometimes, the kernel does not recognize all of your memory (RAM). You can check this with the <command moreinfo="none">cat /proc/meminfo</command> command.
-	</para>
-	 
-	<para>
-		Verify that the displayed quantity is the same as the known amount of RAM in your system. If they are not equal, add the following line to the <filename moreinfo="none">/boot/grub/grub.conf</filename>:
-	</para>
-<screen>
-<userinput moreinfo="none">mem=<replaceable>xx</replaceable>M</userinput>
-</screen>
-	<para>
-		Replace <replaceable>xx</replaceable> with the amount of RAM you have in megabytes.
-	</para>
-	 
-	<para>
-		In <filename moreinfo="none">/boot/grub/grub.conf</filename>, the above example would look similar to the following:
-	</para>
-<!-- (RHEL) <screen>
-# NOTICE: You have a /boot partition. This means that 
-#  all kernel paths are relative to /boot/ 
-default=0 
-timeout=30 
-splashimage=(hd0,0)/grub/splash.xpm.gz 
-title Red Hat Enterprise Linux (2.6.9-5.EL)         
-root (hd0,0)         
-kernel /vmlinuz-2.6.9-5.EL ro root=/dev/hda3 mem=128M
-</screen> -->
-
-<screen>
-# NOTICE: You have a /boot partition. This means that 
-#  all kernel paths are relative to /boot/ 
-default=0 
-timeout=30 
-splashimage=(hd0,0)/grub/splash.xpm.gz 
- title Fedora (2.6.27.19-170.2.35.fc10.i686)
-root (hd0,1)
-kernel /vmlinuz-2.6.27.19-170.2.35.fc10.i686 ro root=UUID=04a07c13-e6bf-6d5a-b207-002689545705 mem=1024M
-initrd /initrd-2.6.27.19-170.2.35.fc10.i686.img 
-</screen>
-
-	<para>
-		Once you reboot, the changes made to <filename moreinfo="none">grub.conf</filename> are reflected on your system.
-	</para>
-	 
-	<para>
-		Once you have loaded the GRUB boot screen, type <command moreinfo="none">e</command> for edit. You are presented with a list of items in the configuration file for the boot label you have selected.
-	</para>
-	 
-	<para>
-		Choose the line that starts with <computeroutput moreinfo="none">kernel</computeroutput> and type <command moreinfo="none">e</command> to edit this boot entry.
-	</para>
-	 
-	<para>
-		At the end of the <computeroutput moreinfo="none">kernel</computeroutput> line, add
-	</para>
-<screen>
-<userinput moreinfo="none">mem=<replaceable>xx</replaceable>M</userinput>
-</screen>
-	<para>
-		where <replaceable>xx</replaceable> equals the amount of RAM in your system.
-	</para>
-	 
-	<para>
-		Press <keycap moreinfo="none">Enter</keycap> to exit edit mode.
-	</para>
-	 
-	<para>
-		Once the boot loader screen has returned, type <command moreinfo="none">b</command> to boot the system.
-	</para>
-	 
-	<para>
-		Itanium users must enter boot commands with <command moreinfo="none">elilo</command> followed by the boot command.
-	</para>
-	 
-	<para>
-		Remember to replace <replaceable>xx</replaceable> with the amount of RAM in your system. Press <keycap moreinfo="none">Enter</keycap> to boot.
-	</para>
-</section>
diff --git a/en-US/Trouble_After_common-indexterm-1.xml b/en-US/Trouble_After_common-indexterm-1.xml
deleted file mode 100644
index 4be9c63..0000000
--- a/en-US/Trouble_After_common-indexterm-1.xml
+++ /dev/null
@@ -1,11 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE indexterm PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<indexterm significance="normal">
-	<primary>troubleshooting</primary>
-	<secondary>after the installation</secondary>
-</indexterm>
\ No newline at end of file
diff --git a/en-US/Trouble_After_common-title-1.xml b/en-US/Trouble_After_common-title-1.xml
deleted file mode 100644
index 20e6d7a..0000000
--- a/en-US/Trouble_After_common-title-1.xml
+++ /dev/null
@@ -1,8 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE title PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<title>Problems After Installation</title>
\ No newline at end of file
diff --git a/en-US/Trouble_Begin_GUI-indexterm-1.xml b/en-US/Trouble_Begin_GUI-indexterm-1.xml
deleted file mode 100644
index 2db0aa4..0000000
--- a/en-US/Trouble_Begin_GUI-indexterm-1.xml
+++ /dev/null
@@ -1,12 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE indexterm PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<indexterm significance="normal">
-	<primary>troubleshooting</primary>
-	<secondary>beginning the installation</secondary>
-	<tertiary>GUI installation method unavailable</tertiary>
-</indexterm>
\ No newline at end of file
diff --git a/en-US/Trouble_Begin_GUI-indexterm-2.xml b/en-US/Trouble_Begin_GUI-indexterm-2.xml
deleted file mode 100644
index 9212c6e..0000000
--- a/en-US/Trouble_Begin_GUI-indexterm-2.xml
+++ /dev/null
@@ -1,12 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE indexterm PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<indexterm significance="normal">
-	<primary>troubleshooting</primary>
-	<secondary>beginning the installation</secondary>
-	<tertiary>frame buffer, disabling</tertiary>
-</indexterm>
\ No newline at end of file
diff --git a/en-US/Trouble_Begin_GUI-note-1.xml b/en-US/Trouble_Begin_GUI-note-1.xml
deleted file mode 100644
index d1bc320..0000000
--- a/en-US/Trouble_Begin_GUI-note-1.xml
+++ /dev/null
@@ -1,14 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE note PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<note>
-	<title>Note</title>
-	
-	<para>
-		To disable frame buffer support and allow the installation program to run in text mode, try using the <command moreinfo="none">nofb</command> boot option. This command may be necessary for accessibility with some screen reading hardware.
-	</para>
-</note>
\ No newline at end of file
diff --git a/en-US/Trouble_Begin_GUI-para-1.xml b/en-US/Trouble_Begin_GUI-para-1.xml
deleted file mode 100644
index 5823489..0000000
--- a/en-US/Trouble_Begin_GUI-para-1.xml
+++ /dev/null
@@ -1,11 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<para>
-	There are some video cards that have trouble booting into the graphical installation program. If the installation program does not run using its default settings, it tries to run in a lower resolution mode. If that still fails, the installation program
-	attempts to run in text mode.
-</para>
\ No newline at end of file
diff --git a/en-US/Trouble_Begin_GUI-title.xml b/en-US/Trouble_Begin_GUI-title.xml
deleted file mode 100644
index 18ea83e..0000000
--- a/en-US/Trouble_Begin_GUI-title.xml
+++ /dev/null
@@ -1,8 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE title PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<title>Problems with Booting into the Graphical Installation</title>
\ No newline at end of file
diff --git a/en-US/Trouble_Begin_x86_ppc_indexterm-1.xml b/en-US/Trouble_Begin_x86_ppc_indexterm-1.xml
deleted file mode 100644
index b8c0bbe..0000000
--- a/en-US/Trouble_Begin_x86_ppc_indexterm-1.xml
+++ /dev/null
@@ -1,10 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE indexterm PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-	  
-	  
-	  
-	  ]>
-<indexterm significance="normal">
-	<primary>troubleshooting</primary>
-	<secondary>beginning the installation</secondary>
-</indexterm>
\ No newline at end of file
diff --git a/en-US/Trouble_Begin_x86_ppc_title-1.xml b/en-US/Trouble_Begin_x86_ppc_title-1.xml
deleted file mode 100644
index 6857524..0000000
--- a/en-US/Trouble_Begin_x86_ppc_title-1.xml
+++ /dev/null
@@ -1,8 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE title PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-	  
-	  
-	  
-	  ]>
-
-<title>Trouble Beginning the Installation</title>
\ No newline at end of file
diff --git a/en-US/Trouble_During-x86.xml b/en-US/Trouble_During-x86.xml
deleted file mode 100644
index 98a4304..0000000
--- a/en-US/Trouble_During-x86.xml
+++ /dev/null
@@ -1,119 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<section id="s1-trouble-install-x86">
-	<title>Trouble During the Installation</title>
-	<indexterm significance="normal">
-		<primary>troubleshooting</primary>
-		<secondary>during the installation</secondary>
-	</indexterm>
-	<section id="s2-trouble-nodevicefound-x86">
-		
-		<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Trouble_During_common-title-1.xml"/>
-		
-		<indexterm significance="normal">
-			<primary>troubleshooting</primary>
-			<secondary>during the installation</secondary>
-			<tertiary><computeroutput moreinfo="none">No devices found to install Fedora</computeroutput> error message</tertiary>
-		</indexterm>
-		
-		<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Trouble_During_x86_ppc-para-1.xml"/>
-		<!-- FIXME not in F11 
-		<para>
-			Check your hardware vendor's website to determine if a driver diskette image is available that fixes your problem. For more general information on driver diskettes, refer to <xref linkend="ch-driverdisk-x86"/>.
-		</para>
-		 -->
-		<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Trouble_During_x86_ppc-para-3.xml"/>
-		
-		<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Trouble_During_x86_ppc-screen-1.xml"/>
-		
-	</section>
-	 
-	<section id="s2-trouble-tracebacks-x86">
-		
-		<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Trouble_During_x86_ppc-sectiontitle-2.xml"/>
-		<!-- title: Saving Traceback Messages Without removeable media -->
-		
-		<!-- Three index terms -->
-		<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Trouble_During_x86_ppc-section-2-indexterms.xml"/>
-		
-		<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Trouble_During_x86_ppc-section-2-indexterms-2.xml"/>
-		
-		<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Trouble_During_x86_ppc-section-2-indexterms-3.xml"/>
-		
-		<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Trouble_During_x86_ppc-section-2-para-1.xml"/>
-		<!-- If anaconda encounters an error -->
-		
-		<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Trouble_During_x86_ppc-section-2-figure-1.xml"/>
-		<!-- The Crash Reporting Dialog Box -->
-		
-		<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Trouble_During_x86_ppc-section-2-variablelist-1.xml"/>
-		<!-- Details shows you the details of the error -->
-		 
-		<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Trouble_During_x86_ppc-section-2-para-2.xml"/>
-		<!-- If you select Save from the main dialog, -->
-		
-	</section>
-	 
-	<section id="s2-trouble-part-tables-x86">
-		<title>Trouble with Partition Tables</title>
-		
-		<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Trouble_During_common-partitions-indexterm-1.xml"/>
-		
-		<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Trouble_During_common-partitions-indexterm-2.xml"/>
-		
-		<para>
-			If you receive an error at the beginning of the installation process (<xref linkend="sn-initialize-hdd-x86"/>) that says something similar to:
-		</para>
-		
-		<blockquote><xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Trouble_During_common-partitions-para-1.xml"/></blockquote>
-		 
-		<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Trouble_During_common-partitions-para-2.xml"/>
-		 
-		<para>
-			Users who have used programs such as <application moreinfo="none">EZ-BIOS</application> have experienced similar problems, causing data to be lost (assuming the data was not backed up before the installation began) that could not be recovered.
-		</para>
-		 
-		<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Trouble_During_common-partitions-para-3.xml"/>
-	</section>
-	 
-	<section id="s2-trouble-space-x86">
-		<title>Using Remaining Space</title>
-		<indexterm significance="normal">
-			<primary>troubleshooting</primary>
-			<secondary>during the installation</secondary>
-			<tertiary>using remaining hard drive space</tertiary>
-		</indexterm>
-		<para>
-			You have a <filename moreinfo="none">swap</filename> and a <filename moreinfo="none">/</filename> (root) partition created, and you have selected the root partition to use the remaining space, but it does not fill the hard drive.
-		</para>
-		 
-		<para>
-			If your hard drive is more than 1024 cylinders, you must create a <filename moreinfo="none">/boot</filename> partition if you want the <filename moreinfo="none">/</filename> (root) partition to use all of the remaining space on your hard drive.
-		</para>
-	</section>
-	 
-	<section id="s2-trouble-completeparts-x86">
-		
-		<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Trouble_During_common-other-partitioning-title-1.xml"/>
-		
-		<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Trouble_During_common-other-partitioning-indexterm-1.xml"/>
-		
-		<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Trouble_During_common-other-partitioning-para-1.xml"/>
-	
-		<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Trouble_During_common-other-partitioning-para-2.xml"/>
-
-		<itemizedlist>
-			<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Trouble_During_common-other-partitioning-listitem-1.xml"/>
-			
-			<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Trouble_During_common-other-partitioning-listitem-3.xml"/>
-		</itemizedlist>
-		
-		<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Trouble_During_common-other-partitioning-tip-1.xml"/>
-	
-	</section>
-	 
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Trouble_During_common-python-errors.xml"/>
-	
-</section>
diff --git a/en-US/Trouble_During_common-other-partitioning-indexterm-1.xml b/en-US/Trouble_During_common-other-partitioning-indexterm-1.xml
deleted file mode 100644
index 1c83720..0000000
--- a/en-US/Trouble_During_common-other-partitioning-indexterm-1.xml
+++ /dev/null
@@ -1,12 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE indexterm PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-	  
-	  
-	  
-]>
-
-<indexterm significance="normal">
-	<primary>troubleshooting</primary>
-	<secondary>during the installation</secondary>
-	<tertiary>completing partitions</tertiary>
-</indexterm>
\ No newline at end of file
diff --git a/en-US/Trouble_During_common-other-partitioning-listitem-1.xml b/en-US/Trouble_During_common-other-partitioning-listitem-1.xml
deleted file mode 100644
index edff9f2..0000000
--- a/en-US/Trouble_During_common-other-partitioning-listitem-1.xml
+++ /dev/null
@@ -1,12 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE listitem PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-	  
-	  
-	  
-]>
-
-<listitem>
-	<para>
-		A <filename moreinfo="none">/</filename> (root) partition
-	</para>
-</listitem>
\ No newline at end of file
diff --git a/en-US/Trouble_During_common-other-partitioning-listitem-3.xml b/en-US/Trouble_During_common-other-partitioning-listitem-3.xml
deleted file mode 100644
index b23dadb..0000000
--- a/en-US/Trouble_During_common-other-partitioning-listitem-3.xml
+++ /dev/null
@@ -1,12 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE listitem PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-	  
-	  
-	  
-]>
-
-<listitem>
-	<para>
-		A &lt;swap&gt; partition of type swap
-	</para>
-</listitem>
diff --git a/en-US/Trouble_During_common-other-partitioning-para-1.xml b/en-US/Trouble_During_common-other-partitioning-para-1.xml
deleted file mode 100644
index 41102cb..0000000
--- a/en-US/Trouble_During_common-other-partitioning-para-1.xml
+++ /dev/null
@@ -1,7 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<para>
-	If you create partitions manually, but cannot move to the next screen, you probably have not created all the partitions necessary for installation to proceed.
-</para>
\ No newline at end of file
diff --git a/en-US/Trouble_During_common-other-partitioning-para-2.xml b/en-US/Trouble_During_common-other-partitioning-para-2.xml
deleted file mode 100644
index e3bf672..0000000
--- a/en-US/Trouble_During_common-other-partitioning-para-2.xml
+++ /dev/null
@@ -1,10 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-	  
-	  
-	  
-]>
-
-<para>
-	You must have the following partitions as a bare minimum:
-</para>
\ No newline at end of file
diff --git a/en-US/Trouble_During_common-other-partitioning-tip-1.xml b/en-US/Trouble_During_common-other-partitioning-tip-1.xml
deleted file mode 100644
index a9a7c5f..0000000
--- a/en-US/Trouble_During_common-other-partitioning-tip-1.xml
+++ /dev/null
@@ -1,9 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE tip PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<note><title>Note</title>
-	<para>
-		When defining a partition's type as swap, do not assign it a mount point. <application>Anaconda</application> automatically assigns the mount point for you.
-	</para>
-</note>
\ No newline at end of file
diff --git a/en-US/Trouble_During_common-other-partitioning-title-1.xml b/en-US/Trouble_During_common-other-partitioning-title-1.xml
deleted file mode 100644
index af907e1..0000000
--- a/en-US/Trouble_During_common-other-partitioning-title-1.xml
+++ /dev/null
@@ -1,8 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE title PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-	  
-	  
-	  
-]>
-
-<title>Other Partitioning Problems</title>
\ No newline at end of file
diff --git a/en-US/Trouble_During_common-partitions-indexterm-1.xml b/en-US/Trouble_During_common-partitions-indexterm-1.xml
deleted file mode 100644
index accf7ed..0000000
--- a/en-US/Trouble_During_common-partitions-indexterm-1.xml
+++ /dev/null
@@ -1,12 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE indexterm PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-	  
-	  
-	  
-]>
-
-<indexterm significance="normal">
-	<primary>troubleshooting</primary>
-	<secondary>during the installation</secondary>
-	<tertiary>partition tables</tertiary>
-</indexterm>
\ No newline at end of file
diff --git a/en-US/Trouble_During_common-partitions-indexterm-2.xml b/en-US/Trouble_During_common-partitions-indexterm-2.xml
deleted file mode 100644
index d25494e..0000000
--- a/en-US/Trouble_During_common-partitions-indexterm-2.xml
+++ /dev/null
@@ -1,13 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE indexterm PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-	  
-	  
-	  
-]>
-
-<indexterm significance="normal">
-	<primary>troubleshooting</primary>
-	<secondary>during the installation</secondary>
-	<tertiary>partition tables</tertiary>
-</indexterm>
-
diff --git a/en-US/Trouble_During_common-partitions-para-1.xml b/en-US/Trouble_During_common-partitions-para-1.xml
deleted file mode 100644
index 251ead4..0000000
--- a/en-US/Trouble_During_common-partitions-para-1.xml
+++ /dev/null
@@ -1,9 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<blockquote>
-	<para>
-		Error processing drive sda. Maybe it needs to be reinitialized. YOU WILL LOSE ALL DATA ON THIS DRIVE!
-	</para>
-</blockquote>
\ No newline at end of file
diff --git a/en-US/Trouble_During_common-partitions-para-2.xml b/en-US/Trouble_During_common-partitions-para-2.xml
deleted file mode 100644
index a4a624c..0000000
--- a/en-US/Trouble_During_common-partitions-para-2.xml
+++ /dev/null
@@ -1,10 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-	  
-	  
-	  
-]>
-
-<para>
-	you may not have a partition table on that drive or the partition table on the drive may not be recognizable by the partitioning software used in the installation program.
-</para>
\ No newline at end of file
diff --git a/en-US/Trouble_During_common-partitions-para-3.xml b/en-US/Trouble_During_common-partitions-para-3.xml
deleted file mode 100644
index 262015c..0000000
--- a/en-US/Trouble_During_common-partitions-para-3.xml
+++ /dev/null
@@ -1,10 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-	  
-	  
-	  
-]>
-
-<para>
-	No matter what type of installation you are performing, backups of the existing data on your systems should always be made.
-</para>
\ No newline at end of file
diff --git a/en-US/Trouble_During_common-python-errors.xml b/en-US/Trouble_During_common-python-errors.xml
deleted file mode 100644
index 12f3520..0000000
--- a/en-US/Trouble_During_common-python-errors.xml
+++ /dev/null
@@ -1,66 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<section>
-		<title>Are You Seeing Python Errors?</title>
-		<indexterm significance="normal">
-			<primary>troubleshooting</primary>
-			<secondary>during the installation</secondary>
-			<tertiary>Python errors</tertiary>
-		</indexterm>
-		<para>
-			During some upgrades or installations of Fedora, the installation program (also known as <application moreinfo="none">anaconda</application>) may fail with a Python or traceback error. This error may occur after the selection of individual packages or while trying to save the upgrade log in the <filename moreinfo="none">/tmp/</filename>directory. The error may look similar to:
-		</para>
-<screen>
-<!--<computeroutput>-->Traceback (innermost last):
-File "/var/tmp/anaconda-7.1//usr/lib/anaconda/iw/progress_gui.py", line 20, in run
-rc = self.todo.doInstall ()    
-File "/var/tmp/anaconda-7.1//usr/lib/anaconda/todo.py", line 1468, in doInstall 
-self.fstab.savePartitions ()    
-File "fstab.py", line 221, in savePartitions      
-sys.exit(0)  
-SystemExit: 0   
-Local variables in innermost frame:  
-self: &lt;fstab.GuiFstab instance at 8446fe0&gt;  
-sys: &lt;module 'sys' (built-in)&gt;  
-ToDo object:  (itodo  ToDo  p1  (dp2  S'method'  p3  (iimage  CdromInstallMethod  
-p4  (dp5  S'progressWindow'  p6   &lt;failed&gt;<!--</computeroutput>-->
-</screen>
-		<para>
-			This error occurs in some systems where links to <filename>/tmp/</filename> are symbolic to other locations or have been changed since creation. These symbolic or changed links are invalid during the installation process, so the
-			installation program cannot write information and fails.
-		</para>
-		
-		<para>
-			If you experience such an error, first try to download any available updates for <application moreinfo="none">anaconda</application>. Updates for <application>anaconda</application> and instructions for using them can be found at:
-		</para>
-<screen>
-<ulink url="http://fedoraproject.org/wiki/Anaconda/Updates">http://fedoraproject.org/wiki/Anaconda/Updates</ulink>
-</screen>
-		 
-		<!-- (RHEL) <para>
-			If you experience such an error, first try to download any available errata for <application moreinfo="none">anaconda</application>. Errata can be found at:
-		</para>
-<screen>
-<ulink url="http://www.redhat.com/support/errata/">http://www.redhat.com/support/errata/</ulink>
-</screen>-->
-		<para>
-			The <application>anaconda</application> website may also be a useful reference and can be found online at:
-		</para>
-<screen>
-<ulink url="http://fedoraproject.org/wiki/Anaconda">http://fedoraproject.org/wiki/Anaconda</ulink>
-</screen>
-		<para>
-			You can also search for bug reports related to this problem. To search Red Hat's bug tracking system, go to:
-		</para>
-<screen>
-<ulink url="http://bugzilla.redhat.com/bugzilla/">http://bugzilla.redhat.com/bugzilla/</ulink>
-</screen>
-		<!-- (RHEL) <para>
-			Finally, if you are still facing problems related to this error, register your product and contact our support team. To register your product, go to:
-		</para>
-<screen>
-<ulink url="http://www.redhat.com/apps/activate/">http://www.redhat.com/apps/activate/</ulink>
-</screen> -->
-	</section>
\ No newline at end of file
diff --git a/en-US/Trouble_During_common-title-1.xml b/en-US/Trouble_During_common-title-1.xml
deleted file mode 100644
index a749275..0000000
--- a/en-US/Trouble_During_common-title-1.xml
+++ /dev/null
@@ -1,6 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE title PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-
-<title><computeroutput moreinfo="none">No devices found to install Fedora </computeroutput> Error Message</title>
\ No newline at end of file
diff --git a/en-US/Trouble_During_x86_ppc-para-1.xml b/en-US/Trouble_During_x86_ppc-para-1.xml
deleted file mode 100644
index d2af105..0000000
--- a/en-US/Trouble_During_x86_ppc-para-1.xml
+++ /dev/null
@@ -1,8 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-
-<para>
-	If you receive an error message stating <computeroutput moreinfo="none">No devices found to install Fedora</computeroutput>, there is probably a SCSI controller that is not being recognized by the installation program.
-</para>
\ No newline at end of file
diff --git a/en-US/Trouble_During_x86_ppc-para-3.xml b/en-US/Trouble_During_x86_ppc-para-3.xml
deleted file mode 100644
index 3a851de..0000000
--- a/en-US/Trouble_During_x86_ppc-para-3.xml
+++ /dev/null
@@ -1,7 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<para>
-	You can also refer to the LinuxQuestions.org Hardware Compatibility List<!-- (RHEL) <citetitle>Red Hat Hardware Compatibility List</citetitle>-->, available online at:
-</para>
\ No newline at end of file
diff --git a/en-US/Trouble_During_x86_ppc-screen-1.xml b/en-US/Trouble_During_x86_ppc-screen-1.xml
deleted file mode 100644
index 1d2c058..0000000
--- a/en-US/Trouble_During_x86_ppc-screen-1.xml
+++ /dev/null
@@ -1,8 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<para>
-	<ulink url="http://www.linuxquestions.org/hcl/index.php">http://www.linuxquestions.org/hcl/index.php</ulink>
-	<!-- (RHEL) <ulink url="http://hardware.redhat.com/hcl/">http://hardware.redhat.com/hcl/</ulink> -->
-</para> 
diff --git a/en-US/Trouble_During_x86_ppc-section-2-figure-1.xml b/en-US/Trouble_During_x86_ppc-section-2-figure-1.xml
deleted file mode 100644
index ce12f7a..0000000
--- a/en-US/Trouble_During_x86_ppc-section-2-figure-1.xml
+++ /dev/null
@@ -1,13 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<figure float="0"><title>The Crash Reporting Dialog Box</title>
-	<mediaobject>
-		<imageobject><imagedata fileref="images/crashreporting/crashreporting.png" format="PNG"/></imageobject>
-		<textobject><para>
-				An unhandled exception has occurred. This is most likely a bug. Please save a copy of the detailed exception and file a bug report against anaconda at https://bugzilla.redhat.com/bugzilla/
-			</para>
-		</textobject>
-	</mediaobject>
-</figure>
diff --git a/en-US/Trouble_During_x86_ppc-section-2-indexterms-2.xml b/en-US/Trouble_During_x86_ppc-section-2-indexterms-2.xml
deleted file mode 100644
index d06312f..0000000
--- a/en-US/Trouble_During_x86_ppc-section-2-indexterms-2.xml
+++ /dev/null
@@ -1,8 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE indexterm PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<indexterm significance="normal">
-	<primary>traceback messages</primary>
-	<secondary>saving traceback messages without removeable media</secondary>
-</indexterm>
\ No newline at end of file
diff --git a/en-US/Trouble_During_x86_ppc-section-2-indexterms-3.xml b/en-US/Trouble_During_x86_ppc-section-2-indexterms-3.xml
deleted file mode 100644
index d06312f..0000000
--- a/en-US/Trouble_During_x86_ppc-section-2-indexterms-3.xml
+++ /dev/null
@@ -1,8 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE indexterm PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<indexterm significance="normal">
-	<primary>traceback messages</primary>
-	<secondary>saving traceback messages without removeable media</secondary>
-</indexterm>
\ No newline at end of file
diff --git a/en-US/Trouble_During_x86_ppc-section-2-indexterms.xml b/en-US/Trouble_During_x86_ppc-section-2-indexterms.xml
deleted file mode 100644
index f9f540e..0000000
--- a/en-US/Trouble_During_x86_ppc-section-2-indexterms.xml
+++ /dev/null
@@ -1,9 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE indexterm PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<indexterm significance="normal">
-	<primary>troubleshooting</primary>
-	<secondary>during the installation</secondary>
-	<tertiary>saving traceback messages without removeable media</tertiary>
-</indexterm>
\ No newline at end of file
diff --git a/en-US/Trouble_During_x86_ppc-section-2-para-1.xml b/en-US/Trouble_During_x86_ppc-section-2-para-1.xml
deleted file mode 100644
index 561ef48..0000000
--- a/en-US/Trouble_During_x86_ppc-section-2-para-1.xml
+++ /dev/null
@@ -1,8 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-
-<para>
-	If <application>anaconda</application> encounters an error during the graphical installation process, it presents you with a crash reporting dialog box:
-</para>
\ No newline at end of file
diff --git a/en-US/Trouble_During_x86_ppc-section-2-para-2.xml b/en-US/Trouble_During_x86_ppc-section-2-para-2.xml
deleted file mode 100644
index 4f4e04f..0000000
--- a/en-US/Trouble_During_x86_ppc-section-2-para-2.xml
+++ /dev/null
@@ -1,60 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<para>
-	If you select <guimenuitem>Save</guimenuitem> from the main dialog, you can choose from the following options:
-	<variablelist>
-		<varlistentry>
-			<term>Local disk</term>
-			<listitem>
-				<para>
-					saves details of the error to the local hard drive, in a directory that you select with the file browser:
-				</para>
-				<figure float="0"><title>Save Crash Report to a Local disk</title>
-					<mediaobject>
-						<imageobject><imagedata fileref="images/crashreporting/crashreporting_local.png" format="PNG"/></imageobject>
-						<textobject><para>
-								<literal>Local disk</literal> selected, displaying user's home directory
-							</para>
-						</textobject>
-					</mediaobject>
-				</figure>
-			</listitem>
-		</varlistentry>
-		<varlistentry>
-			<term>Bugzilla</term>
-			<listitem>
-				<para>
-					submits details of the error to Red Hat's bug-tracking system, Bugzilla. You must supply an existing Bugzilla username and password, and a description of the bug. 
-				</para>
-				<figure float="0"><title>Save Crash Report to Bugzilla</title>
-					<mediaobject>
-						<imageobject><imagedata fileref="images/crashreporting/crashreporting_bugzilla.png" format="PNG"/></imageobject>
-						<textobject><para>
-								<literal>Bugzilla</literal> selected, displaying fields for username, password, and description
-							</para>
-						</textobject>
-					</mediaobject>
-				</figure>
-			</listitem>
-		</varlistentry>
-		<varlistentry>
-			<term>Remote server</term>
-			<listitem>
-				<para>
-					saves details of the error to a remote location using <application>SCP</application>. You must specify the username, password, host, and destination file. 
-				</para>
-				<figure float="0"><title>Save Crash Report to Remote Server</title>
-					<mediaobject>
-						<imageobject><imagedata fileref="images/crashreporting/crashreporting_scp.png" format="PNG"/></imageobject>
-						<textobject><para>
-								<literal>Remote server</literal> selected, displaying fields for username, password, host, and destination file
-							</para>
-						</textobject>
-					</mediaobject>
-				</figure>
-			</listitem>
-		</varlistentry>
-	</variablelist>
-</para>
diff --git a/en-US/Trouble_During_x86_ppc-section-2-variablelist-1.xml b/en-US/Trouble_During_x86_ppc-section-2-variablelist-1.xml
deleted file mode 100644
index a67e38c..0000000
--- a/en-US/Trouble_During_x86_ppc-section-2-variablelist-1.xml
+++ /dev/null
@@ -1,48 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<variablelist>
-	<varlistentry>
-		<term>Details</term>
-		<listitem>
-			<para>
-				shows you the details of the error:
-			</para>
-			<figure float="0"><title>Details of the Crash</title>
-				<mediaobject>
-					<imageobject><imagedata fileref="images/crashreporting/crashreporting_details.png" format="PNG"/></imageobject>
-					<textobject><para>
-							Details of the crash, showing the python traceback
-						</para>
-					</textobject>
-				</mediaobject>
-			</figure>
-		</listitem>
-	</varlistentry>
-	<varlistentry>
-		<term>Save</term>
-		<listitem>
-			<para>
-				saves details of the error locally or remotely:
-			</para>
-			<figure float="0"><title>Choosing a Destination for Saving the Traceback</title>
-				<mediaobject>
-					<imageobject><imagedata fileref="images/crashreporting/crashreporting.png" format="PNG"/></imageobject>
-					<textobject><para>
-							The three options presented are <literal>Local disk</literal>, <literal>Bugzilla</literal>, or <literal>Remote server</literal>.
-						</para>
-					</textobject>
-				</mediaobject>
-			</figure>
-		</listitem>
-	</varlistentry>
-	<varlistentry>
-		<term>Exit installer</term>
-		<listitem>
-			<para>
-				exits the installation process.
-			</para>
-		</listitem>
-	</varlistentry>
-</variablelist>
diff --git a/en-US/Trouble_During_x86_ppc-sectiontitle-2.xml b/en-US/Trouble_During_x86_ppc-sectiontitle-2.xml
deleted file mode 100644
index 59bb872..0000000
--- a/en-US/Trouble_During_x86_ppc-sectiontitle-2.xml
+++ /dev/null
@@ -1,5 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE title PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<title>Saving traceback messages without removeable media</title>
\ No newline at end of file
diff --git a/en-US/Trouble_No_Boot-Sig11-indexterm-1.xml b/en-US/Trouble_No_Boot-Sig11-indexterm-1.xml
deleted file mode 100644
index 04aad30..0000000
--- a/en-US/Trouble_No_Boot-Sig11-indexterm-1.xml
+++ /dev/null
@@ -1,12 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE indexterm PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<indexterm significance="normal">
-	<primary>troubleshooting</primary>
-	<secondary>booting</secondary>
-	<tertiary>signal 11 error</tertiary>
-</indexterm>
\ No newline at end of file
diff --git a/en-US/Trouble_No_Boot-Sig11-para-1.xml b/en-US/Trouble_No_Boot-Sig11-para-1.xml
deleted file mode 100644
index 1527abe..0000000
--- a/en-US/Trouble_No_Boot-Sig11-para-1.xml
+++ /dev/null
@@ -1,10 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<para>
-	A signal 11 error, commonly know as a <firstterm>segmentation fault</firstterm>, means that the program accessed a memory location that was not assigned to it.  A signal 11 error may be due to a bug in one of the software programs that is installed, or faulty hardware.
-</para>
\ No newline at end of file
diff --git a/en-US/Trouble_No_Boot-Sig11-para-2.xml b/en-US/Trouble_No_Boot-Sig11-para-2.xml
deleted file mode 100644
index 6fb1b11..0000000
--- a/en-US/Trouble_No_Boot-Sig11-para-2.xml
+++ /dev/null
@@ -1,7 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<para>
-	If you receive a fatal signal 11 error during your installation, it is probably due to a hardware error in memory on your system's bus. Like other operating systems, Fedora places its own demands on your system's hardware. Some of this hardware may not be able to meet those demands, even if they work properly under another OS.
-</para>
\ No newline at end of file
diff --git a/en-US/Trouble_No_Boot-Sig11-para-3.xml b/en-US/Trouble_No_Boot-Sig11-para-3.xml
deleted file mode 100644
index daaeff7..0000000
--- a/en-US/Trouble_No_Boot-Sig11-para-3.xml
+++ /dev/null
@@ -1,7 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<para>
-	Ensure that you have the latest installation updates and images. Review the online errata to see if newer versions are available. If the latest images still fail, it may be due to a problem with your hardware. Commonly, these errors are in your memory or CPU-cache. A possible solution for this error is turning off the CPU-cache in the BIOS, if your system supports this. You could also try to swap your memory around in the motherboard slots to check if the problem is either slot or memory related.
-</para>
\ No newline at end of file
diff --git a/en-US/Trouble_No_Boot-Sig11-para-7.xml b/en-US/Trouble_No_Boot-Sig11-para-7.xml
deleted file mode 100644
index 7a3a763..0000000
--- a/en-US/Trouble_No_Boot-Sig11-para-7.xml
+++ /dev/null
@@ -1,7 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<para>
-	Another option is to perform a media check on your installation CD-ROMs. <application>Anaconda</application>, the installation program, has the ability to test the integrity of the installation media. It works with the CD, DVD, hard drive ISO, and NFS ISO installation methods. Red Hat recommends that you test all installation media before starting the installation process, and before reporting any installation-related bugs (many of the bugs reported are actually due to improperly-burned CDs). To use this test, type the following command at the <prompt>boot:</prompt> <!-- (RHEL) or <prompt>yaboot:</prompt> -->prompt<!-- (prepend with <command>elilo</command> for Itanium systems)-->:
-</para>
\ No newline at end of file
diff --git a/en-US/Trouble_No_Boot-Sig11-para-8.xml b/en-US/Trouble_No_Boot-Sig11-para-8.xml
deleted file mode 100644
index e91cb18..0000000
--- a/en-US/Trouble_No_Boot-Sig11-para-8.xml
+++ /dev/null
@@ -1,10 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<para>
-	For more information concerning signal 11 errors, refer to:
-</para>
\ No newline at end of file
diff --git a/en-US/Trouble_No_Boot-Sig11-screen-2.xml b/en-US/Trouble_No_Boot-Sig11-screen-2.xml
deleted file mode 100644
index 472bbe7..0000000
--- a/en-US/Trouble_No_Boot-Sig11-screen-2.xml
+++ /dev/null
@@ -1,10 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE screen PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<screen>
-	<userinput moreinfo="none">linux mediacheck</userinput>
-</screen>
\ No newline at end of file
diff --git a/en-US/Trouble_No_Boot-Sig11-screen-3.xml b/en-US/Trouble_No_Boot-Sig11-screen-3.xml
deleted file mode 100644
index 720fb83..0000000
--- a/en-US/Trouble_No_Boot-Sig11-screen-3.xml
+++ /dev/null
@@ -1,10 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE screen PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<screen>
-	<ulink url="http://www.bitwizard.nl/sig11/">http://www.bitwizard.nl/sig11/</ulink>
-</screen>
\ No newline at end of file
diff --git a/en-US/Trouble_No_Boot-Sig11-title-1.xml b/en-US/Trouble_No_Boot-Sig11-title-1.xml
deleted file mode 100644
index f842d25..0000000
--- a/en-US/Trouble_No_Boot-Sig11-title-1.xml
+++ /dev/null
@@ -1,8 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE title PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<title>Is Your System Displaying Signal 11 Errors?</title>
\ No newline at end of file
diff --git a/en-US/Trouble_No_Boot-indexterm-1.xml b/en-US/Trouble_No_Boot-indexterm-1.xml
deleted file mode 100644
index 263968d..0000000
--- a/en-US/Trouble_No_Boot-indexterm-1.xml
+++ /dev/null
@@ -1,11 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE indexterm PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<indexterm significance="normal">
-	<primary>troubleshooting</primary>
-	<secondary>booting</secondary>
-</indexterm>
\ No newline at end of file
diff --git a/en-US/Trouble_No_Boot-title-1.xml b/en-US/Trouble_No_Boot-title-1.xml
deleted file mode 100644
index 9ae7290..0000000
--- a/en-US/Trouble_No_Boot-title-1.xml
+++ /dev/null
@@ -1,5 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE title PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<title>You are unable to boot Fedora</title>
\ No newline at end of file
diff --git a/en-US/Trouble_common-indexterm-1.xml b/en-US/Trouble_common-indexterm-1.xml
deleted file mode 100644
index 9516ad6..0000000
--- a/en-US/Trouble_common-indexterm-1.xml
+++ /dev/null
@@ -1,7 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE indexterm PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<indexterm significance="normal">
-	<primary>troubleshooting</primary>
-</indexterm>
diff --git a/en-US/Trouble_common-indexterm-2.xml b/en-US/Trouble_common-indexterm-2.xml
deleted file mode 100644
index 5136dec..0000000
--- a/en-US/Trouble_common-indexterm-2.xml
+++ /dev/null
@@ -1,7 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE indexterm PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<indexterm significance="normal">
-	<primary>log files</primary>
-</indexterm>
diff --git a/en-US/Trouble_common-indexterm-3.xml b/en-US/Trouble_common-indexterm-3.xml
deleted file mode 100644
index 456a9fe..0000000
--- a/en-US/Trouble_common-indexterm-3.xml
+++ /dev/null
@@ -1,7 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE indexterm PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<indexterm significance="normal">
-	<primary>anaconda.log</primary>
-</indexterm>
diff --git a/en-US/Trouble_common-indexterm-4.xml b/en-US/Trouble_common-indexterm-4.xml
deleted file mode 100644
index ad4c14b..0000000
--- a/en-US/Trouble_common-indexterm-4.xml
+++ /dev/null
@@ -1,7 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE indexterm PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<indexterm significance="normal">
-	<primary>program.log</primary>
-</indexterm>
diff --git a/en-US/Trouble_common-indexterm-5.xml b/en-US/Trouble_common-indexterm-5.xml
deleted file mode 100644
index fe17b3a..0000000
--- a/en-US/Trouble_common-indexterm-5.xml
+++ /dev/null
@@ -1,7 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE indexterm PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<indexterm significance="normal">
-	<primary>storage.log</primary>
-</indexterm>
diff --git a/en-US/Trouble_common-indexterm-6.xml b/en-US/Trouble_common-indexterm-6.xml
deleted file mode 100644
index 3308023..0000000
--- a/en-US/Trouble_common-indexterm-6.xml
+++ /dev/null
@@ -1,7 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE indexterm PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<indexterm significance="normal">
-	<primary>yum.log</primary>
-</indexterm>
diff --git a/en-US/Trouble_common-indexterm-7.xml b/en-US/Trouble_common-indexterm-7.xml
deleted file mode 100644
index 0deff66..0000000
--- a/en-US/Trouble_common-indexterm-7.xml
+++ /dev/null
@@ -1,7 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE indexterm PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<indexterm significance="normal">
-	<primary>syslog</primary>
-</indexterm>
diff --git a/en-US/Trouble_common-indexterm-8.xml b/en-US/Trouble_common-indexterm-8.xml
deleted file mode 100644
index dd4a3cc..0000000
--- a/en-US/Trouble_common-indexterm-8.xml
+++ /dev/null
@@ -1,7 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE indexterm PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<indexterm significance="normal">
-	<primary>anacdump.txt</primary>
-</indexterm>
diff --git a/en-US/Trouble_common-para-1.xml b/en-US/Trouble_common-para-1.xml
deleted file mode 100644
index 3d954f8..0000000
--- a/en-US/Trouble_common-para-1.xml
+++ /dev/null
@@ -1,8 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<para>
-	This section discusses some common installation problems and their solutions.
-</para>
-
diff --git a/en-US/Trouble_common-para-2.xml b/en-US/Trouble_common-para-2.xml
deleted file mode 100644
index b930092..0000000
--- a/en-US/Trouble_common-para-2.xml
+++ /dev/null
@@ -1,8 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<para>
-	For debugging purposes, <application>anaconda</application> logs installation actions into files in the <filename>/tmp</filename> directory. These files include:
-</para>
-
diff --git a/en-US/Trouble_common-para-3.xml b/en-US/Trouble_common-para-3.xml
deleted file mode 100644
index 9557098..0000000
--- a/en-US/Trouble_common-para-3.xml
+++ /dev/null
@@ -1,7 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<para>
-	If the installation fails, the messages from these files are consolidated into <filename>/tmp/anacdump.txt</filename>.
-</para>
diff --git a/en-US/Trouble_common-variablelist-1.xml b/en-US/Trouble_common-variablelist-1.xml
deleted file mode 100644
index 5e603c7..0000000
--- a/en-US/Trouble_common-variablelist-1.xml
+++ /dev/null
@@ -1,46 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE variablelist PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<variablelist>
-	<varlistentry>
-		<term><filename>/tmp/anaconda.log</filename></term>
-		<listitem>
-			<para>
-				general <application>anaconda</application> messages
-			</para>
-		</listitem>
-	</varlistentry>
-	<varlistentry>
-		<term><filename>/tmp/program.log</filename></term>
-		<listitem>
-			<para>
-				all external programs run by <application>anaconda</application>
-			</para>
-		</listitem>
-	</varlistentry>
-	<varlistentry>
-		<term><filename>/tmp/storage.log</filename></term>
-		<listitem>
-			<para>
-				extensive storage module information
-			</para>
-		</listitem>
-	</varlistentry>
-	<varlistentry>
-		<term><filename>/tmp/yum.log</filename></term>
-		<listitem>
-			<para>
-				<application>yum</application> package installation messages
-			</para>
-		</listitem>
-	</varlistentry>
-	<varlistentry>
-		<term><filename>/tmp/syslog</filename></term>
-		<listitem>
-			<para>
-				hardware-related system messages
-			</para>
-		</listitem>
-	</varlistentry>
-</variablelist>
diff --git a/en-US/Understanding_LVM.xml b/en-US/Understanding_LVM.xml
deleted file mode 100644
index 788aaa8..0000000
--- a/en-US/Understanding_LVM.xml
+++ /dev/null
@@ -1,77 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-
-<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
- "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd">
-
-  <appendix id="sn-partitioning-lvm">
-    <title>Understanding LVM</title>
-    <indexterm>
-      <primary>LVM</primary>
-      <secondary>understanding</secondary>
-    </indexterm>
-    <para>
-        LVM (Logical Volume Management) partitions provide a number of
-      advantages over standard partitions. LVM partitions are formatted
-      as
-        <indexterm>
-	<primary>LVM</primary>
-	<secondary>physical volume</secondary>
-        </indexterm> <firstterm>physical volumes</firstterm>. One or
-      more physical volumes are combined to form a
-        <indexterm>
-	<primary>LVM</primary>
-	<secondary>volume group</secondary>
-        </indexterm> <firstterm>volume group</firstterm>. Each volume
-      group's total storage is then divided into one or more
-        <indexterm>
-	<primary>LVM</primary>
-	<secondary>logical volume</secondary>
-        </indexterm> <firstterm>logical volumes</firstterm>. The logical
-      volumes function much like standard partitions. They have a file
-      system type, such as <systemitem
-	class="filesystem">ext4</systemitem>, and a mount point.
-    </para>
-
-    <note>
-      <title>The <filename>/boot</filename> Partition and LVM</title>
-      <para>
-	The boot loader cannot read LVM volumes.  You must make a
-	standard, non-LVM disk partition for your <filename
-	  class="partition">/boot</filename> partition.
-      </para>
-    </note>
-
-    <para>To understand LVM better, imagine the physical volume as a
-      pile of <firstterm>blocks</firstterm>.  A block is simply a
-      storage unit used to store data. Several piles of blocks can be
-      combined to make a much larger pile, just as physical volumes are
-      combined to make a volume group. The resulting pile can be
-      subdivided into several smaller piles of arbitrary size, just as a
-      volume group is allocated to several logical volumes.</para>
-
-    <para>
-      An administrator may grow or shrink logical volumes without
-      destroying data, unlike standard disk partitions. If the physical
-      volumes in a volume group are on separate drives or RAID arrays
-      then administrators may also spread a logical volume across the
-      storage devices.
-    </para>
-
-    <para>
-      You may lose data if you shrink a logical volume to a smaller
-      capacity than the data on the volume requires. To ensure maximum
-      flexibility, create logical volumes to meet your current needs,
-      and leave excess storage capacity unallocated. You may safely grow
-      logical volumes to use unallocated space, as your needs dictate.
-    </para>
-
-    <note>
-      <title>LVM and the Default Partition Layout</title>
-
-      <para>
-	By default, the installation process creates <filename
-	  class="partition">/</filename> and swap partitions within LVM
-	volumes, with a separate <filename>/boot</filename> partition.
-      </para>
-    </note>
-  </appendix>
diff --git a/en-US/Upgrade-x86.xml b/en-US/Upgrade-x86.xml
deleted file mode 100644
index a7dc2bc..0000000
--- a/en-US/Upgrade-x86.xml
+++ /dev/null
@@ -1,50 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE appendix PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-]>
-
-<chapter id="ch-upgrade-x86">
-
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Upgrade_common-title-1.xml"/>
-	<!-- Upgrading Your Current System -->
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Upgrade_common-para-1.xml"/>
-	<!-- This chapter explains the various methods available -->
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Upgrade_common-section-1.xml"/>
-	<!-- Determining Whether to Upgrade or Re-Install -->
-	
-	<section>
-		<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Upgrade_common-section-2-title.xml"/>
-		<!-- Title: Upgrading Your System -->
-		
-		<para>
-			In most cases, the simplest way to upgrade an existing Fedora installation is with the <application>preupgrade</application> tool. When a new version of Fedora is available, <application>preupgrade</application> downloads the packages necessary to upgrade your installation, and initiates the upgrade process.
-		</para>
-		<para>
-			Install <application>preupgrade</application> with your graphical package manager, or type <command>yum install preupgrade</command> at the command line and press <keycap>Enter</keycap>. 
-		</para>
-		<para>
-			To run <application>preupgrade</application>, type <command>preupgrade</command> at the command line and press <keycap>Enter</keycap>. 
-		</para>
-
-		<para>
-			You can also upgrade a Fedora installation by starting the installation process by any of the methods described in <xref linkend="ch-guimode-x86"/>. If the installer detects a previous Fedora installation on the system, it will ask you whether you want to upgrade that installation &mdash; refer to <xref linkend="sn-upgrade-examine-x86"/>
-		</para>
-		
-		<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Upgrade_common-section-2-para-1.xml"/>
-		<!-- The Upgrade Examine screen appears -->
-		
-		<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Upgrade_common-section-2-note-1.xml"/>
-		<!-- If the contents of your /etc/redhat-release file have been changed from the default, -->
-		
-		<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Upgrade_common-section-2-para-2.xml"/>
-		<!-- To perform an upgrade, select Perform an upgrade of an existing installation -->
-		
-		<para>
-			To re-install your system, select <guilabel>Perform a new Fedora installation</guilabel> and refer to <!-- (RHEL) <ulink url="http://www.redhat.com/docs/wp/">http://www.redhat.com/docs/wp/</ulink> as well as
-			--><xref linkend="ch-guimode-x86"/><!--, <xref linkend="ch-guimode-ppc"/>, or <xref linkend="ch-guimode-s390"/>--> for further instructions.
-		</para>
-		
-	</section>
-</chapter> 
\ No newline at end of file
diff --git a/en-US/Upgrade_common-para-1.xml b/en-US/Upgrade_common-para-1.xml
deleted file mode 100644
index 6222078..0000000
--- a/en-US/Upgrade_common-para-1.xml
+++ /dev/null
@@ -1,7 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<para>
-	This chapter explains the various methods available for upgrading your Fedora system.
-</para>
\ No newline at end of file
diff --git a/en-US/Upgrade_common-section-1.xml b/en-US/Upgrade_common-section-1.xml
deleted file mode 100644
index 5e91e74..0000000
--- a/en-US/Upgrade_common-section-1.xml
+++ /dev/null
@@ -1,100 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<section>
-	<title>Determining Whether to Upgrade or Re-Install</title>
-	<indexterm significance="normal">
-		<primary>upgrade</primary>
-	</indexterm>
-	<indexterm significance="normal">
-		<primary>re-installation</primary>
-	</indexterm>
-	<para>
-		While upgrading from Fedora&nbsp;&PREVVER; is supported, you are more likely to have a consistent experience by backing up your data and then installing this release of Fedora&nbsp;&PRODVER; over your previous Fedora installation.
-	</para>
-	
-	<para>
-		To upgrade from Fedora&nbsp;&PREVVER; you should bring your system up to date before performing the upgrade.
-	</para>
-	
-	<para>
-		<emphasis>This recommended reinstallation method helps to ensure the best system stability possible.</emphasis>
-	</para>
-	
-	<!-- (RHEL) <para>
-		For more information about re-installing your Fedora system, refer to the Whitepapers available online at <ulink url="http://www.redhat.com/rhel/resource_center/" />.
-	</para> -->
-	
-	<para>
-		If you currently use Fedora&nbsp;&PREVVER;, you can perform a traditional, installation program-based upgrade.
-	</para>
-	
-	<para>
-		However, before you chose to upgrade your system, there are a few things you should keep in mind:
-	</para>
-	
-	<itemizedlist>
-		<listitem>
-			<para>
-				Individual package configuration files may or may not work after performing an upgrade due to changes in various configuration file formats or layouts.
-			</para>
-		</listitem>
-		
-		<listitem>
-			<para>
-				If you have one of Red Hat's layered products (such as the Cluster Suite) installed, it may need to be manually upgraded after the upgrade has been completed.
-			</para>
-		</listitem>
-		
-		<listitem>
-			<para>
-				Third party or ISV applications may not work correctly following the upgrade.
-			</para>
-		</listitem>
-	</itemizedlist>
-	
-	<para>
-		Upgrading your system installs updated versions of the packages which are currently installed on your system.
-	</para>
-	
-	<para>
-		The upgrade process preserves existing configuration files by renaming them with an <filename>.rpmsave</filename> extension (for example, <filename>sendmail.cf.rpmsave</filename>). The upgrade process also creates a log
-		of its actions in <filename>/root/upgrade.log</filename>.
-	</para>
-	
-	<warning>
-		<title>Warning</title>
-		
-		<para>
-			As software evolves, configuration file formats can change. It is very important to carefully compare your original configuration files to the new files before integrating your changes.
-		</para>
-	</warning>
-	
-	<note>
-		<title>Note</title>
-		
-		<para>
-			It is always a good idea to back up any data that you have on your systems. For example, if you are upgrading or creating a dual-boot system, you should back up any data you wish to keep on your hard drive(s). Mistakes do happen and can result in the
-			loss of all of your data.
-		</para>
-	</note>
-	
-	<para>
-		Some upgraded packages may require the installation of other packages for proper operation. If you choose to customize your packages to upgrade, you may be required to resolve dependency problems. Otherwise, the upgrade procedure takes care of these
-		dependencies, but it may need to install additional packages which are not on your system.
-	</para>
-	
-	<para>
-		Depending on how you have partitioned your system, the upgrade program may prompt you to add an additional swap file. If the upgrade program does not detect a swap file that equals twice your RAM, it asks you if you would like to add a new swap file. If
-		your system does not have a lot of RAM (less than 256 MB), it is recommended that you add this swap file.
-	</para>
-	<indexterm significance="normal">
-		<primary>swap file</primary>
-		<secondary>upgrade</secondary>
-	</indexterm>
-	<indexterm significance="normal">
-		<primary>upgrade</primary>
-		<secondary>adding a swap file</secondary>
-	</indexterm>
-</section>
\ No newline at end of file
diff --git a/en-US/Upgrade_common-section-2-note-1.xml b/en-US/Upgrade_common-section-2-note-1.xml
deleted file mode 100644
index 795f0ae..0000000
--- a/en-US/Upgrade_common-section-2-note-1.xml
+++ /dev/null
@@ -1,20 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE note PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-]>
-
-<note>
-	<title>Note</title>
-	
-	<para>
-		If the contents of your <filename>/etc/<!-- (RHEL) redhat-->fedora-release</filename> file have been changed from the default, your Fedora installation may not be found when attempting an upgrade to Fedora &PRODVER;.
-	</para>
-	
-	<para>
-		You can relax some of the checks against this file by booting with the following boot command:
-	</para>
-	<screen>linux upgradeany</screen>
-	<para>
-		Use the <command>linux upgradeany</command> command if your Fedora installation was not given as an option to upgrade.
-	</para>
-</note>
\ No newline at end of file
diff --git a/en-US/Upgrade_common-section-2-para-1.xml b/en-US/Upgrade_common-section-2-para-1.xml
deleted file mode 100644
index eeb40af..0000000
--- a/en-US/Upgrade_common-section-2-para-1.xml
+++ /dev/null
@@ -1,10 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<para>
-	The <guilabel>Upgrade Examine</guilabel> screen appears if you have instructed the installation program to perform an upgrade.
-</para>
\ No newline at end of file
diff --git a/en-US/Upgrade_common-section-2-para-2.xml b/en-US/Upgrade_common-section-2-para-2.xml
deleted file mode 100644
index 0dffe01..0000000
--- a/en-US/Upgrade_common-section-2-para-2.xml
+++ /dev/null
@@ -1,8 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-]>
-
-<para>
-	To perform an upgrade, select <guilabel>Perform an upgrade of an existing installation</guilabel>. Click <guibutton>Next</guibutton> when you are ready to begin your upgrade.
-</para>
\ No newline at end of file
diff --git a/en-US/Upgrade_common-section-2-title.xml b/en-US/Upgrade_common-section-2-title.xml
deleted file mode 100644
index a2f6c48..0000000
--- a/en-US/Upgrade_common-section-2-title.xml
+++ /dev/null
@@ -1,8 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE title PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<title>Upgrading Your System</title>
\ No newline at end of file
diff --git a/en-US/Upgrade_common-title-1.xml b/en-US/Upgrade_common-title-1.xml
deleted file mode 100644
index dfd813e..0000000
--- a/en-US/Upgrade_common-title-1.xml
+++ /dev/null
@@ -1,8 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE title PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<title>Upgrading Your Current System</title>
\ No newline at end of file
diff --git a/en-US/Upgrading-common-figure-1.xml b/en-US/Upgrading-common-figure-1.xml
deleted file mode 100644
index 0a6ec47..0000000
--- a/en-US/Upgrading-common-figure-1.xml
+++ /dev/null
@@ -1,14 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-<!DOCTYPE figure PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
- "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
-]>
-
-<figure float="0"><title>The Upgrade Dialog</title>
-	<mediaobject>
-		<imageobject><imagedata fileref="images/upgrading/upgrading.png" format="PNG"/></imageobject>
-		<textobject><para>
-				The Upgrade Dialog
-			</para>
-		</textobject>
-	</mediaobject>
-</figure>
diff --git a/en-US/Upgrading-common-figure-2.xml b/en-US/Upgrading-common-figure-2.xml
deleted file mode 100644
index cd3356e..0000000
--- a/en-US/Upgrading-common-figure-2.xml
+++ /dev/null
@@ -1,14 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-<!DOCTYPE figure PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
- "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
-]>
-
-<figure float="0"><title>The Upgrade Boot Loader Dialog</title>
-	<mediaobject>
-		<imageobject><imagedata fileref="images/upgrading/upgradebootloader.png" format="PNG"/></imageobject>
-		<textobject><para>
-				The dialog includes three radio buttons, labeled <guilabel>Update boot loader configuration</guilabel>, <guilabel>Skip boot loader updating</guilabel>, and <guilabel>Create new boot loader configuration</guilabel>
-			</para>
-		</textobject>
-	</mediaobject>
-</figure>
diff --git a/en-US/Upgrading-common-indexterm-1.xml b/en-US/Upgrading-common-indexterm-1.xml
deleted file mode 100644
index 2c73900..0000000
--- a/en-US/Upgrading-common-indexterm-1.xml
+++ /dev/null
@@ -1,11 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-<!DOCTYPE title PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
- "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
-]>
-
-<indexterm>
-	<primary>boot loader</primary>
-	<secondary>upgrading</secondary>
-</indexterm>
-      
-      
diff --git a/en-US/Upgrading-common-note-1.xml b/en-US/Upgrading-common-note-1.xml
deleted file mode 100644
index 1e03a5e..0000000
--- a/en-US/Upgrading-common-note-1.xml
+++ /dev/null
@@ -1,11 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-<!DOCTYPE note PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
- "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
-]>
-
-<note>
-	<title>Manually Installed Software</title>
-	<para>
-		Software you have installed manually on your existing Fedora or Red Hat Linux system may behave differently after an upgrade.  You may need to manually reinstall or recompile this software after an upgrade to ensure it performs correctly on the updated system.
-	</para>
-</note>
diff --git a/en-US/Upgrading-common-note-2.xml b/en-US/Upgrading-common-note-2.xml
deleted file mode 100644
index ad90b5e..0000000
--- a/en-US/Upgrading-common-note-2.xml
+++ /dev/null
@@ -1,12 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-<!DOCTYPE note PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
- "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
-]>
-
-<note>
-	<title>Installations are Recommended</title>
-	<para>
-		In general, the Fedora Project recommends that you keep user data on a separate <filename class="partition">/home</filename> partition and perform a fresh installation.  For more information on partitions and how to set them up, refer to <xref linkend="s1-diskpartsetup-x86"/>.
-	</para>
-</note>
-
diff --git a/en-US/Upgrading-common-para-1.xml b/en-US/Upgrading-common-para-1.xml
deleted file mode 100644
index 6ae74c3..0000000
--- a/en-US/Upgrading-common-para-1.xml
+++ /dev/null
@@ -1,9 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
- "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
-]>
-
-<para>
-	The installation system automatically detects any existing installation of Red Hat Enterprise Linux.  The upgrade process updates the existing system software with new versions, but does not remove any data from users' home directories.  The existing partition structure on your hard drives does not change.  Your system configuration changes only if a package upgrade demands it.  Most package upgrades do not change system configuration, but rather install an additional configuration file for you to examine later.
-</para>
-
diff --git a/en-US/Upgrading-common-para-2.xml b/en-US/Upgrading-common-para-2.xml
deleted file mode 100644
index 1987193..0000000
--- a/en-US/Upgrading-common-para-2.xml
+++ /dev/null
@@ -1,8 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
- "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
-]>
-
-<para>
-	Note that the installation medium that you are using might not contain all the software packages that you need to upgrade your computer. In particular, the Fedora live CD contains a relatively small subset of the packages available in Fedora. To update packages that are not included on the installation medium, make sure that you select the <literal>Fedora &PRODVER; - <replaceable>architecture</replaceable></literal> or the <literal>Fedora &PRODVER; - <replaceable>architecture</replaceable> - Updates</literal> repository the during package group selection &mdash; refer to <xref linkend="sn-additional-repos"/>.
-</para>
diff --git a/en-US/Upgrading-common-para-3.xml b/en-US/Upgrading-common-para-3.xml
deleted file mode 100644
index 650487d..0000000
--- a/en-US/Upgrading-common-para-3.xml
+++ /dev/null
@@ -1,9 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
- "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
-]>
-
-<para>
-      If your system contains a Fedora or Red Hat Linux installation, a dialog appears asking whether you want to upgrade that installation. To perform an upgrade of an existing system, choose the appropriate installation from the drop-down list and select <guibutton>Next</guibutton>.  
-</para>
-
diff --git a/en-US/Upgrading-common-para-4.xml b/en-US/Upgrading-common-para-4.xml
deleted file mode 100644
index bd350bb..0000000
--- a/en-US/Upgrading-common-para-4.xml
+++ /dev/null
@@ -1,9 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
- "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
-]>
-
-<para>
-	If you choose to upgrade your system using the installation program, any software that is not part of the Fedora distribution that conflicts with software that is part of the distribution is overwritten.  Before you begin an upgrade this way, make a list of your system's current packages for later reference:
-</para>
-
diff --git a/en-US/Upgrading-common-para-5.xml b/en-US/Upgrading-common-para-5.xml
deleted file mode 100644
index 9fec8a5..0000000
--- a/en-US/Upgrading-common-para-5.xml
+++ /dev/null
@@ -1,9 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
- "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
-]>
-
-<para>
-	After installation, consult this list to discover which packages you may need to rebuild or retrieve from sources other than the Fedora repositories.
-</para>
-
diff --git a/en-US/Upgrading-common-para-6.xml b/en-US/Upgrading-common-para-6.xml
deleted file mode 100644
index 4f725df..0000000
--- a/en-US/Upgrading-common-para-6.xml
+++ /dev/null
@@ -1,9 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
- "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
-]>
-
-<para>
-	Next, make a backup of any system configuration data:
-</para>
-
diff --git a/en-US/Upgrading-common-para-7.xml b/en-US/Upgrading-common-para-7.xml
deleted file mode 100644
index 546a4ca..0000000
--- a/en-US/Upgrading-common-para-7.xml
+++ /dev/null
@@ -1,9 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
- "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
-]>
-
-<para>
-	Make a complete backup of any important data before performing an upgrade.  Important data may include the contents of your entire <filename class="directory">/home</filename> directory as well as content from services such as an Apache, FTP, or SQL server, or a source code management system. Although upgrades are not destructive, if you perform one improperly there is a small possibility of data loss.
-</para>
-
diff --git a/en-US/Upgrading-common-para-8.xml b/en-US/Upgrading-common-para-8.xml
deleted file mode 100644
index 4c6f153..0000000
--- a/en-US/Upgrading-common-para-8.xml
+++ /dev/null
@@ -1,10 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
- "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
-]>
-
-<para>
-	For more information on completing the upgrade process later, refer to <xref linkend="sn-finishing-upgrade"/>.
-</para>
-
-
diff --git a/en-US/Upgrading-common-para-9.xml b/en-US/Upgrading-common-para-9.xml
deleted file mode 100644
index ccdf7a9..0000000
--- a/en-US/Upgrading-common-para-9.xml
+++ /dev/null
@@ -1,11 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
- "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
-]>
-
-<para>
-	If the existing boot loader was installed by a Linux distribution, the installation system can modify it to load the new Fedora system. To update the existing Linux boot loader, select <guilabel>Update boot loader configuration</guilabel>.  This is the default behavior when you upgrade an existing Red Hat Linux or Fedora installation.
-</para>
-    
-    
-      
diff --git a/en-US/Upgrading-common-screen-1.xml b/en-US/Upgrading-common-screen-1.xml
deleted file mode 100644
index 018eb07..0000000
--- a/en-US/Upgrading-common-screen-1.xml
+++ /dev/null
@@ -1,8 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-<!DOCTYPE screen PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
- "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
-]>
-
-<screen><command>rpm -qa --qf '%{NAME} %{VERSION}-%{RELEASE} %{ARCH}\n' > ~/old-pkglist.txt</command></screen>
-
-
diff --git a/en-US/Upgrading-common-screen-2.xml b/en-US/Upgrading-common-screen-2.xml
deleted file mode 100644
index 82ffb50..0000000
--- a/en-US/Upgrading-common-screen-2.xml
+++ /dev/null
@@ -1,8 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-<!DOCTYPE screen PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
- "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
-]>
-
-<screen><command>su -c 'tar czf /tmp/etc-`date +%F`.tar.gz /etc' </command>
-<command>su -c 'mv /tmp/etc-*.tar.gz /home'</command></screen>
-
diff --git a/en-US/Upgrading-common-title-1.xml b/en-US/Upgrading-common-title-1.xml
deleted file mode 100644
index ee9978a..0000000
--- a/en-US/Upgrading-common-title-1.xml
+++ /dev/null
@@ -1,8 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
- "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
-]>
-
-<title>
-	Upgrading an Existing System
-</title>
diff --git a/en-US/Upgrading-common-title-2.xml b/en-US/Upgrading-common-title-2.xml
deleted file mode 100644
index 75b1ba5..0000000
--- a/en-US/Upgrading-common-title-2.xml
+++ /dev/null
@@ -1,8 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-<!DOCTYPE title PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
- "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
-]>
-
-<title>
-	The Upgrade Dialog
-</title>
diff --git a/en-US/Upgrading-common-title-3.xml b/en-US/Upgrading-common-title-3.xml
deleted file mode 100644
index 121acd3..0000000
--- a/en-US/Upgrading-common-title-3.xml
+++ /dev/null
@@ -1,8 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-<!DOCTYPE title PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
- "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
-]>
-
-<title>
-	Upgrading Using the Installer
-</title>
diff --git a/en-US/Upgrading-common-title-4.xml b/en-US/Upgrading-common-title-4.xml
deleted file mode 100644
index 873eee4..0000000
--- a/en-US/Upgrading-common-title-4.xml
+++ /dev/null
@@ -1,8 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-<!DOCTYPE title PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
- "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
-]>
-
-<title>
-	Upgrading Boot Loader Configuration
-</title>
diff --git a/en-US/Upgrading-common-warning-1.xml b/en-US/Upgrading-common-warning-1.xml
deleted file mode 100644
index 43881fd..0000000
--- a/en-US/Upgrading-common-warning-1.xml
+++ /dev/null
@@ -1,13 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-<!DOCTYPE warning PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
- "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
-]>
-
-<warning>
-	<title>Storing Backups</title>
-	<para>
-		Note that the above examples store backup materials in a <filename class="directory">/home</filename> directory.  If your <filename class="directory">/home</filename> directory is not a separate partition, <emphasis>you should not follow these examples verbatim!</emphasis>  Store your backups on another device such as CD or DVD discs or an external hard disk.
-	</para>
-</warning>
-
-
diff --git a/en-US/Verifying_Media.xml b/en-US/Verifying_Media.xml
deleted file mode 100644
index c388669..0000000
--- a/en-US/Verifying_Media.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
- "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd">
-
-<section>
-	<title>Verifying Media</title>
-	<para>
-		The DVD offers an option to verify the integrity of the media.  Recording errors sometimes occur while producing CD or DVD media.  An error in the data for package chosen in the installation program can cause the installation to abort.  To minimize the chances of data errors affecting the installation, verify the media before installing.
-	</para>
-	<para>
-		If the verification succeeds, the installation process proceeds normally.  If the process fails, create a new DVD using the ISO image you downloaded earlier.
-	</para>
-</section>
-
-
diff --git a/en-US/Welcome-x86.xml b/en-US/Welcome-x86.xml
deleted file mode 100644
index b476b14..0000000
--- a/en-US/Welcome-x86.xml
+++ /dev/null
@@ -1,22 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<section id="sn-welcome-x86">
-	<title>Welcome to Fedora</title>
-	 
-	<para>
-		The <guilabel>Welcome</guilabel> screen does not prompt you for any input.
-	</para>
-	
-	<mediaobject>
-		<imageobject><imagedata fileref="images/welcome/welcome.png" format="PNG"/></imageobject>
-		<textobject><para>
-				Welcome to Fedora &PRODVER;
-			</para>
-		</textobject>
-	</mediaobject>
-	<para>
-		Click on the <guibutton>Next</guibutton> button to continue.
-	</para>
-</section>
diff --git a/en-US/Write_changes_to_disk.xml b/en-US/Write_changes_to_disk.xml
deleted file mode 100644
index 2a6a071..0000000
--- a/en-US/Write_changes_to_disk.xml
+++ /dev/null
@@ -1,34 +0,0 @@
-<?xml version='1.0'?>
-<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docarticle/xml/4.5/docarticlex.dtd" [
-]>
-
-<section id="Write_changes_to_disk">
-	<title>Write changes to disk</title>
-	<para>
-		The installer prompts you to confirm the partitioning options that you selected. Click <guibutton>Write changes to disk</guibutton> to allow the installer to partition your hard drive and install Fedora.
-	</para>
-	<figure float="0" id="fig-Writing_storage_configuration_to_disk"><title>Writing storage configuration to disk</title>
-		<mediaobject>
-			<imageobject><imagedata fileref="images/diskpartitioning/write_changes.png" format="PNG"/></imageobject>
-			<textobject><para>
-					The <guilabel>Writing storage configuration to disk</guilabel> dialog box lets you choose to <guibutton>Write changes to disk</guibutton> or to <guibutton>Go back</guibutton>.
-				</para>
-			</textobject>
-		</mediaobject>
-	</figure>
-	<para>
-		If you are certain that you want to proceed, click <guibutton>Write changes to disk</guibutton>.
-	</para>
-	<warning>
-		<title>Last chance to cancel safely</title>
-		<para>
-			Up to this point in the installation process, the installer has made no lasting changes to your computer. When you click <guibutton>Write changes to disk</guibutton>, the installer will allocate space on your hard drive and start to transfer Fedora into this space. Depending on the partitioning option that you chose, this process might include erasing data that already exists on your computer. 
-		</para>
-		<para>
-			To revise any of the choices that you made up to this point, click <guibutton>Go back</guibutton>. To cancel installation completely, switch off your computer. To switch off most computers at this stage, press the power button and hold it down for a few seconds.
-		</para>
-		<para>
-			After you click <guibutton>Write changes to disk</guibutton>, allow the installation process to complete. If the process is interrupted (for example, by you switching off or resetting the computer, or by a power outage) you will probably not be able to use your computer until you restart and complete the Fedora installation process, or install a different operating system.
-		</para>
-	</warning>
-</section>
\ No newline at end of file
diff --git a/en-US/X86_Bios_Tip.xml b/en-US/X86_Bios_Tip.xml
deleted file mode 100644
index 6b61b19..0000000
--- a/en-US/X86_Bios_Tip.xml
+++ /dev/null
@@ -1,19 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE tip PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<note><title>Note</title>
-	<para>
-		While partitioning your hard drive, keep in mind that the BIOS in some older systems cannot access more than the first 1024 cylinders on a hard drive. If this is the case, leave enough room for the <filename>/boot</filename> Linux
-		partition on the first 1024 cylinders of your hard drive to boot Linux. The other Linux partitions can be after cylinder 1024.
-	</para>
-	<para>
-		In <command>parted</command>, 1024 cylinders equals 528MB. For more information, refer to:
-	</para>
-<screen>
-<ulink url="http://www.pcguide.com/ref/hdd/bios/sizeMB504-c.html">http://www.pcguide.com/ref/hdd/bios/sizeMB504-c.html</ulink>
-</screen>
-</note>
diff --git a/en-US/X86_Bootloader.xml b/en-US/X86_Bootloader.xml
deleted file mode 100644
index c10dd52..0000000
--- a/en-US/X86_Bootloader.xml
+++ /dev/null
@@ -1,510 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<section id="s1-x86-bootloader">
-	<title>x86, AMD64, and <trademark class="registered">Intel</trademark> 64 Boot Loader Configuration</title>
-	<indexterm significance="normal">
-		<primary>boot loader</primary>
-	</indexterm>
-	<indexterm significance="normal">
-		<primary>boot loader</primary>
-		<secondary>GRUB</secondary>
-	</indexterm>
-	<indexterm significance="normal">
-		<primary>GRUB</primary>
-	</indexterm>
-	<indexterm significance="normal">
-		<primary>configuration</primary>
-		<secondary>GRUB</secondary>
-	</indexterm>
-	<indexterm significance="normal">
-		<primary>GRUB</primary>
-		<secondary>configuration</secondary>
-	</indexterm>
-	<indexterm significance="normal">
-		<primary>boot loader</primary>
-		<secondary>configuration</secondary>
-	</indexterm>
-	<indexterm significance="normal">
-		<primary>master boot record</primary>
-	</indexterm>
-	<para>
-		To boot the system without boot media, you usually need to install a boot loader. A boot loader is the first software program that runs when a computer starts. It is responsible for loading and transferring control to the operating system kernel
-		software. The kernel, in turn, initializes the rest of the operating system.
-	</para>
-
-  <important>
-    <title>Installing in text mode</title>
-    <para>If you install Fedora in text mode, the installer configures the bootloader automatically and you cannot customize bootloader settings during the installation process.</para>
-  </important>
-
-	<para>
-		GRUB (GRand Unified Bootloader), which is installed by default, is a very powerful boot loader. GRUB can load a variety of free operating systems, as well as proprietary operating systems with chain-loading (the mechanism for loading unsupported
-		operating systems, such as DOS or Windows, by loading another boot loader).
-	</para>
-	
-	  <note>
-	    <title>The GRUB boot menu</title>
-	    <para>The GRUB menu
-	    defaults to being hidden, except on dual-boot systems.
-	    To show the GRUB menu during system boot, press and hold the
-	    <keycap>Shift</keycap> key before the kernel is loaded.  (Any other
-	    key works as well but the <keycap>Shift</keycap> key is the safest to use.)
-	    </para>
-	  </note>
-	
-	<figure float="0" id="fig-x86-bootloader"><title>Boot Loader Configuration</title>
-		<mediaobject>
-			<imageobject><imagedata fileref="images/x86-bootloader/x86-bootloader.png" format="PNG"/></imageobject>
-			<textobject><para>
-					Configure how you would like to boot the system.
-				</para>
-			</textobject>
-		</mediaobject>
-	</figure>
-	<!-- <para>
-		If you do not want to install GRUB as your boot loader, click <guibutton>Change boot loader</guibutton>, where you can choose not to install a boot loader at all.
-	</para>
-	 
-	<para>
-		If you already have a boot loader that can boot Fedora and do not want to overwrite your current boot loader, choose <guilabel>Do not install a boot loader</guilabel> by clicking on the <guibutton>Change
-		boot loader</guibutton> button.
-	</para> -->
-	  <para>
-	    If there are no other operating systems on your computer, or you are
-	    completely removing any other operating systems the installation 
-	    program will install <application>GRUB</application> as your boot 
-	    loader without any intervention. In that case you may continue on to
-	    <xref linkend="s1-pkgselection-x86"/>.
-	  </para>
-	  	  
-	  <para>
-	    You may have a boot loader installed on your system already. An
-	    operating system may install its own preferred boot loader, or you
-	    may have installed a third-party boot loader.If your boot loader
-	    does not recognize Linux partitions, you may not be able to boot
-	    Fedora. Use <application>GRUB</application> as your boot loader to
-	    boot Linux and most other operating systems. Follow the directions
-	    in this chapter to install <application>GRUB</application>.
-	  </para>
-
-
-	  <warning>
-	    <title>Installing GRUB</title>
-
-	    <para>
-	      If you install GRUB, it may overwrite your existing boot loader.
-	    </para>
-	  </warning>
-	  
-    <para>
-      By default, the installation program installs GRUB in the
-      master boot record or <abbrev>MBR</abbrev>, of the device for the root
-      file system. To decline installation of a new boot loader, unselect
-      <guilabel>Install boot loader on /dev/sda</guilabel>.
-    </para>
-	 
-	<warning>
-		<title>Warning</title>
-
-		<para>
-			If you choose not to install GRUB for any reason, you will not be able to boot the system directly, and you must use another boot method (such as a commercial boot loader application). Use this option only if you are sure you have another way of booting the system!
-		</para>
-	</warning>
-	 
-	<!-- <para>
-		Every bootable partition is listed, including partitions used by other operating systems. The partition holding the system's root file system has a <guilabel>Label</guilabel> of <filename>Fedora</filename> (for GRUB). Other partitions may also have boot labels. To add or change the boot label for other partitions that have been detected by the installation program, click once on the partition to select it. Once selected, you can change the boot label by clicking the <guibutton>Edit</guibutton> button.
-	</para> -->
-	
-	    <para>
-		If you have other operating systems already installed, Fedora
-		attempts to automatically detect and configure
-		<application>GRUB</application> to boot them. You may manually
-		configure any additional operating systems if
-		<application>GRUB</application> does not detect them.
-	    </para>
-	    
-	        <para>To add, remove, or change the detected operating system
-      settings, use the options provided.</para>
-
-    <variablelist>
-      <varlistentry>
-        <term><guibutton>Add</guibutton></term>
-        <listitem>
-          <para>
-            Select <guibutton>Add</guibutton> to include an additional
-	    operating system in GRUB.
-          </para>
-          <para>
-            Select the disk partition which contains the bootable
-            operating system from the drop-down list and give the entry
-            a label. <application>GRUB</application> displays this label
-            in its boot menu.
-          </para>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry>
-        <term><guibutton>Edit</guibutton></term>
-        <listitem>
-          <para>
-            To change an entry in the GRUB boot menu, select the entry
-            and then select <guibutton>Edit</guibutton>.
-          </para>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry>
-        <term><guibutton>Delete</guibutton></term>
-        <listitem>
-          <para>
-            To remove an entry from the GRUB boot menu, select the entry
-            and then select <guibutton>Delete</guibutton>.
-          </para>
-        </listitem>
-      </varlistentry>
-    </variablelist>
-	 
-	<para>
-		Select <guilabel>Default</guilabel> beside the preferred boot partition to choose your default bootable OS. You cannot move forward in the installation unless you choose a default boot image.
-	</para>
-	 
-	<note>
-		<title>Note</title>
-
-		<para>
-			The <guilabel>Label</guilabel> column lists what you must enter at the boot prompt, in non-graphical boot loaders, in order to boot the desired operating system.
-		</para>
-
-		<para>
-			Once you have loaded the GRUB boot screen, use the arrow keys to choose a boot label or type <keycap>e</keycap> for edit. You are presented with a list of items in the configuration file for the boot label you have selected.
-		</para>
-	</note>
-	 
-	<para>
-		Boot loader passwords provide a security mechanism in an environment where physical access to your server is available.
-	</para>
-	 
-	<para>
-		If you are installing a boot loader, you should create a password to protect your system. Without a boot loader password, users with access to your system can pass options to the kernel which can compromise your system security. With a boot loader password in place, the password must first be entered before selecting any non-standard boot options. However, it is still possible for someone with physical access to the machine to boot from a diskette, CD-ROM, or USB media if the BIOS supports it. Security plans which include boot loader passwords should also address alternate boot methods.
-	</para>
-	<indexterm significance="normal">
-		<primary>boot loader password</primary>
-	</indexterm>
-	<indexterm significance="normal">
-		<primary>password</primary>
-		<secondary>boot loader</secondary>
-	</indexterm>
-	<indexterm significance="normal">
-		<primary>boot loader</primary>
-		<secondary>password</secondary>
-	</indexterm>
-
-    <note>
-      <title>GRUB Passwords Not Required</title>
-      <para>
-        You may not require a <application>GRUB</application> password
-	if your system only has trusted operators, or is physically
-	secured with controlled console access. However, if an untrusted
-	person can get physical access to your computer's keyboard and
-	monitor, that person can reboot the system and access
-	<application>GRUB</application>. A password is helpful in this
-	case.
-      </para>
-    </note>
-
-
-	<para>
-		If you choose to use a boot loader password to enhance your system security, be sure to select the checkbox labeled <guilabel>Use a boot loader password</guilabel>.
-	</para>
-	 
-	<para>
-		Once selected, enter a password and confirm it.
-	</para>
-
-      <para>
-        <application>GRUB</application> stores the password in encrypted
-	form, so it <emphasis>cannot</emphasis> be read or recovered. If
-	you forget the boot password, boot the system normally and then
-	change the password entry in the
-	<filename>/boot/grub/grub.conf</filename> file. If you cannot
-	boot, you may be able to use the "rescue" mode on the first Fedora
-	installation disc to reset the GRUB password.
-      </para>
-
-      <para>
-	If you do need to change the <application>GRUB</application>
-	password, use the <command>grub-md5-crypt</command> utility. For
-	information on using this utility, use the command <command>man
-	  grub-md5-crypt</command> in a terminal window to read the
-	manual pages.
-      </para>
-      
-	<important>
-		<title>GRUB recognizes only the QWERTY keyboard layout</title>
-		<para>
-			When selecting a GRUB password, be aware that GRUB recognizes only the QWERTY keyboard layout, regardless of the keyboard actually attached to the system. If you use a keyboard with a significantly different layout, it might be more effective to memorize a pattern of keystrokes rather than the word that the pattern produces. 
-		</para>
-	</important>
-
-	<para>
-		To configure more advanced boot loader options, such as changing the drive order or passing options to the kernel, be sure <guilabel>Configure advanced boot loader options</guilabel> is selected before clicking <guibutton>Next</guibutton>.
-	</para>
-	 
-	<section id="x86-bootloader-adv">
-		<title>Advanced Boot Loader Configuration</title>
-		 
-		<para>
-			Now that you have chosen which boot loader to install, you can also determine where you want the boot loader to be installed. You may install the boot loader in one of two places:
-		</para>
-		<indexterm significance="normal">
-			<primary>boot loader</primary>
-			<secondary>MBR</secondary>
-		</indexterm>
-		<indexterm significance="normal">
-			<primary>MBR</primary>
-			<secondary>installing boot loader on</secondary>
-		</indexterm>
-		<indexterm significance="normal">
-			<primary>OS/2 boot manager</primary>
-		</indexterm>
-		<itemizedlist>
-			<listitem>
-				<para>
-					The master boot record (MBR) &mdash; This is the recommended place to install a boot loader, unless the MBR already starts another operating system loader, such as System Commander. The MBR is a special area on your hard drive that is automatically loaded by your computer's BIOS, and is the earliest point at which the boot loader can take control of the boot process. If you install it in the MBR, when your machine boots, GRUB presents a boot prompt. You can then boot Fedora or any other operating system that you have configured the boot loader to boot.
-				</para>
-			</listitem>
-			<listitem>
-				<para>
-	
-			<indexterm significance="normal">
-				<primary>boot loader</primary>
-				<secondary>installing on boot partition</secondary>
-			</indexterm>
-			The first sector of your boot partition &mdash; This is recommended if you are already using another boot loader on your system. In this case, your other boot loader takes control first. You can then configure that boot loader to start GRUB, which then boots Fedora.
-				</para>
-				
-				    <note>
-				      <title>GRUB as a Secondary Boot Loader</title>
-				      <para>
-					If you install GRUB as a secondary boot loader, you must
-					reconfigure your primary boot loader whenever you install and
-					boot from a new kernel.  The kernel of an operating system such
-					as Microsoft Windows does not boot in the same fashion.  Most
-					users therefore use GRUB as the primary boot loader on dual-boot
-					systems.
-				      </para>
-				    </note>
-
-				
-			</listitem>
-		</itemizedlist>
-		<figure float="0" id="fig-x86-adv-bootloader"><title>Boot Loader Installation</title>
-			<mediaobject>
-				<imageobject><imagedata fileref="images/x86-bootloader/x86-adv-bootloader.png" format="PNG"/></imageobject>
-				<textobject><para>
-						Choose where to install a boot loader and how to configure it.
-					</para>
-				</textobject>
-			</mediaobject>
-		</figure>
-		<note><title>Note</title>
-			<para>
-				If you have a RAID card, be aware that some BIOSes do not support booting from the RAID card. In cases such as these, the boot loader <emphasis>should not</emphasis> be installed on the MBR of the RAID array. Rather, the boot loader should be installed on the MBR of the same drive as the <filename>/boot/</filename> partition was created.
-			</para>
-		</note>
-		<para>
-			If your system only uses Fedora, you should choose the MBR.
-		</para>
-		 
-		<para>
-			Click the <guibutton>Change Drive Order</guibutton> button if you would like to rearrange the drive order or if your BIOS does not return the correct drive order. Changing the drive order may be useful if you have multiple SCSI adapters, or both SCSI and IDE adapters, and you want to boot from the SCSI device.
-		</para>
-		 
-		<!-- <para>
-			The <guilabel>Force LBA32 (not normally required)</guilabel> option allows you to exceed the 1024 cylinder limit for the <filename>/boot/</filename> partition. If you have a system which supports the LBA32 extension for booting operating systems above the 1024 cylinder limit, and you want to place your <filename>/boot/</filename> partition above cylinder 1024, you should select this option.
-		</para> -->
-<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="X86_Bios_Tip.xml"/>
-		<!-- <para>
-			To add default options to the boot command, enter them into the <guilabel>Kernel parameters</guilabel> field. Any options you enter are passed to the Linux kernel every time it boots.
-		</para> -->
-	</section>
-	 
-	<section id="s2-x86-bootloader-rescue">
-		<title>Rescue Mode</title>
-		<indexterm significance="normal">
-			<primary>rescue mode</primary>
-		</indexterm>
-		<para>
-			Rescue mode provides the ability to boot a small Fedora environment entirely from boot media or some other boot method instead of the system's hard drive. There may be times when you are unable to get Fedora running completely enough to access files on your system's hard drive. Using rescue mode, you can access the files stored on your system's hard drive, even if you cannot actually run Fedora from that hard drive. If you need to use rescue mode, try the following method:
-		</para>
-		 
-		<itemizedlist>
-			<listitem>
-				<para>
-					Boot an x86, AMD64, or <trademark class="registered">Intel</trademark> 64 system from any installation medium, such as CD, DVD, USB, or PXE, and type <userinput>linux rescue</userinput> at the installation boot prompt. <!-- (RHEL) Itanium users should type <userinput>elilo linux rescue</userinput> to enter rescue mode. --> Refer to <xref linkend="ap-rescuemode"/> for a more complete description of rescue mode.
-				</para>
-			</listitem>
-		</itemizedlist>
-		 
-		<!-- Reference to RHEL Deployment Guide: <para>
-			For additional information, refer to the <citetitle>Red Hat Enterprise Linux Deployment Guide</citetitle>.
-		</para> -->
-	</section>
-	 
-	<section id="s2-x86-bootloader-alt">
-		<title>Alternative Boot Loaders</title>
-		<!-- <indexterm significance="normal">
-			<primary>boot loader</primary>
-			<secondary>alternatives to</secondary>
-		</indexterm> -->
-		<indexterm significance="normal">
-			<primary>GRUB</primary>
-			<secondary>alternatives to</secondary>
-		</indexterm>
-		
-		<para>
-			<application>GRUB</application> is the default bootloader for Fedora, but is not the only choice. A variety of open-source and proprietary alternatives to <application>GRUB</application> are available to load Fedora, including <application>LILO</application>, <application>SYSLINUX</application>, <application>Acronis Disk Director Suite</application>, and <application>Apple Boot Camp</application>.
-		</para>
-		
-		<!-- <para>
-			If you do not wish to use a boot loader, you have several alternatives:
-		</para> 
-		 
-		<variablelist>
-			<varlistentry>
-				<term>
-				<indexterm significance="normal">
-					<primary>boot loader</primary>
-					<secondary>alternatives to</secondary>
-					<tertiary>LOADLIN</tertiary>
-				</indexterm>
-				<indexterm significance="normal">
-					<primary>GRUB</primary>
-					<secondary>alternatives to</secondary>
-					<tertiary>LOADLIN</tertiary>
-				</indexterm>
-				<indexterm significance="normal">
-					<primary>LOADLIN</primary>
-				</indexterm>
-LOADLIN 	</term>				<listitem>
-					<para>
-						You can load Linux from MS-DOS. Unfortunately, this requires a copy of the Linux kernel (and an initial RAM disk, if you have a SCSI adapter) to be available on an MS-DOS partition. The only way to accomplish this is to boot your Fedora system using some other method (for example, from a boot CD-ROM) and then copy the kernel to an MS-DOS partition. LOADLIN is available from
-					</para>
-<para>
-<ulink url="ftp://metalab.unc.edu/pub/Linux/system/boot/dualboot/" /></para>
-					<para>
-						and associated mirror sites.
-					</para>
-				</listitem>
-			</varlistentry>
-
-			<varlistentry>
-				<term>
-				<indexterm significance="normal">
-					<primary>boot loader</primary>
-					<secondary>alternatives to</secondary>
-					<tertiary>SYSLINUX</tertiary>
-				</indexterm>
-				<indexterm significance="normal">
-					<primary>GRUB</primary>
-					<secondary>alternatives to</secondary>
-					<tertiary>SYSLINUX</tertiary>
-				</indexterm>
-				<indexterm significance="normal">
-					<primary>SYSLINUX</primary>
-				</indexterm>SYSLINUX 	</term>
-				<listitem>
-					<para>
-						SYSLINUX is an MS-DOS program very similar to LOADLIN. It is also available from
-					</para>
-<para>
-<ulink url="ftp://metalab.unc.edu/pub/Linux/system/boot/loaders/"/></para>
-					<para>
-						and associated mirror sites.
-					</para>
-				</listitem>
-			</varlistentry>
-
-			<varlistentry>
-				<term>
-				<indexterm significance="normal">
-					<primary>boot loader</primary>
-					<secondary>alternatives to</secondary>
-					<tertiary>commercial products</tertiary>
-				</indexterm> 
-				<indexterm significance="normal">
-					<primary>GRUB</primary>
-					<secondary>alternatives to</secondary>
-					<tertiary>commercial products</tertiary>
-				</indexterm>
-				<indexterm significance="normal">
-					<primary>System Commander</primary>
-				</indexterm>
-				<indexterm significance="normal">
-					<primary>Partition Magic</primary>
-				</indexterm>
-Commercial boot loaders 	</term>				<listitem>
-					<para>
-						You can load Linux using commercial boot loaders. For example, System Commander and Partition Magic are able to boot Linux (but still require GRUB to be installed in your Linux root partition).
-					</para>
-				</listitem>
-			</varlistentry>
-		</variablelist>
-		 
-		(RHEL) <note>
-			<title>Note</title>
-
-			<para>
-				Boot loaders such as LOADLIN and System Commander are considered to be third-party boot loaders and are not supported by Red Hat.
-			</para>
-		</note> -->
-	</section>
-<!--	 
-	<section id="s2-x86-bootloader-smp">
-		<title>SMP Motherboards and GRUB</title>
-		<indexterm significance="normal">
-			<primary>SMP motherboards</primary>
-			<secondary>GRUB</secondary>
-		</indexterm>
-		<indexterm significance="normal">
-			<primary>GRUB</primary>
-			<secondary>SMP motherboards</secondary>
-		</indexterm>
-	
-		<para>
-			
-		</para>
-		
-		
-		<para>
-			In previous versions of Fedora there were two different kernel versions, a uniprocessor version and an SMP version. In Fedora &PRODVER; the kernel is SMP-enabled by default and will take advantage of multiple core, hyperthreading, and multiple CPU capabilities when they are present. This same kernel can run on single CPUs with a single core and no hyperthreading.
-		</para>
-		
-		
-		<para>
-			This section is specific to SMP motherboards only. SMP, short for Symmetric Multiprocessing, is a computer architecture providing fast performance by making multiple CPUs available to complete individual processes simultaneously (multiprocessing).
-		</para>
-		 
-		<para>
-			If the installation program detects an SMP motherboard on your system, it automatically creates two boot loader entries.
-		</para>
-		 
-		<note>
-			<title>Note</title>
-
-			<para>
-				An SMP kernel is installed by default on <trademark class="registered">Intel</trademark> <trademark class="registered">Pentium</trademark> 4 systems with hyperthreading.
-			</para>
-		</note>
-		 
-		<para>
-			The two GRUB entries are <computeroutput>Red Hat Enterprise Linux (<replaceable>kernel version</replaceable>)</computeroutput> and <computeroutput>Red Hat Enterprise Linux (<replaceable>kernel
-			version</replaceable>-smp)</computeroutput>. The <computeroutput>Red Hat Enterprise Linux (<replaceable>kernel version</replaceable>-smp)</computeroutput> boots by default. However, if you have trouble with the SMP kernel, you can elect
-			to boot the <computeroutput>Red Hat Enterprise Linux (<replaceable>kernel version</replaceable>)</computeroutput> entry instead. You retain all the functionality as before, but only operate with a single processor.
-		</para>
-	
-		
-	</section> -->
-</section>
diff --git a/en-US/X86_Trouble_After_Grub.xml b/en-US/X86_Trouble_After_Grub.xml
deleted file mode 100644
index 0de7e0e..0000000
--- a/en-US/X86_Trouble_After_Grub.xml
+++ /dev/null
@@ -1,39 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-
-
-
-]>
-
-<section id="s2-trouble-grub">
-	<title>Trouble With the Graphical GRUB Screen on an x86-based System?</title>
-	<indexterm significance="normal">
-		<primary>troubleshooting</primary>
-		<secondary>after the installation</secondary>
-		<tertiary>graphical GRUB screen</tertiary>
-	</indexterm>
-	<para>
-		If you are experiencing problems with GRUB, you may need to disable the graphical boot screen. To do this, become the root user and edit the <filename>/boot/grub/grub.conf</filename> file.
-	</para>
-	 
-	<para>
-		Within the <filename>grub.conf</filename> file, comment out the line which begins with <computeroutput>splashimage</computeroutput> by inserting the <computeroutput>#</computeroutput> character at the
-		beginning of the line.
-	</para>
-	 
-	<para>
-		Press <keycap>Enter</keycap> to exit the editing mode.
-	</para>
-	 
-	<para>
-		Once the boot loader screen has returned, type <command>b</command> to boot the system.
-	</para>
-	 
-	<para>
-		Once you reboot, the <filename>grub.conf</filename> file is reread and any changes you have made take effect.
-	</para>
-	 
-	<para>
-		You may re-enable the graphical boot screen by uncommenting (or adding) the above line back into the <filename>grub.conf</filename> file.
-	</para>
-</section>
diff --git a/en-US/X86_Uninstall-Linux-bootloader.xml b/en-US/X86_Uninstall-Linux-bootloader.xml
deleted file mode 100644
index c3ee217..0000000
--- a/en-US/X86_Uninstall-Linux-bootloader.xml
+++ /dev/null
@@ -1,62 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE appendix PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<listitem> <!-- Remove Fedora from the Bootloader -->
-	<orderedlist>
-	<title>Remove Fedora entries from your bootloader</title>
-		<important>
-			<title>
-				Example only
-			</title>
-			<para>
-				These instructions assume that your system uses the <application>GRUB</application> bootloader. If you use a different bootloader (such as <application>LILO</application>) consult the documentation for that software to identify and remove Fedora entries from its list of boot targets and to ensure that your default operating system is correctly specified. 
-			</para>
-		</important>
-		<listitem>
-			<para>
-				At the command line, type <command>su&nbsp;-</command> and press <keycap>Enter</keycap>. When the system prompts you for the root password, type the password and press <keycap>Enter</keycap>.
-			</para>
-		</listitem>
-		<listitem>
-			<para>
-				Type <command>gedit&nbsp;/boot/grub/grub.conf</command> and press <keycap>Enter</keycap>. This opens the <filename>grub.conf</filename> file in the <application>gedit</application> text editor.
-			</para>
-		</listitem>
-		<listitem>
-			<para>
-				A typical Fedora entry in the <filename>grub.conf</filename> file consists of four lines:
-					<example>
-						<title>Example Fedora entry in <filename>grub.conf</filename></title>
-						<para>
-							title Fedora (2.6.27.19-170.2.35.fc10.i686)
-						</para>
-						<para>
-							root (hd0,1)
-						</para>
-						<para>
-							kernel /vmlinuz-2.6.27.19-170.2.35.fc10.i686 ro root=UUID=04a07c13-e6bf-6d5a-b207-002689545705 rhgb quiet
-						</para>
-						<para>
-							initrd /initrd-2.6.27.19-170.2.35.fc10.i686.img
-						</para>
-					</example>
-				Depending on the configuration of your system, there may be multiple Fedora entries in <filename>grub.conf</filename>, each corresponding to a different version of the Linux kernel. Delete each of the Fedora entries from the file.
-			</para>
-		</listitem>
-		<listitem>
-			<para>
-				<filename>Grub.conf</filename> contains a line that specifies the default operating system to boot, in the format <literal>default=<replaceable>N</replaceable></literal> where <replaceable>N</replaceable> is a number equal to or greater than 0. If <replaceable>N</replaceable> is set to 0, <application>GRUB</application> will boot the first operating system in the list. If <replaceable>N</replaceable> is set to 1, it will boot the second operating system, and so forth. 
-			</para>
-			<para>
-				Identify the entry for the operating system that you want <application>GRUB</application> to boot by default and note its place in the order within the list.
-			</para>
-			<para>
-				Make sure that the <literal>default=</literal> line contains the number <emphasis>one below</emphasis> the number of your chosen default operating system in the list.
-			</para>
-			<para>
-				Save the updated <filename>grub.conf</filename> file and close <application>gedit</application>
-			</para>
-		</listitem>
-	</orderedlist>
-</listitem>
\ No newline at end of file
diff --git a/en-US/X86_Uninstall-Linux-expand-lvm.xml b/en-US/X86_Uninstall-Linux-expand-lvm.xml
deleted file mode 100644
index 38b0779..0000000
--- a/en-US/X86_Uninstall-Linux-expand-lvm.xml
+++ /dev/null
@@ -1,115 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE appendix PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<listitem> <!-- LVM -->
-	<orderedlist>
-	<title>If you use LVM</title>
-		<listitem> <!-- boot -->
-			<para>
-				Boot your computer from Linux live media and install <application>gparted</application> and <application>lvm2</application> if they are not already present.
-			</para>
-		</listitem>
-		<listitem> <!-- create partition -->
-			<orderedlist>
-			<title>Create a new partition in the free space on the disk</title>
-				<listitem>
-					<para>
-						Open <application>GParted</application>, either from a desktop menu or by typing <command>gparted</command> at the command line and pressing <keycap>Enter</keycap>.
-					</para>
-				</listitem>
-				<listitem>
-					<para>
-						<application>GParted</application> displays the partitions on your system both as a graph and as a table. The space freed by removing Fedora is labeled <literal>unallocated</literal>. Right-click on the unallocated space and select <guilabel>New</guilabel>. Accept the defaults and <application>GParted</application> will create a new partition that fills the space available on the drive.
-					</para>
-				</listitem>
-				<listitem>
-					<para>
-						Click <guilabel>Apply</guilabel>. <application>GParted</application> writes the changes to your hard drive. Take note of the name of the partition that you just created, and the name of the device that holds the partition. For example, you may have created <filename>/dev/sda3</filename> on device <filename>/dev/sda</filename>.
-					</para>
-				</listitem>
-			</orderedlist>
-		</listitem>
-		<listitem> <!-- change partition type code -->
-			<orderedlist>
-			<title>Change the partition type identifier</title>
-				<listitem>
-					<para>
-						<application>Fdisk</application> is a partitioning tool capable of preparing partitions for LVM. At a command line, type <command>fdisk <replaceable>device</replaceable></command> and press <keycap>Enter</keycap>, where <replaceable>device</replaceable> is the name of the device on which you just created a partition. For example, <command>fdisk /dev/sda</command>.
-					</para>
-				</listitem>
-				<listitem>
-					<para>
-						At the prompt <prompt>Command (m for help):</prompt>, press <keycap>T</keycap> and <keycap>Enter</keycap> to use <application>fdisk</application> to change a partition type.
-					</para>
-				</listitem>
-				<listitem>
-					<para>
-						At the prompt <prompt>Partition number (1-4):</prompt>, type the number of the partition that you just created. For example, if you just created partition <filename>/dev/sda3</filename>, type the number <literal>3</literal> and press <keycap>Enter</keycap>. This identifies the partition whose type  <application>fdisk</application> will change.
-					</para>
-				</listitem>
-				<listitem>
-					<para>
-						At the prompt <prompt>Hex code (type L to list codes):</prompt>, type the code <literal>8e</literal> and press <keycap>Enter</keycap>. This is the code for a Linux LVM partition.
-					</para>
-				</listitem>
-				<listitem>
-					<para>
-						At the prompt <prompt>Command (m for help):</prompt>, press <keycap>W</keycap> and <keycap>Enter</keycap>. <application>Fdisk</application> writes the new type code to the partition and exits.
-					</para>
-				</listitem>
-			</orderedlist>
-		</listitem>
-		<listitem> <!-- expand the volume group and logical volume-->
-			<orderedlist>
-			<title>Expand the volume group</title>
-				<listitem>
-					<para>
-						At the command prompt, type <command>lvm</command> and press <keycap>Enter</keycap> to start the <application>lvm2</application> tool.
-					</para>
-				</listitem>
-				<listitem>
-					<para>
-						At the <prompt>lvm&gt;</prompt> prompt, type <command>pvcreate <replaceable>partition</replaceable></command> and press <keycap>Enter</keycap>, where <replaceable>partition</replaceable> is the partition that you recently created. For example, <command>pvcreate /dev/sda3</command>. This creates <filename>/dev/sda3</filename> as a physical volume in LVM.
-					</para>
-				</listitem>
-				<listitem>
-					<para>
-						At the <prompt>lvm&gt;</prompt> prompt, type <command>vgextend <replaceable>VolumeGroup</replaceable> <replaceable>partition</replaceable></command> and press <keycap>Enter</keycap>, where <replaceable>VolumeGroup</replaceable> is the LVM volume group on which Linux is installed and <replaceable>partition</replaceable> is the partition that you recently created. For example, if Linux is installed on <filename>/dev/VolumeGroup00</filename>, you would type <command>vgextend /dev/VolumeGroup00 /dev/sda3</command> to extend that volume group to include the physical volume at <filename>/dev/sda3</filename>.
-					</para>
-				</listitem>
-				<listitem>
-					<para>
-						At the <prompt>lvm&gt;</prompt> prompt, type <command>lvextend -l +100%FREE <replaceable>LogVol</replaceable></command> and press <keycap>Enter</keycap>, where <replaceable>LogVol</replaceable> is the logical volume that contains your Linux filesystem. For example, to extend <filename>LogVol00</filename> to fill the newly-available space in its volume group, <filename>VolGroup00</filename>, type <command>lvextend -l +100%FREE /dev/VolGroup00/LogVol00</command>.
-					</para>
-				</listitem>
-				<listitem>
-					<para>
-						At the <prompt>lvm&gt;</prompt> prompt, type <command>exit</command> and press <keycap>Enter</keycap> to exit <application>lvm2</application>
-					</para>
-				</listitem>
-			</orderedlist>
-		</listitem>
-		<listitem> <!-- file system check -->
-			<para>
-				Type <command>e2fsck <replaceable>LogVol</replaceable></command> at the command line and press <keycap>Enter</keycap>, where <replaceable>LogVol</replaceable> is the logical volume that you just resized. For example, if you just resized <filename>/dev/VolumeGroup00/LogVol00</filename>, you would type <command>e2fsck&nbsp;/dev/VolumeGroup00/LogVol00</command>.
-			</para>
-			<para>
-				Linux now checks the file system of the newly-resized logical volume.
-			</para>
-		</listitem>
-		<listitem> <!-- resize file system -->
-			<para>
-				When the file system check finishes, type <command>resize2fs <replaceable>LogVol</replaceable></command> at a command line and press <keycap>Enter</keycap>, where <replaceable>LogVol</replaceable> is the partition that you just resized. For example, if you just resized <filename>/dev/VolumeGroup00/LogVol00</filename>, you would type <command>resize2fs&nbsp;/dev/VolumeGroup00/LogVol00</command>.
-			</para>
-			<para>
-				Linux now resizes your file system to fill the newly-resized logical volume.
-			</para>
-		</listitem>
-		<listitem> <!-- restart -->
-			<para>
-				Restart your computer. The extra space is now available to your Linux installation.
-			</para>
-		</listitem>
-	</orderedlist>
-</listitem>
\ No newline at end of file
diff --git a/en-US/X86_Uninstall-Linux-expand-nolvm.xml b/en-US/X86_Uninstall-Linux-expand-nolvm.xml
deleted file mode 100644
index d936264..0000000
--- a/en-US/X86_Uninstall-Linux-expand-nolvm.xml
+++ /dev/null
@@ -1,55 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE appendix PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<listitem> <!-- no LVM -->
-	<orderedlist> 
-	<title>If you do not use LVM</title>
-		<listitem>
-			<para>
-				Boot your computer from Linux live media, and install <application>gparted</application> if it is not already present.
-			</para>
-		</listitem>
-		<listitem>
-			<para>
-				Open <application>GParted</application>, either from a desktop menu or by typing <command>gparted</command> at the command line and pressing <keycap>Enter</keycap>.
-			</para>
-		</listitem>
-		<listitem>
-			<para>
-				<application>GParted</application> displays the partitions on your system both as a graph and as a table. Click on the partition that you want to extend to use the space freed by removing Fedora, and click the <guilabel>Resize/Move</guilabel> button. 
-			</para>
-		</listitem>
-		<listitem>
-			<para>
-				A new dialog opens, allowing you to specify a new size for the partition by entering it as numbers, or by dragging the sides of the graphical representation of the partition so that it fills the available space. Click the <guilabel>Resize/Move</guilabel> button in this dialog to confirm your choice. 
-			</para>
-		</listitem>
-		<listitem>
-			<para>
-				Back in the main <application>GParted</application> window, click <guilabel>Apply</guilabel>. Take note of the name of the partition that you just resized, for example, <filename>/dev/sda3</filename>.
-			</para>
-		</listitem>
-		<listitem>
-			<para>
-				When <application>GParted</application> finishes resizing the partition, type <command>e2fsck <replaceable>partition</replaceable></command> at a command line and press <keycap>Enter</keycap>, where <replaceable>partition</replaceable> is the partition that you just resized. For example, if you just resized <filename>/dev/sda3</filename>, you would type <command>e2fsck&nbsp;/dev/sda3</command>.
-			</para>
-			<para>
-				Linux now checks the file system of the newly-resized partition.
-			</para>
-		</listitem>
-		<listitem>
-			<para>
-				When the file system check finishes, type <command>resize2fs <replaceable>partition</replaceable></command> at a command line and press <keycap>Enter</keycap>, where <replaceable>partition</replaceable> is the partition that you just resized. For example, if you just resized <filename>/dev/sda3</filename>, you would type <command>resize2fs&nbsp;/dev/sda3</command>.
-			</para>
-			<para>
-				Linux now resizes your file system to fill the newly-resized partition.
-			</para>
-		</listitem>
-		<listitem>
-			<para>
-				Restart your computer. The extra space is now available to your Linux installation.
-			</para>
-		</listitem>
-	</orderedlist>
-</listitem>
\ No newline at end of file
diff --git a/en-US/X86_Uninstall-Linux-expand.xml b/en-US/X86_Uninstall-Linux-expand.xml
deleted file mode 100644
index 535b601..0000000
--- a/en-US/X86_Uninstall-Linux-expand.xml
+++ /dev/null
@@ -1,24 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE appendix PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<listitem> <!-- Reclaim the space freed by removing Fedora -->
-	<itemizedlist>
-	<title>Make space available to your operating system</title>
-		<note>
-			<para>
-				This step is not required to remove Fedora from your computer. However, if you skip this step, you will leave part of your hard drive's storage capacity unusable by your other Linux operating system. Depending on your configuration, this might be a a significant portion of the storage capacity of the drive.
-			</para>
-		</note>
-		<note>
-			<para>
-				To carry out this step, you require live media for a Linux distribution, for example, the Fedora Live CD or the Knoppix DVD.
-			</para>
-		</note>
-		<para>
-			The method to make the space freed by removing the Fedora partitions available to your other Linux operating system differs, depending on whether your chosen operating system is installed on disk partitions configured to use Logical Volume Management (LVM) or not.
-		</para>
-		<xi:include href="X86_Uninstall-Linux-expand-nolvm.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
-		<xi:include href="X86_Uninstall-Linux-expand-lvm.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
-		</itemizedlist>
-</listitem>
diff --git a/en-US/X86_Uninstall-Linux-partitions.xml b/en-US/X86_Uninstall-Linux-partitions.xml
deleted file mode 100644
index 127110c..0000000
--- a/en-US/X86_Uninstall-Linux-partitions.xml
+++ /dev/null
@@ -1,27 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE appendix PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<listitem> <!-- Remove Fedora partitions -->
-	<orderedlist>
-	<title>Remove Fedora partitions</title>
-		<listitem>
-			<para>
-				Boot the Linux version that you want to keep on your computer.
-			</para>
-		</listitem>
-		<listitem>
-			<para>
-				Open <application>GParted</application>, either from a desktop menu or by typing <command>gparted</command> at the command line and pressing <keycap>Enter</keycap>.
-			</para>
-		</listitem>
-		<listitem>
-			<para>
-				<application>GParted</application> displays the partitions that it detects on your computer, both as a graph and as a table.
-			</para>
-			<para>
-				Right-click the Fedora partitions, then select <guilabel>Delete</guilabel>.
-			</para>
-		</listitem>
-	</orderedlist>
-</listitem>
\ No newline at end of file
diff --git a/en-US/X86_Uninstall-Linux.xml b/en-US/X86_Uninstall-Linux.xml
deleted file mode 100644
index 751449d..0000000
--- a/en-US/X86_Uninstall-Linux.xml
+++ /dev/null
@@ -1,18 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE appendix PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-
-<section id="sn-x86-uninstall-dual-linux">
-<title>Your computer dual-boots Fedora and a different Linux distribution</title>
-	<note>
-		<para>
-			Because of the differences between the many different Linux distributions, these instructions are a general guide only. Specific details will vary according to your chosen distribution and the configuration of your particular computer. This example uses <application>GParted</application> as a partition editor and <application>gedit</application> as a text editor, but many other tools are available to perform these tasks. To follow these instructions exactly as written, install <application>GParted</application> and <application>gedit</application>.
-		</para>
-	</note>
-	<orderedlist>
-		<xi:include href="X86_Uninstall-Linux-partitions.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
-		<xi:include href="X86_Uninstall-Linux-bootloader.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
-		<xi:include href="X86_Uninstall-Linux-expand.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>		
-	</orderedlist>
-</section>
diff --git a/en-US/X86_Uninstall-Mac.xml b/en-US/X86_Uninstall-Mac.xml
deleted file mode 100644
index f808d46..0000000
--- a/en-US/X86_Uninstall-Mac.xml
+++ /dev/null
@@ -1,62 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE appendix PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<section id="sn-x86-uninstall-dual-mac">
-		<title>Your computer dual-boots Fedora and Mac OS X</title>
-			<para>
-				The procedure to remove Fedora from a system that dual-boots Fedora and Mac OS X varies depending on whether you have installed <application>Boot Camp</application> on your computer:
-			</para>
-			<orderedlist>
-			<title>You are not using <application>Boot Camp</application> on your computer</title>
-				<listitem>
-					<para>
-						Open the <application>Disk Utility</application> in <filename>/Applications/Utilities</filename>.
-					</para>
-				</listitem>
-				<listitem>
-					<para>
-						Select the entry on the left for the disk volume containing Fedora.
-					</para>
-				</listitem>
-				<listitem>
-					<para>
-						Click the <guilabel>Partition</guilabel> tab on the right side of the dialog.
-					</para>
-				</listitem>
-				<listitem>
-					<para>
-						Select the Fedora partitions and click the minus button below the partition layout diagram.
-					</para>
-				</listitem>
-					<listitem>
-					<para>
-						Resize your OS X partition to include the newly freed space.
-					</para>
-					</listitem> 
-			</orderedlist>
-			
-			<orderedlist>
-			<title>You are using <application>Boot Camp</application> on your computer</title>
-				<listitem>
-					<para>
-						Open the <application>Boot Camp Assistant</application> in <filename>/Applications/Utilities</filename>.
-					</para>
-				</listitem>
-				<listitem>
-					<para>
-						Select <guilabel>Create or remove a Windows partition</guilabel> and click <guilabel>Next</guilabel>.
-					</para>
-				</listitem>
-				<listitem>
-					<para>
-						If your computer has a single internal disk, click <guilabel>Restore</guilabel>.
-					</para>
-				</listitem>
-				<listitem>
-					<para>
-						If your computer has multiple internal disks, select the Linux disk, and then select <guilabel>Restore to a single Mac OS partition</guilabel>. Click <guilabel>Continue</guilabel>.
-					</para>
-				</listitem> 
-			</orderedlist>
-		</section>
\ No newline at end of file
diff --git a/en-US/X86_Uninstall-Windows-2000XP2003.xml b/en-US/X86_Uninstall-Windows-2000XP2003.xml
deleted file mode 100644
index 2523c34..0000000
--- a/en-US/X86_Uninstall-Windows-2000XP2003.xml
+++ /dev/null
@@ -1,129 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE appendix PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-			<section id="sn-x86-uninstall-dual-windows-2000xp2003">
-			<title>Windows 2000, Windows Server 2000, Windows XP, and Windows Server 2003</title>
-			<warning>
-				<xi:include href="X86_Uninstall-Windows-warning-para-1.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
-				<para>
-					This procedure relies on the <application>Windows Recovery Console</application> that loads from the Windows installation disk, so you will not be able to complete the procedure without access to this disk. If you start this procedure and do not complete it, you could leave your computer in a condition where you cannot boot it. The "system restore disk" supplied with some factory-built computers that are sold with Windows pre-installed on them might not include the <application>Windows Recovery Console</application>.
-				</para>
-				<para>
-					During the process outlined in these instructions, the <application>Windows Recovery Console</application> will prompt you for the Administrator password for your Windows system. Do not follow these instructions unless you know the Administrator password for your system or are certain that an Administrator password has never been created, even by the computer manufacturer.
-				</para>
-			</warning>
-			<orderedlist>
-				<listitem>
-					<xi:include href="X86_Uninstall-Windows-remove-para-1.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
-
-					<orderedlist>
-						<listitem>
-							<xi:include href="X86_Uninstall-Windows-remove-para-2.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
-						</listitem>
-						<listitem>
-							<para>
-								Click <guilabel>Start</guilabel>&gt;<guilabel>Run...</guilabel>, type <command>diskmgmt.msc</command> and press <keycap>Enter</keycap>. The <application>Disk Management</application> tool opens. 
-							</para>
-							<xi:include href="X86_Uninstall-Windows-remove-para-3.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
-						</listitem>
-						<listitem>
-							<xi:include href="X86_Uninstall-Windows-remove-para-4.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
-						</listitem>
-					</orderedlist>
-				</listitem>
-
-				<listitem>
-					<xi:include href="X86_Uninstall-Windows-extend-para-1.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
-					<xi:include href="X86_Uninstall-Windows-extend-note-1.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
-					<xi:include href="X86_Uninstall-Windows-extend-para-2.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
-					<orderedlist>
-						<xi:include href="X86_Uninstall-Windows-extend-title-1.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
-						<note>
-							<para>
-								The <application>diskpart</application> tool used in this step is installed as part of the Windows XP and Windows 2003 operating systems. If you are performing this step on a computer running Windows 2000 or Windows Server 2000, you can download a version of <application>diskpart</application> for your operating system from the Microsoft website. 
-							</para>
-						</note>
-						<listitem>
-							<para>
-								Click <guilabel>Start</guilabel>&gt;<guilabel>Run...</guilabel>, type <command>diskpart</command> and press <keycap>Enter</keycap>. A command window appears.
-							</para>
-						</listitem>
-						<listitem>
-							<para>
-								Type <command>list volume</command> and press <keycap>Enter</keycap>. <application>Diskpart</application> displays a list of the partitions on your system with a volume number, its drive letter, volume label, filesystem type, and size. Identify the Windows partition that you would like to use to occupy the space vacated on your hard drive by Fedora and take note of its volume number (for example, your Windows <filename>C:</filename> drive might be "Volume 0").
-							</para>
-						</listitem>
-						<listitem>
-							<para>
-								Type <command>select volume <replaceable>N</replaceable></command> (where <replaceable>N</replaceable> is the volume number for the Windows partition that you want to extend) and press <keycap>Enter</keycap>. Now type <command>extend</command> and press <keycap>Enter</keycap>. <application>Diskpart</application> now extends your chosen partition to fill the remaining space on your hard drive. It will notify you when the operation is complete.
-							</para>
-						</listitem>
-					</orderedlist>
-					<orderedlist>
-					<xi:include href="X86_Uninstall-Windows-add-title-1.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
-						<listitem>
-							<para>
-								In the the <literal>Disk Management</literal> window, right-click on disk space that Windows labels as <literal>unallocated</literal> and select <literal>New Partition</literal> from the menu. The <application>New Partition Wizard</application> starts.
-							</para>
-						</listitem>
-						<listitem>
-							<para>
-								Follow the prompts presented by the <application>New Partition Wizard</application>. If you accept the default options, the tool will create a new partition that fills all available space on the hard drive, assigns it the next available drive letter, and formats it with the NTFS file system.
-							</para>
-						</listitem>
-					</orderedlist>
-				</listitem>
-				<listitem>
-					<xi:include href="X86_Uninstall-Windows-bootloader-para-1.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
-					<orderedlist>
-					      <listitem>
-							<xi:include href="X86_Uninstall-Windows-bootloader-para-2.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
-<screen><prompt>Press any key to boot from CD</prompt></screen>
-							<xi:include href="X86_Uninstall-Windows-bootloader-para-3.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
-					      </listitem>
-					      <listitem>
-							<para>
-								When the <literal>Welcome to Setup</literal> screen appears, you can start the <application>Windows Recovery Console</application>. The procedure is slightly different on different versions of Windows:
-							</para>
-							<itemizedlist>
-								<listitem>
-									<para>
-										On Windows 2000 and Windows Server 2000, press the <keycap>R</keycap> key, then the <keycap>C</keycap> key. 
-									</para>
-								</listitem>
-								<listitem>
-									<para>
-										On Windows XP and Windows Server 2003, press the <keycap>R</keycap> key. 
-									</para>
-								</listitem>
-							</itemizedlist>
-						</listitem>
-						<listitem>
-							<para>
-								The <application>Windows Recovery Console</application> scans your hard drives for Windows installations, and assigns a number to each one. It displays a list of Windows installations and prompts you to select one. Type the number corresponding to the Windows installation that you want to restore. 
-							</para>
-						</listitem>
-						<listitem>
-							<para>
-								The <application>Windows Recovery Console</application> prompts you for the Administrator password for your Windows installation. Type the Administrator password and press the <keycap>Enter</keycap> key. If there is no administrator password for this system, press only the <keycap>Enter</keycap> key.
-							</para>
-						</listitem>
-						<listitem>
-							<para>
-								At the prompt, type the command <command>fixmbr</command> and press the <keycap>Enter</keycap>. The <application>fixmbr</application> tool now restores the Master Boot Record for the system.
-							</para>
-						</listitem>
-						<listitem>
-							<para>
-								When the prompt reappears, type <command>exit</command> and press the <keycap>Enter</keycap> key.
-							</para>
-						</listitem>
-						<listitem>
-							<xi:include href="X86_Uninstall-Windows-bootloader-para-4.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
-						</listitem>
-					</orderedlist>
-				</listitem>
-			</orderedlist>
-			</section>
-
diff --git a/en-US/X86_Uninstall-Windows-Vista2008.xml b/en-US/X86_Uninstall-Windows-Vista2008.xml
deleted file mode 100644
index 6cf6e8e..0000000
--- a/en-US/X86_Uninstall-Windows-Vista2008.xml
+++ /dev/null
@@ -1,109 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE appendix PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-			<section id="sn-x86-uninstall-dual-windows-vista2008">
-			<title>Windows Vista and Windows Server 2008</title>
- 			<warning>
-				<xi:include href="X86_Uninstall-Windows-warning-para-1.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
-				<para>
-					This procedure relies on the <application>Windows Recovery Environment</application> that loads from the Windows installation disk and you will not be able to complete the procedure without access to this disk. If you start this procedure and do not complete it, you could leave your computer in a condition where you cannot boot it. The "system restore disk" supplied with some factory-built computers that are sold with Windows pre-installed on them might not include the <application>Windows Recovery Environment</application>.
-				</para>
-			</warning>
-			<orderedlist>
-				<listitem>
-					<xi:include href="X86_Uninstall-Windows-remove-para-1.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
-
-					<orderedlist>
-						<listitem>
-							<xi:include href="X86_Uninstall-Windows-remove-para-2.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
-						</listitem>
-						<listitem>
-							<para>
-								Click <guilabel>Start</guilabel> then type <command>diskmgmt.msc</command> into the <guilabel>Start Search</guilabel> box and press <keycap>Enter</keycap>. The <application>Disk Management</application> tool opens. 
-							</para>
-							<xi:include href="X86_Uninstall-Windows-remove-para-3.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
-						</listitem>
-						<listitem>
-							<xi:include href="X86_Uninstall-Windows-remove-para-4.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
-						</listitem>
-					</orderedlist>
-				</listitem>
-
-				<listitem>
-					<xi:include href="X86_Uninstall-Windows-extend-para-1.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
-					<xi:include href="X86_Uninstall-Windows-extend-note-1.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
-					<xi:include href="X86_Uninstall-Windows-extend-para-2.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
-					<orderedlist>
-						<xi:include href="X86_Uninstall-Windows-extend-title-1.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
-						<listitem>
-							<para>
-								In the <application>Disk Management</application> window, right-click on the Windows partition that you want to extend and select <guilabel>Extend Volume</guilabel> from the menu. The <application>Extend Volume Wizard</application> opens.
-							</para>
-						</listitem>
-						<listitem>
-							<para>
-								Follow the prompts presented by the <application>Extend Volume Wizard</application>. If you accept the defaults that it offers you, the tool will extend the selected volume to fill all available space on the hard drive.
-							</para>
-						</listitem>
-					</orderedlist>
-					<orderedlist>
-					<xi:include href="X86_Uninstall-Windows-add-title-1.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
-						<listitem>
-							<para>
-								In the <literal>Disk Management</literal> window, right-click on disk space that Windows labels as <literal>unallocated</literal> and select <literal>New Simple Volume</literal> from the menu. The <application>New Simple Volume Wizard</application> starts.
-							</para>
-						</listitem>
-						<listitem>
-							<para>
-								Follow the prompts presented by the <application>New Simple Volume Wizard</application>. If you accept the default options, the tool will create a new partition that fills all available space on the hard drive, assigns it the next available drive letter, and formats it with the NTFS file system.
-							</para>
-						</listitem>
-					</orderedlist>
-				</listitem>
-				<listitem>
-					<xi:include href="X86_Uninstall-Windows-bootloader-para-1.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
-					<orderedlist>
-						<listitem>
-							<xi:include href="X86_Uninstall-Windows-bootloader-para-2.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
-<screen><prompt>Press any key to boot from CD or DVD</prompt></screen>
-							<xi:include href="X86_Uninstall-Windows-bootloader-para-3.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
-						</listitem>
-						<listitem>
-							<para>
-								In the <guilabel>Install Windows</guilabel> dialog, select a language, time and currency format, and keyboard type. Click <guilabel>Next</guilabel>
-							</para>
-						</listitem>
-						<listitem>
-							<para>
-								Click <guilabel>Repair your computer</guilabel>.
-							</para>
-						</listitem>
-						<listitem>
-							<para>
-								The <application>Windows Recovery Environment</application> (WRE) shows you the Windows installations that it can detect on your system. Select the installation that you want to restore, then click <guilabel>Next</guilabel>.
-							</para>
-						</listitem>
-						<listitem>
-							<para>
-								Click <guilabel>Command prompt</guilabel>. A command window will open.
-							</para>
-						</listitem>
-						<listitem>
-							<para>
-								Type <command>bootrec /fixmbr</command> and press <keycap>Enter</keycap>.
-							</para>
-						</listitem>
-						<listitem>
-							<para>
-								When the prompt reappears, close the command window, then click <guilabel>Restart</guilabel>.
-							</para>
-						</listitem>
-						<listitem>
-							<xi:include href="X86_Uninstall-Windows-bootloader-para-4.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
-						</listitem>
-					</orderedlist>
-				</listitem>
-			</orderedlist>
-			</section>
-
diff --git a/en-US/X86_Uninstall-Windows-add-title-1.xml b/en-US/X86_Uninstall-Windows-add-title-1.xml
deleted file mode 100644
index 7c368fb..0000000
--- a/en-US/X86_Uninstall-Windows-add-title-1.xml
+++ /dev/null
@@ -1,5 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE appendix PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<title>Adding a new Windows partition</title>
\ No newline at end of file
diff --git a/en-US/X86_Uninstall-Windows-bootloader-para-1.xml b/en-US/X86_Uninstall-Windows-bootloader-para-1.xml
deleted file mode 100644
index 0918a01..0000000
--- a/en-US/X86_Uninstall-Windows-bootloader-para-1.xml
+++ /dev/null
@@ -1,7 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE appendix PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<para>
-	Restore the Windows bootloader
-</para>
\ No newline at end of file
diff --git a/en-US/X86_Uninstall-Windows-bootloader-para-2.xml b/en-US/X86_Uninstall-Windows-bootloader-para-2.xml
deleted file mode 100644
index 6cd9b9c..0000000
--- a/en-US/X86_Uninstall-Windows-bootloader-para-2.xml
+++ /dev/null
@@ -1,7 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE appendix PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<para>
-	Insert the Windows installation disk and restart your computer. As your computer starts, the following message will appear on the screen for a few seconds:
-</para>
\ No newline at end of file
diff --git a/en-US/X86_Uninstall-Windows-bootloader-para-3.xml b/en-US/X86_Uninstall-Windows-bootloader-para-3.xml
deleted file mode 100644
index 581cab3..0000000
--- a/en-US/X86_Uninstall-Windows-bootloader-para-3.xml
+++ /dev/null
@@ -1,7 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE appendix PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<para>
-	Press any key while the message is still showing and the Windows installation software will load.
-</para>
\ No newline at end of file
diff --git a/en-US/X86_Uninstall-Windows-bootloader-para-4.xml b/en-US/X86_Uninstall-Windows-bootloader-para-4.xml
deleted file mode 100644
index f2536ee..0000000
--- a/en-US/X86_Uninstall-Windows-bootloader-para-4.xml
+++ /dev/null
@@ -1,7 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE appendix PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<para>
-	Your computer will restart and boot your Windows operating system.
-</para>
\ No newline at end of file
diff --git a/en-US/X86_Uninstall-Windows-extend-note-1.xml b/en-US/X86_Uninstall-Windows-extend-note-1.xml
deleted file mode 100644
index 13a42e3..0000000
--- a/en-US/X86_Uninstall-Windows-extend-note-1.xml
+++ /dev/null
@@ -1,9 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE appendix PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<note>
-	<para>
-		  This step is not required to remove Fedora from your computer. However, if you skip this step, you will leave part of your hard drive's storage capacity unusable by Windows. Depending on your configuration, this might be a a significant portion of the storage capacity of the drive.
-	</para>
-</note>
diff --git a/en-US/X86_Uninstall-Windows-extend-para-1.xml b/en-US/X86_Uninstall-Windows-extend-para-1.xml
deleted file mode 100644
index a5e095c..0000000
--- a/en-US/X86_Uninstall-Windows-extend-para-1.xml
+++ /dev/null
@@ -1,7 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE appendix PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<para>
-	Enable Windows to use the space on your hard drive vacated by Fedora (optional)
-</para>
\ No newline at end of file
diff --git a/en-US/X86_Uninstall-Windows-extend-para-2.xml b/en-US/X86_Uninstall-Windows-extend-para-2.xml
deleted file mode 100644
index fc2b8f4..0000000
--- a/en-US/X86_Uninstall-Windows-extend-para-2.xml
+++ /dev/null
@@ -1,7 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE appendix PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<para>
-	Decide whether to extend an existing Windows partition to use the extra space, or create a new Windows partition in that space. If you create new a Windows partition, Windows will allocate a new drive letter to it and will interact with it as if it is a separate hard drive.
-</para>
\ No newline at end of file
diff --git a/en-US/X86_Uninstall-Windows-extend-title-1.xml b/en-US/X86_Uninstall-Windows-extend-title-1.xml
deleted file mode 100644
index ad4c38d..0000000
--- a/en-US/X86_Uninstall-Windows-extend-title-1.xml
+++ /dev/null
@@ -1,5 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE appendix PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<title>Extending an existing Windows partition</title>
diff --git a/en-US/X86_Uninstall-Windows-remove-para-1.xml b/en-US/X86_Uninstall-Windows-remove-para-1.xml
deleted file mode 100644
index b4a5d8d..0000000
--- a/en-US/X86_Uninstall-Windows-remove-para-1.xml
+++ /dev/null
@@ -1,7 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE appendix PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<para>
-	Remove the Fedora partitions
-</para>
\ No newline at end of file
diff --git a/en-US/X86_Uninstall-Windows-remove-para-2.xml b/en-US/X86_Uninstall-Windows-remove-para-2.xml
deleted file mode 100644
index 4faad77..0000000
--- a/en-US/X86_Uninstall-Windows-remove-para-2.xml
+++ /dev/null
@@ -1,7 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE appendix PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<para>
-	Boot your computer into your Microsoft Windows environment.
-</para>
diff --git a/en-US/X86_Uninstall-Windows-remove-para-3.xml b/en-US/X86_Uninstall-Windows-remove-para-3.xml
deleted file mode 100644
index e165145..0000000
--- a/en-US/X86_Uninstall-Windows-remove-para-3.xml
+++ /dev/null
@@ -1,7 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE appendix PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<para>
-	The tool displays a graphical representation of your disk, with bars representing each partition. The first partition is usually labeled <literal>NTFS</literal> and corresponds to your <filename>C:</filename> drive. At least two Fedora partitions will be visible. Windows will not display a file system type for these partitions, but may allocate drive letters to some of them.
-</para>
\ No newline at end of file
diff --git a/en-US/X86_Uninstall-Windows-remove-para-4.xml b/en-US/X86_Uninstall-Windows-remove-para-4.xml
deleted file mode 100644
index 0c32b46..0000000
--- a/en-US/X86_Uninstall-Windows-remove-para-4.xml
+++ /dev/null
@@ -1,7 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE appendix PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<para>
-	Right-click on one of the Fedora partitions, then click <guilabel>Delete Partition</guilabel> and click <guilabel>Yes</guilabel> to confirm the deletion. Repeat this process for the other Fedora partitions on your system. As you delete partitions, Windows labels the space on the hard drive previously occupied by those partitions as <literal>unallocated</literal>.
-</para>
\ No newline at end of file
diff --git a/en-US/X86_Uninstall-Windows-warning-para-1.xml b/en-US/X86_Uninstall-Windows-warning-para-1.xml
deleted file mode 100644
index 9c16661..0000000
--- a/en-US/X86_Uninstall-Windows-warning-para-1.xml
+++ /dev/null
@@ -1,7 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE appendix PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<para>
-	Once you commence this process, your computer may be left in an unbootable state until you complete the entire set of instructions. Carefully read the steps below before beginning the removal process. Consider opening these instructions on another computer or printing them so that you have access to them at all times during the process.
-</para>
diff --git a/en-US/X86_Uninstall-msdos.xml b/en-US/X86_Uninstall-msdos.xml
deleted file mode 100644
index 4efac36..0000000
--- a/en-US/X86_Uninstall-msdos.xml
+++ /dev/null
@@ -1,75 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE appendix PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-	<section id="sn-x86-uninstall-legacy">
-	<title>Replacing Fedora with MS-DOS or legacy versions of Microsoft Windows</title>
-		<para>
-			In DOS and Windows, use the Windows <command>fdisk</command> utility to create a new MBR with the <wordasword>undocumented</wordasword> flag <command>/mbr</command>. This <emphasis>ONLY</emphasis> rewrites the MBR to boot
-			the primary DOS partition. The command should look like the following:
-		</para>
-<screen>
-<command>fdisk /mbr</command>
-</screen>
-		<para>
-			If you need to remove Linux from a hard drive and have attempted to do this with the default DOS (Windows) <command>fdisk</command>, you will experience the <emphasis>Partitions exist but they do not exist</emphasis> problem. The best way
-			to remove non-DOS partitions is with a tool that understands partitions other than DOS.
-		</para>
-		<para>
-			To begin, insert the Fedora CD #1 and boot your system. Once you have booted off the CD, a boot prompt appears. At the boot prompt, type: <userinput>linux rescue</userinput>. This starts the rescue mode program.
-		</para>
-		<para>
-			You are prompted for your keyboard and language requirements. Enter these values as you would during the installation of Fedora.
-		</para>
-		<para>
-			Next, a screen appears telling you that the program attempts to find a Fedora install to rescue. Select <guibutton>Skip</guibutton> on this screen.
-		</para>
-		<para>
-			After selecting <guibutton>Skip</guibutton>, you are given a command prompt where you can access the partitions you would like to remove.
-		</para>
-		<para>
-			First, type the command <command>list-harddrives</command>. This command lists all hard drives on your system that are recognizable by the installation program, as well as their sizes in megabytes.
-		</para>
-		<warning>
-			<title>Warning</title>
-
-			<para>
-				Be careful to remove only the necessary Fedora partitions. Removing other partitions could result in data loss or a corrupted system environment.
-			</para>
-		</warning>
-		<para>
-			To remove partitions, use the partitioning utility <command>parted</command>. Start <command>parted</command>, where <replaceable>/dev/hda</replaceable> is the device on which to remove the partition:
-		</para>
-<screen>parted /dev/hda</screen>
-		<para>
-			Using the <command>print</command> command, view the current partition table to determine the minor number of the partition to remove:
-		</para>
-<screen>print</screen>
-		<para>
-			The <command>print</command> command also displays the partition's type (such as linux-swap, ext2, ext3, ext4 and so on). Knowing the type of the partition helps you in determining whether to remove the partition.
-		</para>
-		<para>
-			Remove the partition with the command <command>rm</command>. For example, to remove the partition with minor number 3:
-		</para>
-<screen>rm 3</screen>
-		<important>
-			<title>Important</title>
-
-			<para>
-				The changes start taking place as soon as you press [Enter], so review the command before committing to it.
-			</para>
-		</important>
-		<para>
-			After removing the partition, use the <command>print</command> command to confirm that it is removed from the partition table.
-		</para>
-		<para>
-			Once you have removed the Linux partitions and made all of the changes you need to make, type <command>quit</command> to quit <command>parted</command>.
-		</para>
-		<para>
-			After quitting <command>parted</command>, type <command>exit</command> at the boot prompt to exit rescue mode and reboot your system, instead of continuing with the installation. The system should reboot automatically. If
-			it does not, you can reboot your computer using
-			<keycombo><keycap>Control</keycap><keycap>Alt</keycap><keycap>Delete</keycap>
-			</keycombo>
-			.
-		</para>
-	</section>
diff --git a/en-US/X86_Uninstall-single.xml b/en-US/X86_Uninstall-single.xml
deleted file mode 100644
index acca65c..0000000
--- a/en-US/X86_Uninstall-single.xml
+++ /dev/null
@@ -1,47 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE appendix PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-	<section id="sn-x86-uninstall-single">
-	<title>Fedora is the only operating system on the computer</title>
-	
-		<para>
-			If Fedora is the only operating system on your computer, use the installation media for the replacement operating system to remove Fedora. Examples of installation media include the Windows XP installation CD, Windows Vista installation DVD, Mac OS X installation CDs or DVD, or the installation CD, CDs, or DVD of another Linux distribution. 
-		</para>
-		
-		<para>
-			Note that some manufacturers of factory-built computers pre-installed with Microsoft Windows do not supply the Windows installation CD or DVD with the computer. The manufacturer may instead have supplied their own "system restore disk", or have included software with the computer that allowed you to create your own "system restore disk" when you first started the computer. In some cases, the system restore software is stored on a separate partition on the system's hard drive. If you cannot identify the installation media for an operating system that was pre-installed on your computer, consult the documentation supplied with the machine, or contact the manufacturer.
-		</para>
-		
-		<para>
-			When you have located the installation media for your chosen operating system:
-		</para>
-		
-		<orderedlist>
-			<listitem>
-				<para>
-					Back up any data that you want to keep.
-				</para>
-			</listitem>
-			<listitem>
-				<para>
-					Shut down the computer.
-				</para>
-			</listitem>
-			<listitem>
-				<para>
-					Boot your computer with the installation disk for the replacement operating system. 
-				</para>
-			</listitem>
-			<listitem>
-				<para>
-					Follow the prompts presented during the installation process. Windows, OS X, and most Linux installation disks allow you to manually partition your hard drive during the installation process, or will offer you the option to remove all partitions and start with a fresh partition scheme. At this point, remove any existing partitions that the installation software detects or allow the installer to remove the partitions automatically. "System restore" media for computers pre-installed with Microsoft Windows might create a default partition layout automatically without input from you.
-				</para>
-				<warning>
-					<para>
-						If your computer has system restore software stored on a partition on a hard drive, take care when removing partitions while installing an operating system from other media. Under these circumstances, you could destroy the partition holding the system restore software.
-					</para>
-				</warning>
-			</listitem>
-		</orderedlist>
-	</section>
diff --git a/en-US/X86_Uninstall.xml b/en-US/X86_Uninstall.xml
deleted file mode 100644
index 8b059f9..0000000
--- a/en-US/X86_Uninstall.xml
+++ /dev/null
@@ -1,75 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE appendix PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<chapter id="ch-x86-uninstall"><title>Removing Fedora</title>
-
-<!-- Index terms -->
-<indexterm significance="normal">
-		<primary>uninstalling</primary>
-	</indexterm>
-	<indexterm significance="normal">
-		<primary>removing</primary>
-		<secondary>Fedora</secondary>
-	</indexterm>
-<!-- End Index terms -->
-
-	<para>
-		We respect your freedom to choose an operating system for your computer. This section explains how to uninstall Fedora.
-	</para>
-
-	<warning>
-		<title>
-			These instructions may destroy data!
-		</title>
-		<para>
-			If you have data from Fedora that you want to keep, back it up before you proceed. Write your data to CD, DVD, external hard disk, or other storage device. 
-		</para>
-		<para>
-			As a precaution, also back up data from any other operating systems that are installed on the same computer. Mistakes do happen and can result in the loss of all your data.
-		</para>
-		<para>
-			If you back up data from Fedora to be used later in another operating system, make sure that the storage medium or device is readable by that other operating system. For example, without extra third-party software, Microsoft Windows cannot read an external hard drive that you have formatted with Fedora to use the ext2, ext3, or ext4 file system.
-		</para>
-	</warning>
-	
-	<para>
-		To uninstall Fedora from your x86-based system, you must remove the Fedora boot loader information from your master boot record (MBR) and remove any partitions that contain the operating system. The method for removing Fedora from your computer varies, depending on whether Fedora is the only operating system installed on the computer, or whether the computer is configured to dual-boot Fedora and another operating system.
-	</para>
-	
-	<para>
-		These instructions cannot cover every possible computer configuration. If your computer is configured to boot three or more operating systems, or has a highly-customized partition scheme, use the following sections as a general guide to partition removal with the various tools described. In these situations, you will also need to learn to configure your chosen bootloader. See <xref linkend="ch-grub"/> for a general introduction to the subject, but detailed instructions are beyond the scope of this document.
-	</para>
-	
-	<important>
-		<title>Legacy versions of Microsoft operating systems</title>
-		<para>
-			<application>Fdisk</application>, the disk partitioning tool provided with MS-DOS and Microsoft Windows, is unable to remove the file systems used by Fedora. MS-DOS and versions of Windows prior to Windows XP (except for Windows 2000) have no other means of removing or modifying partitions. Refer to <xref linkend="sn-x86-uninstall-legacy" /> for alternative removal methods for use with MS-DOS and these versions of Windows.
-		</para>
-	</important>
-	
-	<xi:include href="X86_Uninstall-single.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
-	
-	<section id="sn-x86-uninstall-dual">
-	<title>Your computer dual-boots Fedora and another operating system</title>
-		<para>
-			If your computer is configured to dual-boot Fedora and another operating system, removing Fedora without removing the partitions containing the other operating system and its data is more complicated. Specific instructions for a number of operating systems are set out below. To keep neither Fedora nor the other operating system, follow the steps described for a computer with only Fedora installed: <xref linkend="sn-x86-uninstall-single" />
-		</para>
-		
-		<section id="sn-x86-uninstall-dual-windows">
-		<title>Your computer dual-boots Fedora and a Microsoft Windows operating system</title>
-			<xi:include href="X86_Uninstall-Windows-2000XP2003.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
-			<xi:include href="X86_Uninstall-Windows-Vista2008.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
-		</section>
-		
-		<xi:include href="X86_Uninstall-Mac.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
-		<!-- Uninstalling if you dual-boot Fedora and another Mac OS X -->
-		
-		<xi:include href="X86_Uninstall-Linux.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
-		<!-- Uninstalling if you dual-boot Fedora and another Linux distro -->
-		
-	</section>
-	
-	<xi:include href="X86_Uninstall-msdos.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
-
-</chapter>
diff --git a/en-US/adminoptions.xml b/en-US/adminoptions.xml
deleted file mode 100644
index b0444e3..0000000
--- a/en-US/adminoptions.xml
+++ /dev/null
@@ -1,905 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-<!DOCTYPE appendix PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
- "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd">
-
-<!-- $Id: -->
-
-<chapter id="ap-admin-options">
-  <title>Boot Options</title>
-  <para>
-    The Fedora installation system includes a range of functions and
-    options for administrators. To use boot options, enter
-    <userinput>linux <replaceable>option</replaceable></userinput> at
-    the
-    <prompt>boot:</prompt>
-    prompt.
-  </para>
-  <para>
-    If you specify more than one option, separate each of the options by
-    a single space. For example:
-  </para>
-<screen><userinput>linux <replaceable>option1</replaceable> <replaceable>option2</replaceable> <replaceable>option3</replaceable></userinput>
-</screen>
-  <note>
-    <title>Anaconda Boot Options</title>
-
-    <para>
-      The anaconda installer has many boot options, most are listed on 
-      the wiki <ulink url="http://fedoraproject.org/wiki/Anaconda/Options"/>.
-    </para>
-  </note>
-  <note>
-    <title>Kernel Boot Options</title>
-
-    <para>
-      The <ulink url="http://fedoraproject.org/wiki/KernelCommonProblems"/> page lists many common kernel boot options.
-      The full list of kernel options is in the file 
-      /usr/share/doc/kernel-doc-<replaceable>version</replaceable>/Documentation/kernel-parameters.txt, 
-      which is installed with the kernel-doc package.
-    </para>
-  </note>
-  <note>
-    <title>Rescue Mode</title>
-
-    <para>
-      The Fedora installation and <firstterm>rescue discs</firstterm> may
-      either boot with <firstterm>rescue mode</firstterm>, or load the
-      installation system. For more information on rescue discs and
-      rescue mode, refer to <xref linkend="sn-mode-rescue"/>.
-    </para>
-  </note>
-  <section id="sn-bootoptions-installer">
-    <title>Configuring the Installation System at the Boot Menu</title>
-
-    <para>
-      You can use the boot menu to specify a number of settings for the
-      installation system, including:
-    </para>
-
-    <itemizedlist>
-      <listitem>
-        <para>
-          language
-        </para>
-      </listitem>
-      <listitem>
-        <para>
-          display resolution
-        </para>
-      </listitem>
-      <listitem>
-        <para>
-          interface type
-        </para>
-      </listitem>
-      <listitem>
-        <para>
-          Installation method
-        </para>
-      </listitem>
-      <listitem>
-        <para>
-          network settings
-        </para>
-      </listitem>
-    </itemizedlist>
-
-    <section id="sn-boot-options-language">
-      <title>Specifying the Language</title>
-
-      <para>
-        To set the language for both the installation process and the
-        final system, specify the ISO code for that language with the
-        <option>lang</option> option. Use the <option>keymap</option>
-        option to configure the correct keyboard layout.
-      </para>
-
-      <para>
-        For example, the ISO codes <userinput>el_GR</userinput> and
-        <userinput>gr</userinput> identify the Greek language and the
-        Greek keyboard layout:
-      </para>
-<screen><userinput>linux lang=<replaceable>el_GR</replaceable> keymap=<replaceable>gr</replaceable></userinput>
-</screen>
-    </section>
-
-    <section id="sn-boot-options-interface">
-      <title>Configuring the Interface</title>
-
-      <para>
-        You may force the installation system to use the lowest possible
-        screen resolution (640x480) with the <option>lowres</option>
-        option. To use a specific display resolution, enter
-        <option>resolution=<replaceable>setting</replaceable></option>
-        as a boot option. For example, to set the display resolution to
-        1024x768, enter:
-      </para>
-<screen><userinput>linux resolution=<replaceable>1024x768</replaceable></userinput>
-</screen>
-      <para>
-        To run the installation process in
-        <indexterm>
-          <primary>text interface</primary>
-        </indexterm>
-        <option>text</option> mode, enter:
-      </para>
-<screen><userinput>linux text</userinput>
-</screen>
-      <para>
-        To enable support for a
-        <indexterm>
-          <primary>serial console</primary>
-        </indexterm>
-        serial console, enter <option>serial</option> as an additional
-        option.
-      </para>
-
-	<para>
-			Use <option>display=<replaceable>ip</replaceable>:0</option> to allow remote display forwarding. In this command, <replaceable>ip</replaceable> should be replaced with the IP address of the system on which you want the display to appear.
-		</para>
-
-		<para>
-			On the system you want the display to appear on, you must execute the command <command>xhost +<replaceable>remotehostname</replaceable></command>, where <replaceable>remotehostname</replaceable> is the name of the host from which you are running the original display. Using the command <command>xhost +<replaceable>remotehostname</replaceable></command> limits access to the remote display terminal and does not allow access from anyone or any system not specifically authorized for remote access.
-		</para>
-
-    </section>
-    
-    <section id="sn-boot-options-update">
-      <title>Updating anaconda</title>
-	<para>
-		You can install Fedora with a newer version of the <application>anaconda</application> installation program than the one supplied on your installation media.
-	</para>
-	<para>
-		The boot option
-	</para>
-<screen><userinput>linux updates</userinput>
-</screen>
-	<para>
-		presents you with a prompt that asks you for a floppy disk containing <application>anaconda</application> updates. You do not need to specify this option if you are performing a network installation and have already placed the updates image contents in <filename>rhupdates/</filename> on the server.
-	</para>
-	<para>
-		To load the <application>anaconda</application> updates from a network location instead, use:
-	</para>
-<screen>
-  <userinput>linux updates=</userinput>
-</screen>
-	<para>
-		followed by the URL for the location where the updates are stored.
-	</para>
-    </section>
-
-    <section id="sn-boot-options-installmethod">
-      <title>Specifying the Installation Method</title>
-
-      <para>
-        Use the <option>askmethod</option> option to display additional
-        menus that enable you to specify the installation method and
-        network settings. You may also configure the installation method
-        and network settings at the
-        <prompt>boot:</prompt>
-        prompt itself.
-      </para>
-
-      <para>
-        To specify the installation method from the
-        <prompt>boot:</prompt>
-        prompt, use the <option>repo</option> option. Refer to
-        <xref linkend="tb-installmethods"/> for the supported
-        installation methods.
-      </para>    
-      <table id="tb-installmethods" frame='all'><title>Installation methods</title>
-	<tgroup cols='2' align='left' colsep='1' rowsep='1'>
-	<colspec colnum="1" colwidth="1*"/>
-        <colspec colnum="2" colwidth="3*"/>
-	  <thead>
-	      <row>
-		<entry>Installation method</entry>
-		<entry>Option format</entry>
-	      </row>
-	  </thead>
-	  <tbody>
-	    <row>
-	      <entry>CD or DVD drive</entry>
-	      <entry><option>repo=cdrom:<replaceable>device</replaceable></option></entry>
-	    </row>
-	    <row>
-	      <entry>Hard Drive</entry>
-	      <entry><option>repo=hd:<replaceable>device</replaceable>/<replaceable>path</replaceable></option></entry>
-	    </row>
-	    <row>
-	      <entry>HTTP Server</entry>
-	      <entry><option>repo=http://<replaceable>host</replaceable>/<replaceable>path</replaceable></option></entry>
-	    </row>
-	    <row>
-	      <entry>FTP Server</entry>
-	      <entry><option>repo=ftp://<replaceable>username</replaceable>:<replaceable>password</replaceable>@<replaceable>host</replaceable>/<replaceable>path</replaceable></option></entry>
-	    </row>
-	    <row>
-	      <entry>NFS Server</entry>
-	      <entry><option>repo=nfs:<replaceable>server</replaceable>:/<replaceable>path</replaceable></option></entry>
-	    </row>
-	    <row>
-	      <entry>ISO images on an NFS Server</entry>
-	      <entry><option>repo=nfsiso:<replaceable>server</replaceable>:/<replaceable>path</replaceable></option></entry>
-	    </row>
-	  </tbody>
-	</tgroup>
-      </table>
-    </section>
-    <section id="sn-boot-options-network">
-      <title>Manually Configuring the Network Settings</title>
-      <para>
-        By default, the installation system uses DHCP to automatically
-        obtain the correct network settings. To manually configure the
-        network settings yourself, either enter them in the
-        <guilabel>Configure TCP/IP</guilabel> screen, or at the
-        <prompt>boot:</prompt>
-        prompt. You may specify the <option>ip</option> address,
-        <option>netmask</option>, <option>gateway</option>, and
-        <option>dns</option> server settings for the installation system
-        at the prompt. If you specify the network configuration at the
-        <prompt>boot:</prompt>
-        prompt, these settings are used for the installation process,
-        and the <guilabel>Configure TCP/IP</guilabel> screen does not
-        appear.
-      </para>
-
-      <para>
-        This example configures the network settings for an installation
-        system that uses the IP address
-        <systemitem class="ipaddress">192.168.1.10</systemitem>:
-      </para>
-<screen><userinput>linux ip=<replaceable>192.168.1.10</replaceable> netmask=<replaceable>255.255.255.0</replaceable> gateway=<replaceable>192.168.1.1</replaceable> dns=<replaceable>192.168.1.2,192.168.1.3</replaceable></userinput>
-</screen>
-      <!-- <note>
-        <title>Configuring the Installed System</title>
-
-        <para>
-          Use the Network Configuration screen to specify the network
-          settings for the new system. Refer to
-          <xref linkend="sn-networkconfig-fedora_manual-configuration"/> for more information on
-          configuring the network settings for the installed system.
-        </para>
-      </note> -->
-    </section>
-  </section>
-  <section id="sn-remoteaccess-installation">
-    <title>Enabling Remote Access to the Installation System</title>
-<!-- SE: Note that there is also a "display" option that redirects anaconda's X display to an X server on another system. -->
-    <para>
-      You may access either graphical or text interfaces for the
-      installation system from any other system. Access to a text mode
-      display requires <application>telnet</application>, which is installed by default on Fedora systems. To remotely access the graphical display
-      of an installation system, use client software that supports the
-      <indexterm>
-        <primary>VNC (Virtual Network Computing)</primary>
-      </indexterm>
-      VNC (Virtual Network Computing) display protocol. A number of
-      providers offer VNC clients for Microsoft Windows and Mac OS, as
-      well as UNIX-based systems.
-    </para>
-    <note>
-      <title>Installing a VNC Client on Fedora</title>
-      <para>
-        <indexterm>
-          <primary>VNC (Virtual Network Computing)</primary>
-          <secondary>installing client</secondary>
-        </indexterm>
-        Fedora includes the VNC client <application>vncviewer</application>. To obtain
-        <application>vncviewer</application>, install the
-        <package>tigervnc</package> package.
-      </para>
-    </note>
-    <para>
-      The installation system supports two methods of establishing a VNC
-      connection. You may start the installation, and manually login to
-      the graphical display with a VNC client on another system.
-      Alternatively, you may configure the installation system to
-      automatically connect to a VNC client on the network that is
-      running in <firstterm>listening mode</firstterm>.
-    </para>
-
-    <section id="sn-remoteaccess-installation-vnc">
-      <title>Enabling Remote Access with VNC</title>
-
-      <para>
-        <indexterm>
-          <primary>VNC (Virtual Network Computing)</primary>
-          <secondary>enabling</secondary>
-        </indexterm>
-        To enable remote graphical access to the installation system,
-        enter two options at the prompt:
-      </para>
-<screen><userinput>linux vnc vncpassword=<replaceable>qwerty</replaceable></userinput>
-</screen>
-      <para>
-        The <option>vnc</option> option enables the VNC service. The
-        <option>vncpassword</option> option sets a password for remote
-        access. The example shown above sets the password as
-        <userinput>qwerty</userinput>.
-      </para>
-
-      <note>
-        <title>VNC Passwords</title>
-
-        <para>
-          The VNC password must be at least six characters long.
-        </para>
-      </note>
-
-      <para>
-        Specify the language, keyboard layout and network settings for
-        the installation system with the screens that follow. You may
-        then access the graphical interface through a VNC client. The
-        installation system displays the correct connection setting for
-        the VNC client:
-      </para>
-<screen>Starting VNC...
-The VNC server is now running.
-Please connect to computer.mydomain.com:1 to begin the install...
-Starting graphical installation...
-Press &lt;enter&gt; for a shell</screen>
-      <para>
-        You may then login to the installation system with a VNC client.
-        To run the <application>vncviewer</application> client on Fedora,
-        choose <menuchoice> <guimenu>Applications</guimenu>
-        <guisubmenu>Accessories</guisubmenu><guimenuitem>VNC
-        Viewer</guimenuitem></menuchoice>, or type the command
-        <application>vncviewer</application> in a terminal window. Enter
-        the server and display number in the <guilabel>VNC
-        Server</guilabel> dialog. For the example above, the
-        <guilabel>VNC Server</guilabel> is
-        <userinput>computer.mydomain.com:1</userinput>.
-      </para>
-    </section>
-
-    <section id="sn-remoteaccess-installation-vnclistener">
-      <title>Connecting the Installation System to a VNC Listener</title>
-
-      <para>
-        To have the installation system automatically connect to a VNC
-        client, first start the client in
-        <indexterm>
-          <primary>VNC (Virtual Network Computing)</primary>
-          <secondary>listening mode</secondary>
-        </indexterm>
-        listening mode. On Fedora systems, use the
-        <option>-listen</option> option to run
-        <application>vncviewer</application> as a listener. In a
-        terminal window, enter the command:
-      </para>
-<screen><userinput>vncviewer -listen</userinput>
-</screen>
-      <note>
-        <title>Firewall Reconfiguration Required</title>
-
-        <para>
-          By default, <application>vncviewer</application> uses TCP port
-          5500 when in listening mode. To permit connections to this
-          port from other systems, choose <menuchoice>
-          <guimenu>System</guimenu>
-          <guisubmenu>Administration</guisubmenu> <guimenuitem>
-          Firewall</guimenuitem> </menuchoice>. Select
-          <guilabel>Other ports</guilabel>, and
-          <guibutton>Add</guibutton>. Enter <userinput>5500</userinput>
-          in the <guilabel>Port(s)</guilabel> field, and specify
-          <userinput>tcp</userinput> as the
-          <guilabel>Protocol</guilabel>.
-        </para>
-      </note>
-
-      <para>
-        Once the listening client is active, start the installation
-        system and set the VNC options at the
-        <prompt>boot:</prompt>
-        prompt. In addition to <option>vnc</option> and
-        <option>vncpassword</option> options, use the
-        <option>vncconnect</option> option to specify the name or IP
-        address of the system that has the listening client. To specify
-        the TCP port for the listener, add a colon and the port number
-        to the name of the system.
-      </para>
-
-      <para>
-        For example, to connect to a VNC client on the system
-        <systemitem
-	class="systemname">desktop.mydomain.com</systemitem>
-        on the port 5500, enter the following at the
-        <prompt>boot:</prompt>
-        prompt:
-      </para>
-<screen><userinput>linux vnc vncpassword=<replaceable>qwerty</replaceable> vncconnect=<replaceable>desktop.mydomain.com:5500</replaceable></userinput>
-</screen>
-    </section>
-
-    <section id="sn-telnet-installation">
-      <title>Enabling Remote Access with Telnet</title>
-
-      <para>
-        To enable remote access to a text mode installation, use the
-        <indexterm>
-          <primary>Telnet</primary>
-        </indexterm>
-        <option>telnet</option> option at the
-        <prompt>boot:</prompt>
-        prompt:
-      </para>
-<!--SE: The "text" option is necessary to stop the installer switching to graphical mode and losing the telnet interface. This is expected behavior. -->
-<screen><userinput>linux text telnet</userinput>
-</screen>
-      <para>
-        You may then connect to the installation system with the
-        <command>telnet</command> utility. The <command>telnet</command>
-        command requires the name or IP address of the installation
-        system:
-      </para>
-<screen><userinput>telnet computer.mydomain.com</userinput>
-</screen>
-      <warning>
-        <title>Telnet Access Requires No Password</title>
-
-        <para>
-          To ensure the security of the installation process, only use
-          the <option>telnet</option> option to install systems on
-          networks with restricted access.
-        </para>
-      </warning>
-    </section>
-  </section>
-  <section id="sn-remote-logging">
-    <title>Logging to a Remote System During the Installation</title>
-
-    <para>
-      By default, the installation process sends log messages to the
-      console as they are generated. You may specify that these messages
-      go to a remote system that runs a
-      <indexterm>
-        <primary>syslog</primary>
-      </indexterm>
-      <firstterm>syslog</firstterm> service.
-    </para>
-
-    <para>
-      To configure remote logging, add the <option>syslog</option>
-      option. Specify the IP address of the logging system, and the UDP
-      port number of the log service on that system. By default, syslog
-      services that accept remote messages listen on UDP port 514.
-    </para>
-
-    <para>
-      For example, to connect to a syslog service on the system
-      <systemitem
-	class="ipaddress">192.168.1.20</systemitem>, enter
-      the following at the
-      <prompt>boot:</prompt>
-      prompt:
-    </para>
-<screen><userinput>linux syslog=<replaceable>192.168.1.20:514</replaceable></userinput>
-</screen>
-    <section id="sn-remote-logging-logserver">
-      <title>Configuring a Log Server</title>
-
-      <para>
-        Fedora uses <command>rsyslog</command> to provide a syslog
-        service. The default configuration of <command>rsyslog</command>
-        rejects messages from remote systems.
-      </para>
-
-      <warning>
-        <title>Only Enable Remote Syslog Access on Secured Networks</title>
-
-        <para>
-          The <command>rsyslog</command> configuration detailed below 
-          does not make use of any of the security measures available
-          in <command>rsyslog</command> Crackers may slow or crash systems 
-          that permit access to the logging service, by sending large 
-          quantities of false log messages. In addition, hostile users may 
-          intercept or falsify messages sent to the logging service over the
-          network.
-        </para>
-      </warning>
-
-      <para>
-        To configure a Fedora system to accept log messages from other
-        systems on the network, edit the file
-        <filename>/etc/rsyslog.conf</filename>. You must use
-        <systemitem class="username">root</systemitem> privileges to
-        edit the file <filename>/etc/rsyslog.conf</filename>. Uncomment the
-	following lines by removing the hash preceding them:</para>
-<screen><computeroutput>$ModLoad imudp.so</computeroutput> 
-<computeroutput>$UDPServerRun 514</computeroutput></screen>
-      <para>
-        Restart the <command>rsyslog</command> service to apply the
-        change:
-      </para>
-<screen><userinput>su -c '/sbin/service rsyslog restart'</userinput>
-</screen>
-      <para>
-        Enter the <systemitem class="username">root</systemitem>
-        password when prompted.
-      </para>
-
-      <note>
-        <title>Firewall Reconfiguration Required</title>
-
-        <para>
-          By default, the syslog service listens on UDP port 514. To
-          permit connections to this port from other systems, choose
-          <menuchoice> <guimenu>System</guimenu>
-          <guisubmenu>Administration</guisubmenu> <guimenuitem>
-          Firewall</guimenuitem> </menuchoice>. Select
-          <guilabel>Other ports</guilabel>, and
-          <guibutton>Add</guibutton>. Enter <userinput>514</userinput>
-          in the <guilabel>Port(s)</guilabel> field, and specify
-          <userinput>udp</userinput> as the
-          <guilabel>Protocol</guilabel>.
-        </para>
-      </note>
-    </section>
-  </section>
-  <section id="sn-automating-installation">
-    <title>Automating the Installation with Kickstart</title>
-
-    <para>
-      A
-      <indexterm>
-        <primary>Kickstart</primary>
-      </indexterm>
-      <firstterm>Kickstart</firstterm> file specifies settings for an
-      installation. Once the installation system boots, it can read a
-      Kickstart file and carry out the installation process without any
-      further input from a user.
-    </para>
-    <note>
-      <title>Every Installation Produces a Kickstart File</title>
-      <para>
-        The Fedora installation process automatically writes a Kickstart
-        file that contains the settings for the installed system. This
-        file is always saved as
-        <filename>/root/anaconda-ks.cfg</filename>. You may use this
-        file to repeat the installation with identical settings, or
-        modify copies to specify settings for other systems.
-      </para>
-    </note>
-	    <xi:include href="Important-Kickstart_and_Firstboot.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> 
-    <para>
-      Fedora includes a graphical application to create and modify
-      Kickstart files by selecting the options that you require. Use the
-      package <filename>system-config-kickstart</filename> to install
-      this utility. To load the Fedora Kickstart editor, choose
-      <menuchoice> <guimenu>Applications</guimenu> <guisubmenu>System
-      Tools</guisubmenu><guimenuitem>Kickstart</guimenuitem></menuchoice>.
-    </para>
-
-    <para>
-      Kickstart files list installation settings in plain text, with one
-      option per line. This format lets you modify your Kickstart files
-      with any text editor, and write scripts or applications that
-      generate custom Kickstart files for your systems.
-    </para>
-
-    <para>
-      To automate the installation process with a Kickstart file, use
-      the <option>ks</option> option to specify the name and location of
-      the file:
-    </para>
-<screen><userinput>linux ks=<replaceable>location/kickstart-file.cfg</replaceable></userinput>
-</screen>
-    <para>
-      You may use Kickstart files that are held on either removable
-      storage, a hard drive, or a network server. Refer to
-      <xref linkend="tb-kssources"/> for the supported Kickstart
-      sources.
-    </para>
-    
-    <table id="tb-kssources" frame='all'><title>Kickstart sources</title>
-	<tgroup cols='2' align='left' colsep='1' rowsep='1'>
-	<colspec colnum="1" colwidth="1*"/>
-        <colspec colnum="2" colwidth="3*"/>
-	  <thead>
-	      <row>
-		<entry>Kickstart source</entry>
-		<entry>Option format</entry>
-	      </row>
-	  </thead>
-	  <tbody>
-	      <row>
-		<entry>CD or DVD drive</entry>
-		<entry><option>ks=<replaceable>cdrom:/directory/ks.cfg</replaceable></option></entry>
-	      </row>
-	      <row>
-		<entry>Hard Drive</entry>
-		<entry><option>ks=<replaceable>hd:/device/directory/ks.cfg</replaceable></option></entry>
-	      </row>
-	      <row>
-		<entry>Other Device</entry>
-		<entry><option>ks=<replaceable>file:/device/directory/ks.cfg</replaceable></option></entry>
-	      </row>
-	      <row>
-		<entry>HTTP Server</entry>
-		<entry><option>ks=<replaceable>http://server.mydomain.com/directory/ks.cfg</replaceable></option></entry>
-	      </row>
-	      <row>
-		<entry>FTP Server</entry>
-		<entry><option>ks=<replaceable>ftp://server.mydomain.com/directory/ks.cfg</replaceable></option></entry>
-	      </row>
-	      <row>
-		<entry>NFS Server</entry>
-		<entry><option>ks=<replaceable>nfs:server.mydomain.com:/directory/ks.cfg</replaceable></option></entry>
-	      </row>
-	    </tbody>
-	</tgroup>
-    </table>
-    <para>
-      To obtain a Kickstart file from a script or application on a Web
-      server, specify the URL of the application with the
-      <option>ks=</option> option. If you add the option
-      <option>kssendmac</option>, the request also sends HTTP headers to
-      the Web application. Your application can use these headers to
-      identify the computer. This line sends a request with headers to
-      the application
-      <wordasword>http://server.mydomain.com/kickstart.cgi</wordasword>:
-    </para>
-<screen><userinput>linux ks=http://server.mydomain.com/kickstart.cgi kssendmac</userinput>
-</screen>
-  </section>
-  <section id="sn-bootoptions-hardware">
-    <title>Enhancing Hardware Support</title>
-
-    <para>
-      By default, Fedora attempts to automatically detect and configure
-      support for all of the components of your computer. Fedora supports
-      the majority of hardware in common use with the software
-      <firstterm>drivers</firstterm> that are included with the
-      operating system. To support other devices you may supply
-      additional drivers during the installation process, or at a later
-      time.
-    </para>
-
-    <section id="sn-bootoptions-hwdetection">
-      <title>Overriding Automatic Hardware Detection</title>
-
-      <para>
-        For some models of device automatic hardware configuration may
-        fail, or cause instability. In these cases, you may need to
-        disable automatic configuration for that type of device, and
-        take additional steps to manually configure the device after the
-        installation process is complete.
-      </para>
-      <note>
-        <title>Check the Release Notes</title>
-        <para>
-          Refer to the Release Notes for information on known issues
-          with specific devices.
-        </para>
-      </note>
-      <para>
-        To override the automatic hardware detection, use one or more of
-        the following options:
-      </para>
-
-      <table id="tb-hardwareoptions" frame='all'><title>Hardware Options</title>
-	<tgroup cols='2' align='left' colsep='1' rowsep='1'>
-	<colspec colnum="1" colwidth="3*"/>
-        <colspec colnum="2" colwidth="2*"/>
-	  <thead>
-	      <row>
-		<entry>Compatibility</entry>
-		<entry>Option</entry>
-	      </row>
-	  </thead>
-	  <tbody>
-	      <row>
-		<entry>Disable all hardware detection</entry>
-		<entry><option>noprobe</option></entry>
-	      </row>
-	      <row>
-		<entry>Disable graphics, keyboard, and mouse detection</entry>
-		<entry><option>headless</option></entry>
-	      </row>
-	      <row>
-		<entry>Disable passing keyboard and mouse information to stage 2 of the installation program</entry>
-		<entry><option>nopass</option></entry>
-	      </row>
-	      <row>
-		<entry>Use basic VESA driver for video</entry>
-		<entry><option>xdriver=vesa</option></entry>
-	      </row>
-	      <row>
-		<entry>Disable shell access on virtual console 2 during installation</entry>
-		<entry><option>noshell</option></entry>
-	      </row>
-	      <row>
-		<entry>Disable advanced configuration and power interface (ACPI)</entry>
-		<entry><option>acpi=off</option></entry>
-	      </row>
-	      <row>
-		<entry>Disable machine check exception (MCE) CPU self-diagnosis.</entry>
-		<entry><option>nomce</option></entry>
-	      </row>
-	      <row>
-		<entry>Disable non-uniform menory access on the AMD64 architecture</entry>
-		<entry><option>numa-off</option></entry>
-	      </row>
-	      <row>
-		<entry>Force kernel to detect a specific amount of memory, where <replaceable>xxx</replaceable> is a value in megabytes</entry>
-		<entry><option>mem=<replaceable>xxx</replaceable>m</option></entry>
-	      </row>
-	      <row>
-		<entry>Enable DMA only for IDE and SATA drives</entry>
-		<entry><option>libata.dma=1</option></entry>
-	      </row>
-	      <row>
-		<entry>Disable BIOS-assisted RAID</entry>
-		<entry><option>nodmraid</option></entry>
-	      </row>
-	      <row>
-		<entry>Disable Firewire device detection</entry>
-		<entry><option>nofirewire</option></entry>
-	      </row>
-	      <row>
-		<entry>Disable parallel port detection</entry>
-		<entry><option>noparport</option></entry>
-	      </row>
-	      <row>
-		<entry>Disable PC Card (PCMCIA) device detection</entry>
-		<entry><option>nopcmcia</option></entry>
-	      </row>
-	      <row>
-		<entry>Disable USB storage device detection</entry>
-		<entry><option>nousbstorage</option></entry>
-	      </row>
-	      <row>
-		<entry>Disable all USB device detection</entry>
-		<entry><option>nousb</option></entry>
-	      </row> 
-	      <row>
-		<entry>Disable all probing of network hardware</entry>
-		<entry><option>nonet</option></entry>
-	      </row>
-	    </tbody>
-	  </tgroup>
-      </table>
-      <note>
-        <title>Additional Screen</title>
-
-        <para>
-          The <option>isa</option> option causes the system to display
-          an additional text screen at the beginning of the installation
-          process. Use this screen to configure the ISA devices on your
-          computer.
-        </para>
-      </note>
-      
-      <important>
-	      <para>
-		      Other kernel boot options have no particular meaning for <application>anaconda</application> and do not affect the installation process. However, if you use these options to boot the installation system, <application>anaconda</application> will preserve them in the bootloader configuration.
-	      </para>
-      </important>
-      
-    </section>
-  </section>
-
-  <section id="sn-boot-modes">
-    <title>Using the Maintenance Boot Modes</title>
-
-    <section id="sn-memtest">
-      <title>Loading the Memory (RAM) Testing Mode</title>
-
-      <para>
-        Faults in memory modules may cause your system to freeze or
-        crash unpredictably. In some cases, memory faults may only cause
-        errors with particular combinations of software. For this
-        reason, you should test the memory of a computer before you
-        install Fedora for the first time, even if it has previously run
-        other operating systems.
-      </para>
-
-      <para>
-        Fedora includes the <application>Memtest86+</application>
-	memory testing application.  To boot your computer in
-        <indexterm>
-          <primary>memory testing mode</primary>
-        </indexterm> memory testing mode, choose <guimenuitem>Memory
-	  test</guimenuitem> at the boot menu. The first test starts
-	immediately. By default, <application>Memtest86+</application>
-	carries out a total of ten tests.
-      </para>
-      
-	<para>
-		In most cases, a single successful pass with <application>Memtest86+</application> is sufficient to verify that your RAM is in good condition. In some rare circumstances, however, errors that went undetected on the first pass might appear on subsequent passes. To perform a thorough test of the RAM on an important system, leave <application>Memtest86+</application> running overnight or for a few days.
-	</para>
-	<para>
-		For more information on using <application>Memtest86+</application>, refer to the <citetitle>Memtest86+ FAQ</citetitle> available at <ulink url="http://forum.canardpc.com/showthread.php?t=28864"></ulink>.
-	</para>
-      <para>
-        To halt the tests and reboot your computer, enter
-        <keycap>Esc</keycap> at any time.
-      </para>
-    </section>
-    
-    <section id="sn-boot-mediacheck">
-    <title>Verifying boot media</title>
-	    <para>
-		    You can test the integrity of an ISO-based installation source before using it to install Fedora. These sources include CD, DVD, and ISO images stored on a local hard drive or on an NFS server. Verifying that the ISO images are instace before you attempt an installation helps to avoid problems that are often encountered during installation.
-	    </para>
-	    <para>
-		    Fedora offers you three ways to test installation ISOs:
-	    </para>
-	    <itemizedlist>
-		    <listitem>
-			    <para>
-				    select the <guilabel>Verify and Boot</guilabel> option on the Fedora Live CD. To access the Live CD boot menu, press any key within ten seconds of the splash screen appearing.
-			    </para>
-		    </listitem>
-		    <listitem>
-			    <para>
-				    select <guilabel>OK</guilabel> at the prompt to test the media before installation when booting from the Fedora distribution CD set or DVD
-			    </para>
-		    </listitem>
-		    <listitem>
-			    <para>
-				    boot Fedora with the option <option>mediacheck</option> option.
-			    </para>
-		    </listitem>
-	    </itemizedlist>
-    </section>
-
-    <section id="sn-mode-rescue">
-      <title>Booting Your Computer with the Rescue Mode</title>
-      <indexterm>
-        <primary>rescue mode</primary>
-      </indexterm>
-      <para>
-        You may boot a command-line Linux system from either a
-        <indexterm>
-          <primary>rescue discs</primary>
-        </indexterm>
-        rescue disc or an installation disc, without installing
-        Fedora on the computer. This enables you to use the utilities and
-        functions of a running Linux system to modify or repair systems
-        that are already installed on your computer.
-      </para>
-
-      <para>
-        The rescue disc starts the rescue mode system by default. To
-	load the rescue system with the installation disc, choose
-	<guimenuitem>Rescue installed system</guimenuitem> from the boot
-	menu.
-      </para>
-      <para>
-        Specify the language, keyboard layout and network settings for
-        the rescue system with the screens that follow. The final setup
-        screen configures access to the existing system on your
-        computer.
-      </para>
-
-      <para>
-        By default, rescue mode attaches an existing operating system to
-        the rescue system under the directory
-        <filename>/mnt/sysimage/</filename>.
-      </para>
-    </section>
-    
-    <section id="sn-mode-upgradeany">
-      <title>Upgrading your computer</title>
-    
-	  <para>
-		A previous boot option, <option>upgrade</option>, has been superceded by a stage in the installation process where the installation program prompts you to upgrade or reinstall earlier versions of Fedora that it detects on your system. 
-	  </para>
-	  
-	  <para>
-		However, the installation program may not correctly detect a previous version of Fedora if the contents of the <filename>/etc/fedora-release</filename> file have changed. The boot option <option>upgradeany</option> relaxes the test that the installation program performs and allows you to upgrade a Fedora installation that the installation program has not correctly identified.
-	  </para>
-    
-    </section>
-  </section>
-
-</chapter>
-
-<!--
-Local variables:
-mode: xml
-fill-column: 72
-End:
--->
diff --git a/en-US/expert-quickstart.xml b/en-US/expert-quickstart.xml
deleted file mode 100644
index 0e1435a..0000000
--- a/en-US/expert-quickstart.xml
+++ /dev/null
@@ -1,137 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
-"http://www.docbook.org/xml/4.4/docbookx.dtd">
-
-<chapter id="ch-experts-quickstart">
-  <title>Quick Start for Experts</title>
-  <para>This section offers a very brief overview of installation tasks
-    for experienced readers who are eager to get started. Note that many
-    explanatory notes and helpful hints appear in the following chapters
-    of this guide. If an issue arises during the installation process,
-    consult the appropriate chapters in the full guide for help.</para>
-  <warning>
-    <title>Experts Only</title>
-    <para>This section is intended only for experts. Other readers may
-      not be familiar with some of the terms in this section, and should
-      move on to <xref linkend="ch-new-users"/> instead.</para>
-  </warning>
-  <section id="sn-expert-overview">
-    <title>Overview</title>
-    <para>The installation procedure is fairly simple, and consists of
-      only a few steps:</para>
-    <orderedlist>
-      <listitem>
-	<para>Download files to make media or another bootable
-	  configuration.</para>
-      </listitem>
-      <listitem>
-	<para>Prepare system for installation.</para>
-      </listitem>
-      <listitem>
-	<para>Boot the computer and run the installation process.</para>
-      </listitem>
-      <listitem>
-	<para>Reboot and perform post-installation configuration.</para>
-      </listitem>
-    </orderedlist>
-  </section>
-  <section id="sn-expert-download">
-    <title>Download Files</title>
-    <para>Do any one of the following:</para>
-    <note>
-      <title>Verify your downloads</title>
-      <para>Downloads may fail for any number of reasons.  Always verify
-      the sha256sum of the downloaded files.</para>
-    </note>
-    <orderedlist>
-      <listitem>
-	<indexterm>
-	  <primary>ISO images</primary>
-	  <secondary>downloading</secondary>
-	</indexterm>
-	<para>Download the ISO image for a Live image. Create CD media
-	  from the ISO file using your preferred application.  You may
-	  also use the <package>livecd-tools</package> package to write
-	  the image to other bootable media such as a USB flash disk.
-	  To install the distribution to your hard disk, use the
-	  shortcut on the desktop after you log in.</para>
-      </listitem>
-      <listitem>
-	<para>Download the ISO images for the full distribution on CD or
-	  DVD. Create CD or DVD media from the ISO files using your
-	  preferred application, or put the images on a Windows FAT32 or
-	  Linux ext2/ext3 partition.</para>
-      </listitem>
-      <listitem>
-	<para>Download the <filename>boot.iso</filename> image for a
-	minimal boot CD or USB flash drive. Write the image to the
-	approriate physical media to create bootable media.  The boot
-	media contains no packages but must be pointed at a hard disk or
-	online repository to complete the installation.</para>
-      </listitem>
-      <listitem>
-	<para>Download the <filename>netinst.iso</filename> image for
-	  a reduced-size boot CD.  Write the image to the appropriate
-	  physical media to create bootable media.</para>
-      </listitem>
-      <listitem>
-	<para>Download the <filename>vmlinuz</filename> kernel file and
-	  the <filename>initrd.img</filename> ramdisk image from the
-	  distribution's <filename
-	    class="directory">isolinux/</filename> directory. Configure
-	  your operating system to boot the kernel and load the ramdisk
-	  image.  For further information on installation without media,
-	  refer to <xref linkend="ap-medialess-install"/>.</para>
-	<para>For information on setting up a network boot server from
-	  which you can install Fedora, refer to <xref
-	    linkend="ap-install-server"/>.</para>
-      </listitem>
-    </orderedlist>
-    <para>
-	To learn how to turn ISO images into CD or DVD media, refer to <citetitle>Making Fedora Discs</citetitle> available from 
-	<ulink
-	url="http://docs.fedoraproject.org/readme-burning-isos/"/>.</para>
-  </section>
-  <section id="sn-expert-prepare">
-    <title>Prepare for Installation</title>
-    <indexterm>
-      <primary>NTFS partitions</primary>
-      <secondary>resizing</secondary>
-    </indexterm>
-    <para>Back up any user data you need to preserve.</para>
-		<note>
-			<title>Resizing Partitions</title>
-			<para>The installation program provides functions for resizing
-			ext2, ext3, ext4, and NTFS formatted partitions.  Refer to <xref
-			linkend="s1-diskpartitioning-x86" /> for more information.</para>
-		</note>
-  </section>
-  <section id="sn-expert-install">
-    <title>Install Fedora</title>
-    <para>Boot from the desired media, with any options appropriate for
-      your hardware and installation mode. Refer to <xref
-    linkend="ap-admin-options"/> for more information about boot
-      options.  If you boot from the Live CD, select the "Install to
-      Hard Disk" option from the desktop to run the installation program.
-      If you boot from minimal media or a downloaded kernel, select a
-      network or hard disk resource from which to install.</para>
-    <para>Proceed through all the steps of the installation program. The
-      installation program does not change your system until you make a
-      final confirmation to proceed. When installation is finished,
-      reboot your system.</para>
-  </section>
-  <section id="sn-expert-post-install">
-    <title>Perform Post-installation Steps</title>
-    <para>After the system reboots, it displays additional configuration
-      options. Make appropriate changes to your system and proceed to
-      the login prompt.</para>
-    <para>Refer to <xref linkend="ch-firstboot"/> or the Firstboot page on the Fedora wiki: <ulink url="http://fedoraproject.org/wiki/FirstBoot"/> for more detail.</para>
-  </section>
-</chapter>
-
-<!--
-Local variables:
-mode: xml
-fill-column: 72
-End:
--->
diff --git a/en-US/ext4-and-btrfs.xml b/en-US/ext4-and-btrfs.xml
deleted file mode 100644
index 1f24f0c..0000000
--- a/en-US/ext4-and-btrfs.xml
+++ /dev/null
@@ -1,11 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-
-<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
- "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd">
-
-<important>
-	<title>Btrfs</title>
-		<para>
-			  The <application>GRUB</application> bootloader does not support the Btrfs file system. You cannot use a btrfs partition for <filename>/boot</filename>.
-		</para>
-</important>
diff --git a/en-US/firstboot.xml b/en-US/firstboot.xml
deleted file mode 100644
index 4626582..0000000
--- a/en-US/firstboot.xml
+++ /dev/null
@@ -1,198 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-
-<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
- "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd">
-
-<!-- $Id: -->
-
-<chapter id="ch-firstboot">
-  <title>Firstboot</title>
-  <indexterm>
-    <primary>Firstboot</primary>
-  </indexterm>
-  <para>
-    <application>Firstboot</application> launches the first time
-    that you start a new Fedora system. Use <application>Firstboot</application> to configure the system for use before you log
-    in.
-  </para>
-  
-<figure float="0"><title>Firstboot welcome screen</title>
-	<mediaobject>
-		<imageobject><imagedata fileref="images/firstboot/fb-welcome.png" format="PNG"/></imageobject>
-		<textobject><para>
-				Firstboot welcome screen
-			</para>
-		</textobject>
-	</mediaobject>
-</figure>
-  
-  <para>
-    Select <guibutton>Forward</guibutton> to start 
-    <application>Firstboot</application>.
-  </para>
-  <note>
-    <title>Graphical Interface Required</title>
-
-    <para>
-      <application>Firstboot</application> requires a graphical
-      interface.  If you did not install one, or if Fedora has trouble
-      starting it, you may see a slightly different setup screen.
-    </para>
-  </note>
-  <section id="sn-firstboot-license">
-    <title>License Agreement</title>
-
-    <para>
-      This screen displays the overall licensing terms for
-      Fedora. Each software package in Fedora is covered by its own
-      license.  All licensing guidelines for Fedora are located at
-      <ulink url="http://fedoraproject.org/wiki/Legal/Licenses"/>.
-    </para>
-
-<figure float="0"><title>Firstboot license screen</title>
-	<mediaobject>
-		<imageobject><imagedata fileref="images/firstboot/fb-license.png" format="PNG"/></imageobject>
-		<textobject><para>
-				Firstboot license screen
-			</para>
-		</textobject>
-	</mediaobject>
-</figure>
-
-
-    <para>
-      If you agree to the terms of the licence, select <guibutton>Forward</guibutton>.
-    </para>
-  </section>
-  <section id="sn-firstboot-systemuser">
-    <title>System User</title>
-
-    <para>
-      Create a user account for yourself with this screen. Always use
-      this account to log in to your Fedora system, rather than using the
-      <systemitem class="username">root</systemitem> account.
-    </para>
-    
-<figure float="0"><title>Firstboot create user screen</title>
-	<mediaobject>
-		<imageobject><imagedata fileref="images/firstboot/fb-createuser.png" format="PNG"/></imageobject>
-		<textobject><para>
-				Firstboot create user screen
-			</para>
-		</textobject>
-	</mediaobject>
-</figure>
-
-    
-    <para>
-      Enter a user name and your full name, and then enter your chosen
-      password. Type your password once more in the <guilabel>Confirm
-      Password</guilabel> box to ensure that it is correct. Refer to
-      <xref linkend="sn-account_configuration" /> for guidelines on selecting a
-      secure password.
-    </para>
-    <para>
-      To configure Fedora to use network services for authentication or
-      user information, select <guibutton>Use Network
-      Login...</guibutton>.
-    </para>
-    <important>
-      <title>Create at least one user account</title>
-      <para>
-      If you do not create at least one user account in this step, you will not be able to log in to the Fedora graphical environment. If you skipped this step during installation, refer to <xref linkend="Trouble_After_Booting-GUI"/>.
-      </para>
-    </important>
-    <note>
-      <title>Creating Extra User Accounts</title>
-      <para>
-        To add additional user accounts to your system after the
-        installation is complete, choose <menuchoice>
-        <guimenu>System</guimenu>
-        <guisubmenu>Administration</guisubmenu> <guimenuitem>Users &amp;
-        Groups</guimenuitem> </menuchoice>.
-      </para>
-    </note>
-  </section>
-  
-<section id="sn-firstboot-datetime">
-    <title>Date and Time</title>
-    
-    <indexterm>
-        <primary>NTP (Network Time Protocol)</primary>
-      </indexterm>
-
-    <para>
-      Use this screen to adjust the date and time of the system clock. To change these settings after installation, click <menuchoice> <guimenu>System</guimenu> <guisubmenu>Administration</guisubmenu> <guimenuitem>Date &amp; Time</guimenuitem> </menuchoice>.
-    </para>
-    
-    
-
-<!--     <para>
-      The initial display enables you to set the date and time of your
-      system manually.
-    </para> -->
-    
-<figure float="0"><title>Firstboot date and time screen</title>
-	<mediaobject>
-		<imageobject><imagedata fileref="images/firstboot/fb-datetime.png" format="PNG"/></imageobject>
-		<textobject><para>
-				Firstboot date and time screen
-			</para>
-		</textobject>
-	</mediaobject>
-</figure>
-
-<para>
-      Click the <guilabel>Synchronize date and time over the network</guilabel> checkbox to configure your system to use <firstterm>Network Time Protocol</firstterm> (NTP) servers to maintain the accuracy of the clock. NTP provides time synchronization service to computers on the same network. Many public NTP servers are available on the Internet.
-    </para>
-
-    
-
-  </section>
-  
-  <section id="sn-smolt">
-    <title>Hardware Profile</title>
-    <para>
-      <application>Firstboot</application> displays a screen that
-      allows you to submit your hardware information anonymously to the
-      Fedora Project.  Developers use these hardware details to guide further
-      support efforts.  You can read more about this project and its
-      development at <ulink url="http://smolts.org/"/>.
-    </para>
-    
-<figure float="0"><title>Firstboot hardware profile screen</title>
-	<mediaobject>
-		<imageobject><imagedata fileref="images/firstboot/fb-profile.png" format="PNG"/></imageobject>
-		<textobject><para>
-				Firstboot hardware profile screen
-			</para>
-		</textobject>
-	</mediaobject>
-</figure>
-
-    
-    <para>
-      To opt in to this important work, select <guilabel>Send
-      Profile</guilabel>.  If you choose not to submit any profile data,
-      do not change the default.  Select <guilabel>Finish</guilabel> to
-      continue to the login screen.
-    </para>
-    <important>
-      <title>Update Your System</title>
-
-      <para>
-        To ensure the security of your system, run a package update
-        after the installation completes.
-        <xref linkend="ch-next-steps" /> explains how to update your
-        Fedora system.
-      </para>
-    </important>
-  </section>
-</chapter>
-
-<!--
-Local variables:
-mode: xml
-fill-column: 72
-End:
--->
diff --git a/en-US/iSCSI.xml b/en-US/iSCSI.xml
deleted file mode 100644
index 2d6dfa3..0000000
--- a/en-US/iSCSI.xml
+++ /dev/null
@@ -1,60 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-
-<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
- "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd">
-
-<appendix id="ISCSI_disks">
-<title>ISCSI disks</title>
-	<para><firstterm>Internet Small Computer System Interface</firstterm> (iSCSI) is a protocol that allows computers to communicate with storage devices by SCSI requests and responses carried over TCP/IP. Because iSCSI is based on the standard SCSI protocols, it uses some terminology from SCSI. The device on the SCSI bus to which requests get sent (and which answers these requests) is known as the <firstterm>target</firstterm> and the device issuing requests is known as the <firstterm>initiator</firstterm>. In other words, an iSCSI disk is a target and the iSCSI software equivalent of a SCSI controller or SCSI Host Bus Adapter (HBA) is called an initiator. This appendix only covers Linux as an iSCSI initiator: how Linux uses iSCSI disks, but not how Linux hosts iSCSI disks.</para>
-
-	<para>Linux has a software iSCSI initiator in the kernel that takes the place and form of a SCSI HBA driver and therefore allows Linux to use iSCSI disks. However, as iSCSI is a fully network-based protocol, iSCSI initiator support needs more than just the ability to send SCSI packets over the network. Before Linux can use an iSCSI target, Linux must find the target on the network and make a connection to it. In some cases, Linux must send authentication information to gain access to the target. Linux must also detect any failure of the network connection and must establish a new connection, including logging in again if necessary.</para>
-
-	<para>The discovery, connection, and logging in is handled in userspace by the <application>iscsiadm</application> utility, and the error handling is also handled in userspace by <application>iscsid</application>.</para>
-
-	<para>Both <application>iscsiadm</application> and <application>iscsid</application> are part of the <application>iscsi-initiator-utils</application> package under Fedora.</para>
-
-
-	<section id="sn-iSCSI_in_Fedora-iSCSI_disks_in_anaconda">
-	<title>iSCSI disks in <application>anaconda</application></title>
-		<para><application>Anaconda</application> can discover (and then log in to) iSCSI disks in two ways:</para>
-
-		<orderedlist>
-			<listitem>
-				<para>When anaconda starts, it checks if the BIOS or add-on boot ROMs of the system support <firstterm>iSCSI Boot Firmware Table</firstterm> (iBFT), a BIOS extension for systems which can boot from iSCSI. If the BIOS supports iBFT, <application>anaconda</application> will read the iSCSI target information for the configured boot disk from the BIOS and log in to this target, making it available as an installation target.</para>
-			</listitem>
-			<listitem>
-				<para>The initial partitioning screen presents you with an <guilabel>Advanced storage configuration</guilabel> button that allows you to add iSCSI target information like the discovery IP-address. <application>Anaconda</application> will probe the given IP-address and log in to any targets that it finds. See <xref linkend="s1-advanced-storage-x86"/> for the details that you can specify for iSCSI targets.</para>
-			</listitem>
-		</orderedlist>
-
-		<para>While <application>anaconda</application> uses <application>iscsiadm</application> to find and log into iSCSI targets, <application>iscsiadm</application> automatically stores any information about these targets iscsiadm iSCSI database. <application>Anaconda</application> then copies this database to the installed system and marks any iSCSI targets not used for <filename>/</filename> so that the system will automatically log in to them when it starts. If <filename>/</filename> is placed on an iSCSI target, <application>initrd</application> will log into this target and <application>anaconda</application> does not include this target in start up scripts to avoid multiple attempts to log into the same target.</para>
-
-		<para>If <filename>/</filename> is placed on an iSCSI target, <application>anaconda</application> sets <application>NetworkManager</application> to ignore any network interfaces that were active during the installation process. These interfaces will also be configured by <application>initrd</application> when the system starts. If <application>NetworkManager</application> were to reconfigure these interfaces, the system would lose its connection to <filename>/</filename>.</para>
-	</section>
-	
-	
-	<section id="sn-iSCSI_disks_during_start_up">
-	<title>iSCSI disks during start up</title>
-		<para>ISCSI-related events might occur at a number of points while the system starts:</para>
-
-		<orderedlist>
-			<listitem>
-				<para>The init script in the <application>initrd</application> will log in to iSCSI targets used for <filename>/</filename> (if any). This is done using the <application>iscsistart</application> utility (which can do this without requiring <application>iscsid</application> to run).</para>
-			</listitem>
-			<listitem>
-				<para>When the root filesystem has been mounted and the various service initscripts get run, the <application>iscsid</application> initscript will get called. This script will then start <application>iscsid</application> if any iSCSI targets are used for <filename>/</filename>, or if any targets in the iSCSI database are marked to be logged in to automatically.</para>
-			</listitem>
-			<listitem>
-				<para>After the classic network service script has been run (or would have been run if enabled) the iscsi initscript will run. If the network is accessible, this will log in to any targets in the iSCSI database which are marked to be logged in to automatically. If the network is not accessible, this script will exit quietly.</para>
-			</listitem>
-			<listitem>
-				<para>When using <application>NetworkManager</application> to access the network (instead of the classic network service script), <application>NetworkManager</application> will call the iscsi initscript. See: <filename>/etc/NetworkManager/dispatcher.d/04-iscsi</filename></para>
-				<important>
-					<para>Because <application>NetworkManager</application> is installed in <filename>/usr</filename>, you cannot use it to configure network access if <filename>/usr</filename> is on network-attached storage such as an iSCSI target.</para>
-				</important>
-			</listitem>
-		</orderedlist>
-		
-		<para>If <application>iscsid</application> is not needed as the system starts, it will not start automatically. If you start <application>iscsiadm</application>,  <application>iscsiadm</application> will start <application>iscsid</application> in turn.</para>
-	</section>
-</appendix>
\ No newline at end of file
diff --git a/en-US/images/accountconfig/rootpassword.png b/en-US/images/accountconfig/rootpassword.png
deleted file mode 100644
index c66cb7a..0000000
Binary files a/en-US/images/accountconfig/rootpassword.png and /dev/null differ
diff --git a/en-US/images/begininstall/configure_tcp.png b/en-US/images/begininstall/configure_tcp.png
deleted file mode 100644
index 58ed097..0000000
Binary files a/en-US/images/begininstall/configure_tcp.png and /dev/null differ
diff --git a/en-US/images/begininstall/hd.png b/en-US/images/begininstall/hd.png
deleted file mode 100644
index 410a6f6..0000000
Binary files a/en-US/images/begininstall/hd.png and /dev/null differ
diff --git a/en-US/images/begininstall/nfs.png b/en-US/images/begininstall/nfs.png
deleted file mode 100644
index 4fdc008..0000000
Binary files a/en-US/images/begininstall/nfs.png and /dev/null differ
diff --git a/en-US/images/begininstall/url.png b/en-US/images/begininstall/url.png
deleted file mode 100644
index 18f7e53..0000000
Binary files a/en-US/images/begininstall/url.png and /dev/null differ
diff --git a/en-US/images/boot/.svn/all-wcprops b/en-US/images/boot/.svn/all-wcprops
deleted file mode 100644
index 1b0658e..0000000
--- a/en-US/images/boot/.svn/all-wcprops
+++ /dev/null
@@ -1,11 +0,0 @@
-K 25
-svn:wc:ra_dav:version-url
-V 91
-/repos/ecs/!svn/ver/25519/Red_Hat_Enterprise_Linux/6.0/Installation_Guide/en-US/images/boot
-END
-boot_screen.png
-K 25
-svn:wc:ra_dav:version-url
-V 107
-/repos/ecs/!svn/ver/27233/Red_Hat_Enterprise_Linux/6.0/Installation_Guide/en-US/images/boot/boot_screen.png
-END
diff --git a/en-US/images/boot/.svn/entries b/en-US/images/boot/.svn/entries
deleted file mode 100644
index f202b2e..0000000
--- a/en-US/images/boot/.svn/entries
+++ /dev/null
@@ -1,62 +0,0 @@
-10
-
-dir
-26020
-https://svn.devel.redhat.com/repos/ecs/Red_Hat_Enterprise_Linux/6.0/Installation_Guide/en-US/images/boot
-https://svn.devel.redhat.com/repos/ecs
-
-
-
-2010-01-15T06:56:59.508401Z
-25519
-rlandman at REDHAT.COM
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-88604915-f33d-0410-84cb-d394843949d3
-
-boot_screen.png
-file
-27233
-
-
-
-2010-02-21T07:39:07.000000Z
-4fcec4bcccac8be11e924352b64bc611
-2010-02-21T07:48:14.398750Z
-27233
-rlandman at REDHAT.COM
-has-props
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-324747
-
diff --git a/en-US/images/boot/.svn/prop-base/boot_screen.png.svn-base b/en-US/images/boot/.svn/prop-base/boot_screen.png.svn-base
deleted file mode 100644
index 5e9587e..0000000
--- a/en-US/images/boot/.svn/prop-base/boot_screen.png.svn-base
+++ /dev/null
@@ -1,5 +0,0 @@
-K 13
-svn:mime-type
-V 24
-application/octet-stream
-END
diff --git a/en-US/images/boot/.svn/text-base/boot_screen.png.svn-base b/en-US/images/boot/.svn/text-base/boot_screen.png.svn-base
deleted file mode 100644
index 2c45c1c..0000000
Binary files a/en-US/images/boot/.svn/text-base/boot_screen.png.svn-base and /dev/null differ
diff --git a/en-US/images/boot/boot_screen.png b/en-US/images/boot/boot_screen.png
deleted file mode 100644
index 9bfcbed..0000000
Binary files a/en-US/images/boot/boot_screen.png and /dev/null differ
diff --git a/en-US/images/crashreporting/crashreporting.png b/en-US/images/crashreporting/crashreporting.png
deleted file mode 100644
index 791a8ce..0000000
Binary files a/en-US/images/crashreporting/crashreporting.png and /dev/null differ
diff --git a/en-US/images/crashreporting/crashreporting_bugzilla.png b/en-US/images/crashreporting/crashreporting_bugzilla.png
deleted file mode 100644
index d281635..0000000
Binary files a/en-US/images/crashreporting/crashreporting_bugzilla.png and /dev/null differ
diff --git a/en-US/images/crashreporting/crashreporting_choose.png b/en-US/images/crashreporting/crashreporting_choose.png
deleted file mode 100644
index d8d883b..0000000
Binary files a/en-US/images/crashreporting/crashreporting_choose.png and /dev/null differ
diff --git a/en-US/images/crashreporting/crashreporting_details.png b/en-US/images/crashreporting/crashreporting_details.png
deleted file mode 100644
index de7809f..0000000
Binary files a/en-US/images/crashreporting/crashreporting_details.png and /dev/null differ
diff --git a/en-US/images/crashreporting/crashreporting_local.png b/en-US/images/crashreporting/crashreporting_local.png
deleted file mode 100644
index 3c7e3e9..0000000
Binary files a/en-US/images/crashreporting/crashreporting_local.png and /dev/null differ
diff --git a/en-US/images/crashreporting/crashreporting_scp.png b/en-US/images/crashreporting/crashreporting_scp.png
deleted file mode 100644
index 856e57f..0000000
Binary files a/en-US/images/crashreporting/crashreporting_scp.png and /dev/null differ
diff --git a/en-US/images/diskpartadvanced/advanced_storage.png b/en-US/images/diskpartadvanced/advanced_storage.png
deleted file mode 100644
index 85444ad..0000000
Binary files a/en-US/images/diskpartadvanced/advanced_storage.png and /dev/null differ
diff --git a/en-US/images/diskpartadvanced/fcoe-config.png b/en-US/images/diskpartadvanced/fcoe-config.png
deleted file mode 100644
index e796aaf..0000000
Binary files a/en-US/images/diskpartadvanced/fcoe-config.png and /dev/null differ
diff --git a/en-US/images/diskpartadvanced/iscsi-config.png b/en-US/images/diskpartadvanced/iscsi-config.png
deleted file mode 100644
index 99911b1..0000000
Binary files a/en-US/images/diskpartadvanced/iscsi-config.png and /dev/null differ
diff --git a/en-US/images/diskpartauto/autopart.png b/en-US/images/diskpartauto/autopart.png
deleted file mode 100644
index 674df73..0000000
Binary files a/en-US/images/diskpartauto/autopart.png and /dev/null differ
diff --git a/en-US/images/diskpartitioning/ddmain.png b/en-US/images/diskpartitioning/ddmain.png
deleted file mode 100644
index 0bdffbd..0000000
Binary files a/en-US/images/diskpartitioning/ddmain.png and /dev/null differ
diff --git a/en-US/images/diskpartitioning/lvm-lv.png b/en-US/images/diskpartitioning/lvm-lv.png
deleted file mode 100644
index 1445188..0000000
Binary files a/en-US/images/diskpartitioning/lvm-lv.png and /dev/null differ
diff --git a/en-US/images/diskpartitioning/lvm-pv.png b/en-US/images/diskpartitioning/lvm-pv.png
deleted file mode 100644
index 6fde276..0000000
Binary files a/en-US/images/diskpartitioning/lvm-pv.png and /dev/null differ
diff --git a/en-US/images/diskpartitioning/lvm-vg.png b/en-US/images/diskpartitioning/lvm-vg.png
deleted file mode 100644
index 0bd41fa..0000000
Binary files a/en-US/images/diskpartitioning/lvm-vg.png and /dev/null differ
diff --git a/en-US/images/diskpartitioning/part-add.png b/en-US/images/diskpartitioning/part-add.png
deleted file mode 100644
index 10eab51..0000000
Binary files a/en-US/images/diskpartitioning/part-add.png and /dev/null differ
diff --git a/en-US/images/diskpartitioning/part-create.png b/en-US/images/diskpartitioning/part-create.png
deleted file mode 100644
index 4e68c53..0000000
Binary files a/en-US/images/diskpartitioning/part-create.png and /dev/null differ
diff --git a/en-US/images/diskpartitioning/raid-clone.png b/en-US/images/diskpartitioning/raid-clone.png
deleted file mode 100644
index c1ecfbd..0000000
Binary files a/en-US/images/diskpartitioning/raid-clone.png and /dev/null differ
diff --git a/en-US/images/diskpartitioning/raid-device.png b/en-US/images/diskpartitioning/raid-device.png
deleted file mode 100644
index 740f850..0000000
Binary files a/en-US/images/diskpartitioning/raid-device.png and /dev/null differ
diff --git a/en-US/images/diskpartitioning/raid-options.png b/en-US/images/diskpartitioning/raid-options.png
deleted file mode 100644
index d6c1105..0000000
Binary files a/en-US/images/diskpartitioning/raid-options.png and /dev/null differ
diff --git a/en-US/images/diskpartitioning/software-raid.png b/en-US/images/diskpartitioning/software-raid.png
deleted file mode 100644
index 78c31eb..0000000
Binary files a/en-US/images/diskpartitioning/software-raid.png and /dev/null differ
diff --git a/en-US/images/diskpartitioning/write_changes.png b/en-US/images/diskpartitioning/write_changes.png
deleted file mode 100644
index 6491de4..0000000
Binary files a/en-US/images/diskpartitioning/write_changes.png and /dev/null differ
diff --git a/en-US/images/diskpartsetup/disk-setup.png b/en-US/images/diskpartsetup/disk-setup.png
deleted file mode 100644
index 2fbf243..0000000
Binary files a/en-US/images/diskpartsetup/disk-setup.png and /dev/null differ
diff --git a/en-US/images/encrypt/.svn/all-wcprops b/en-US/images/encrypt/.svn/all-wcprops
deleted file mode 100644
index 46bed9a..0000000
--- a/en-US/images/encrypt/.svn/all-wcprops
+++ /dev/null
@@ -1,11 +0,0 @@
-K 25
-svn:wc:ra_dav:version-url
-V 94
-/repos/ecs/!svn/ver/27523/Red_Hat_Enterprise_Linux/6.0/Installation_Guide/en-US/images/encrypt
-END
-passphrase.png
-K 25
-svn:wc:ra_dav:version-url
-V 109
-/repos/ecs/!svn/ver/27523/Red_Hat_Enterprise_Linux/6.0/Installation_Guide/en-US/images/encrypt/passphrase.png
-END
diff --git a/en-US/images/encrypt/.svn/entries b/en-US/images/encrypt/.svn/entries
deleted file mode 100644
index b8a3938..0000000
--- a/en-US/images/encrypt/.svn/entries
+++ /dev/null
@@ -1,62 +0,0 @@
-10
-
-dir
-27523
-https://svn.devel.redhat.com/repos/ecs/Red_Hat_Enterprise_Linux/6.0/Installation_Guide/en-US/images/encrypt
-https://svn.devel.redhat.com/repos/ecs
-
-
-
-2010-02-24T23:24:20.129538Z
-27523
-rlandman at REDHAT.COM
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-88604915-f33d-0410-84cb-d394843949d3
-
-passphrase.png
-file
-
-
-
-
-2010-02-24T09:27:41.000000Z
-3641bebe9b0616389dc6fb9310d5786f
-2010-02-24T23:24:20.129538Z
-27523
-rlandman at REDHAT.COM
-has-props
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-19996
-
diff --git a/en-US/images/encrypt/.svn/prop-base/passphrase.png.svn-base b/en-US/images/encrypt/.svn/prop-base/passphrase.png.svn-base
deleted file mode 100644
index 5e9587e..0000000
--- a/en-US/images/encrypt/.svn/prop-base/passphrase.png.svn-base
+++ /dev/null
@@ -1,5 +0,0 @@
-K 13
-svn:mime-type
-V 24
-application/octet-stream
-END
diff --git a/en-US/images/encrypt/.svn/text-base/passphrase.png.svn-base b/en-US/images/encrypt/.svn/text-base/passphrase.png.svn-base
deleted file mode 100644
index 4045de1..0000000
Binary files a/en-US/images/encrypt/.svn/text-base/passphrase.png.svn-base and /dev/null differ
diff --git a/en-US/images/encrypt/passphrase.png b/en-US/images/encrypt/passphrase.png
deleted file mode 100644
index 4045de1..0000000
Binary files a/en-US/images/encrypt/passphrase.png and /dev/null differ
diff --git a/en-US/images/firstboot/fb-createuser.png b/en-US/images/firstboot/fb-createuser.png
deleted file mode 100644
index 773b0df..0000000
Binary files a/en-US/images/firstboot/fb-createuser.png and /dev/null differ
diff --git a/en-US/images/firstboot/fb-datetime.png b/en-US/images/firstboot/fb-datetime.png
deleted file mode 100644
index 2f58def..0000000
Binary files a/en-US/images/firstboot/fb-datetime.png and /dev/null differ
diff --git a/en-US/images/firstboot/fb-license.png b/en-US/images/firstboot/fb-license.png
deleted file mode 100644
index 575b3a7..0000000
Binary files a/en-US/images/firstboot/fb-license.png and /dev/null differ
diff --git a/en-US/images/firstboot/fb-ntp.png b/en-US/images/firstboot/fb-ntp.png
deleted file mode 100644
index 4011adc..0000000
Binary files a/en-US/images/firstboot/fb-ntp.png and /dev/null differ
diff --git a/en-US/images/firstboot/fb-profile.png b/en-US/images/firstboot/fb-profile.png
deleted file mode 100644
index b173bc4..0000000
Binary files a/en-US/images/firstboot/fb-profile.png and /dev/null differ
diff --git a/en-US/images/firstboot/fb-welcome.png b/en-US/images/firstboot/fb-welcome.png
deleted file mode 100644
index 46815ce..0000000
Binary files a/en-US/images/firstboot/fb-welcome.png and /dev/null differ
diff --git a/en-US/images/guimode/widget1.png b/en-US/images/guimode/widget1.png
deleted file mode 100644
index abdd1be..0000000
Binary files a/en-US/images/guimode/widget1.png and /dev/null differ
diff --git a/en-US/images/guimode/widget2.png b/en-US/images/guimode/widget2.png
deleted file mode 100644
index b809b58..0000000
Binary files a/en-US/images/guimode/widget2.png and /dev/null differ
diff --git a/en-US/images/icon.svg b/en-US/images/icon.svg
deleted file mode 100644
index c471a60..0000000
--- a/en-US/images/icon.svg
+++ /dev/null
@@ -1,3936 +0,0 @@
-<?xml version="1.0" encoding="UTF-8" standalone="no"?>
-<!-- Created with Inkscape (http://www.inkscape.org/) -->
-<svg
-   xmlns:ns="http://ns.adobe.com/AdobeSVGViewerExtensions/3/"
-   xmlns:a="http://ns.adobe.com/AdobeSVGViewerExtensions/3.0/"
-   xmlns:dc="http://purl.org/dc/elements/1.1/"
-   xmlns:cc="http://web.resource.org/cc/"
-   xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
-   xmlns:svg="http://www.w3.org/2000/svg"
-   xmlns="http://www.w3.org/2000/svg"
-   xmlns:xlink="http://www.w3.org/1999/xlink"
-   xmlns:sodipodi="http://sodipodi.sourceforge.net/DTD/sodipodi-0.dtd"
-   xmlns:inkscape="http://www.inkscape.org/namespaces/inkscape"
-   version="1.0"
-   width="32"
-   height="32"
-   id="svg3017"
-   sodipodi:version="0.32"
-   inkscape:version="0.44+devel"
-   sodipodi:docname="book.svg"
-   sodipodi:docbase="/home/andy/Desktop">
-  <metadata
-     id="metadata489">
-    <rdf:RDF>
-      <cc:Work
-         rdf:about="">
-        <dc:format>image/svg+xml</dc:format>
-        <dc:type
-           rdf:resource="http://purl.org/dc/dcmitype/StillImage" />
-      </cc:Work>
-    </rdf:RDF>
-  </metadata>
-  <sodipodi:namedview
-     inkscape:window-height="480"
-     inkscape:window-width="858"
-     inkscape:pageshadow="0"
-     inkscape:pageopacity="0.0"
-     guidetolerance="10.0"
-     gridtolerance="10.0"
-     objecttolerance="10.0"
-     borderopacity="1.0"
-     bordercolor="#666666"
-     pagecolor="#ffffff"
-     id="base"
-     inkscape:zoom="1"
-     inkscape:cx="16"
-     inkscape:cy="15.944056"
-     inkscape:window-x="0"
-     inkscape:window-y="33"
-     inkscape:current-layer="svg3017" />
-  <defs
-     id="defs3019">
-    <linearGradient
-       id="linearGradient2381">
-      <stop
-         style="stop-color:white;stop-opacity:1"
-         offset="0"
-         id="stop2383" />
-      <stop
-         style="stop-color:white;stop-opacity:0"
-         offset="1"
-         id="stop2385" />
-    </linearGradient>
-    <linearGradient
-       x1="415.73831"
-       y1="11.854"
-       x2="418.13361"
-       y2="18.8104"
-       id="XMLID_1758_"
-       gradientUnits="userSpaceOnUse"
-       gradientTransform="matrix(0.8362,0.5206,-1.1904,0.992,147.62,-30.9374)">
-      <stop
-         style="stop-color:#ccc;stop-opacity:1"
-         offset="0"
-         id="stop3903" />
-      <stop
-         style="stop-color:#f2f2f2;stop-opacity:1"
-         offset="1"
-         id="stop3905" />
-      <a:midPointStop
-         style="stop-color:#CCCCCC"
-         offset="0" />
-      <a:midPointStop
-         style="stop-color:#CCCCCC"
-         offset="0.5" />
-      <a:midPointStop
-         style="stop-color:#F2F2F2"
-         offset="1" />
-    </linearGradient>
-    <linearGradient
-       x1="500.70749"
-       y1="-13.2441"
-       x2="513.46442"
-       y2="-2.1547"
-       id="XMLID_1757_"
-       gradientUnits="userSpaceOnUse"
-       gradientTransform="matrix(0.6868,0.4269,-0.9821,0.821,111.6149,-5.7901)">
-      <stop
-         style="stop-color:#5387ba;stop-opacity:1"
-         offset="0"
-         id="stop3890" />
-      <stop
-         style="stop-color:#96bad6;stop-opacity:1"
-         offset="1"
-         id="stop3892" />
-      <a:midPointStop
-         style="stop-color:#5387BA"
-         offset="0" />
-      <a:midPointStop
-         style="stop-color:#5387BA"
-         offset="0.5" />
-      <a:midPointStop
-         style="stop-color:#96BAD6"
-         offset="1" />
-    </linearGradient>
-    <clipPath
-       id="XMLID_1755_">
-      <use
-         id="use3874"
-         x="0"
-         y="0"
-         width="744.09448"
-         height="600"
-         xlink:href="#XMLID_343_" />
-    </clipPath>
-    <linearGradient
-       x1="505.62939"
-       y1="-14.9526"
-       x2="527.49402"
-       y2="-0.7536"
-       id="XMLID_1756_"
-       gradientUnits="userSpaceOnUse"
-       gradientTransform="matrix(0.6868,0.4269,-0.9821,0.821,111.6149,-5.7901)">
-      <stop
-         style="stop-color:#b4daea;stop-opacity:1"
-         offset="0"
-         id="stop3877" />
-      <stop
-         style="stop-color:#b4daea;stop-opacity:1"
-         offset="0.51120001"
-         id="stop3879" />
-      <stop
-         style="stop-color:#5387ba;stop-opacity:1"
-         offset="0.64609998"
-         id="stop3881" />
-      <stop
-         style="stop-color:#16336e;stop-opacity:1"
-         offset="1"
-         id="stop3883" />
-      <a:midPointStop
-         style="stop-color:#B4DAEA"
-         offset="0" />
-      <a:midPointStop
-         style="stop-color:#B4DAEA"
-         offset="0.5" />
-      <a:midPointStop
-         style="stop-color:#B4DAEA"
-         offset="0.5112" />
-      <a:midPointStop
-         style="stop-color:#B4DAEA"
-         offset="0.5" />
-      <a:midPointStop
-         style="stop-color:#5387BA"
-         offset="0.6461" />
-      <a:midPointStop
-         style="stop-color:#5387BA"
-         offset="0.5" />
-      <a:midPointStop
-         style="stop-color:#16336E"
-         offset="1" />
-    </linearGradient>
-    <linearGradient
-       x1="471.0806"
-       y1="201.07761"
-       x2="481.91711"
-       y2="210.4977"
-       id="XMLID_1754_"
-       gradientUnits="userSpaceOnUse">
-      <stop
-         style="stop-color:#6498c1;stop-opacity:1"
-         offset="0.005618"
-         id="stop3863" />
-      <stop
-         style="stop-color:#79a9cc;stop-opacity:1"
-         offset="0.2332"
-         id="stop3865" />
-      <stop
-         style="stop-color:#a4cde2;stop-opacity:1"
-         offset="0.74049997"
-         id="stop3867" />
-      <stop
-         style="stop-color:#b4daea;stop-opacity:1"
-         offset="1"
-         id="stop3869" />
-      <a:midPointStop
-         style="stop-color:#6498C1"
-         offset="5.618000e-003" />
-      <a:midPointStop
-         style="stop-color:#6498C1"
-         offset="0.4438" />
-      <a:midPointStop
-         style="stop-color:#B4DAEA"
-         offset="1" />
-    </linearGradient>
-    <linearGradient
-       x1="516.57672"
-       y1="-15.769"
-       x2="516.57672"
-       y2="0.84280002"
-       id="XMLID_1753_"
-       gradientUnits="userSpaceOnUse"
-       gradientTransform="matrix(0.6868,0.4269,-0.9821,0.821,111.6149,-5.7901)">
-      <stop
-         style="stop-color:#b2b2b2;stop-opacity:1"
-         offset="0"
-         id="stop3851" />
-      <stop
-         style="stop-color:#f2f2f2;stop-opacity:1"
-         offset="1"
-         id="stop3853" />
-      <a:midPointStop
-         style="stop-color:#B2B2B2"
-         offset="0" />
-      <a:midPointStop
-         style="stop-color:#B2B2B2"
-         offset="0.5" />
-      <a:midPointStop
-         style="stop-color:#F2F2F2"
-         offset="1" />
-    </linearGradient>
-    <clipPath
-       id="XMLID_1751_">
-      <use
-         id="use3837"
-         x="0"
-         y="0"
-         width="744.09448"
-         height="600"
-         xlink:href="#XMLID_338_" />
-    </clipPath>
-    <linearGradient
-       x1="506.09909"
-       y1="-11.5137"
-       x2="527.99609"
-       y2="2.7063999"
-       id="XMLID_1752_"
-       gradientUnits="userSpaceOnUse"
-       gradientTransform="matrix(0.6868,0.4269,-0.9821,0.821,111.6149,-5.7901)">
-      <stop
-         style="stop-color:#b4daea;stop-opacity:1"
-         offset="0"
-         id="stop3840" />
-      <stop
-         style="stop-color:#b4daea;stop-opacity:1"
-         offset="0.51120001"
-         id="stop3842" />
-      <stop
-         style="stop-color:#5387ba;stop-opacity:1"
-         offset="0.64609998"
-         id="stop3844" />
-      <stop
-         style="stop-color:#16336e;stop-opacity:1"
-         offset="1"
-         id="stop3846" />
-      <a:midPointStop
-         style="stop-color:#B4DAEA"
-         offset="0" />
-      <a:midPointStop
-         style="stop-color:#B4DAEA"
-         offset="0.5" />
-      <a:midPointStop
-         style="stop-color:#B4DAEA"
-         offset="0.5112" />
-      <a:midPointStop
-         style="stop-color:#B4DAEA"
-         offset="0.5" />
-      <a:midPointStop
-         style="stop-color:#5387BA"
-         offset="0.6461" />
-      <a:midPointStop
-         style="stop-color:#5387BA"
-         offset="0.5" />
-      <a:midPointStop
-         style="stop-color:#16336E"
-         offset="1" />
-    </linearGradient>
-    <linearGradient
-       x1="468.2915"
-       y1="204.7612"
-       x2="479.39871"
-       y2="214.4166"
-       id="XMLID_1750_"
-       gradientUnits="userSpaceOnUse">
-      <stop
-         style="stop-color:#5387ba;stop-opacity:1"
-         offset="0"
-         id="stop3830" />
-      <stop
-         style="stop-color:#96bad6;stop-opacity:1"
-         offset="1"
-         id="stop3832" />
-      <a:midPointStop
-         style="stop-color:#5387BA"
-         offset="0" />
-      <a:midPointStop
-         style="stop-color:#5387BA"
-         offset="0.5" />
-      <a:midPointStop
-         style="stop-color:#96BAD6"
-         offset="1" />
-    </linearGradient>
-    <linearGradient
-       x1="502.70749"
-       y1="115.3013"
-       x2="516.39001"
-       y2="127.1953"
-       id="XMLID_1749_"
-       gradientUnits="userSpaceOnUse"
-       gradientTransform="matrix(0.9703,0.2419,-0.2419,0.9703,11.0227,-35.6159)">
-      <stop
-         style="stop-color:#5387ba;stop-opacity:1"
-         offset="0"
-         id="stop3818" />
-      <stop
-         style="stop-color:#96bad6;stop-opacity:1"
-         offset="1"
-         id="stop3820" />
-      <a:midPointStop
-         style="stop-color:#5387BA"
-         offset="0" />
-      <a:midPointStop
-         style="stop-color:#5387BA"
-         offset="0.5" />
-      <a:midPointStop
-         style="stop-color:#96BAD6"
-         offset="1" />
-    </linearGradient>
-    <linearGradient
-       x1="501.0903"
-       y1="-19.2544"
-       x2="531.85413"
-       y2="0.72390002"
-       id="XMLID_1748_"
-       gradientUnits="userSpaceOnUse"
-       gradientTransform="matrix(0.6868,0.4269,-0.9821,0.821,111.6149,-5.7901)">
-      <stop
-         style="stop-color:#b4daea;stop-opacity:1"
-         offset="0"
-         id="stop3803" />
-      <stop
-         style="stop-color:#b4daea;stop-opacity:1"
-         offset="0.51120001"
-         id="stop3805" />
-      <stop
-         style="stop-color:#5387ba;stop-opacity:1"
-         offset="0.64609998"
-         id="stop3807" />
-      <stop
-         style="stop-color:#16336e;stop-opacity:1"
-         offset="1"
-         id="stop3809" />
-      <a:midPointStop
-         style="stop-color:#B4DAEA"
-         offset="0" />
-      <a:midPointStop
-         style="stop-color:#B4DAEA"
-         offset="0.5" />
-      <a:midPointStop
-         style="stop-color:#B4DAEA"
-         offset="0.5112" />
-      <a:midPointStop
-         style="stop-color:#B4DAEA"
-         offset="0.5" />
-      <a:midPointStop
-         style="stop-color:#5387BA"
-         offset="0.6461" />
-      <a:midPointStop
-         style="stop-color:#5387BA"
-         offset="0.5" />
-      <a:midPointStop
-         style="stop-color:#16336E"
-         offset="1" />
-    </linearGradient>
-    <linearGradient
-       x1="481.23969"
-       y1="212.5742"
-       x2="472.92981"
-       y2="207.4967"
-       id="XMLID_2275_"
-       gradientUnits="userSpaceOnUse">
-      <stop
-         style="stop-color:#f3403f;stop-opacity:1"
-         offset="0"
-         id="stop9947" />
-      <stop
-         style="stop-color:#d02a28;stop-opacity:1"
-         offset="0.37889999"
-         id="stop9949" />
-      <stop
-         style="stop-color:#b21714;stop-opacity:1"
-         offset="0.77649999"
-         id="stop9951" />
-      <stop
-         style="stop-color:#a6100c;stop-opacity:1"
-         offset="1"
-         id="stop9953" />
-      <a:midPointStop
-         style="stop-color:#F3403F"
-         offset="0" />
-      <a:midPointStop
-         style="stop-color:#F3403F"
-         offset="0.4213" />
-      <a:midPointStop
-         style="stop-color:#A6100C"
-         offset="1" />
-    </linearGradient>
-    <clipPath
-       id="XMLID_2273_">
-      <use
-         id="use9933"
-         x="0"
-         y="0"
-         width="744.09448"
-         height="600"
-         xlink:href="#XMLID_960_" />
-    </clipPath>
-    <linearGradient
-       x1="473.7681"
-       y1="209.17529"
-       x2="486.98099"
-       y2="213.2001"
-       id="XMLID_2274_"
-       gradientUnits="userSpaceOnUse">
-      <stop
-         style="stop-color:#f3403f;stop-opacity:1"
-         offset="0"
-         id="stop9936" />
-      <stop
-         style="stop-color:#d02a28;stop-opacity:1"
-         offset="0.37889999"
-         id="stop9938" />
-      <stop
-         style="stop-color:#b21714;stop-opacity:1"
-         offset="0.77649999"
-         id="stop9940" />
-      <stop
-         style="stop-color:#a6100c;stop-opacity:1"
-         offset="1"
-         id="stop9942" />
-      <a:midPointStop
-         style="stop-color:#F3403F"
-         offset="0" />
-      <a:midPointStop
-         style="stop-color:#F3403F"
-         offset="0.4213" />
-      <a:midPointStop
-         style="stop-color:#A6100C"
-         offset="1" />
-    </linearGradient>
-    <linearGradient
-       x1="478.21341"
-       y1="-131.9297"
-       x2="469.85818"
-       y2="-140.28481"
-       id="XMLID_2272_"
-       gradientUnits="userSpaceOnUse"
-       gradientTransform="matrix(0.5592,0.829,-0.829,0.5592,101.3357,-104.791)">
-      <stop
-         style="stop-color:#f3403f;stop-opacity:1"
-         offset="0"
-         id="stop9917" />
-      <stop
-         style="stop-color:#d02a28;stop-opacity:1"
-         offset="0.37889999"
-         id="stop9919" />
-      <stop
-         style="stop-color:#b21714;stop-opacity:1"
-         offset="0.77649999"
-         id="stop9921" />
-      <stop
-         style="stop-color:#a6100c;stop-opacity:1"
-         offset="1"
-         id="stop9923" />
-      <a:midPointStop
-         style="stop-color:#F3403F"
-         offset="0" />
-      <a:midPointStop
-         style="stop-color:#F3403F"
-         offset="0.4213" />
-      <a:midPointStop
-         style="stop-color:#A6100C"
-         offset="1" />
-    </linearGradient>
-    <marker
-       refX="0"
-       refY="0"
-       orient="auto"
-       style="overflow:visible"
-       id="TriangleInM">
-      <path
-         d="M 5.77,0 L -2.88,5 L -2.88,-5 L 5.77,0 z "
-         transform="scale(-0.4,-0.4)"
-         style="fill:#5c5c4f"
-         id="path3197" />
-    </marker>
-    <linearGradient
-       x1="200.7363"
-       y1="100.4028"
-       x2="211.99519"
-       y2="89.143997"
-       id="XMLID_3298_"
-       gradientUnits="userSpaceOnUse">
-      <stop
-         style="stop-color:#bfbfbf;stop-opacity:1"
-         offset="0"
-         id="stop20103" />
-      <stop
-         style="stop-color:#f2f2f2;stop-opacity:1"
-         offset="1"
-         id="stop20105" />
-      <a:midPointStop
-         offset="0"
-         style="stop-color:#BFBFBF" />
-      <a:midPointStop
-         offset="0.5"
-         style="stop-color:#BFBFBF" />
-      <a:midPointStop
-         offset="1"
-         style="stop-color:#F2F2F2" />
-    </linearGradient>
-    <linearGradient
-       x1="200.7363"
-       y1="100.4028"
-       x2="211.99519"
-       y2="89.143997"
-       id="linearGradient36592"
-       xlink:href="#XMLID_3298_"
-       gradientUnits="userSpaceOnUse"
-       gradientTransform="matrix(1.029078,0,0,1,-183.2624,-79.44655)" />
-    <linearGradient
-       x1="181.2925"
-       y1="110.8481"
-       x2="192.6369"
-       y2="99.5037"
-       id="XMLID_3297_"
-       gradientUnits="userSpaceOnUse">
-      <stop
-         style="stop-color:#e5e5e5;stop-opacity:1"
-         offset="0"
-         id="stop20096" />
-      <stop
-         style="stop-color:#ccc;stop-opacity:1"
-         offset="1"
-         id="stop20098" />
-      <a:midPointStop
-         offset="0"
-         style="stop-color:#E5E5E5" />
-      <a:midPointStop
-         offset="0.5"
-         style="stop-color:#E5E5E5" />
-      <a:midPointStop
-         offset="1"
-         style="stop-color:#CCCCCC" />
-    </linearGradient>
-    <linearGradient
-       x1="181.2925"
-       y1="110.8481"
-       x2="192.6369"
-       y2="99.5037"
-       id="linearGradient36595"
-       xlink:href="#XMLID_3297_"
-       gradientUnits="userSpaceOnUse"
-       gradientTransform="matrix(1.029078,0,0,1,-183.2624,-79.44655)" />
-    <linearGradient
-       x1="211.77589"
-       y1="105.7749"
-       x2="212.6619"
-       y2="108.2092"
-       id="XMLID_3296_"
-       gradientUnits="userSpaceOnUse">
-      <stop
-         style="stop-color:#0f6124;stop-opacity:1"
-         offset="0"
-         id="stop20087" />
-      <stop
-         style="stop-color:#219630;stop-opacity:1"
-         offset="1"
-         id="stop20089" />
-      <a:midPointStop
-         offset="0"
-         style="stop-color:#0F6124" />
-      <a:midPointStop
-         offset="0.5"
-         style="stop-color:#0F6124" />
-      <a:midPointStop
-         offset="1"
-         style="stop-color:#219630" />
-    </linearGradient>
-    <linearGradient
-       x1="211.77589"
-       y1="105.7749"
-       x2="212.6619"
-       y2="108.2092"
-       id="linearGradient36677"
-       xlink:href="#XMLID_3296_"
-       gradientUnits="userSpaceOnUse"
-       gradientTransform="matrix(1.029078,0,0,1,-183.2624,-79.44655)" />
-    <linearGradient
-       x1="208.9834"
-       y1="116.8296"
-       x2="200.0811"
-       y2="96.834602"
-       id="XMLID_3295_"
-       gradientUnits="userSpaceOnUse">
-      <stop
-         style="stop-color:#b2b2b2;stop-opacity:1"
-         offset="0"
-         id="stop20076" />
-      <stop
-         style="stop-color:#e5e5e5;stop-opacity:1"
-         offset="0.5"
-         id="stop20078" />
-      <stop
-         style="stop-color:white;stop-opacity:1"
-         offset="1"
-         id="stop20080" />
-      <a:midPointStop
-         offset="0"
-         style="stop-color:#B2B2B2" />
-      <a:midPointStop
-         offset="0.5"
-         style="stop-color:#B2B2B2" />
-      <a:midPointStop
-         offset="0.5"
-         style="stop-color:#E5E5E5" />
-      <a:midPointStop
-         offset="0.5"
-         style="stop-color:#E5E5E5" />
-      <a:midPointStop
-         offset="1"
-         style="stop-color:#FFFFFF" />
-    </linearGradient>
-    <linearGradient
-       x1="208.9834"
-       y1="116.8296"
-       x2="200.0811"
-       y2="96.834602"
-       id="linearGradient36604"
-       xlink:href="#XMLID_3295_"
-       gradientUnits="userSpaceOnUse"
-       gradientTransform="matrix(1.029078,0,0,1,-183.2624,-79.44655)" />
-    <linearGradient
-       x1="195.5264"
-       y1="97.911102"
-       x2="213.5213"
-       y2="115.9061"
-       id="XMLID_3294_"
-       gradientUnits="userSpaceOnUse">
-      <stop
-         style="stop-color:#ccc;stop-opacity:1"
-         offset="0"
-         id="stop20069" />
-      <stop
-         style="stop-color:white;stop-opacity:1"
-         offset="1"
-         id="stop20071" />
-      <a:midPointStop
-         offset="0"
-         style="stop-color:#CCCCCC" />
-      <a:midPointStop
-         offset="0.5"
-         style="stop-color:#CCCCCC" />
-      <a:midPointStop
-         offset="1"
-         style="stop-color:#FFFFFF" />
-    </linearGradient>
-    <linearGradient
-       x1="195.5264"
-       y1="97.911102"
-       x2="213.5213"
-       y2="115.9061"
-       id="linearGradient36607"
-       xlink:href="#XMLID_3294_"
-       gradientUnits="userSpaceOnUse"
-       gradientTransform="matrix(1.029078,0,0,1,-183.2624,-79.44655)" />
-    <linearGradient
-       x1="186.1938"
-       y1="109.1343"
-       x2="206.6881"
-       y2="88.639999"
-       id="XMLID_3293_"
-       gradientUnits="userSpaceOnUse">
-      <stop
-         style="stop-color:#b2b2b2;stop-opacity:1"
-         offset="0"
-         id="stop20056" />
-      <stop
-         style="stop-color:#e5e5e5;stop-opacity:1"
-         offset="0.16850001"
-         id="stop20058" />
-      <stop
-         style="stop-color:white;stop-opacity:1"
-         offset="0.23029999"
-         id="stop20060" />
-      <stop
-         style="stop-color:#e5e5e5;stop-opacity:1"
-         offset="0.2809"
-         id="stop20062" />
-      <stop
-         style="stop-color:#c2c2c2;stop-opacity:1"
-         offset="0.5"
-         id="stop20064" />
-      <a:midPointStop
-         offset="0"
-         style="stop-color:#B2B2B2" />
-      <a:midPointStop
-         offset="0.5"
-         style="stop-color:#B2B2B2" />
-      <a:midPointStop
-         offset="0.1685"
-         style="stop-color:#E5E5E5" />
-      <a:midPointStop
-         offset="0.5"
-         style="stop-color:#E5E5E5" />
-      <a:midPointStop
-         offset="0.2303"
-         style="stop-color:#FFFFFF" />
-      <a:midPointStop
-         offset="0.5"
-         style="stop-color:#FFFFFF" />
-      <a:midPointStop
-         offset="0.2809"
-         style="stop-color:#E5E5E5" />
-      <a:midPointStop
-         offset="0.5"
-         style="stop-color:#E5E5E5" />
-      <a:midPointStop
-         offset="0.5"
-         style="stop-color:#C2C2C2" />
-    </linearGradient>
-    <linearGradient
-       x1="186.1938"
-       y1="109.1343"
-       x2="206.6881"
-       y2="88.639999"
-       id="linearGradient36610"
-       xlink:href="#XMLID_3293_"
-       gradientUnits="userSpaceOnUse"
-       gradientTransform="matrix(1.029078,0,0,1,-183.2624,-79.44655)" />
-    <linearGradient
-       x1="184.8569"
-       y1="112.2676"
-       x2="211.94099"
-       y2="89.541397"
-       id="XMLID_3292_"
-       gradientUnits="userSpaceOnUse">
-      <stop
-         style="stop-color:#b2b2b2;stop-opacity:1"
-         offset="0"
-         id="stop20043" />
-      <stop
-         style="stop-color:#e5e5e5;stop-opacity:1"
-         offset="0.16850001"
-         id="stop20045" />
-      <stop
-         style="stop-color:white;stop-opacity:1"
-         offset="0.23029999"
-         id="stop20047" />
-      <stop
-         style="stop-color:#e5e5e5;stop-opacity:1"
-         offset="0.2809"
-         id="stop20049" />
-      <stop
-         style="stop-color:#ccc;stop-opacity:1"
-         offset="1"
-         id="stop20051" />
-      <a:midPointStop
-         offset="0"
-         style="stop-color:#B2B2B2" />
-      <a:midPointStop
-         offset="0.5"
-         style="stop-color:#B2B2B2" />
-      <a:midPointStop
-         offset="0.1685"
-         style="stop-color:#E5E5E5" />
-      <a:midPointStop
-         offset="0.5"
-         style="stop-color:#E5E5E5" />
-      <a:midPointStop
-         offset="0.2303"
-         style="stop-color:#FFFFFF" />
-      <a:midPointStop
-         offset="0.5"
-         style="stop-color:#FFFFFF" />
-      <a:midPointStop
-         offset="0.2809"
-         style="stop-color:#E5E5E5" />
-      <a:midPointStop
-         offset="0.5"
-         style="stop-color:#E5E5E5" />
-      <a:midPointStop
-         offset="1"
-         style="stop-color:#CCCCCC" />
-    </linearGradient>
-    <linearGradient
-       x1="184.8569"
-       y1="112.2676"
-       x2="211.94099"
-       y2="89.541397"
-       id="linearGradient36613"
-       xlink:href="#XMLID_3292_"
-       gradientUnits="userSpaceOnUse"
-       gradientTransform="matrix(1.029078,0,0,1,-183.2624,-79.44655)" />
-    <marker
-       refX="0"
-       refY="0"
-       orient="auto"
-       style="overflow:visible"
-       id="TriangleOutM">
-      <path
-         d="M 5.77,0 L -2.88,5 L -2.88,-5 L 5.77,0 z "
-         transform="scale(0.4,0.4)"
-         style="fill:#5c5c4f;fill-rule:evenodd;stroke-width:1pt;marker-start:none"
-         id="path3238" />
-    </marker>
-    <linearGradient
-       x1="165.3"
-       y1="99.5"
-       x2="165.3"
-       y2="115.9"
-       id="XMLID_3457_"
-       gradientUnits="userSpaceOnUse">
-      <stop
-         style="stop-color:#999;stop-opacity:1"
-         offset="0"
-         id="stop8309" />
-      <stop
-         style="stop-color:#b2b2b2;stop-opacity:1"
-         offset="0.30000001"
-         id="stop8311" />
-      <stop
-         style="stop-color:#b2b2b2;stop-opacity:1"
-         offset="1"
-         id="stop8313" />
-      <a:midPointstop
-         offset="0"
-         style="stop-color:#999999" />
-      <a:midPointstop
-         offset="0.5"
-         style="stop-color:#999999" />
-      <a:midPointstop
-         offset="0.3"
-         style="stop-color:#B2B2B2" />
-      <a:midPointstop
-         offset="0.5"
-         style="stop-color:#B2B2B2" />
-      <a:midPointstop
-         offset="1"
-         style="stop-color:#B2B2B2" />
-    </linearGradient>
-    <linearGradient
-       x1="165.3"
-       y1="99.5"
-       x2="165.3"
-       y2="115.9"
-       id="lg1997"
-       xlink:href="#XMLID_3457_"
-       gradientUnits="userSpaceOnUse"
-       gradientTransform="matrix(1.2,0,0,1.2,-175.9,-114.6)" />
-    <linearGradient
-       x1="175"
-       y1="99.800003"
-       x2="175"
-       y2="112.5"
-       id="XMLID_3456_"
-       gradientUnits="userSpaceOnUse">
-      <stop
-         style="stop-color:#737373;stop-opacity:1"
-         offset="0"
-         id="stop8300" />
-      <stop
-         style="stop-color:#191919;stop-opacity:1"
-         offset="0.60000002"
-         id="stop8302" />
-      <stop
-         style="stop-color:#191919;stop-opacity:1"
-         offset="1"
-         id="stop8304" />
-      <a:midPointstop
-         offset="0"
-         style="stop-color:#737373" />
-      <a:midPointstop
-         offset="0.5"
-         style="stop-color:#737373" />
-      <a:midPointstop
-         offset="0.6"
-         style="stop-color:#191919" />
-      <a:midPointstop
-         offset="0.5"
-         style="stop-color:#191919" />
-      <a:midPointstop
-         offset="1"
-         style="stop-color:#191919" />
-    </linearGradient>
-    <linearGradient
-       x1="175"
-       y1="99.800003"
-       x2="175"
-       y2="112.5"
-       id="lg2000"
-       xlink:href="#XMLID_3456_"
-       gradientUnits="userSpaceOnUse"
-       gradientTransform="matrix(1.2,0,0,1.2,-175.9,-114.6)" />
-    <linearGradient
-       x1="168.8"
-       y1="107.1"
-       x2="164.5"
-       y2="110"
-       id="XMLID_3455_"
-       gradientUnits="userSpaceOnUse">
-      <stop
-         style="stop-color:#666;stop-opacity:1"
-         offset="0"
-         id="stop8291" />
-      <stop
-         style="stop-color:#191919;stop-opacity:1"
-         offset="0.69999999"
-         id="stop8293" />
-      <stop
-         style="stop-color:#191919;stop-opacity:1"
-         offset="1"
-         id="stop8295" />
-      <a:midPointstop
-         offset="0"
-         style="stop-color:#666666" />
-      <a:midPointstop
-         offset="0.5"
-         style="stop-color:#666666" />
-      <a:midPointstop
-         offset="0.7"
-         style="stop-color:#191919" />
-      <a:midPointstop
-         offset="0.5"
-         style="stop-color:#191919" />
-      <a:midPointstop
-         offset="1"
-         style="stop-color:#191919" />
-    </linearGradient>
-    <linearGradient
-       x1="168.8"
-       y1="107.1"
-       x2="164.5"
-       y2="110"
-       id="lg2003"
-       xlink:href="#XMLID_3455_"
-       gradientUnits="userSpaceOnUse"
-       gradientTransform="matrix(1.2,0,0,1.2,-175.9,-114.6)" />
-    <linearGradient
-       id="lg63694">
-      <stop
-         style="stop-color:white;stop-opacity:1"
-         offset="0"
-         id="stop63696" />
-      <stop
-         style="stop-color:white;stop-opacity:0"
-         offset="1"
-         id="stop63698" />
-    </linearGradient>
-    <linearGradient
-       x1="458"
-       y1="483"
-       x2="465.20001"
-       y2="271.39999"
-       id="lg2006"
-       xlink:href="#lg63694"
-       gradientUnits="userSpaceOnUse"
-       gradientTransform="matrix(6.3e-2,0,0,6.3e-2,-1.3,-9.8)" />
-    <linearGradient
-       x1="176.3"
-       y1="110.1"
-       x2="158.7"
-       y2="105"
-       id="XMLID_3453_"
-       gradientUnits="userSpaceOnUse">
-      <stop
-         style="stop-color:#666;stop-opacity:1"
-         offset="0"
-         id="stop8271" />
-      <stop
-         style="stop-color:#737373;stop-opacity:1"
-         offset="0.2"
-         id="stop8273" />
-      <stop
-         style="stop-color:white;stop-opacity:1"
-         offset="1"
-         id="stop8275" />
-      <a:midPointstop
-         offset="0"
-         style="stop-color:#666666" />
-      <a:midPointstop
-         offset="0.5"
-         style="stop-color:#666666" />
-      <a:midPointstop
-         offset="0.2"
-         style="stop-color:#737373" />
-      <a:midPointstop
-         offset="0.5"
-         style="stop-color:#737373" />
-      <a:midPointstop
-         offset="1"
-         style="stop-color:#FFFFFF" />
-    </linearGradient>
-    <linearGradient
-       x1="176.3"
-       y1="110.1"
-       x2="158.7"
-       y2="105"
-       id="lg2009"
-       xlink:href="#XMLID_3453_"
-       gradientUnits="userSpaceOnUse"
-       gradientTransform="matrix(1.2,0,0,1.2,-175.9,-114.6)" />
-    <linearGradient
-       x1="173.60001"
-       y1="118.9"
-       x2="172.8"
-       y2="128.2"
-       id="XMLID_3449_"
-       gradientUnits="userSpaceOnUse">
-      <stop
-         style="stop-color:#ecb300;stop-opacity:1"
-         offset="0"
-         id="stop8232" />
-      <stop
-         style="stop-color:#fff95e;stop-opacity:1"
-         offset="0.60000002"
-         id="stop8234" />
-      <stop
-         style="stop-color:#ecd600;stop-opacity:1"
-         offset="1"
-         id="stop8236" />
-      <a:midPointstop
-         offset="0"
-         style="stop-color:#ECB300" />
-      <a:midPointstop
-         offset="0.5"
-         style="stop-color:#ECB300" />
-      <a:midPointstop
-         offset="0.6"
-         style="stop-color:#FFF95E" />
-      <a:midPointstop
-         offset="0.5"
-         style="stop-color:#FFF95E" />
-      <a:midPointstop
-         offset="1"
-         style="stop-color:#ECD600" />
-    </linearGradient>
-    <linearGradient
-       x1="173.60001"
-       y1="118.9"
-       x2="172.8"
-       y2="128.2"
-       id="lg2016"
-       xlink:href="#XMLID_3449_"
-       gradientUnits="userSpaceOnUse"
-       gradientTransform="matrix(1.2,0,0,1.2,-175.9,-114.6)" />
-    <radialGradient
-       cx="284.60001"
-       cy="172.60001"
-       r="6.5"
-       fx="284.60001"
-       fy="172.60001"
-       id="XMLID_3448_"
-       gradientUnits="userSpaceOnUse"
-       gradientTransform="matrix(1.4,0,0,1.4,-237.3,-126.8)">
-      <stop
-         style="stop-color:#ecb300;stop-opacity:1"
-         offset="0"
-         id="stop8219" />
-      <stop
-         style="stop-color:#ecb300;stop-opacity:1"
-         offset="0.30000001"
-         id="stop8221" />
-      <stop
-         style="stop-color:#c96b00;stop-opacity:1"
-         offset="0.89999998"
-         id="stop8223" />
-      <stop
-         style="stop-color:#9a5500;stop-opacity:1"
-         offset="1"
-         id="stop8225" />
-      <a:midPointstop
-         offset="0"
-         style="stop-color:#ECB300" />
-      <a:midPointstop
-         offset="0.5"
-         style="stop-color:#ECB300" />
-      <a:midPointstop
-         offset="0.3"
-         style="stop-color:#ECB300" />
-      <a:midPointstop
-         offset="0.5"
-         style="stop-color:#ECB300" />
-      <a:midPointstop
-         offset="0.9"
-         style="stop-color:#C96B00" />
-      <a:midPointstop
-         offset="0.5"
-         style="stop-color:#C96B00" />
-      <a:midPointstop
-         offset="1"
-         style="stop-color:#9A5500" />
-    </radialGradient>
-    <radialGradient
-       cx="284.60001"
-       cy="172.60001"
-       r="6.5"
-       fx="284.60001"
-       fy="172.60001"
-       id="rg2020"
-       xlink:href="#XMLID_3448_"
-       gradientUnits="userSpaceOnUse"
-       gradientTransform="matrix(2.513992,0,0,2.347576,-689.1621,-378.5717)" />
-    <linearGradient
-       x1="158.10001"
-       y1="123"
-       x2="164.2"
-       y2="126.6"
-       id="XMLID_3447_"
-       gradientUnits="userSpaceOnUse">
-      <stop
-         style="stop-color:#ecd600;stop-opacity:1"
-         offset="0"
-         id="stop8204" />
-      <stop
-         style="stop-color:#ffffb3;stop-opacity:1"
-         offset="0.30000001"
-         id="stop8206" />
-      <stop
-         style="stop-color:white;stop-opacity:1"
-         offset="1"
-         id="stop8208" />
-      <a:midPointstop
-         offset="0"
-         style="stop-color:#ECD600" />
-      <a:midPointstop
-         offset="0.5"
-         style="stop-color:#ECD600" />
-      <a:midPointstop
-         offset="0.3"
-         style="stop-color:#FFFFB3" />
-      <a:midPointstop
-         offset="0.5"
-         style="stop-color:#FFFFB3" />
-      <a:midPointstop
-         offset="1"
-         style="stop-color:#FFFFFF" />
-    </linearGradient>
-    <linearGradient
-       x1="158.10001"
-       y1="123"
-       x2="164.2"
-       y2="126.6"
-       id="lg2026"
-       xlink:href="#XMLID_3447_"
-       gradientUnits="userSpaceOnUse"
-       gradientTransform="matrix(1.2,0,0,1.2,-175.9,-114.6)" />
-    <radialGradient
-       cx="280.89999"
-       cy="163.7"
-       r="10.1"
-       fx="280.89999"
-       fy="163.7"
-       id="XMLID_3446_"
-       gradientUnits="userSpaceOnUse"
-       gradientTransform="matrix(1.4,0,0,1.4,-237.3,-126.8)">
-      <stop
-         style="stop-color:white;stop-opacity:1"
-         offset="0"
-         id="stop8197" />
-      <stop
-         style="stop-color:#fff95e;stop-opacity:1"
-         offset="1"
-         id="stop8199" />
-      <a:midPointstop
-         offset="0"
-         style="stop-color:#FFFFFF" />
-      <a:midPointstop
-         offset="0.5"
-         style="stop-color:#FFFFFF" />
-      <a:midPointstop
-         offset="1"
-         style="stop-color:#FFF95E" />
-    </radialGradient>
-    <radialGradient
-       cx="280.89999"
-       cy="163.7"
-       r="10.1"
-       fx="280.89999"
-       fy="163.7"
-       id="rg2029"
-       xlink:href="#XMLID_3446_"
-       gradientUnits="userSpaceOnUse"
-       gradientTransform="matrix(1.7,0,0,1.7,-457.5,-266.8)" />
-    <linearGradient
-       x1="156.5"
-       y1="122.7"
-       x2="180.10001"
-       y2="122.7"
-       id="XMLID_3445_"
-       gradientUnits="userSpaceOnUse">
-      <stop
-         style="stop-color:#ecb300;stop-opacity:1"
-         offset="0"
-         id="stop8184" />
-      <stop
-         style="stop-color:#ffe900;stop-opacity:1"
-         offset="0.2"
-         id="stop8186" />
-      <stop
-         style="stop-color:#ffffb3;stop-opacity:1"
-         offset="0.30000001"
-         id="stop8188" />
-      <stop
-         style="stop-color:#ffe900;stop-opacity:1"
-         offset="0.40000001"
-         id="stop8190" />
-      <stop
-         style="stop-color:#d68100;stop-opacity:1"
-         offset="1"
-         id="stop8192" />
-      <a:midPointstop
-         offset="0"
-         style="stop-color:#ECB300" />
-      <a:midPointstop
-         offset="0.5"
-         style="stop-color:#ECB300" />
-      <a:midPointstop
-         offset="0.2"
-         style="stop-color:#FFE900" />
-      <a:midPointstop
-         offset="0.5"
-         style="stop-color:#FFE900" />
-      <a:midPointstop
-         offset="0.3"
-         style="stop-color:#FFFFB3" />
-      <a:midPointstop
-         offset="0.5"
-         style="stop-color:#FFFFB3" />
-      <a:midPointstop
-         offset="0.4"
-         style="stop-color:#FFE900" />
-      <a:midPointstop
-         offset="0.5"
-         style="stop-color:#FFE900" />
-      <a:midPointstop
-         offset="1"
-         style="stop-color:#D68100" />
-    </linearGradient>
-    <linearGradient
-       x1="156.5"
-       y1="122.7"
-       x2="180.10001"
-       y2="122.7"
-       id="lg2032"
-       xlink:href="#XMLID_3445_"
-       gradientUnits="userSpaceOnUse"
-       gradientTransform="matrix(1.2,0,0,1.2,-175.9,-114.6)" />
-    <linearGradient
-       x1="156.39999"
-       y1="115.4"
-       x2="180.10001"
-       y2="115.4"
-       id="XMLID_3444_"
-       gradientUnits="userSpaceOnUse">
-      <stop
-         style="stop-color:#ecb300;stop-opacity:1"
-         offset="0"
-         id="stop8171" />
-      <stop
-         style="stop-color:#ffe900;stop-opacity:1"
-         offset="0.2"
-         id="stop8173" />
-      <stop
-         style="stop-color:#ffffb3;stop-opacity:1"
-         offset="0.30000001"
-         id="stop8175" />
-      <stop
-         style="stop-color:#ffe900;stop-opacity:1"
-         offset="0.40000001"
-         id="stop8177" />
-      <stop
-         style="stop-color:#d68100;stop-opacity:1"
-         offset="1"
-         id="stop8179" />
-      <a:midPointstop
-         offset="0"
-         style="stop-color:#ECB300" />
-      <a:midPointstop
-         offset="0.5"
-         style="stop-color:#ECB300" />
-      <a:midPointstop
-         offset="0.2"
-         style="stop-color:#FFE900" />
-      <a:midPointstop
-         offset="0.5"
-         style="stop-color:#FFE900" />
-      <a:midPointstop
-         offset="0.3"
-         style="stop-color:#FFFFB3" />
-      <a:midPointstop
-         offset="0.5"
-         style="stop-color:#FFFFB3" />
-      <a:midPointstop
-         offset="0.4"
-         style="stop-color:#FFE900" />
-      <a:midPointstop
-         offset="0.5"
-         style="stop-color:#FFE900" />
-      <a:midPointstop
-         offset="1"
-         style="stop-color:#D68100" />
-    </linearGradient>
-    <linearGradient
-       x1="156.39999"
-       y1="115.4"
-       x2="180.10001"
-       y2="115.4"
-       id="lg2035"
-       xlink:href="#XMLID_3444_"
-       gradientUnits="userSpaceOnUse"
-       gradientTransform="matrix(1.2,0,0,1.2,-175.9,-114.6)" />
-    <linearGradient
-       x1="379.70001"
-       y1="167.89999"
-       x2="383.89999"
-       y2="172.89999"
-       id="lg4286_"
-       gradientUnits="userSpaceOnUse"
-       gradientTransform="matrix(0.8,0.2,-0.2,0.8,78.8,38.1)">
-      <stop
-         style="stop-color:white;stop-opacity:1"
-         offset="0"
-         id="s16159" />
-      <stop
-         style="stop-color:white;stop-opacity:1"
-         offset="0.1"
-         id="s16161" />
-      <stop
-         style="stop-color:#737373;stop-opacity:1"
-         offset="1"
-         id="s16163" />
-      <ns:midPointStop
-         style="stop-color:#FFFFFF"
-         offset="0" />
-      <ns:midPointStop
-         style="stop-color:#FFFFFF"
-         offset="0.5" />
-      <ns:midPointStop
-         style="stop-color:#FFFFFF"
-         offset="0.1" />
-      <ns:midPointStop
-         style="stop-color:#FFFFFF"
-         offset="0.5" />
-      <ns:midPointStop
-         style="stop-color:#737373"
-         offset="1" />
-    </linearGradient>
-    <linearGradient
-       x1="379.60001"
-       y1="167.8"
-       x2="383.79999"
-       y2="172"
-       id="lg6416"
-       xlink:href="#lg4286_"
-       gradientUnits="userSpaceOnUse"
-       gradientTransform="matrix(2.622156,0.623859,-0.623859,2.62182,-882.9706,-673.7921)" />
-    <linearGradient
-       x1="384.20001"
-       y1="169.8"
-       x2="384.79999"
-       y2="170.39999"
-       id="lg4285_"
-       gradientUnits="userSpaceOnUse"
-       gradientTransform="matrix(0.8,0.2,-0.2,0.8,78.8,38.1)">
-      <stop
-         style="stop-color:#737373;stop-opacity:1"
-         offset="0"
-         id="s16152" />
-      <stop
-         style="stop-color:#d9d9d9;stop-opacity:1"
-         offset="1"
-         id="s16154" />
-      <ns:midPointStop
-         style="stop-color:#737373"
-         offset="0" />
-      <ns:midPointStop
-         style="stop-color:#737373"
-         offset="0.5" />
-      <ns:midPointStop
-         style="stop-color:#D9D9D9"
-         offset="1" />
-    </linearGradient>
-    <linearGradient
-       x1="384.20001"
-       y1="169.8"
-       x2="384.79999"
-       y2="170.39999"
-       id="lg6453"
-       xlink:href="#lg4285_"
-       gradientUnits="userSpaceOnUse"
-       gradientTransform="matrix(2.6,0.6,-0.6,2.6,-883,-673.8)" />
-    <linearGradient
-       x1="380.5"
-       y1="172.60001"
-       x2="382.79999"
-       y2="173.7"
-       id="lg4284_"
-       gradientUnits="userSpaceOnUse"
-       gradientTransform="matrix(0.8,0.2,-0.2,0.8,78.8,38.1)">
-      <stop
-         style="stop-color:gray;stop-opacity:1"
-         offset="0"
-         id="s16145" />
-      <stop
-         style="stop-color:#e5e5e5;stop-opacity:1"
-         offset="1"
-         id="s16147" />
-      <ns:midPointStop
-         style="stop-color:#808080"
-         offset="0" />
-      <ns:midPointStop
-         style="stop-color:#808080"
-         offset="0.5" />
-      <ns:midPointStop
-         style="stop-color:#E5E5E5"
-         offset="1" />
-    </linearGradient>
-    <linearGradient
-       x1="380.5"
-       y1="172.60001"
-       x2="382.79999"
-       y2="173.7"
-       id="lg6456"
-       xlink:href="#lg4284_"
-       gradientUnits="userSpaceOnUse"
-       gradientTransform="matrix(2.6,0.6,-0.6,2.6,-883,-673.8)" />
-    <radialGradient
-       cx="347.29999"
-       cy="244.5"
-       r="5.1999998"
-       fx="347.29999"
-       fy="244.5"
-       id="lg4282_"
-       gradientUnits="userSpaceOnUse"
-       gradientTransform="matrix(3.4,0,0,3.4,-1148,-802)">
-      <stop
-         style="stop-color:#333;stop-opacity:1"
-         offset="0"
-         id="s16135" />
-      <stop
-         style="stop-color:#999;stop-opacity:1"
-         offset="1"
-         id="s16137" />
-      <ns:midPointStop
-         style="stop-color:#333333"
-         offset="0" />
-      <ns:midPointStop
-         style="stop-color:#333333"
-         offset="0.5" />
-      <ns:midPointStop
-         style="stop-color:#999999"
-         offset="1" />
-    </radialGradient>
-    <linearGradient
-       x1="310.39999"
-       y1="397.70001"
-       x2="310.89999"
-       y2="399.5"
-       id="lg4280_"
-       gradientUnits="userSpaceOnUse"
-       gradientTransform="matrix(0.7,-0.7,0.7,0.7,-153.4,180.6)">
-      <stop
-         style="stop-color:#ffcd00;stop-opacity:1"
-         offset="0"
-         id="s16111" />
-      <stop
-         style="stop-color:#ffffb3;stop-opacity:1"
-         offset="0.60000002"
-         id="s16113" />
-      <stop
-         style="stop-color:#ffffb3;stop-opacity:1"
-         offset="1"
-         id="s16115" />
-      <ns:midPointStop
-         style="stop-color:#FFCD00"
-         offset="0" />
-      <ns:midPointStop
-         style="stop-color:#FFCD00"
-         offset="0.5" />
-      <ns:midPointStop
-         style="stop-color:#FFFFB3"
-         offset="0.6" />
-      <ns:midPointStop
-         style="stop-color:#FFFFB3"
-         offset="0.5" />
-      <ns:midPointStop
-         style="stop-color:#FFFFB3"
-         offset="1" />
-    </linearGradient>
-    <linearGradient
-       x1="310.39999"
-       y1="397.70001"
-       x2="310.89999"
-       y2="399.5"
-       id="lg6467"
-       xlink:href="#lg4280_"
-       gradientUnits="userSpaceOnUse"
-       gradientTransform="matrix(2.4,-2.4,2.4,2.4,-1663.6,-195)" />
-    <linearGradient
-       x1="310.89999"
-       y1="395.79999"
-       x2="313.29999"
-       y2="403.10001"
-       id="lg4279_"
-       gradientUnits="userSpaceOnUse"
-       gradientTransform="matrix(0.7,-0.7,0.7,0.7,-153.4,180.6)">
-      <stop
-         style="stop-color:#ffffb3;stop-opacity:1"
-         offset="0"
-         id="s16100" />
-      <stop
-         style="stop-color:#ffffb3;stop-opacity:1"
-         offset="0.40000001"
-         id="s16102" />
-      <stop
-         style="stop-color:#ffcd00;stop-opacity:1"
-         offset="0.89999998"
-         id="s16104" />
-      <stop
-         style="stop-color:#ffcd00;stop-opacity:1"
-         offset="1"
-         id="s16106" />
-      <ns:midPointStop
-         style="stop-color:#FFFFB3"
-         offset="0" />
-      <ns:midPointStop
-         style="stop-color:#FFFFB3"
-         offset="0.5" />
-      <ns:midPointStop
-         style="stop-color:#FFFFB3"
-         offset="0.4" />
-      <ns:midPointStop
-         style="stop-color:#FFFFB3"
-         offset="0.5" />
-      <ns:midPointStop
-         style="stop-color:#FFCD00"
-         offset="0.9" />
-      <ns:midPointStop
-         style="stop-color:#FFCD00"
-         offset="0.5" />
-      <ns:midPointStop
-         style="stop-color:#FFCD00"
-         offset="1" />
-    </linearGradient>
-    <linearGradient
-       x1="310.89999"
-       y1="395.79999"
-       x2="313.29999"
-       y2="403.10001"
-       id="lg6465"
-       xlink:href="#lg4279_"
-       gradientUnits="userSpaceOnUse"
-       gradientTransform="matrix(2.4,-2.4,2.4,2.4,-1663.6,-195)" />
-    <linearGradient
-       x1="307.79999"
-       y1="395.20001"
-       x2="313.79999"
-       y2="413.60001"
-       id="lg4278_"
-       gradientUnits="userSpaceOnUse"
-       gradientTransform="matrix(0.7,-0.7,0.7,0.7,-153.4,180.6)">
-      <stop
-         style="stop-color:#ffffb3;stop-opacity:1"
-         offset="0"
-         id="s16091" />
-      <stop
-         style="stop-color:#fcd72f;stop-opacity:1"
-         offset="0.40000001"
-         id="s16093" />
-      <stop
-         style="stop-color:#ffcd00;stop-opacity:1"
-         offset="1"
-         id="s16095" />
-      <ns:midPointStop
-         style="stop-color:#FFFFB3"
-         offset="0" />
-      <ns:midPointStop
-         style="stop-color:#FFFFB3"
-         offset="0.5" />
-      <ns:midPointStop
-         style="stop-color:#FCD72F"
-         offset="0.4" />
-      <ns:midPointStop
-         style="stop-color:#FCD72F"
-         offset="0.5" />
-      <ns:midPointStop
-         style="stop-color:#FFCD00"
-         offset="1" />
-    </linearGradient>
-    <linearGradient
-       x1="306.5"
-       y1="393"
-       x2="309"
-       y2="404"
-       id="lg6400"
-       xlink:href="#lg4278_"
-       gradientUnits="userSpaceOnUse"
-       gradientTransform="matrix(2.4,-2.4,2.4,2.4,-1663.6,-195)" />
-    <linearGradient
-       x1="352.10001"
-       y1="253.60001"
-       x2="348.5"
-       y2="237.8"
-       id="lg4276_"
-       gradientUnits="userSpaceOnUse"
-       gradientTransform="matrix(3.4,0,0,3.4,-1148,-802)">
-      <stop
-         style="stop-color:#ffff87;stop-opacity:1"
-         offset="0"
-         id="s16077" />
-      <stop
-         style="stop-color:#ffad00;stop-opacity:1"
-         offset="1"
-         id="s16079" />
-      <ns:midPointStop
-         style="stop-color:#FFFF87"
-         offset="0" />
-      <ns:midPointStop
-         style="stop-color:#FFFF87"
-         offset="0.5" />
-      <ns:midPointStop
-         style="stop-color:#FFAD00"
-         offset="1" />
-    </linearGradient>
-    <linearGradient
-       x1="335.60001"
-       y1="354.79999"
-       x2="337.89999"
-       y2="354.79999"
-       id="lg4275_"
-       gradientUnits="userSpaceOnUse"
-       gradientTransform="matrix(0.9,-0.5,0.5,0.9,-121.7,105.1)">
-      <stop
-         style="stop-color:#d9d9d9;stop-opacity:1"
-         offset="0"
-         id="s16057" />
-      <stop
-         style="stop-color:white;stop-opacity:1"
-         offset="0.80000001"
-         id="s16059" />
-      <stop
-         style="stop-color:white;stop-opacity:1"
-         offset="1"
-         id="s16061" />
-      <ns:midPointStop
-         style="stop-color:#D9D9D9"
-         offset="0" />
-      <ns:midPointStop
-         style="stop-color:#D9D9D9"
-         offset="0.5" />
-      <ns:midPointStop
-         style="stop-color:#FFFFFF"
-         offset="0.8" />
-      <ns:midPointStop
-         style="stop-color:#FFFFFF"
-         offset="0.5" />
-      <ns:midPointStop
-         style="stop-color:#FFFFFF"
-         offset="1" />
-    </linearGradient>
-    <linearGradient
-       x1="335.60001"
-       y1="354.79999"
-       x2="337.89999"
-       y2="354.79999"
-       id="lg6463"
-       xlink:href="#lg4275_"
-       gradientUnits="userSpaceOnUse"
-       gradientTransform="matrix(2.9,-1.7,1.7,2.9,-1557,-448.7)" />
-    <linearGradient
-       x1="337.39999"
-       y1="353.10001"
-       x2="339.39999"
-       y2="357.10001"
-       id="lg4274_"
-       gradientUnits="userSpaceOnUse"
-       gradientTransform="matrix(0.9,-0.5,0.5,0.9,-121.7,105.1)">
-      <stop
-         style="stop-color:white;stop-opacity:1"
-         offset="0"
-         id="s16048" />
-      <stop
-         style="stop-color:white;stop-opacity:1"
-         offset="0.1"
-         id="s16050" />
-      <stop
-         style="stop-color:#ccc;stop-opacity:1"
-         offset="1"
-         id="s16052" />
-      <ns:midPointStop
-         style="stop-color:#FFFFFF"
-         offset="0" />
-      <ns:midPointStop
-         style="stop-color:#FFFFFF"
-         offset="0.5" />
-      <ns:midPointStop
-         style="stop-color:#FFFFFF"
-         offset="0.1" />
-      <ns:midPointStop
-         style="stop-color:#FFFFFF"
-         offset="0.5" />
-      <ns:midPointStop
-         style="stop-color:#CCCCCC"
-         offset="1" />
-    </linearGradient>
-    <linearGradient
-       x1="337.39999"
-       y1="353.10001"
-       x2="339.39999"
-       y2="357.10001"
-       id="lg6461"
-       xlink:href="#lg4274_"
-       gradientUnits="userSpaceOnUse"
-       gradientTransform="matrix(2.9,-1.7,1.7,2.9,-1557,-448.7)" />
-    <linearGradient
-       x1="334.39999"
-       y1="355.5"
-       x2="335.5"
-       y2="356.79999"
-       id="lg4273_"
-       gradientUnits="userSpaceOnUse"
-       gradientTransform="matrix(0.9,-0.5,0.5,0.9,-121.7,105.1)">
-      <stop
-         style="stop-color:white;stop-opacity:1"
-         offset="0"
-         id="s16041" />
-      <stop
-         style="stop-color:#ccc;stop-opacity:1"
-         offset="1"
-         id="s16043" />
-      <ns:midPointStop
-         style="stop-color:#FFFFFF"
-         offset="5.6e-003" />
-      <ns:midPointStop
-         style="stop-color:#FFFFFF"
-         offset="0.5" />
-      <ns:midPointStop
-         style="stop-color:#CCCCCC"
-         offset="1" />
-    </linearGradient>
-    <linearGradient
-       x1="334.39999"
-       y1="355.5"
-       x2="335.5"
-       y2="356.79999"
-       id="lg6381"
-       xlink:href="#lg4273_"
-       gradientUnits="userSpaceOnUse"
-       gradientTransform="matrix(2.9,-1.7,1.7,2.9,-1557,-448.7)" />
-    <linearGradient
-       x1="348.39999"
-       y1="247.39999"
-       x2="354.10001"
-       y2="242"
-       id="lg4271_"
-       gradientUnits="userSpaceOnUse"
-       gradientTransform="matrix(3.4,0,0,3.4,-1148,-802)">
-      <stop
-         style="stop-color:#f2f2f2;stop-opacity:1"
-         offset="0"
-         id="s16025" />
-      <stop
-         style="stop-color:#9e9e9e;stop-opacity:1"
-         offset="0.40000001"
-         id="s16027" />
-      <stop
-         style="stop-color:black;stop-opacity:1"
-         offset="1"
-         id="s16029" />
-      <ns:midPointStop
-         style="stop-color:#F2F2F2"
-         offset="0" />
-      <ns:midPointStop
-         style="stop-color:#F2F2F2"
-         offset="0.5" />
-      <ns:midPointStop
-         style="stop-color:#000000"
-         offset="1" />
-    </linearGradient>
-    <linearGradient
-       x1="351.29999"
-       y1="257.29999"
-       x2="346.29999"
-       y2="235.5"
-       id="lg4270_"
-       gradientUnits="userSpaceOnUse">
-      <stop
-         style="stop-color:#ffff87;stop-opacity:1"
-         offset="0"
-         id="s16007" />
-      <stop
-         style="stop-color:#ffad00;stop-opacity:1"
-         offset="1"
-         id="s16009" />
-      <ns:midPointStop
-         style="stop-color:#FFFF87"
-         offset="0" />
-      <ns:midPointStop
-         style="stop-color:#FFFF87"
-         offset="0.5" />
-      <ns:midPointStop
-         style="stop-color:#FFAD00"
-         offset="1" />
-    </linearGradient>
-    <linearGradient
-       x1="351.29999"
-       y1="257.29999"
-       x2="346.29999"
-       y2="235.5"
-       id="lg6459"
-       xlink:href="#lg4270_"
-       gradientUnits="userSpaceOnUse"
-       gradientTransform="matrix(3.4,0,0,3.4,-1148,-802)" />
-    <linearGradient
-       x1="43.799999"
-       y1="32.5"
-       x2="63.299999"
-       y2="66.400002"
-       id="XMLID_2708_"
-       gradientUnits="userSpaceOnUse">
-      <stop
-         style="stop-color:white;stop-opacity:1"
-         offset="0"
-         id="stop75318" />
-      <stop
-         style="stop-color:#fffcea;stop-opacity:1"
-         offset="1"
-         id="stop75320" />
-      <a:midPointStop
-         style="stop-color:#FFFFFF"
-         offset="0" />
-      <a:midPointStop
-         style="stop-color:#FFFFFF"
-         offset="0.5" />
-      <a:midPointStop
-         style="stop-color:#FFFCEA"
-         offset="1" />
-    </linearGradient>
-    <linearGradient
-       x1="43.799999"
-       y1="32.5"
-       x2="63.299999"
-       y2="66.400002"
-       id="lg1907"
-       xlink:href="#XMLID_2708_"
-       gradientUnits="userSpaceOnUse"
-       gradientTransform="translate(-29,-22.6)" />
-    <linearGradient
-       x1="52.5"
-       y1="40.400002"
-       x2="58.200001"
-       y2="64"
-       id="XMLID_2707_"
-       gradientUnits="userSpaceOnUse">
-      <stop
-         style="stop-color:#ffdea0;stop-opacity:1"
-         offset="0"
-         id="stop75305" />
-      <stop
-         style="stop-color:#ffd89e;stop-opacity:1"
-         offset="0.30000001"
-         id="stop75307" />
-      <stop
-         style="stop-color:#ffd79e;stop-opacity:1"
-         offset="0.30000001"
-         id="stop75309" />
-      <stop
-         style="stop-color:#dbaf6d;stop-opacity:1"
-         offset="0.69999999"
-         id="stop75311" />
-      <stop
-         style="stop-color:#6f4c24;stop-opacity:1"
-         offset="1"
-         id="stop75313" />
-      <a:midPointStop
-         style="stop-color:#FFDEA0"
-         offset="0" />
-      <a:midPointStop
-         style="stop-color:#FFDEA0"
-         offset="0.6" />
-      <a:midPointStop
-         style="stop-color:#FFD79E"
-         offset="0.3" />
-      <a:midPointStop
-         style="stop-color:#FFD79E"
-         offset="0.5" />
-      <a:midPointStop
-         style="stop-color:#DBAF6D"
-         offset="0.7" />
-      <a:midPointStop
-         style="stop-color:#DBAF6D"
-         offset="0.5" />
-      <a:midPointStop
-         style="stop-color:#6F4C24"
-         offset="1" />
-    </linearGradient>
-    <linearGradient
-       x1="52.5"
-       y1="40.400002"
-       x2="58.200001"
-       y2="64"
-       id="lg1910"
-       xlink:href="#XMLID_2707_"
-       gradientUnits="userSpaceOnUse"
-       gradientTransform="translate(-29,-22.6)" />
-    <linearGradient
-       x1="58"
-       y1="73.199997"
-       x2="44.5"
-       y2="19"
-       id="XMLID_2704_"
-       gradientUnits="userSpaceOnUse"
-       gradientTransform="translate(-29,-22.6)">
-      <stop
-         style="stop-color:#d4a96c;stop-opacity:1"
-         offset="0.5"
-         id="stop75284" />
-      <stop
-         style="stop-color:#dcb273;stop-opacity:1"
-         offset="0.60000002"
-         id="stop75286" />
-      <stop
-         style="stop-color:#f0ca87;stop-opacity:1"
-         offset="0.80000001"
-         id="stop75288" />
-      <stop
-         style="stop-color:#ffdc96;stop-opacity:1"
-         offset="0.69999999"
-         id="stop75290" />
-      <stop
-         style="stop-color:#c18a42;stop-opacity:1"
-         offset="1"
-         id="stop75292" />
-      <a:midPointStop
-         style="stop-color:#D4A96C"
-         offset="0.5" />
-      <a:midPointStop
-         style="stop-color:#D4A96C"
-         offset="0.6" />
-      <a:midPointStop
-         style="stop-color:#FFDC96"
-         offset="0.7" />
-      <a:midPointStop
-         style="stop-color:#FFDC96"
-         offset="0.5" />
-      <a:midPointStop
-         style="stop-color:#C18A42"
-         offset="1" />
-    </linearGradient>
-    <linearGradient
-       x1="53.700001"
-       y1="32"
-       x2="53.700001"
-       y2="64.599998"
-       id="XMLID_2703_"
-       gradientUnits="userSpaceOnUse">
-      <stop
-         style="stop-color:#e5c9b0;stop-opacity:1"
-         offset="0"
-         id="stop75268" />
-      <stop
-         style="stop-color:#e5c9b0;stop-opacity:1"
-         offset="0.40000001"
-         id="stop75270" />
-      <stop
-         style="stop-color:#c0aa94;stop-opacity:1"
-         offset="1"
-         id="stop75272" />
-      <a:midPointStop
-         style="stop-color:#E5C9B0"
-         offset="0" />
-      <a:midPointStop
-         style="stop-color:#E5C9B0"
-         offset="0.5" />
-      <a:midPointStop
-         style="stop-color:#E5C9B0"
-         offset="0.4" />
-      <a:midPointStop
-         style="stop-color:#E5C9B0"
-         offset="0.5" />
-      <a:midPointStop
-         style="stop-color:#C0AA94"
-         offset="1" />
-    </linearGradient>
-    <linearGradient
-       x1="53.700001"
-       y1="32"
-       x2="53.700001"
-       y2="64.599998"
-       id="lg1916"
-       xlink:href="#XMLID_2703_"
-       gradientUnits="userSpaceOnUse"
-       gradientTransform="translate(-29,-22.6)" />
-    <linearGradient
-       x1="224.31"
-       y1="19.450001"
-       x2="214.33"
-       y2="11.46"
-       id="XMLID_419_"
-       gradientUnits="userSpaceOnUse">
-      <stop
-         style="stop-color:#404040;stop-opacity:1"
-         offset="0"
-         id="s1903" />
-      <stop
-         style="stop-color:#6d6d6d;stop-opacity:1"
-         offset="0.33000001"
-         id="s1905" />
-      <stop
-         style="stop-color:#e9e9e9;stop-opacity:1"
-         offset="1"
-         id="s1907" />
-      <a:midPointStop
-         offset="0"
-         style="stop-color:#404040" />
-      <a:midPointStop
-         offset="0.5"
-         style="stop-color:#404040" />
-      <a:midPointStop
-         offset="0.33"
-         style="stop-color:#6D6D6D" />
-      <a:midPointStop
-         offset="0.5"
-         style="stop-color:#6D6D6D" />
-      <a:midPointStop
-         offset="1"
-         style="stop-color:#E9E9E9" />
-    </linearGradient>
-    <linearGradient
-       x1="221.84"
-       y1="32.779999"
-       x2="212.2"
-       y2="20.27"
-       id="lg1988"
-       xlink:href="#XMLID_419_"
-       gradientUnits="userSpaceOnUse"
-       gradientTransform="matrix(1.33,0,0,1.31,-274.2,-5.2)" />
-    <linearGradient
-       x1="228.35001"
-       y1="33.279999"
-       x2="215.42999"
-       y2="33.279999"
-       id="lg1900"
-       gradientUnits="userSpaceOnUse">
-      <stop
-         style="stop-color:white;stop-opacity:1"
-         offset="0"
-         id="s1902" />
-      <stop
-         style="stop-color:white;stop-opacity:0"
-         offset="1"
-         id="s1906" />
-      <a:midPointStop
-         style="stop-color:#575757"
-         offset="0" />
-      <a:midPointStop
-         style="stop-color:#575757"
-         offset="0.5" />
-      <a:midPointStop
-         style="stop-color:#6D6D6D"
-         offset="0.33" />
-      <a:midPointStop
-         style="stop-color:#6D6D6D"
-         offset="0.5" />
-      <a:midPointStop
-         style="stop-color:#D3D3D3"
-         offset="1" />
-    </linearGradient>
-    <linearGradient
-       x1="234.81"
-       y1="33.279999"
-       x2="228.27"
-       y2="33.279999"
-       id="lg1908"
-       xlink:href="#lg1900"
-       gradientUnits="userSpaceOnUse"
-       gradientTransform="matrix(1.33,0,0,1.31,-274.2,-5.2)" />
-    <linearGradient
-       x1="228.35001"
-       y1="33.279999"
-       x2="215.42999"
-       y2="33.279999"
-       id="XMLID_416_"
-       gradientUnits="userSpaceOnUse">
-      <stop
-         style="stop-color:#575757;stop-opacity:1"
-         offset="0"
-         id="s1874" />
-      <stop
-         style="stop-color:#6d6d6d;stop-opacity:1"
-         offset="0.33000001"
-         id="s1876" />
-      <stop
-         style="stop-color:#d3d3d3;stop-opacity:1"
-         offset="1"
-         id="s1878" />
-      <a:midPointStop
-         offset="0"
-         style="stop-color:#575757" />
-      <a:midPointStop
-         offset="0.5"
-         style="stop-color:#575757" />
-      <a:midPointStop
-         offset="0.33"
-         style="stop-color:#6D6D6D" />
-      <a:midPointStop
-         offset="0.5"
-         style="stop-color:#6D6D6D" />
-      <a:midPointStop
-         offset="1"
-         style="stop-color:#D3D3D3" />
-    </linearGradient>
-    <linearGradient
-       x1="228.35001"
-       y1="33.279999"
-       x2="215.42999"
-       y2="33.279999"
-       id="lg1991"
-       xlink:href="#XMLID_416_"
-       gradientUnits="userSpaceOnUse"
-       gradientTransform="matrix(1.33,0,0,1.31,-274.2,-5.2)" />
-    <radialGradient
-       cx="603.19"
-       cy="230.77"
-       r="1.67"
-       fx="603.19"
-       fy="230.77"
-       id="x5010_"
-       gradientUnits="userSpaceOnUse"
-       gradientTransform="matrix(1.1,0,0,1.1,-54.33,-75.4)">
-      <stop
-         style="stop-color:#c9ffc9;stop-opacity:1"
-         offset="0"
-         id="stop29201" />
-      <stop
-         style="stop-color:#23a11f;stop-opacity:1"
-         offset="1"
-         id="stop29203" />
-      <a:midPointStop
-         offset="0"
-         style="stop-color:#C9FFC9" />
-      <a:midPointStop
-         offset="0.5"
-         style="stop-color:#C9FFC9" />
-      <a:midPointStop
-         offset="1"
-         style="stop-color:#23A11F" />
-    </radialGradient>
-    <radialGradient
-       cx="603.19"
-       cy="230.77"
-       r="1.67"
-       fx="603.19"
-       fy="230.77"
-       id="radialGradient5711"
-       xlink:href="#x5010_"
-       gradientUnits="userSpaceOnUse"
-       gradientTransform="matrix(1.23,0,0,1.23,-709.93,-245.02)" />
-    <linearGradient
-       x1="592.31"
-       y1="162.60001"
-       x2="609.32001"
-       y2="145.59"
-       id="lg5722"
-       xlink:href="#x5003_"
-       gradientUnits="userSpaceOnUse"
-       gradientTransform="matrix(1.12,0,0,1.12,-649.08,-160.62)" />
-    <linearGradient
-       x1="601.48999"
-       y1="170.16"
-       x2="613.84003"
-       y2="170.16"
-       id="x5002_"
-       gradientUnits="userSpaceOnUse">
-      <stop
-         style="stop-color:#d9d9d9;stop-opacity:1"
-         offset="0"
-         id="stop29134" />
-      <stop
-         style="stop-color:white;stop-opacity:1"
-         offset="0.2"
-         id="stop29136" />
-      <stop
-         style="stop-color:#999;stop-opacity:1"
-         offset="1"
-         id="stop29138" />
-      <a:midPointStop
-         offset="0"
-         style="stop-color:#D9D9D9" />
-      <a:midPointStop
-         offset="0.5"
-         style="stop-color:#D9D9D9" />
-      <a:midPointStop
-         offset="0.20"
-         style="stop-color:#FFFFFF" />
-      <a:midPointStop
-         offset="0.5"
-         style="stop-color:#FFFFFF" />
-      <a:midPointStop
-         offset="1"
-         style="stop-color:#999999" />
-    </linearGradient>
-    <linearGradient
-       x1="601.48999"
-       y1="170.16"
-       x2="613.84003"
-       y2="170.16"
-       id="lg5725"
-       xlink:href="#x5002_"
-       gradientUnits="userSpaceOnUse"
-       gradientTransform="matrix(1.12,0,0,1.12,-649.08,-160.62)" />
-    <linearGradient
-       x1="592.20001"
-       y1="156.45"
-       x2="609.98999"
-       y2="174.23"
-       id="x5004_"
-       gradientUnits="userSpaceOnUse"
-       gradientTransform="matrix(1.12,0,0,1.12,-649.08,-160.62)">
-      <stop
-         style="stop-color:#d9d9d9;stop-opacity:1"
-         offset="0"
-         id="stop29157" />
-      <stop
-         style="stop-color:white;stop-opacity:1"
-         offset="1"
-         id="stop29159" />
-      <a:midPointStop
-         offset="0"
-         style="stop-color:#D9D9D9" />
-      <a:midPointStop
-         offset="0.5"
-         style="stop-color:#D9D9D9" />
-      <a:midPointStop
-         offset="1"
-         style="stop-color:#FFFFFF" />
-    </linearGradient>
-    <linearGradient
-       x1="592.20001"
-       y1="156.45"
-       x2="609.98999"
-       y2="174.23"
-       id="lg5728"
-       xlink:href="#x5004_"
-       gradientUnits="userSpaceOnUse"
-       gradientTransform="matrix(1.12,0,0,1.12,-649.08,-160.62)" />
-    <linearGradient
-       x1="592.31"
-       y1="162.60001"
-       x2="609.32001"
-       y2="145.59"
-       id="x5003_"
-       gradientUnits="userSpaceOnUse">
-      <stop
-         style="stop-color:#f2f2f2;stop-opacity:1"
-         offset="0"
-         id="stop29143" />
-      <stop
-         style="stop-color:#e5e5e5;stop-opacity:1"
-         offset="1"
-         id="stop29145" />
-      <a:midPointStop
-         offset="0"
-         style="stop-color:#F2F2F2" />
-      <a:midPointStop
-         offset="0.5"
-         style="stop-color:#F2F2F2" />
-      <a:midPointStop
-         offset="1"
-         style="stop-color:#E5E5E5" />
-    </linearGradient>
-    <linearGradient
-       x1="592.31"
-       y1="162.60001"
-       x2="609.32001"
-       y2="145.59"
-       id="lg5732"
-       xlink:href="#x5003_"
-       gradientUnits="userSpaceOnUse"
-       gradientTransform="matrix(1.12,0,0,1.12,-649.08,-160.62)" />
-    <linearGradient
-       x1="592.20001"
-       y1="156.45"
-       x2="609.98999"
-       y2="174.24001"
-       id="x5000_"
-       gradientUnits="userSpaceOnUse"
-       gradientTransform="matrix(1.12,0,0,1.12,-649.08,-160.62)">
-      <stop
-         style="stop-color:#d9d9d9;stop-opacity:1"
-         offset="0"
-         id="stop29124" />
-      <stop
-         style="stop-color:white;stop-opacity:1"
-         offset="1"
-         id="stop29126" />
-      <a:midPointStop
-         offset="0"
-         style="stop-color:#D9D9D9" />
-      <a:midPointStop
-         offset="0.5"
-         style="stop-color:#D9D9D9" />
-      <a:midPointStop
-         offset="1"
-         style="stop-color:#FFFFFF" />
-    </linearGradient>
-    <linearGradient
-       x1="592.20001"
-       y1="156.45"
-       x2="609.98999"
-       y2="174.24001"
-       id="lg5735"
-       xlink:href="#x5000_"
-       gradientUnits="userSpaceOnUse"
-       gradientTransform="matrix(1.12,0,0,1.12,-649.08,-160.62)" />
-    <linearGradient
-       x1="308.54999"
-       y1="149.89999"
-       x2="299.72"
-       y2="148.83"
-       id="XMLID_2433_"
-       gradientUnits="userSpaceOnUse">
-      <stop
-         style="stop-color:#d6d6d6;stop-opacity:1"
-         offset="0"
-         id="71615" />
-      <stop
-         style="stop-color:#a5a5a5;stop-opacity:1"
-         offset="1"
-         id="71617" />
-      <a:midPointStop
-         offset="0"
-         style="stop-color:#D6D6D6" />
-      <a:midPointStop
-         offset="0.5"
-         style="stop-color:#D6D6D6" />
-      <a:midPointStop
-         offset="1"
-         style="stop-color:#A5A5A5" />
-    </linearGradient>
-    <linearGradient
-       x1="308.54999"
-       y1="149.89999"
-       x2="299.72"
-       y2="148.83"
-       id="lg1952"
-       xlink:href="#XMLID_2433_"
-       gradientUnits="userSpaceOnUse"
-       gradientTransform="matrix(1.03,0,0,1.03,-279.57,-124.36)" />
-    <radialGradient
-       cx="307.39999"
-       cy="121"
-       r="23.35"
-       fx="307.39999"
-       fy="121"
-       id="XMLID_2432_"
-       gradientUnits="userSpaceOnUse"
-       gradientTransform="matrix(0.98,0,0,0.98,2.88,2.75)">
-      <stop
-         style="stop-color:#d2d2d2;stop-opacity:1"
-         offset="0.19"
-         id="71592" />
-      <stop
-         style="stop-color:#cfcfcf;stop-opacity:1"
-         offset="0.44999999"
-         id="71594" />
-      <stop
-         style="stop-color:#c7c7c7;stop-opacity:1"
-         offset="0.60000002"
-         id="71596" />
-      <stop
-         style="stop-color:#b9b9b9;stop-opacity:1"
-         offset="0.74000001"
-         id="71598" />
-      <stop
-         style="stop-color:#a4a4a4;stop-opacity:1"
-         offset="0.86000001"
-         id="71600" />
-      <stop
-         style="stop-color:#8a8a8a;stop-opacity:1"
-         offset="0.95999998"
-         id="71602" />
-      <stop
-         style="stop-color:gray;stop-opacity:1"
-         offset="1"
-         id="71604" />
-      <a:midPointStop
-         offset="0.19"
-         style="stop-color:#D2D2D2" />
-      <a:midPointStop
-         offset="0.8"
-         style="stop-color:#D2D2D2" />
-      <a:midPointStop
-         offset="1"
-         style="stop-color:#808080" />
-    </radialGradient>
-    <radialGradient
-       cx="307.39999"
-       cy="121"
-       r="23.35"
-       fx="307.39999"
-       fy="121"
-       id="radialGradient2331"
-       xlink:href="#XMLID_2432_"
-       gradientUnits="userSpaceOnUse"
-       gradientTransform="translate(-276.62,-121.54)" />
-    <linearGradient
-       x1="294.13"
-       y1="127.07"
-       x2="294.13"
-       y2="142.2"
-       id="XMLID_2430_"
-       gradientUnits="userSpaceOnUse">
-      <stop
-         style="stop-color:#b5d8ff;stop-opacity:1"
-         offset="0"
-         id="71582" />
-      <stop
-         style="stop-color:black;stop-opacity:1"
-         offset="1"
-         id="71584" />
-      <a:midPointStop
-         offset="0"
-         style="stop-color:#B5D8FF" />
-      <a:midPointStop
-         offset="0.5"
-         style="stop-color:#B5D8FF" />
-      <a:midPointStop
-         offset="1"
-         style="stop-color:#000000" />
-    </linearGradient>
-    <linearGradient
-       x1="294.13"
-       y1="127.07"
-       x2="294.13"
-       y2="142.2"
-       id="lg2820"
-       xlink:href="#XMLID_2430_"
-       gradientUnits="userSpaceOnUse"
-       gradientTransform="matrix(1.03,0,0,1.03,-279.57,-124.36)" />
-    <linearGradient
-       x1="279.10999"
-       y1="148.03"
-       x2="309.16"
-       y2="148.03"
-       id="XMLID_2429_"
-       gradientUnits="userSpaceOnUse">
-      <stop
-         style="stop-color:#e1e1e1;stop-opacity:1"
-         offset="0"
-         id="71564" />
-      <stop
-         style="stop-color:#e1e1e1;stop-opacity:1"
-         offset="0.25"
-         id="71566" />
-      <stop
-         style="stop-color:#a5a5a5;stop-opacity:1"
-         offset="0.44"
-         id="71568" />
-      <stop
-         style="stop-color:#a5a5a5;stop-opacity:1"
-         offset="1"
-         id="71570" />
-      <a:midPointStop
-         offset="0"
-         style="stop-color:#E1E1E1" />
-      <a:midPointStop
-         offset="0.5"
-         style="stop-color:#E1E1E1" />
-      <a:midPointStop
-         offset="0.25"
-         style="stop-color:#E1E1E1" />
-      <a:midPointStop
-         offset="0.5"
-         style="stop-color:#E1E1E1" />
-      <a:midPointStop
-         offset="0.44"
-         style="stop-color:#A5A5A5" />
-      <a:midPointStop
-         offset="0.5"
-         style="stop-color:#A5A5A5" />
-      <a:midPointStop
-         offset="1"
-         style="stop-color:#A5A5A5" />
-    </linearGradient>
-    <linearGradient
-       x1="279.10999"
-       y1="148.03"
-       x2="309.16"
-       y2="148.03"
-       id="lg2818"
-       xlink:href="#XMLID_2429_"
-       gradientUnits="userSpaceOnUse"
-       gradientTransform="matrix(1.03,0,0,1.03,-279.57,-124.36)" />
-    <radialGradient
-       cx="622.34302"
-       cy="14.449"
-       r="26.496"
-       fx="622.34302"
-       fy="14.449"
-       id="lg3499_"
-       gradientUnits="userSpaceOnUse"
-       gradientTransform="matrix(0.851,0,0,0.849,69.297,51.658)">
-      <stop
-         style="stop-color:#23468e;stop-opacity:1"
-         offset="0"
-         id="stop10972" />
-      <stop
-         style="stop-color:#012859;stop-opacity:1"
-         offset="1"
-         id="stop10974" />
-      <a:midPointStop
-         offset="0"
-         style="stop-color:#23468E" />
-      <a:midPointStop
-         offset="0.5"
-         style="stop-color:#23468E" />
-      <a:midPointStop
-         offset="1"
-         style="stop-color:#012859" />
-    </radialGradient>
-    <radialGradient
-       cx="622.34302"
-       cy="14.449"
-       r="26.496"
-       fx="622.34302"
-       fy="14.449"
-       id="rg5791"
-       xlink:href="#lg3499_"
-       gradientUnits="userSpaceOnUse"
-       gradientTransform="matrix(0.858,0,0,0.857,-511.7,9.02)" />
-    <linearGradient
-       x1="616.112"
-       y1="76.247002"
-       x2="588.14099"
-       y2="60.742001"
-       id="lg3497_"
-       gradientUnits="userSpaceOnUse">
-      <stop
-         style="stop-color:#01326e;stop-opacity:1"
-         offset="0"
-         id="stop10962" />
-      <stop
-         style="stop-color:#012859;stop-opacity:1"
-         offset="1"
-         id="stop10964" />
-      <a:midPointStop
-         offset="0"
-         style="stop-color:#01326E" />
-      <a:midPointStop
-         offset="0.5"
-         style="stop-color:#01326E" />
-      <a:midPointStop
-         offset="1"
-         style="stop-color:#012859" />
-    </linearGradient>
-    <linearGradient
-       x1="617.698"
-       y1="82.445999"
-       x2="585.95203"
-       y2="54.848999"
-       id="lg3496_"
-       gradientUnits="userSpaceOnUse">
-      <stop
-         style="stop-color:#e5e5e5;stop-opacity:1"
-         offset="0"
-         id="stop10950" />
-      <stop
-         style="stop-color:#ccc;stop-opacity:1"
-         offset="1"
-         id="stop10952" />
-      <a:midPointStop
-         offset="0"
-         style="stop-color:#E5E5E5" />
-      <a:midPointStop
-         offset="0.5"
-         style="stop-color:#E5E5E5" />
-      <a:midPointStop
-         offset="1"
-         style="stop-color:#CCCCCC" />
-    </linearGradient>
-    <linearGradient
-       x1="617.698"
-       y1="82.445999"
-       x2="585.95203"
-       y2="54.848999"
-       id="lg5794"
-       xlink:href="#lg3496_"
-       gradientUnits="userSpaceOnUse" />
-    <linearGradient
-       x1="601.39001"
-       y1="55.341"
-       x2="588.29199"
-       y2="71.515999"
-       id="lg3495_"
-       gradientUnits="userSpaceOnUse">
-      <stop
-         style="stop-color:#d9d9d9;stop-opacity:1"
-         offset="0"
-         id="stop10941" />
-      <stop
-         style="stop-color:#f2f2f2;stop-opacity:1"
-         offset="0.52200001"
-         id="stop10943" />
-      <stop
-         style="stop-color:#ccc;stop-opacity:1"
-         offset="1"
-         id="stop10945" />
-      <a:midPointStop
-         offset="0"
-         style="stop-color:#D9D9D9" />
-      <a:midPointStop
-         offset="0.5"
-         style="stop-color:#D9D9D9" />
-      <a:midPointStop
-         offset="0.522"
-         style="stop-color:#F2F2F2" />
-      <a:midPointStop
-         offset="0.5"
-         style="stop-color:#F2F2F2" />
-      <a:midPointStop
-         offset="1"
-         style="stop-color:#CCCCCC" />
-    </linearGradient>
-    <linearGradient
-       x1="601.39001"
-       y1="55.341"
-       x2="588.29199"
-       y2="71.515999"
-       id="lg5771"
-       xlink:href="#lg3495_"
-       gradientUnits="userSpaceOnUse"
-       gradientTransform="matrix(1.009,0,0,1.009,-581.615,-43.098)" />
-    <linearGradient
-       x1="611.34601"
-       y1="55.279999"
-       x2="590.39001"
-       y2="81.157997"
-       id="lg3494_"
-       gradientUnits="userSpaceOnUse">
-      <stop
-         style="stop-color:#d9d9d9;stop-opacity:1"
-         offset="0"
-         id="stop10932" />
-      <stop
-         style="stop-color:#f2f2f2;stop-opacity:1"
-         offset="0.52200001"
-         id="stop10934" />
-      <stop
-         style="stop-color:#ccc;stop-opacity:1"
-         offset="1"
-         id="stop10936" />
-      <a:midPointStop
-         offset="0"
-         style="stop-color:#D9D9D9" />
-      <a:midPointStop
-         offset="0.5"
-         style="stop-color:#D9D9D9" />
-      <a:midPointStop
-         offset="0.522"
-         style="stop-color:#F2F2F2" />
-      <a:midPointStop
-         offset="0.5"
-         style="stop-color:#F2F2F2" />
-      <a:midPointStop
-         offset="1"
-         style="stop-color:#CCCCCC" />
-    </linearGradient>
-    <linearGradient
-       x1="611.34601"
-       y1="55.279999"
-       x2="590.39001"
-       y2="81.157997"
-       id="lg5774"
-       xlink:href="#lg3494_"
-       gradientUnits="userSpaceOnUse"
-       gradientTransform="matrix(1.009,0,0,1.009,-581.616,-43.098)" />
-    <linearGradient
-       x1="798.72998"
-       y1="69.839996"
-       x2="799.04999"
-       y2="70.709999"
-       id="g3302_"
-       gradientUnits="userSpaceOnUse">
-      <stop
-         style="stop-color:#005e00;stop-opacity:1"
-         offset="0"
-         id="s6504" />
-      <stop
-         style="stop-color:#23a11f;stop-opacity:1"
-         offset="1"
-         id="s6506" />
-      <a:midPointstop
-         style="stop-color:#005E00"
-         offset="0" />
-      <a:midPointstop
-         style="stop-color:#005E00"
-         offset="0.5" />
-      <a:midPointstop
-         style="stop-color:#23A11F"
-         offset="1" />
-    </linearGradient>
-    <linearGradient
-       x1="798.72998"
-       y1="69.839996"
-       x2="799.04999"
-       y2="70.709999"
-       id="lg5851"
-       xlink:href="#g3302_"
-       gradientUnits="userSpaceOnUse"
-       gradientTransform="matrix(1.204,0,0,1.263,-926.036,-60.001)" />
-    <linearGradient
-       x1="779.19"
-       y1="122.73"
-       x2="811.69"
-       y2="149.74001"
-       id="g3301_"
-       gradientUnits="userSpaceOnUse"
-       gradientTransform="matrix(1,-0.25,0,1,0,129.19)">
-      <stop
-         style="stop-color:#f2f2f2;stop-opacity:1"
-         offset="0"
-         id="s6483" />
-      <stop
-         style="stop-color:#eee;stop-opacity:1"
-         offset="0.17"
-         id="s6485" />
-      <stop
-         style="stop-color:#e3e3e3;stop-opacity:1"
-         offset="0.34"
-         id="s6487" />
-      <stop
-         style="stop-color:#cfcfcf;stop-opacity:1"
-         offset="0.50999999"
-         id="s6489" />
-      <stop
-         style="stop-color:#b4b4b4;stop-opacity:1"
-         offset="0.67000002"
-         id="s6491" />
-      <stop
-         style="stop-color:#919191;stop-opacity:1"
-         offset="0.83999997"
-         id="s6493" />
-      <stop
-         style="stop-color:#666;stop-opacity:1"
-         offset="1"
-         id="s6495" />
-      <a:midPointstop
-         style="stop-color:#F2F2F2"
-         offset="0" />
-      <a:midPointstop
-         style="stop-color:#F2F2F2"
-         offset="0.71" />
-      <a:midPointstop
-         style="stop-color:#666666"
-         offset="1" />
-    </linearGradient>
-    <linearGradient
-       x1="779.19"
-       y1="122.73"
-       x2="811.69"
-       y2="149.74001"
-       id="lg5855"
-       xlink:href="#g3301_"
-       gradientUnits="userSpaceOnUse"
-       gradientTransform="matrix(1.204,-0.316,0,1.263,-926.036,103.123)" />
-    <clipPath
-       id="g3299_">
-      <use
-         id="use6469"
-         x="0"
-         y="0"
-         width="1005.92"
-         height="376.97"
-         xlink:href="#g101_" />
-    </clipPath>
-    <radialGradient
-       cx="1189.9301"
-       cy="100.05"
-       r="40.400002"
-       fx="1189.9301"
-       fy="100.05"
-       id="g3300_"
-       gradientUnits="userSpaceOnUse"
-       gradientTransform="matrix(0.34,-8.46e-2,0,0.34,394.16,137.13)">
-      <stop
-         style="stop-color:white;stop-opacity:1"
-         offset="0"
-         id="s6472" />
-      <stop
-         style="stop-color:white;stop-opacity:0"
-         offset="1"
-         id="s6474" />
-      <a:midPointstop
-         style="stop-color:#FFFFFF"
-         offset="0" />
-      <a:midPointstop
-         style="stop-color:#FFFFFF"
-         offset="0.5" />
-      <a:midPointstop
-         style="stop-color:#000000"
-         offset="1" />
-    </radialGradient>
-    <radialGradient
-       cx="1199.74"
-       cy="97.150002"
-       r="40.400002"
-       fx="1199.74"
-       fy="97.150002"
-       id="rg5860"
-       xlink:href="#g3300_"
-       gradientUnits="userSpaceOnUse"
-       gradientTransform="matrix(0.409,-0.107,0,0.429,-451.489,113.149)" />
-    <linearGradient
-       x1="796.38"
-       y1="67.580002"
-       x2="781.28003"
-       y2="58.549999"
-       id="g3298_"
-       gradientUnits="userSpaceOnUse">
-      <stop
-         style="stop-color:#4c8bca;stop-opacity:1"
-         offset="0"
-         id="s6462" />
-      <stop
-         style="stop-color:#b7e9ff;stop-opacity:1"
-         offset="1"
-         id="s6464" />
-      <a:midPointstop
-         style="stop-color:#4C8BCA"
-         offset="0" />
-      <a:midPointstop
-         style="stop-color:#4C8BCA"
-         offset="0.5" />
-      <a:midPointstop
-         style="stop-color:#B7E9FF"
-         offset="1" />
-    </linearGradient>
-    <linearGradient
-       x1="800.97998"
-       y1="140.72"
-       x2="777.71997"
-       y2="121.76"
-       id="g3297_"
-       gradientUnits="userSpaceOnUse"
-       gradientTransform="matrix(1,-0.25,0,1,0,129.19)">
-      <stop
-         style="stop-color:#e5e5e5;stop-opacity:1"
-         offset="0"
-         id="s6448" />
-      <stop
-         style="stop-color:#ccc;stop-opacity:1"
-         offset="1"
-         id="s6450" />
-      <a:midPointstop
-         style="stop-color:#E5E5E5"
-         offset="0" />
-      <a:midPointstop
-         style="stop-color:#E5E5E5"
-         offset="0.5" />
-      <a:midPointstop
-         style="stop-color:#CCCCCC"
-         offset="1" />
-    </linearGradient>
-    <linearGradient
-       x1="800.97998"
-       y1="140.72"
-       x2="777.71997"
-       y2="121.76"
-       id="lg5890"
-       xlink:href="#g3297_"
-       gradientUnits="userSpaceOnUse"
-       gradientTransform="matrix(1,-0.25,0,1,0,129.19)" />
-    <linearGradient
-       x1="790.03998"
-       y1="-16.33"
-       x2="779.84003"
-       y2="-3.73"
-       id="g3296_"
-       gradientUnits="userSpaceOnUse"
-       gradientTransform="translate(0,70.17)">
-      <stop
-         style="stop-color:#d9d9d9;stop-opacity:1"
-         offset="0"
-         id="s6439" />
-      <stop
-         style="stop-color:#f2f2f2;stop-opacity:1"
-         offset="0.51999998"
-         id="s6441" />
-      <stop
-         style="stop-color:#ccc;stop-opacity:1"
-         offset="1"
-         id="s6443" />
-      <a:midPointstop
-         style="stop-color:#D9D9D9"
-         offset="0" />
-      <a:midPointstop
-         style="stop-color:#D9D9D9"
-         offset="0.5" />
-      <a:midPointstop
-         style="stop-color:#F2F2F2"
-         offset="0.52" />
-      <a:midPointstop
-         style="stop-color:#F2F2F2"
-         offset="0.5" />
-      <a:midPointstop
-         style="stop-color:#CCCCCC"
-         offset="1" />
-    </linearGradient>
-    <linearGradient
-       x1="790.03998"
-       y1="-16.33"
-       x2="779.84003"
-       y2="-3.73"
-       id="lg5866"
-       xlink:href="#g3296_"
-       gradientUnits="userSpaceOnUse"
-       gradientTransform="matrix(1.204,0,0,1.263,-926.036,28.6)" />
-    <linearGradient
-       x1="785.84003"
-       y1="72.989998"
-       x2="785.26001"
-       y2="76.279999"
-       id="g3293_"
-       gradientUnits="userSpaceOnUse">
-      <stop
-         style="stop-color:white;stop-opacity:1"
-         offset="0"
-         id="s6412" />
-      <stop
-         style="stop-color:#737373;stop-opacity:1"
-         offset="1"
-         id="s6414" />
-      <a:midPointstop
-         style="stop-color:#FFFFFF"
-         offset="0" />
-      <a:midPointstop
-         style="stop-color:#FFFFFF"
-         offset="0.5" />
-      <a:midPointstop
-         style="stop-color:#737373"
-         offset="1" />
-    </linearGradient>
-    <linearGradient
-       x1="785.84003"
-       y1="72.989998"
-       x2="785.26001"
-       y2="76.279999"
-       id="lg5871"
-       xlink:href="#g3293_"
-       gradientUnits="userSpaceOnUse"
-       gradientTransform="matrix(1.204,0,0,1.263,-926.036,-60.001)" />
-    <linearGradient
-       x1="789.37"
-       y1="69.879997"
-       x2="791.03998"
-       y2="77.120003"
-       id="g3292_"
-       gradientUnits="userSpaceOnUse">
-      <stop
-         style="stop-color:#999;stop-opacity:1"
-         offset="0"
-         id="s6403" />
-      <stop
-         style="stop-color:#f2f2f2;stop-opacity:1"
-         offset="0.28"
-         id="s6405" />
-      <stop
-         style="stop-color:#666;stop-opacity:1"
-         offset="1"
-         id="s6407" />
-      <a:midPointstop
-         style="stop-color:#999999"
-         offset="0" />
-      <a:midPointstop
-         style="stop-color:#999999"
-         offset="0.5" />
-      <a:midPointstop
-         style="stop-color:#F2F2F2"
-         offset="0.28" />
-      <a:midPointstop
-         style="stop-color:#F2F2F2"
-         offset="0.5" />
-      <a:midPointstop
-         style="stop-color:#666666"
-         offset="1" />
-    </linearGradient>
-    <linearGradient
-       x1="789.37"
-       y1="69.879997"
-       x2="791.03998"
-       y2="77.120003"
-       id="lg5874"
-       xlink:href="#g3292_"
-       gradientUnits="userSpaceOnUse"
-       gradientTransform="matrix(1.204,0,0,1.263,-926.036,-60.001)" />
-    <linearGradient
-       x1="786.65997"
-       y1="136.12"
-       x2="786.71002"
-       y2="134.33"
-       id="g3290_"
-       gradientUnits="userSpaceOnUse"
-       gradientTransform="matrix(1,-0.25,0,1,0,137.29)">
-      <stop
-         style="stop-color:#d9d9d9;stop-opacity:1"
-         offset="0"
-         id="s6380" />
-      <stop
-         style="stop-color:#b2b2b2;stop-opacity:1"
-         offset="1"
-         id="s6382" />
-      <a:midPointstop
-         style="stop-color:#D9D9D9"
-         offset="0" />
-      <a:midPointstop
-         style="stop-color:#D9D9D9"
-         offset="0.5" />
-      <a:midPointstop
-         style="stop-color:#B2B2B2"
-         offset="1" />
-    </linearGradient>
-    <linearGradient
-       x1="786.65997"
-       y1="136.12"
-       x2="786.71002"
-       y2="134.33"
-       id="lg5878"
-       xlink:href="#g3290_"
-       gradientUnits="userSpaceOnUse"
-       gradientTransform="matrix(1.204,-0.316,0,1.263,-926.036,113.351)" />
-    <radialGradient
-       cx="1458.77"
-       cy="-5.0999999"
-       r="35.130001"
-       fx="1458.77"
-       fy="-5.0999999"
-       id="g3289_"
-       gradientUnits="userSpaceOnUse"
-       gradientTransform="matrix(0.42,0,0,0.42,167.09,79.84)">
-      <stop
-         style="stop-color:white;stop-opacity:1"
-         offset="0"
-         id="s6371" />
-      <stop
-         style="stop-color:#999;stop-opacity:1"
-         offset="1"
-         id="s6373" />
-      <a:midPointstop
-         style="stop-color:#FFFFFF"
-         offset="0" />
-      <a:midPointstop
-         style="stop-color:#FFFFFF"
-         offset="0.5" />
-      <a:midPointstop
-         style="stop-color:#999999"
-         offset="1" />
-    </radialGradient>
-    <radialGradient
-       cx="1458.77"
-       cy="-5.0999999"
-       r="35.130001"
-       fx="1458.77"
-       fy="-5.0999999"
-       id="rg5881"
-       xlink:href="#g3289_"
-       gradientUnits="userSpaceOnUse"
-       gradientTransform="matrix(0.505,0,0,0.53,-724.957,40.636)" />
-    <radialGradient
-       cx="1612.98"
-       cy="-4.4699998"
-       r="36.580002"
-       fx="1612.98"
-       fy="-4.4699998"
-       id="g3288_"
-       gradientUnits="userSpaceOnUse"
-       gradientTransform="matrix(0.34,0,0,0.36,238.56,86.87)">
-      <stop
-         style="stop-color:#e5e5e5;stop-opacity:1"
-         offset="0"
-         id="s6362" />
-      <stop
-         style="stop-color:#b2b2b2;stop-opacity:1"
-         offset="0.63999999"
-         id="s6364" />
-      <stop
-         style="stop-color:#737373;stop-opacity:1"
-         offset="1"
-         id="s6366" />
-      <a:midPointstop
-         style="stop-color:#E5E5E5"
-         offset="0" />
-      <a:midPointstop
-         style="stop-color:#E5E5E5"
-         offset="0.5" />
-      <a:midPointstop
-         style="stop-color:#B2B2B2"
-         offset="0.64" />
-      <a:midPointstop
-         style="stop-color:#B2B2B2"
-         offset="0.5" />
-      <a:midPointstop
-         style="stop-color:#737373"
-         offset="1" />
-    </radialGradient>
-    <radialGradient
-       cx="1612.98"
-       cy="-4.4699998"
-       r="36.580002"
-       fx="1612.98"
-       fy="-4.4699998"
-       id="rg5884"
-       xlink:href="#g3288_"
-       gradientUnits="userSpaceOnUse"
-       gradientTransform="matrix(0.408,0,0,0.448,-638.943,49.495)" />
-    <radialGradient
-       cx="1470.5"
-       cy="-10.21"
-       r="33.290001"
-       fx="1470.5"
-       fy="-10.21"
-       id="g3287_"
-       gradientUnits="userSpaceOnUse"
-       gradientTransform="matrix(0.42,0,0,0.42,167.09,79.84)">
-      <stop
-         style="stop-color:#e5e5e5;stop-opacity:1"
-         offset="0"
-         id="s6347" />
-      <stop
-         style="stop-color:#b2b2b2;stop-opacity:1"
-         offset="0.38999999"
-         id="s6349" />
-      <stop
-         style="stop-color:#b1b1b1;stop-opacity:1"
-         offset="0.75"
-         id="s6351" />
-      <stop
-         style="stop-color:#aaa;stop-opacity:1"
-         offset="0.88"
-         id="s6353" />
-      <stop
-         style="stop-color:#9e9e9e;stop-opacity:1"
-         offset="0.97000003"
-         id="s6355" />
-      <stop
-         style="stop-color:#999;stop-opacity:1"
-         offset="1"
-         id="s6357" />
-      <a:midPointstop
-         style="stop-color:#E5E5E5"
-         offset="0" />
-      <a:midPointstop
-         style="stop-color:#E5E5E5"
-         offset="0.5" />
-      <a:midPointstop
-         style="stop-color:#B2B2B2"
-         offset="0.39" />
-      <a:midPointstop
-         style="stop-color:#B2B2B2"
-         offset="0.87" />
-      <a:midPointstop
-         style="stop-color:#999999"
-         offset="1" />
-    </radialGradient>
-    <radialGradient
-       cx="1470.5"
-       cy="-10.21"
-       r="33.290001"
-       fx="1470.5"
-       fy="-10.21"
-       id="rg5887"
-       xlink:href="#g3287_"
-       gradientUnits="userSpaceOnUse"
-       gradientTransform="matrix(0.505,0,0,0.53,-724.957,40.636)" />
-    <pattern
-       patternTransform="matrix(0.592927,0,0,0.592927,78,462)"
-       id="cream-spots"
-       height="32"
-       width="32"
-       patternUnits="userSpaceOnUse">
-      <g
-         transform="translate(-365.3146,-513.505)"
-         id="g3047">
-           id=&quot;path2858&quot; /&gt;
-        <path
-   inkscape:label="#path2854"
-   sodipodi:nodetypes="czzzz"
-   style="fill:#e3dcc0"
-   id="path3060"
-   d="M 390.31462,529.50504 C 390.31462,534.47304 386.28262,538.50504 381.31462,538.50504 C 376.34662,538.50504 372.31462,534.47304 372.31462,529.50504 C 372.31462,524.53704 376.34662,520.50504 381.31462,520.50504 C 386.28262,520.50504 390.31462,524.53704 390.31462,529.50504 z " />
-</g>
-    </pattern>
-    <pattern
-       patternTransform="matrix(0.733751,0,0,0.733751,67,367)"
-       id="dark-cream-spots"
-       height="32"
-       width="32"
-       patternUnits="userSpaceOnUse">
-      <g
-         transform="translate(-408.0946,-513.505)"
-         id="dark-cream-spot"
-         inkscape:label="#g3043">
-        <path
-           sodipodi:nodetypes="czzzz"
-           style="fill:#c8c5ac"
-           d="M 433.09458,529.50504 C 433.09458,534.47304 429.06258,538.50504 424.09458,538.50504 C 419.12658,538.50504 415.09458,534.47304 415.09458,529.50504 C 415.09458,524.53704 419.12658,520.50504 424.09458,520.50504 C 429.06258,520.50504 433.09458,524.53704 433.09458,529.50504 z "
-           id="path2953" />
-      </g>
-    </pattern>
-    <pattern
-       patternTransform="matrix(0.375,0,0,0.375,379,400)"
-       id="white-spots"
-       height="32"
-       width="32"
-       patternUnits="userSpaceOnUse">
-      <g
-         transform="translate(-484.3997,-513.505)"
-         id="white-spot"
-         inkscape:label="#g3035">
-        <path
-           style="opacity:0.25;fill:white"
-           id="path3033"
-           d="M 509.39967,529.50504 C 509.39967,534.47304 505.36767,538.50504 500.39967,538.50504 C 495.43167,538.50504 491.39967,534.47304 491.39967,529.50504 C 491.39967,524.53704 495.43167,520.50504 500.39967,520.50504 C 505.36767,520.50504 509.39967,524.53704 509.39967,529.50504 z "
-           sodipodi:nodetypes="czzzz" />
-      </g>
-    </pattern>
-    <pattern
-       patternTransform="matrix(0.455007,0,0,0.455007,-5e-5,1.9e-5)"
-       id="black-spots"
-       height="32"
-       width="32"
-       patternUnits="userSpaceOnUse">
-      <g
-         transform="translate(-448.3997,-513.505)"
-         id="black-spot"
-         inkscape:label="#g3039">
-        <path
-           sodipodi:nodetypes="czzzz"
-           d="M 473.39967,529.50504 C 473.39967,534.47304 469.36767,538.50504 464.39967,538.50504 C 459.43167,538.50504 455.39967,534.47304 455.39967,529.50504 C 455.39967,524.53704 459.43167,520.50504 464.39967,520.50504 C 469.36767,520.50504 473.39967,524.53704 473.39967,529.50504 z "
-           id="path2961"
-           style="opacity:0.25;fill:black" />
-      </g>
-    </pattern>
-    <linearGradient
-       x1="501.0903"
-       y1="-19.2544"
-       x2="531.85413"
-       y2="0.72390002"
-       id="linearGradient17334"
-       gradientUnits="userSpaceOnUse"
-       gradientTransform="matrix(0.6868,0.4269,-0.9821,0.821,111.6149,-5.7901)">
-      <stop
-         style="stop-color:#b4daea;stop-opacity:1"
-         offset="0"
-         id="stop17336" />
-      <stop
-         style="stop-color:#b4daea;stop-opacity:1"
-         offset="0.51120001"
-         id="stop17338" />
-      <stop
-         style="stop-color:#5387ba;stop-opacity:1"
-         offset="0.64609998"
-         id="stop17340" />
-      <stop
-         style="stop-color:#16336e;stop-opacity:1"
-         offset="1"
-         id="stop17342" />
-      <a:midPointStop
-         offset="0"
-         style="stop-color:#B4DAEA" />
-      <a:midPointStop
-         offset="0.5"
-         style="stop-color:#B4DAEA" />
-      <a:midPointStop
-         offset="0.5112"
-         style="stop-color:#B4DAEA" />
-      <a:midPointStop
-         offset="0.5"
-         style="stop-color:#B4DAEA" />
-      <a:midPointStop
-         offset="0.6461"
-         style="stop-color:#5387BA" />
-      <a:midPointStop
-         offset="0.5"
-         style="stop-color:#5387BA" />
-      <a:midPointStop
-         offset="1"
-         style="stop-color:#16336E" />
-    </linearGradient>
-    <linearGradient
-       x1="415.73831"
-       y1="11.854"
-       x2="418.13361"
-       y2="18.8104"
-       id="linearGradient17426"
-       gradientUnits="userSpaceOnUse"
-       gradientTransform="matrix(0.8362,0.5206,-1.1904,0.992,147.62,-30.9374)">
-      <stop
-         style="stop-color:#ccc;stop-opacity:1"
-         offset="0"
-         id="stop17428" />
-      <stop
-         style="stop-color:#f2f2f2;stop-opacity:1"
-         offset="1"
-         id="stop17430" />
-      <a:midPointStop
-         offset="0"
-         style="stop-color:#CCCCCC" />
-      <a:midPointStop
-         offset="0.5"
-         style="stop-color:#CCCCCC" />
-      <a:midPointStop
-         offset="1"
-         style="stop-color:#F2F2F2" />
-    </linearGradient>
-    <linearGradient
-       x1="478.21341"
-       y1="-131.9297"
-       x2="469.85818"
-       y2="-140.28481"
-       id="linearGradient17434"
-       gradientUnits="userSpaceOnUse"
-       gradientTransform="matrix(0.5592,0.829,-0.829,0.5592,101.3357,-104.791)">
-      <stop
-         style="stop-color:#f3403f;stop-opacity:1"
-         offset="0"
-         id="stop17436" />
-      <stop
-         style="stop-color:#d02a28;stop-opacity:1"
-         offset="0.37889999"
-         id="stop17438" />
-      <stop
-         style="stop-color:#b21714;stop-opacity:1"
-         offset="0.77649999"
-         id="stop17440" />
-      <stop
-         style="stop-color:#a6100c;stop-opacity:1"
-         offset="1"
-         id="stop17442" />
-      <a:midPointStop
-         offset="0"
-         style="stop-color:#F3403F" />
-      <a:midPointStop
-         offset="0.4213"
-         style="stop-color:#F3403F" />
-      <a:midPointStop
-         offset="1"
-         style="stop-color:#A6100C" />
-    </linearGradient>
-    <linearGradient
-       x1="502.70749"
-       y1="115.3013"
-       x2="516.39001"
-       y2="127.1953"
-       id="linearGradient17709"
-       xlink:href="#XMLID_1749_"
-       gradientUnits="userSpaceOnUse"
-       gradientTransform="matrix(0.9703,0.2419,-0.2419,0.9703,11.0227,-35.6159)" />
-    <linearGradient
-       x1="506.09909"
-       y1="-11.5137"
-       x2="527.99609"
-       y2="2.7063999"
-       id="linearGradient17711"
-       xlink:href="#XMLID_1752_"
-       gradientUnits="userSpaceOnUse"
-       gradientTransform="matrix(0.6868,0.4269,-0.9821,0.821,111.6149,-5.7901)" />
-    <linearGradient
-       x1="516.57672"
-       y1="-15.769"
-       x2="516.57672"
-       y2="0.84280002"
-       id="linearGradient17713"
-       xlink:href="#XMLID_1753_"
-       gradientUnits="userSpaceOnUse"
-       gradientTransform="matrix(0.6868,0.4269,-0.9821,0.821,111.6149,-5.7901)" />
-    <linearGradient
-       x1="505.62939"
-       y1="-14.9526"
-       x2="527.49402"
-       y2="-0.7536"
-       id="linearGradient17715"
-       xlink:href="#XMLID_1756_"
-       gradientUnits="userSpaceOnUse"
-       gradientTransform="matrix(0.6868,0.4269,-0.9821,0.821,111.6149,-5.7901)" />
-    <linearGradient
-       x1="500.70749"
-       y1="-13.2441"
-       x2="513.46442"
-       y2="-2.1547"
-       id="linearGradient17717"
-       xlink:href="#XMLID_1757_"
-       gradientUnits="userSpaceOnUse"
-       gradientTransform="matrix(0.6868,0.4269,-0.9821,0.821,111.6149,-5.7901)" />
-    <linearGradient
-       x1="473.7681"
-       y1="209.17529"
-       x2="486.98099"
-       y2="213.2001"
-       id="linearGradient17721"
-       xlink:href="#XMLID_2274_"
-       gradientUnits="userSpaceOnUse" />
-    <linearGradient
-       x1="481.23969"
-       y1="212.5742"
-       x2="472.92981"
-       y2="207.4967"
-       id="linearGradient17723"
-       xlink:href="#XMLID_2275_"
-       gradientUnits="userSpaceOnUse" />
-    <linearGradient
-       x1="500.70749"
-       y1="-13.2441"
-       x2="513.46442"
-       y2="-2.1547"
-       id="linearGradient17416"
-       gradientUnits="userSpaceOnUse"
-       gradientTransform="matrix(0.6868,0.4269,-0.9821,0.821,111.6149,-5.7901)">
-      <stop
-         style="stop-color:#5387ba;stop-opacity:1"
-         offset="0"
-         id="stop17418" />
-      <stop
-         style="stop-color:#96bad6;stop-opacity:1"
-         offset="1"
-         id="stop17420" />
-      <a:midPointStop
-         style="stop-color:#5387BA"
-         offset="0" />
-      <a:midPointStop
-         style="stop-color:#5387BA"
-         offset="0.5" />
-      <a:midPointStop
-         style="stop-color:#96BAD6"
-         offset="1" />
-    </linearGradient>
-    <defs
-       id="defs9929">
-      <path
-         d="M 489.21,209.35 L 485.35,203.63 C 483.63,204.25 473.47,208.93 471.5,210.18 C 470.57,210.77 470.17,211.16 469.72,212.48 C 470.93,212.31 471.72,212.49 473.42,213.04 C 473.26,214.77 473.24,215.74 473.57,218.2 C 474.01,216.88 474.41,216.49 475.34,215.9 C 477.33,214.65 487.49,209.97 489.21,209.35 z "
-         id="XMLID_960_" />
-    </defs>
-    <clipPath
-       id="clipPath17448">
-      <use
-         id="use17450"
-         x="0"
-         y="0"
-         width="744.09448"
-         height="600"
-         xlink:href="#XMLID_960_" />
-    </clipPath>
-    <linearGradient
-       x1="473.7681"
-       y1="209.17529"
-       x2="486.98099"
-       y2="213.2001"
-       id="linearGradient17452"
-       gradientUnits="userSpaceOnUse">
-      <stop
-         style="stop-color:#f3403f;stop-opacity:1"
-         offset="0"
-         id="stop17454" />
-      <stop
-         style="stop-color:#d02a28;stop-opacity:1"
-         offset="0.37889999"
-         id="stop17456" />
-      <stop
-         style="stop-color:#b21714;stop-opacity:1"
-         offset="0.77649999"
-         id="stop17458" />
-      <stop
-         style="stop-color:#a6100c;stop-opacity:1"
-         offset="1"
-         id="stop17460" />
-      <a:midPointStop
-         style="stop-color:#F3403F"
-         offset="0" />
-      <a:midPointStop
-         style="stop-color:#F3403F"
-         offset="0.4213" />
-      <a:midPointStop
-         style="stop-color:#A6100C"
-         offset="1" />
-    </linearGradient>
-    <linearGradient
-       x1="481.23969"
-       y1="212.5742"
-       x2="472.92981"
-       y2="207.4967"
-       id="linearGradient17463"
-       gradientUnits="userSpaceOnUse">
-      <stop
-         style="stop-color:#f3403f;stop-opacity:1"
-         offset="0"
-         id="stop17465" />
-      <stop
-         style="stop-color:#d02a28;stop-opacity:1"
-         offset="0.37889999"
-         id="stop17467" />
-      <stop
-         style="stop-color:#b21714;stop-opacity:1"
-         offset="0.77649999"
-         id="stop17469" />
-      <stop
-         style="stop-color:#a6100c;stop-opacity:1"
-         offset="1"
-         id="stop17471" />
-      <a:midPointStop
-         style="stop-color:#F3403F"
-         offset="0" />
-      <a:midPointStop
-         style="stop-color:#F3403F"
-         offset="0.4213" />
-      <a:midPointStop
-         style="stop-color:#A6100C"
-         offset="1" />
-    </linearGradient>
-    <linearGradient
-       x1="481.23969"
-       y1="212.5742"
-       x2="472.92981"
-       y2="207.4967"
-       id="linearGradient17807"
-       xlink:href="#XMLID_2275_"
-       gradientUnits="userSpaceOnUse"
-       gradientTransform="translate(-177.1654,35.43307)" />
-    <linearGradient
-       x1="473.7681"
-       y1="209.17529"
-       x2="486.98099"
-       y2="213.2001"
-       id="linearGradient17810"
-       xlink:href="#XMLID_2274_"
-       gradientUnits="userSpaceOnUse"
-       gradientTransform="translate(-177.1654,35.43307)" />
-    <linearGradient
-       x1="502.70749"
-       y1="115.3013"
-       x2="516.39001"
-       y2="127.1953"
-       id="linearGradient17812"
-       xlink:href="#XMLID_1749_"
-       gradientUnits="userSpaceOnUse"
-       gradientTransform="matrix(0.9703,0.2419,-0.2419,0.9703,11.0227,-35.6159)" />
-    <linearGradient
-       x1="506.09909"
-       y1="-11.5137"
-       x2="527.99609"
-       y2="2.7063999"
-       id="linearGradient17814"
-       xlink:href="#XMLID_1752_"
-       gradientUnits="userSpaceOnUse"
-       gradientTransform="matrix(0.6868,0.4269,-0.9821,0.821,111.6149,-5.7901)" />
-    <linearGradient
-       x1="516.57672"
-       y1="-15.769"
-       x2="516.57672"
-       y2="0.84280002"
-       id="linearGradient17816"
-       xlink:href="#XMLID_1753_"
-       gradientUnits="userSpaceOnUse"
-       gradientTransform="matrix(0.6868,0.4269,-0.9821,0.821,111.6149,-5.7901)" />
-    <linearGradient
-       x1="505.62939"
-       y1="-14.9526"
-       x2="527.49402"
-       y2="-0.7536"
-       id="linearGradient17818"
-       xlink:href="#XMLID_1756_"
-       gradientUnits="userSpaceOnUse"
-       gradientTransform="matrix(0.6868,0.4269,-0.9821,0.821,111.6149,-5.7901)" />
-    <linearGradient
-       x1="502.70749"
-       y1="115.3013"
-       x2="516.39001"
-       y2="127.1953"
-       id="linearGradient17347"
-       gradientUnits="userSpaceOnUse"
-       gradientTransform="matrix(0.9703,0.2419,-0.2419,0.9703,11.0227,-35.6159)">
-      <stop
-         style="stop-color:#5387ba;stop-opacity:1"
-         offset="0"
-         id="stop17349" />
-      <stop
-         style="stop-color:#96bad6;stop-opacity:1"
-         offset="1"
-         id="stop17351" />
-      <a:midPointStop
-         offset="0"
-         style="stop-color:#5387BA" />
-      <a:midPointStop
-         offset="0.5"
-         style="stop-color:#5387BA" />
-      <a:midPointStop
-         offset="1"
-         style="stop-color:#96BAD6" />
-    </linearGradient>
-    <linearGradient
-       x1="516.57672"
-       y1="-15.769"
-       x2="516.57672"
-       y2="0.84280002"
-       id="linearGradient17379"
-       gradientUnits="userSpaceOnUse"
-       gradientTransform="matrix(0.6868,0.4269,-0.9821,0.821,111.6149,-5.7901)">
-      <stop
-         style="stop-color:#b2b2b2;stop-opacity:1"
-         offset="0"
-         id="stop17381" />
-      <stop
-         style="stop-color:#f2f2f2;stop-opacity:1"
-         offset="1"
-         id="stop17383" />
-      <a:midPointStop
-         offset="0"
-         style="stop-color:#B2B2B2" />
-      <a:midPointStop
-         offset="0.5"
-         style="stop-color:#B2B2B2" />
-      <a:midPointStop
-         offset="1"
-         style="stop-color:#F2F2F2" />
-    </linearGradient>
-    <linearGradient
-       x1="502.70749"
-       y1="115.3013"
-       x2="516.39001"
-       y2="127.1953"
-       id="linearGradient17862"
-       xlink:href="#XMLID_1749_"
-       gradientUnits="userSpaceOnUse"
-       gradientTransform="matrix(0.9703,0.2419,-0.2419,0.9703,-166.1427,-0.18283)" />
-    <linearGradient
-       x1="505.62939"
-       y1="-14.9526"
-       x2="527.49402"
-       y2="-0.7536"
-       id="linearGradient17864"
-       xlink:href="#XMLID_1756_"
-       gradientUnits="userSpaceOnUse"
-       gradientTransform="matrix(0.6868,0.4269,-0.9821,0.821,111.6149,-5.7901)" />
-    <defs
-       id="defs3859">
-      <polygon
-         points="465.54,213.52 481.94,217.46 482.74,216.71 487.46,198.05 471.08,194.07 470.26,194.83 465.54,213.52 "
-         id="XMLID_343_" />
-    </defs>
-    <linearGradient
-       x1="471.0806"
-       y1="201.07761"
-       x2="481.91711"
-       y2="210.4977"
-       id="linearGradient17389"
-       gradientUnits="userSpaceOnUse">
-      <stop
-         style="stop-color:#6498c1;stop-opacity:1"
-         offset="0.005618"
-         id="stop17391" />
-      <stop
-         style="stop-color:#79a9cc;stop-opacity:1"
-         offset="0.2332"
-         id="stop17393" />
-      <stop
-         style="stop-color:#a4cde2;stop-opacity:1"
-         offset="0.74049997"
-         id="stop17395" />
-      <stop
-         style="stop-color:#b4daea;stop-opacity:1"
-         offset="1"
-         id="stop17397" />
-      <a:midPointStop
-         style="stop-color:#6498C1"
-         offset="5.618000e-003" />
-      <a:midPointStop
-         style="stop-color:#6498C1"
-         offset="0.4438" />
-      <a:midPointStop
-         style="stop-color:#B4DAEA"
-         offset="1" />
-    </linearGradient>
-    <clipPath
-       id="clipPath17400">
-      <use
-         id="use17402"
-         x="0"
-         y="0"
-         width="744.09448"
-         height="600"
-         xlink:href="#XMLID_343_" />
-    </clipPath>
-    <linearGradient
-       x1="505.62939"
-       y1="-14.9526"
-       x2="527.49402"
-       y2="-0.7536"
-       id="linearGradient17404"
-       gradientUnits="userSpaceOnUse"
-       gradientTransform="matrix(0.6868,0.4269,-0.9821,0.821,111.6149,-5.7901)">
-      <stop
-         style="stop-color:#b4daea;stop-opacity:1"
-         offset="0"
-         id="stop17406" />
-      <stop
-         style="stop-color:#b4daea;stop-opacity:1"
-         offset="0.51120001"
-         id="stop17408" />
-      <stop
-         style="stop-color:#5387ba;stop-opacity:1"
-         offset="0.64609998"
-         id="stop17410" />
-      <stop
-         style="stop-color:#16336e;stop-opacity:1"
-         offset="1"
-         id="stop17412" />
-      <a:midPointStop
-         style="stop-color:#B4DAEA"
-         offset="0" />
-      <a:midPointStop
-         style="stop-color:#B4DAEA"
-         offset="0.5" />
-      <a:midPointStop
-         style="stop-color:#B4DAEA"
-         offset="0.5112" />
-      <a:midPointStop
-         style="stop-color:#B4DAEA"
-         offset="0.5" />
-      <a:midPointStop
-         style="stop-color:#5387BA"
-         offset="0.6461" />
-      <a:midPointStop
-         style="stop-color:#5387BA"
-         offset="0.5" />
-      <a:midPointStop
-         style="stop-color:#16336E"
-         offset="1" />
-    </linearGradient>
-    <linearGradient
-       x1="506.09909"
-       y1="-11.5137"
-       x2="527.99609"
-       y2="2.7063999"
-       id="linearGradient17882"
-       xlink:href="#XMLID_1752_"
-       gradientUnits="userSpaceOnUse"
-       gradientTransform="matrix(0.6868,0.4269,-0.9821,0.821,111.6149,-5.7901)" />
-    <defs
-       id="defs3826">
-      <polygon
-         points="463.52,216.14 480.56,220.24 481.36,219.5 483.03,202.04 469.05,196.69 468.24,197.45 463.52,216.14 "
-         id="XMLID_338_" />
-    </defs>
-    <linearGradient
-       x1="468.2915"
-       y1="204.7612"
-       x2="479.39871"
-       y2="214.4166"
-       id="linearGradient17357"
-       gradientUnits="userSpaceOnUse">
-      <stop
-         style="stop-color:#5387ba;stop-opacity:1"
-         offset="0"
-         id="stop17359" />
-      <stop
-         style="stop-color:#96bad6;stop-opacity:1"
-         offset="1"
-         id="stop17361" />
-      <a:midPointStop
-         style="stop-color:#5387BA"
-         offset="0" />
-      <a:midPointStop
-         style="stop-color:#5387BA"
-         offset="0.5" />
-      <a:midPointStop
-         style="stop-color:#96BAD6"
-         offset="1" />
-    </linearGradient>
-    <clipPath
-       id="clipPath17364">
-      <use
-         id="use17366"
-         x="0"
-         y="0"
-         width="744.09448"
-         height="600"
-         xlink:href="#XMLID_338_" />
-    </clipPath>
-    <linearGradient
-       x1="506.09909"
-       y1="-11.5137"
-       x2="527.99609"
-       y2="2.7063999"
-       id="linearGradient17368"
-       gradientUnits="userSpaceOnUse"
-       gradientTransform="matrix(0.6868,0.4269,-0.9821,0.821,111.6149,-5.7901)">
-      <stop
-         style="stop-color:#b4daea;stop-opacity:1"
-         offset="0"
-         id="stop17370" />
-      <stop
-         style="stop-color:#b4daea;stop-opacity:1"
-         offset="0.51120001"
-         id="stop17372" />
-      <stop
-         style="stop-color:#5387ba;stop-opacity:1"
-         offset="0.64609998"
-         id="stop17374" />
-      <stop
-         style="stop-color:#16336e;stop-opacity:1"
-         offset="1"
-         id="stop17376" />
-      <a:midPointStop
-         style="stop-color:#B4DAEA"
-         offset="0" />
-      <a:midPointStop
-         style="stop-color:#B4DAEA"
-         offset="0.5" />
-      <a:midPointStop
-         style="stop-color:#B4DAEA"
-         offset="0.5112" />
-      <a:midPointStop
-         style="stop-color:#B4DAEA"
-         offset="0.5" />
-      <a:midPointStop
-         style="stop-color:#5387BA"
-         offset="0.6461" />
-      <a:midPointStop
-         style="stop-color:#5387BA"
-         offset="0.5" />
-      <a:midPointStop
-         style="stop-color:#16336E"
-         offset="1" />
-    </linearGradient>
-    <linearGradient
-       x1="296.4996"
-       y1="188.81061"
-       x2="317.32471"
-       y2="209.69398"
-       id="linearGradient2387"
-       xlink:href="#linearGradient2381"
-       gradientUnits="userSpaceOnUse"
-       gradientTransform="matrix(0.90776,0,0,0.90776,24.35648,49.24131)" />
-    <linearGradient
-       x1="296.4996"
-       y1="188.81061"
-       x2="317.32471"
-       y2="209.69398"
-       id="linearGradient5105"
-       xlink:href="#linearGradient2381"
-       gradientUnits="userSpaceOnUse"
-       gradientTransform="matrix(0.90776,0,0,0.90776,24.35648,49.24131)" />
-    <linearGradient
-       x1="296.4996"
-       y1="188.81061"
-       x2="317.32471"
-       y2="209.69398"
-       id="linearGradient5145"
-       xlink:href="#linearGradient2381"
-       gradientUnits="userSpaceOnUse"
-       gradientTransform="matrix(0.90776,0,0,0.90776,24.35648,49.24131)" />
-    <linearGradient
-       inkscape:collect="always"
-       xlink:href="#linearGradient2381"
-       id="linearGradient2371"
-       gradientUnits="userSpaceOnUse"
-       gradientTransform="matrix(0.90776,0,0,0.90776,24.35648,49.24131)"
-       x1="296.4996"
-       y1="188.81061"
-       x2="317.32471"
-       y2="209.69398" />
-  </defs>
-  <g
-     transform="matrix(0.437808,-0.437808,0.437808,0.437808,-220.8237,43.55311)"
-     id="g5089">
-    <path
-       d="M 8.4382985,-6.28125 C 7.8309069,-6.28125 4.125,-0.33238729 4.125,1.96875 L 4.125,28.6875 C 4.125,29.533884 4.7068159,29.8125 5.28125,29.8125 L 30.84375,29.8125 C 31.476092,29.8125 31.968751,29.319842 31.96875,28.6875 L 31.96875,23.46875 L 32.25,23.46875 C 32.74684,23.46875 33.156249,23.059339 33.15625,22.5625 L 33.15625,-5.375 C 33.15625,-5.8718398 32.74684,-6.28125 32.25,-6.28125 L 8.4382985,-6.28125 z "
-       transform="translate(282.8327,227.1903)"
-       style="fill:#5c5c4f;stroke:black;stroke-width:3.23021388;stroke-miterlimit:4;stroke-dasharray:none"
-       id="path5091" />
-    <rect
-       width="27.85074"
-       height="29.369793"
-       rx="1.1414107"
-       ry="1.1414107"
-       x="286.96509"
-       y="227.63805"
-       style="fill:#032c87"
-       id="rect5093" />
-    <path
-       d="M 288.43262,225.43675 L 313.67442,225.43675 L 313.67442,254.80655 L 287.29827,254.83069 L 288.43262,225.43675 z "
-       style="fill:white"
-       id="rect5095" />
-    <path
-       d="M 302.44536,251.73726 C 303.83227,259.59643 301.75225,263.02091 301.75225,263.02091 C 303.99609,261.41329 305.71651,259.54397 306.65747,257.28491 C 307.62455,259.47755 308.49041,261.71357 310.9319,263.27432 C 310.9319,263.27432 309.33686,256.07392 309.22047,251.73726 L 302.44536,251.73726 z "
-       style="fill:#a70000;fill-opacity:1;stroke-width:2"
-       id="path5097" />
-    <rect
-       width="25.241802"
-       height="29.736675"
-       rx="0.89682275"
-       ry="0.89682275"
-       x="290.73544"
-       y="220.92249"
-       style="fill:#809cc9"
-       id="rect5099" />
-    <path
-       d="M 576.47347,725.93939 L 582.84431,726.35441 L 583.25121,755.8725 C 581.35919,754.55465 576.39694,752.1117 574.98889,754.19149 L 574.98889,727.42397 C 574.98889,726.60151 575.65101,725.93939 576.47347,725.93939 z "
-       transform="matrix(0.499065,-0.866565,0,1,0,0)"
-       style="fill:#4573b3;fill-opacity:1"
-       id="rect5101" />
-    <path
-       d="M 293.2599,221.89363 L 313.99908,221.89363 C 314.45009,221.89363 314.81318,222.25673 314.81318,222.70774 C 315.02865,229.0361 295.44494,244.47124 292.44579,240.30491 L 292.44579,222.70774 C 292.44579,222.25673 292.80889,221.89363 293.2599,221.89363 z "
-       style="opacity:0.65536726;fill:url(#linearGradient2371);fill-opacity:1"
-       id="path5103" />
-  </g>
-</svg>
diff --git a/en-US/images/initializing/initializing.png b/en-US/images/initializing/initializing.png
deleted file mode 100644
index a10b461..0000000
Binary files a/en-US/images/initializing/initializing.png and /dev/null differ
diff --git a/en-US/images/installationmethod/.svn/all-wcprops b/en-US/images/installationmethod/.svn/all-wcprops
deleted file mode 100644
index 8d1213e..0000000
--- a/en-US/images/installationmethod/.svn/all-wcprops
+++ /dev/null
@@ -1,11 +0,0 @@
-K 25
-svn:wc:ra_dav:version-url
-V 105
-/repos/ecs/!svn/ver/27523/Red_Hat_Enterprise_Linux/6.0/Installation_Guide/en-US/images/installationmethod
-END
-method.png
-K 25
-svn:wc:ra_dav:version-url
-V 116
-/repos/ecs/!svn/ver/27523/Red_Hat_Enterprise_Linux/6.0/Installation_Guide/en-US/images/installationmethod/method.png
-END
diff --git a/en-US/images/installationmethod/.svn/entries b/en-US/images/installationmethod/.svn/entries
deleted file mode 100644
index 368ac39..0000000
--- a/en-US/images/installationmethod/.svn/entries
+++ /dev/null
@@ -1,62 +0,0 @@
-10
-
-dir
-27523
-https://svn.devel.redhat.com/repos/ecs/Red_Hat_Enterprise_Linux/6.0/Installation_Guide/en-US/images/installationmethod
-https://svn.devel.redhat.com/repos/ecs
-
-
-
-2010-02-24T23:24:20.129538Z
-27523
-rlandman at REDHAT.COM
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-88604915-f33d-0410-84cb-d394843949d3
-
-method.png
-file
-
-
-
-
-2010-02-22T00:08:37.000000Z
-f74240f276919ae274f3cf5ffca40291
-2010-02-24T23:24:20.129538Z
-27523
-rlandman at REDHAT.COM
-has-props
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-2727
-
diff --git a/en-US/images/installationmethod/.svn/prop-base/method.png.svn-base b/en-US/images/installationmethod/.svn/prop-base/method.png.svn-base
deleted file mode 100644
index 5e9587e..0000000
--- a/en-US/images/installationmethod/.svn/prop-base/method.png.svn-base
+++ /dev/null
@@ -1,5 +0,0 @@
-K 13
-svn:mime-type
-V 24
-application/octet-stream
-END
diff --git a/en-US/images/installationmethod/.svn/text-base/method.png.svn-base b/en-US/images/installationmethod/.svn/text-base/method.png.svn-base
deleted file mode 100644
index dbd128b..0000000
Binary files a/en-US/images/installationmethod/.svn/text-base/method.png.svn-base and /dev/null differ
diff --git a/en-US/images/installationmethod/method.png b/en-US/images/installationmethod/method.png
deleted file mode 100644
index dbd128b..0000000
Binary files a/en-US/images/installationmethod/method.png and /dev/null differ
diff --git a/en-US/images/kbdconfig/keyboard.png b/en-US/images/kbdconfig/keyboard.png
deleted file mode 100644
index 5c118e1..0000000
Binary files a/en-US/images/kbdconfig/keyboard.png and /dev/null differ
diff --git a/en-US/images/ksconfig/ksconfig-auth.png b/en-US/images/ksconfig/ksconfig-auth.png
deleted file mode 100644
index 92b3724..0000000
Binary files a/en-US/images/ksconfig/ksconfig-auth.png and /dev/null differ
diff --git a/en-US/images/ksconfig/ksconfig-basic.png b/en-US/images/ksconfig/ksconfig-basic.png
deleted file mode 100644
index 185b231..0000000
Binary files a/en-US/images/ksconfig/ksconfig-basic.png and /dev/null differ
diff --git a/en-US/images/ksconfig/ksconfig-bootloader.png b/en-US/images/ksconfig/ksconfig-bootloader.png
deleted file mode 100644
index b9ee971..0000000
Binary files a/en-US/images/ksconfig/ksconfig-bootloader.png and /dev/null differ
diff --git a/en-US/images/ksconfig/ksconfig-confirm.png b/en-US/images/ksconfig/ksconfig-confirm.png
deleted file mode 100644
index 66fdc0e..0000000
Binary files a/en-US/images/ksconfig/ksconfig-confirm.png and /dev/null differ
diff --git a/en-US/images/ksconfig/ksconfig-firewall.png b/en-US/images/ksconfig/ksconfig-firewall.png
deleted file mode 100644
index 751ebcc..0000000
Binary files a/en-US/images/ksconfig/ksconfig-firewall.png and /dev/null differ
diff --git a/en-US/images/ksconfig/ksconfig-install.png b/en-US/images/ksconfig/ksconfig-install.png
deleted file mode 100644
index a7a047b..0000000
Binary files a/en-US/images/ksconfig/ksconfig-install.png and /dev/null differ
diff --git a/en-US/images/ksconfig/ksconfig-network.png b/en-US/images/ksconfig/ksconfig-network.png
deleted file mode 100644
index 453030b..0000000
Binary files a/en-US/images/ksconfig/ksconfig-network.png and /dev/null differ
diff --git a/en-US/images/ksconfig/ksconfig-part-options.png b/en-US/images/ksconfig/ksconfig-part-options.png
deleted file mode 100644
index d256baf..0000000
Binary files a/en-US/images/ksconfig/ksconfig-part-options.png and /dev/null differ
diff --git a/en-US/images/ksconfig/ksconfig-partitions.png b/en-US/images/ksconfig/ksconfig-partitions.png
deleted file mode 100644
index a7416b8..0000000
Binary files a/en-US/images/ksconfig/ksconfig-partitions.png and /dev/null differ
diff --git a/en-US/images/ksconfig/ksconfig-pkgs.png b/en-US/images/ksconfig/ksconfig-pkgs.png
deleted file mode 100644
index 41717d1..0000000
Binary files a/en-US/images/ksconfig/ksconfig-pkgs.png and /dev/null differ
diff --git a/en-US/images/ksconfig/ksconfig-postscript.png b/en-US/images/ksconfig/ksconfig-postscript.png
deleted file mode 100644
index 1259609..0000000
Binary files a/en-US/images/ksconfig/ksconfig-postscript.png and /dev/null differ
diff --git a/en-US/images/ksconfig/ksconfig-prescript.png b/en-US/images/ksconfig/ksconfig-prescript.png
deleted file mode 100644
index b7755c7..0000000
Binary files a/en-US/images/ksconfig/ksconfig-prescript.png and /dev/null differ
diff --git a/en-US/images/ksconfig/ksconfig-raid-device.png b/en-US/images/ksconfig/ksconfig-raid-device.png
deleted file mode 100644
index 7f00448..0000000
Binary files a/en-US/images/ksconfig/ksconfig-raid-device.png and /dev/null differ
diff --git a/en-US/images/ksconfig/ksconfig-raid-new.png b/en-US/images/ksconfig/ksconfig-raid-new.png
deleted file mode 100644
index f689b89..0000000
Binary files a/en-US/images/ksconfig/ksconfig-raid-new.png and /dev/null differ
diff --git a/en-US/images/ksconfig/ksconfig-xconfig.png b/en-US/images/ksconfig/ksconfig-xconfig.png
deleted file mode 100644
index 8ec59f8..0000000
Binary files a/en-US/images/ksconfig/ksconfig-xconfig.png and /dev/null differ
diff --git a/en-US/images/langselection/lang.png b/en-US/images/langselection/lang.png
deleted file mode 100644
index 7f28901..0000000
Binary files a/en-US/images/langselection/lang.png and /dev/null differ
diff --git a/en-US/images/netconfig/hostname.png b/en-US/images/netconfig/hostname.png
deleted file mode 100644
index 4eb3165..0000000
Binary files a/en-US/images/netconfig/hostname.png and /dev/null differ
diff --git a/en-US/images/netconfig/net-edit.png b/en-US/images/netconfig/net-edit.png
deleted file mode 100644
index fb787c6..0000000
Binary files a/en-US/images/netconfig/net-edit.png and /dev/null differ
diff --git a/en-US/images/nextsteps/updating.png b/en-US/images/nextsteps/updating.png
deleted file mode 100644
index cfea6e4..0000000
Binary files a/en-US/images/nextsteps/updating.png and /dev/null differ
diff --git a/en-US/images/partitions/compression.png b/en-US/images/partitions/compression.png
deleted file mode 100644
index 690614a..0000000
Binary files a/en-US/images/partitions/compression.png and /dev/null differ
diff --git a/en-US/images/partitions/dos-single-partition.png b/en-US/images/partitions/dos-single-partition.png
deleted file mode 100644
index 0220cf8..0000000
Binary files a/en-US/images/partitions/dos-single-partition.png and /dev/null differ
diff --git a/en-US/images/partitions/dstrct-reprt.png b/en-US/images/partitions/dstrct-reprt.png
deleted file mode 100644
index cb6fb5c..0000000
Binary files a/en-US/images/partitions/dstrct-reprt.png and /dev/null differ
diff --git a/en-US/images/partitions/extended-partitions.png b/en-US/images/partitions/extended-partitions.png
deleted file mode 100644
index 61ec9de..0000000
Binary files a/en-US/images/partitions/extended-partitions.png and /dev/null differ
diff --git a/en-US/images/partitions/formatted-drive.png b/en-US/images/partitions/formatted-drive.png
deleted file mode 100644
index 52139e0..0000000
Binary files a/en-US/images/partitions/formatted-drive.png and /dev/null differ
diff --git a/en-US/images/partitions/nondestruct-fin.png b/en-US/images/partitions/nondestruct-fin.png
deleted file mode 100644
index c1bc2f4..0000000
Binary files a/en-US/images/partitions/nondestruct-fin.png and /dev/null differ
diff --git a/en-US/images/partitions/other-formatted-drive.png b/en-US/images/partitions/other-formatted-drive.png
deleted file mode 100644
index 9675179..0000000
Binary files a/en-US/images/partitions/other-formatted-drive.png and /dev/null differ
diff --git a/en-US/images/partitions/part-resize.png b/en-US/images/partitions/part-resize.png
deleted file mode 100644
index d8debc8..0000000
Binary files a/en-US/images/partitions/part-resize.png and /dev/null differ
diff --git a/en-US/images/partitions/unpart-space.png b/en-US/images/partitions/unpart-space.png
deleted file mode 100644
index 7bdebe8..0000000
Binary files a/en-US/images/partitions/unpart-space.png and /dev/null differ
diff --git a/en-US/images/partitions/unused-drive.png b/en-US/images/partitions/unused-drive.png
deleted file mode 100644
index 08ccd68..0000000
Binary files a/en-US/images/partitions/unused-drive.png and /dev/null differ
diff --git a/en-US/images/partitions/unused-partition.png b/en-US/images/partitions/unused-partition.png
deleted file mode 100644
index 9622aba..0000000
Binary files a/en-US/images/partitions/unused-partition.png and /dev/null differ
diff --git a/en-US/images/partitions/unused-partitioned-drive.png b/en-US/images/partitions/unused-partitioned-drive.png
deleted file mode 100644
index 8a6925d..0000000
Binary files a/en-US/images/partitions/unused-partitioned-drive.png and /dev/null differ
diff --git a/en-US/images/partitions/used-formatted-drive.png b/en-US/images/partitions/used-formatted-drive.png
deleted file mode 100644
index e7ae5c2..0000000
Binary files a/en-US/images/partitions/used-formatted-drive.png and /dev/null differ
diff --git a/en-US/images/pkgselection/pkg-group-details.png b/en-US/images/pkgselection/pkg-group-details.png
deleted file mode 100644
index 663627d..0000000
Binary files a/en-US/images/pkgselection/pkg-group-details.png and /dev/null differ
diff --git a/en-US/images/pkgselection/pkg-group-repos.png b/en-US/images/pkgselection/pkg-group-repos.png
deleted file mode 100644
index 76785da..0000000
Binary files a/en-US/images/pkgselection/pkg-group-repos.png and /dev/null differ
diff --git a/en-US/images/pkgselection/pkg-group.png b/en-US/images/pkgselection/pkg-group.png
deleted file mode 100644
index 5b44bd0..0000000
Binary files a/en-US/images/pkgselection/pkg-group.png and /dev/null differ
diff --git a/en-US/images/pxe/netboot-add-host-dialog.png b/en-US/images/pxe/netboot-add-host-dialog.png
deleted file mode 100644
index 32af362..0000000
Binary files a/en-US/images/pxe/netboot-add-host-dialog.png and /dev/null differ
diff --git a/en-US/images/pxe/netboot-add-hosts.png b/en-US/images/pxe/netboot-add-hosts.png
deleted file mode 100644
index da2235e..0000000
Binary files a/en-US/images/pxe/netboot-add-hosts.png and /dev/null differ
diff --git a/en-US/images/storagedevices/.svn/all-wcprops b/en-US/images/storagedevices/.svn/all-wcprops
deleted file mode 100644
index 8ca4199..0000000
--- a/en-US/images/storagedevices/.svn/all-wcprops
+++ /dev/null
@@ -1,35 +0,0 @@
-K 25
-svn:wc:ra_dav:version-url
-V 101
-/repos/ecs/!svn/ver/27523/Red_Hat_Enterprise_Linux/6.0/Installation_Guide/en-US/images/storagedevices
-END
-assignstoragedevices.png
-K 25
-svn:wc:ra_dav:version-url
-V 126
-/repos/ecs/!svn/ver/27762/Red_Hat_Enterprise_Linux/6.0/Installation_Guide/en-US/images/storagedevices/assignstoragedevices.png
-END
-searchstoragedevices.png
-K 25
-svn:wc:ra_dav:version-url
-V 126
-/repos/ecs/!svn/ver/27523/Red_Hat_Enterprise_Linux/6.0/Installation_Guide/en-US/images/storagedevices/searchstoragedevices.png
-END
-selectstoragedevices.png
-K 25
-svn:wc:ra_dav:version-url
-V 126
-/repos/ecs/!svn/ver/27523/Red_Hat_Enterprise_Linux/6.0/Installation_Guide/en-US/images/storagedevices/selectstoragedevices.png
-END
-storagedevices.png
-K 25
-svn:wc:ra_dav:version-url
-V 120
-/repos/ecs/!svn/ver/27523/Red_Hat_Enterprise_Linux/6.0/Installation_Guide/en-US/images/storagedevices/storagedevices.png
-END
-storagedevicescolumns.png
-K 25
-svn:wc:ra_dav:version-url
-V 127
-/repos/ecs/!svn/ver/27523/Red_Hat_Enterprise_Linux/6.0/Installation_Guide/en-US/images/storagedevices/storagedevicescolumns.png
-END
diff --git a/en-US/images/storagedevices/.svn/entries b/en-US/images/storagedevices/.svn/entries
deleted file mode 100644
index ad169da..0000000
--- a/en-US/images/storagedevices/.svn/entries
+++ /dev/null
@@ -1,198 +0,0 @@
-10
-
-dir
-27523
-https://svn.devel.redhat.com/repos/ecs/Red_Hat_Enterprise_Linux/6.0/Installation_Guide/en-US/images/storagedevices
-https://svn.devel.redhat.com/repos/ecs
-
-
-
-2010-02-24T23:24:20.129538Z
-27523
-rlandman at REDHAT.COM
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-88604915-f33d-0410-84cb-d394843949d3
-
-assignstoragedevices.png
-file
-27762
-
-
-
-2010-03-01T00:28:53.000000Z
-5b2cbfa2972215e77225a07b312ab27d
-2010-03-01T00:53:43.748712Z
-27762
-rlandman at REDHAT.COM
-has-props
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-46137
-
-searchstoragedevices.png
-file
-
-
-
-
-2010-02-23T01:55:09.000000Z
-7d2ebd1e07ded0854f3c4467fa581f77
-2010-02-24T23:24:20.129538Z
-27523
-rlandman at REDHAT.COM
-has-props
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-19058
-
-selectstoragedevices.png
-file
-
-
-
-
-2010-02-23T01:24:50.000000Z
-a47f847879951d9477437ae94367673d
-2010-02-24T23:24:20.129538Z
-27523
-rlandman at REDHAT.COM
-has-props
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-42974
-
-storagedevices.png
-file
-
-
-
-
-2010-02-23T11:18:16.000000Z
-30a39c0905c0b7448ace35ddb11b8026
-2010-02-24T23:24:20.129538Z
-27523
-rlandman at REDHAT.COM
-has-props
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-25528
-
-storagedevicescolumns.png
-file
-
-
-
-
-2010-02-23T02:26:51.000000Z
-5351a33c27a3c539a9420dffa1b232e3
-2010-02-24T23:24:20.129538Z
-27523
-rlandman at REDHAT.COM
-has-props
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-15554
-
diff --git a/en-US/images/storagedevices/.svn/prop-base/assignstoragedevices.png.svn-base b/en-US/images/storagedevices/.svn/prop-base/assignstoragedevices.png.svn-base
deleted file mode 100644
index 5e9587e..0000000
--- a/en-US/images/storagedevices/.svn/prop-base/assignstoragedevices.png.svn-base
+++ /dev/null
@@ -1,5 +0,0 @@
-K 13
-svn:mime-type
-V 24
-application/octet-stream
-END
diff --git a/en-US/images/storagedevices/.svn/prop-base/searchstoragedevices.png.svn-base b/en-US/images/storagedevices/.svn/prop-base/searchstoragedevices.png.svn-base
deleted file mode 100644
index 5e9587e..0000000
--- a/en-US/images/storagedevices/.svn/prop-base/searchstoragedevices.png.svn-base
+++ /dev/null
@@ -1,5 +0,0 @@
-K 13
-svn:mime-type
-V 24
-application/octet-stream
-END
diff --git a/en-US/images/storagedevices/.svn/prop-base/selectstoragedevices.png.svn-base b/en-US/images/storagedevices/.svn/prop-base/selectstoragedevices.png.svn-base
deleted file mode 100644
index 5e9587e..0000000
--- a/en-US/images/storagedevices/.svn/prop-base/selectstoragedevices.png.svn-base
+++ /dev/null
@@ -1,5 +0,0 @@
-K 13
-svn:mime-type
-V 24
-application/octet-stream
-END
diff --git a/en-US/images/storagedevices/.svn/prop-base/storagedevices.png.svn-base b/en-US/images/storagedevices/.svn/prop-base/storagedevices.png.svn-base
deleted file mode 100644
index 5e9587e..0000000
--- a/en-US/images/storagedevices/.svn/prop-base/storagedevices.png.svn-base
+++ /dev/null
@@ -1,5 +0,0 @@
-K 13
-svn:mime-type
-V 24
-application/octet-stream
-END
diff --git a/en-US/images/storagedevices/.svn/prop-base/storagedevicescolumns.png.svn-base b/en-US/images/storagedevices/.svn/prop-base/storagedevicescolumns.png.svn-base
deleted file mode 100644
index 5e9587e..0000000
--- a/en-US/images/storagedevices/.svn/prop-base/storagedevicescolumns.png.svn-base
+++ /dev/null
@@ -1,5 +0,0 @@
-K 13
-svn:mime-type
-V 24
-application/octet-stream
-END
diff --git a/en-US/images/storagedevices/.svn/text-base/assignstoragedevices.png.svn-base b/en-US/images/storagedevices/.svn/text-base/assignstoragedevices.png.svn-base
deleted file mode 100644
index 51c542f..0000000
Binary files a/en-US/images/storagedevices/.svn/text-base/assignstoragedevices.png.svn-base and /dev/null differ
diff --git a/en-US/images/storagedevices/.svn/text-base/searchstoragedevices.png.svn-base b/en-US/images/storagedevices/.svn/text-base/searchstoragedevices.png.svn-base
deleted file mode 100644
index 4f96463..0000000
Binary files a/en-US/images/storagedevices/.svn/text-base/searchstoragedevices.png.svn-base and /dev/null differ
diff --git a/en-US/images/storagedevices/.svn/text-base/selectstoragedevices.png.svn-base b/en-US/images/storagedevices/.svn/text-base/selectstoragedevices.png.svn-base
deleted file mode 100644
index 99c5dd8..0000000
Binary files a/en-US/images/storagedevices/.svn/text-base/selectstoragedevices.png.svn-base and /dev/null differ
diff --git a/en-US/images/storagedevices/.svn/text-base/storagedevices.png.svn-base b/en-US/images/storagedevices/.svn/text-base/storagedevices.png.svn-base
deleted file mode 100644
index a2a3af2..0000000
Binary files a/en-US/images/storagedevices/.svn/text-base/storagedevices.png.svn-base and /dev/null differ
diff --git a/en-US/images/storagedevices/.svn/text-base/storagedevicescolumns.png.svn-base b/en-US/images/storagedevices/.svn/text-base/storagedevicescolumns.png.svn-base
deleted file mode 100644
index d1a86fe..0000000
Binary files a/en-US/images/storagedevices/.svn/text-base/storagedevicescolumns.png.svn-base and /dev/null differ
diff --git a/en-US/images/storagedevices/assignstoragedevices.png b/en-US/images/storagedevices/assignstoragedevices.png
deleted file mode 100644
index 51c542f..0000000
Binary files a/en-US/images/storagedevices/assignstoragedevices.png and /dev/null differ
diff --git a/en-US/images/storagedevices/searchstoragedevices.png b/en-US/images/storagedevices/searchstoragedevices.png
deleted file mode 100644
index 4f96463..0000000
Binary files a/en-US/images/storagedevices/searchstoragedevices.png and /dev/null differ
diff --git a/en-US/images/storagedevices/selectstoragedevices.png b/en-US/images/storagedevices/selectstoragedevices.png
deleted file mode 100644
index 99c5dd8..0000000
Binary files a/en-US/images/storagedevices/selectstoragedevices.png and /dev/null differ
diff --git a/en-US/images/storagedevices/storagedevices.png b/en-US/images/storagedevices/storagedevices.png
deleted file mode 100644
index a2a3af2..0000000
Binary files a/en-US/images/storagedevices/storagedevices.png and /dev/null differ
diff --git a/en-US/images/storagedevices/storagedevicescolumns.png b/en-US/images/storagedevices/storagedevicescolumns.png
deleted file mode 100644
index d1a86fe..0000000
Binary files a/en-US/images/storagedevices/storagedevicescolumns.png and /dev/null differ
diff --git a/en-US/images/timezone/timezone.png b/en-US/images/timezone/timezone.png
deleted file mode 100644
index b57b6c4..0000000
Binary files a/en-US/images/timezone/timezone.png and /dev/null differ
diff --git a/en-US/images/upgrading/upgradebootloader.png b/en-US/images/upgrading/upgradebootloader.png
deleted file mode 100644
index 5684228..0000000
Binary files a/en-US/images/upgrading/upgradebootloader.png and /dev/null differ
diff --git a/en-US/images/upgrading/upgrading.png b/en-US/images/upgrading/upgrading.png
deleted file mode 100644
index f7701e6..0000000
Binary files a/en-US/images/upgrading/upgrading.png and /dev/null differ
diff --git a/en-US/images/welcome/welcome.png b/en-US/images/welcome/welcome.png
deleted file mode 100644
index b92011f..0000000
Binary files a/en-US/images/welcome/welcome.png and /dev/null differ
diff --git a/en-US/images/x86-bootloader/x86-adv-bootloader.png b/en-US/images/x86-bootloader/x86-adv-bootloader.png
deleted file mode 100644
index 863ee12..0000000
Binary files a/en-US/images/x86-bootloader/x86-adv-bootloader.png and /dev/null differ
diff --git a/en-US/images/x86-bootloader/x86-bootloader.png b/en-US/images/x86-bootloader/x86-bootloader.png
deleted file mode 100644
index 73b9f59..0000000
Binary files a/en-US/images/x86-bootloader/x86-bootloader.png and /dev/null differ
diff --git a/en-US/intro.xml b/en-US/intro.xml
deleted file mode 100644
index e6c56c9..0000000
--- a/en-US/intro.xml
+++ /dev/null
@@ -1,69 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
-"http://www.docbook.org/xml/4.4/docbookx.dtd" [
-]>
-
-<preface id="ch-introduction">
-  <title>Introduction</title>
-  <para>This guide covers installation of Fedora, a Linux distribution
-    built on free and open source software. This manual helps you
-    install Fedora on desktops, laptops, and servers. The installation
-    system is easy to use even if you lack previous
-    knowledge of Linux or computer networks. If you select default
-    options, Fedora provides a complete desktop operating system,
-    including productivity applications, Internet utilities, and desktop
-    tools.</para>
-  <para>This document details the full range of installation options, including those that apply only in limited or unusual circumstances. The <citetitle>Fedora &PRODVER; Installation Quick Start Guide</citetitle> provides a much-abbreviated set of instructions for downloading Fedora, creating an installation disc, and installing Fedora on a typical desktop or laptop computer. The <citetitle>Fedora &PRODVER; Installation Quick Start Guide</citetitle> is available from <ulink url="http://docs.fedoraproject.org/installation-quick-start-guide/"></ulink>.</para>
-  <section id="sn-background">
-    <title>Background</title>
-    <section id="sn-about-fedora">
-      <title>About Fedora</title>
-      <para>To find out more about Fedora, refer to <ulink
-	  url="http://fedoraproject.org/"/>. To read other documentation
-	on Fedora related topics, refer to <ulink
-	  url="http://docs.fedoraproject.org/"/>.</para>
-    </section>
-    <section id="sn-additional-help">
-      <title>Getting Additional Help</title>
-      <para>For information on additional help resources for Fedora,
-	visit <ulink
-	  url="http://fedoraproject.org/wiki/Communicate"/>.</para>
-    </section>
-  </section>
-  <section id="sn-about-document">
-    <title>About This Document</title>
-    <section id="sn-goals">
-      <title>Goals</title>
-      <para>This guide helps a reader:</para>
-      <orderedlist>
-	<listitem>
-	  <para>Understand how to locate the Fedora distribution
-	    online</para>
-	</listitem>
-	<listitem>
-	  <para>Create configuration data that allows a computer to boot
-	    Fedora</para>
-	</listitem>
-	<listitem>
-	  <para>Understand and interact with the Fedora installation
-	    program</para>
-	</listitem>
-	<listitem>
-	  <para>Complete basic post-installation configuration of a
-	    Fedora system</para>
-	</listitem>
-      </orderedlist>
-      <note>
-	<title>Other Sources of Documentation</title>
-	<para>This guide does not cover use of Fedora. To learn how to
-	  use an installed Fedora system, refer to <ulink
-	    url="http://docs.fedoraproject.org/"/> for other
-	  documentation.</para>
-      </note>
-    </section>
-    <section id="sn-audience">
-      <title>Audience</title>
-      <para>This guide is intended for Fedora users of all levels of experience. However, it treats the installation process and its many options in far greater detail than most novice users are likely to require. You do not need to read and understand this entire document to install Fedora on a computer. This document is most likely to help experienced users perform advanced and unusual installations.</para>
-    </section>
-  </section>
-</preface>
diff --git a/en-US/medialess.xml b/en-US/medialess.xml
deleted file mode 100644
index df6fb2a..0000000
--- a/en-US/medialess.xml
+++ /dev/null
@@ -1,136 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE appendix PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
-"http://www.docbook.org/xml/4.4/docbookx.dtd" [
-]>
-
-<chapter id='ap-medialess-install'>
-	<title>Installing Without Media</title>
-	<important>
-		<title>Linux Required</title>
-		<para>
-			This procedure assumes you are already using Fedora or another relatively modern Linux distribution, and the <application>GRUB</application> boot loader. It also assumes you are a somewhat experienced Linux user.
-		</para>
-	</important>
-	<note>
-		<title>Preupgrade</title>
-		<para>
-			If you have an earlier version of Fedora installed on your system, you might be able to upgrade to Fedora &PRODVER; without making additional physical media by using the <application>preupgrade</application> tool. Refer to <xref linkend="ch-upgrade-x86"/> for details of using <application>preupgrade</application>. 
-		</para>
-	</note>
-	<para>
-		This section discusses how to install Fedora to your system without making any additional physical media.  Instead, you can use your existing <application>GRUB</application> boot loader to start the installation program.
-	</para>
-
-  <section id="sn-medialess-getting-files">
-    <title>Retrieving Boot Files</title>
-    <para>To perform an installation without media or a PXE server, your
-      system must have two files stored locally, a kernel and an initial
-      RAM disk.</para>
-    <procedure>
-      <step>
-	<para>Download a Live image or DVD distribution, or to locate an
-	  installation mirror, visit <ulink
-	    url="http://mirrors.fedoraproject.org/publiclist/Fedora/13/"/>.</para>
-      </step>
-      <step>
-	<para>Locate the <filename
-	    class="directory">isolinux/</filename> folder using one of
-	  the following methods:</para>
-	<itemizedlist>
-	  <listitem>
-	    <para>If you chose to download an image, open it with the
-	      appropriate desktop tool.  If you are using Fedora,
-	      double-click the file to open it with the
-	      <application>Archive Manager</application>.  Open the
-	      <filename class="directory">isolinux/</filename>
-	      folder.</para>
-	  </listitem>
-	  <listitem>
-	    <para>If you chose not to download a whole image because you
-	      wish to install via the network, locate the desired
-	      release. In general, once you find a suitable mirror,
-	      browse to the
-	      <filename>releases/&PRODVER;/Fedora/<replaceable>arch</replaceable>/os/isolinux/</filename> 
-	      folder.</para>
-	  </listitem>
-	</itemizedlist>
-	<note>
-	  <title>Installation Types Available</title>
-	  <para>If you download an image, you may then choose a hard
-	    disk-based installation or a network installation.  If you
-	    only download selected files from a mirror, you may only
-	    perform a network installation.</para>
-	</note>
-      </step>
-      <step>
-	<para>Copy the <filename>vmlinuz</filename> and
-	  <filename>initrd.img</filename> files from the chosen source
-	  to the <filename class="directory">/boot/</filename>
-	  directory, renaming them to
-	  <filename>vmlinuz-install</filename> and
-	  <filename>initrd.img-install</filename>You must have
-	  <systemitem class="username">root</systemitem> privileges to
-	  write files into the <filename
-	    class="directory">/boot/</filename> directory.</para>
-      </step>
-    </procedure>
-  </section>
-  <section id="sn-medialess-editing-grub-conf">
-    <title>Editing the <application>GRUB</application>
-      Configuration</title>
-    <para>The <application>GRUB</application> boot loader uses the
-      configuration file <filename>/boot/grub/grub.conf</filename>. To
-      configure <application>GRUB</application> to boot from the new
-      files, add a boot stanza to
-      <filename>/boot/grub/grub.conf</filename>that refers to
-      them.</para>
-    <para>A minimal boot stanza looks like the following listing:</para>
-    <screen><![CDATA[title Installation
-        root (hd0,0)
-        kernel /vmlinuz-install
-        initrd /initrd.img-install]]></screen>
-    <para>You may wish to add options to the end of the
-      <option>kernel</option> line of the boot stanza.  These options
-      set preliminary options in <application>Anaconda</application>
-      which the user normally sets interactively.  For a list of
-      available installer boot options, refer to <xref
-	linkend="ap-admin-options"/>.</para>
-    <para>The following options are generally useful for medialess
-      installations:</para>
-    <itemizedlist>
-      <listitem>
-	<para><option>ip=</option></para>
-      </listitem>
-      <listitem>
-	<para><option>repo=</option></para>
-      </listitem>
-      <listitem>
-	<para><option>lang=</option></para>
-      </listitem>
-      <listitem>
-	<para><option>keymap=</option></para>
-      </listitem>
-      <listitem>
-	<para><option>ksdevice=</option> (if installation requires an
-	  interface other than eth0)</para>
-      </listitem>
-      <listitem>
-	<para><option>vnc</option> and <option>vncpassword=</option> for
-	  a remote installation</para>
-      </listitem>
-    </itemizedlist>
-    <para>When you are finished, change the <option>default</option>
-      option in <filename>/boot/grub/grub.conf</filename> to point to
-      the new first stanza you added:</para>
-    <screen><![CDATA[default 0]]></screen>
-  </section>
-  <section id="sn-medialess-booting">
-    <title>Booting to Installation</title>
-    <para>Reboot the system.  <application>GRUB</application> boots the
-      installation kernel and RAM disk, including any options you set.
-      You may now refer to the appropriate chapter in this guide for the
-      next step.  If you chose to install remotely using VNC, refer to
-      <xref linkend="sn-remoteaccess-installation"/> for assistance in
-      connecting to the remote system.</para>
-  </section>
-</chapter>
diff --git a/en-US/networkconfig-fedora.xml b/en-US/networkconfig-fedora.xml
deleted file mode 100644
index d5f71e6..0000000
--- a/en-US/networkconfig-fedora.xml
+++ /dev/null
@@ -1,158 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
- "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
-]>
-
-<!-- $Id: -->
-
-<section id="sn-networkconfig-fedora">
-  <title>Setting the Hostname</title>
-
-<!-- Indexterms -->
-<indexterm>
-      <primary>DHCP (Dynamic Host Configuration Protocol)</primary>
-    </indexterm>
-  <indexterm>
-    <primary>IPv4</primary>
-  </indexterm>
-  <indexterm>
-	<primary>hostname</primary>
-      </indexterm>
-  <indexterm> <primary>modem</primary>
-	</indexterm>
-<!-- end Indexterms -->
-
-    <para>
-	    Fedora contains support for both IPv4 and IPv6. However, by default, the installation program configures network interfaces on your computer for IPv4, and to use DHCP via <application>NetworkManager</application>. Currently <application>NetworkManager</application> does not support IPv6. If your network only supports IPv6 you should use <application>system-config-network</application> after installation to configure your network interfaces.
-    </para>
-
-  <para>
-	  Setup prompts you to supply a host name and domain name for this computer, in the format <replaceable>hostname</replaceable>.<replaceable>domainname</replaceable>. Many networks have a  DHCP (Dynamic Host Configuration Protocol) service that automatically supplies connected systems with a domain name, leaving the user to enter a hostname.
-  </para>
-  
-  <para>
-	  Unless you have a specific need to customize the host name and domain name, the default setting  <literal>localhost.localdomain</literal> is a good choice for most users.
-  </para>
-
-    	<figure float="0" id="fig-networkconfig-fedora"><title>Setting the hostname</title>
-		<mediaobject>
-			<imageobject><imagedata fileref="images/netconfig/hostname.png" format="PNG"/></imageobject>
-			<textobject><para>
-					Setting the hostname
-				</para>
-			</textobject>
-		</mediaobject>
-	</figure>
-    
-    <para>
-	    To set up a network that is behind an Internet firewall or router, you may want to use <systemitem class="fqdomainname"><replaceable>hostname</replaceable>.localdomain</systemitem> for your Fedora system.  If you have more than one computer on this network, you should give each one a separate host name in this domain.
-      </para>
-    <note>
-      <title>Valid Hostnames</title>
-      <para>
-	You may give your system any name provided that the full
-	hostname is unique.  The hostname may include letters, numbers
-	and hyphens.
-      </para>
-    </note>
-    
-        <para>
-	      On some networks, the DHCP provider also provides the name of the computer, or hostname. The complete hostname includes both the name of the machine and the name of the domain of which it is a member, such as <systemitem class="fqdomainname"><replaceable>machine1.example.com</replaceable></systemitem>. The machine name (or "short hostname") is <systemitem class="systemname"><replaceable>machine1</replaceable></systemitem>, and the <indexterm> <primary>domain name</primary> </indexterm> domain name is <systemitem class="domainname"><replaceable>example.com</replaceable></systemitem>.
-    </para>
-    
-    <para>If your Fedora system is connected
-      <emphasis>directly</emphasis> to the Internet, you must pay
-      attention to additional considerations to avoid service
-      interruptions or risk action by your upstream service provider.  A
-      full discussion of these issues is beyond the scope of this
-      document.</para>
-    
-
- <note>
-      <title>Modem Configuration</title>
-      <para>
-	The installation program does not configure modems.  Configure these devices after installation
-	with the <application>Network</application> utility. The
-	settings for your modem are specific to your particular Internet
-	Service Provider (ISP).
-      </para>
-    </note>
-
-<!--	<section id="sn-networkconfig-fedora_manual-configuration">
-	<title>Manual configuration</title>
-		<para>
-			Installations that require certain advanced configurations cannot succeed without network connectivity during the installation process, for example, installations on systems with ISCSI drives. In situations where successful installation depends upon correct network settings, the installation program will present you with a dialog that allows you to confirm these details. 
-		</para>
-		
-		    	<figure float="0" id="fig-networkconfig-net-edit"><title>Manual network configuration</title>
-				<mediaobject>
-					<imageobject><imagedata fileref="images/netconfig/net-edit.png" format="PNG"/></imageobject>
-					<textobject><para>
-							Manual network configuration
-						</para>
-					</textobject>
-				</mediaobject>
-			</figure>
-	
-		<para>
-			If your network does not have DHCP enabled, or if you need to override the DHCP settings, select the network interface that you plan to use from the <guilabel>Interfaces</guilabel> menu. Clear the checkbox for <guilabel>Use dynamic IP configuration (DHCP)</guilabel>. You can now enter an IPv4 address and netmask for this system in the form <replaceable>address</replaceable>&nbsp;/&nbsp;<replaceable>netmask</replaceable>, along with the gateway address and nameserver address for your network. 
-		</para>
-		
-		<para>
-			Click <guilabel>OK</guilabel> to accept these settings and continue.
-		</para>
-			  
-	</section>
-
-
-      <section id="sn-hostname">
-    <title>Hostname</title>
-  <section id="sn-network-misc-settings">
-    <title>Miscellaneous Settings</title>
-    <para>
-      To manually configure a network interface, you may also provide
-      other network settings for your computer. All of these settings
-      are the IP addresses of other systems on the network.
-    </para>
-
-    <para>
-      A <firstterm>gateway</firstterm> <indexterm>
-	<primary>gateway</primary>
-      </indexterm> is the device that provides access to other networks.
-      Gateways are also referred to as <indexterm>
-	<primary>router</primary>
-	<see>gateway</see>
-      </indexterm> <firstterm>routers</firstterm>.  If your system
-      connects to other networks through a gateway, enter its IP address
-      in the <guilabel>Gateway</guilabel> box.
-    </para>
-
-    <para>
-      Most software relies on the <indexterm>
-	<primary>DNS (Domain Name Service)</primary>
-      </indexterm> <firstterm>DNS</firstterm> (Domain Name Service)
-      provider to locate machines and services on the network.  DNS
-      converts hostnames to IP addresses and vice versa.  A Fedora system
-      may use more than one DNS server.  If the primary DNS server does
-      not respond, the computer sends any query to the secondary DNS
-      server, and so on.  To assign DNS servers, type their IP addresses
-      into the <guilabel>Primary DNS</guilabel> or <guilabel>Secondary
-	DNS</guilabel> boxes.
-    </para>
-
-    <para>
-      Select <guibutton>Next</guibutton> once you are satisfied with the
-      network settings for your system.
-    </para>
-
-  </section>
-Commented out this section since network configuration is really transparent now. DJN
--->
-</section>
-
-<!--
-Local variables:
-mode: xml
-fill-column: 72
-End:
--->
diff --git a/en-US/new-users.xml b/en-US/new-users.xml
deleted file mode 100644
index ac917ae..0000000
--- a/en-US/new-users.xml
+++ /dev/null
@@ -1,315 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
-"http://www.docbook.org/xml/4.4/docbookx.dtd" [
-]>
-
-<chapter id="ch-new-users">
-  <title>Obtaining Fedora</title>
-  <indexterm>
-	<primary>CD/DVD media</primary>
-	<secondary>downloading</secondary>
-	<seealso>ISO images</seealso>
-      </indexterm>
-      <indexterm>
-	<primary>ISO images</primary>
-	<secondary>downloading</secondary>
-      </indexterm>
-      <indexterm>
-	<primary>USB flash media</primary>
-	<secondary>downloading</secondary>
-      </indexterm>
-  <para>
-    This chapter explains how to get the files you need to install and
-    run Fedora on your computer.  Concepts in this chapter
-    may be new, especially if this is your first free and open source
-    operating system.  If you have any trouble with this chapter, find 
-    help by visiting the Fedora Forums at <ulink
-    url="http://www.fedoraforum.org/"/>.
-  </para>
-
-    <para>The Fedora Project distributes Fedora in many ways, mostly free of 
-      cost and downloaded over the Internet. The most common
-      distribution method is CD and DVD media. There are several types
-      of CD and DVD media available, including:</para>
-    <itemizedlist>
-      <listitem>
-	<para>A full set of the software on DVD media</para>
-      </listitem>
-      <listitem>
-	<para>Live images you can use to try Fedora, and then install
-	to your system if you so choose</para>
-      </listitem>
-      <listitem>
-	<para>Reduced-size bootable CD and USB flash disk images you can
-	use to install over an Internet connection</para>
-      </listitem>
-      <listitem>
-	<para>Source code on DVD media</para>
-      </listitem>
-    </itemizedlist>
-    <para>Most users want the Fedora Live image or the full set of
-      installable software on DVD or CDs.  The reduced bootable images are
-      suitable for use with a fast Internet connection and install Fedora 
-      on one computer.  Source code discs are not used for installing Fedora, 
-      but are resources for experienced users and software developers.</para>
-
-      
-      <para>Users with a broadband Internet connection can download
-	<firstterm>ISO images</firstterm> of CD and DVD media or images
-	of USB flash disks.  An ISO image is a copy of an entire disc in
-	a format suitable for writing directly to a CD or DVD.  A USB
-	flash disk image is a copy of an entire disk in a format
-	suitable for writing directly to a USB flash disk.</para>
-      <para>For more information on burning CDs and DVDs, refer to
-	<xref linkend="sn-making-media"/>.</para>
-
-    
-    <para>
-        If downloading the Fedora ISO images and burning them to CD or DVD is impossible or impractical for you, refer to <xref linkend="sect-Obtaining_Fedora-Obtaining_Fedora_on_CD_or_DVD"/> to learn about other ways that you can obtain Fedora. 
-      </para>
-
-<section id="sect-Obtaining_Fedora-Downloading_Fedora">
-<title>Downloading Fedora</title>
-  <section id="sn-howto-download">
-    <title>How Do I Download Installation Files?</title>
-  <note>
-    <title>Download Links</title>
-    <para>
-      To follow a Web-based guide to downloading, visit <ulink
-      url="http://get.fedoraproject.org/"/>.  For guidance on which
-      architecture to download, refer to <xref
-      linkend="sn-which-arch"/>.
-    </para>
-  </note>
-
-<para>Fedora software is available for download at no cost in a
-      variety of ways. </para>
-    <section id="sn-which-download-mirror">
-      <title>From a Mirror</title>
-      <indexterm>
-	<primary>mirror</primary>
-      </indexterm>
-      <para>The Fedora installation files are freely available from web servers located in many parts of the world. These servers <firstterm>mirror</firstterm> the files available from the Fedora Project. If you visit <ulink url="http://download.fedoraproject.org/"/>, you are redirected to a mirror, based on a calculation of which mirror is likely to offer you the best download speed. Alternatively, you can choose a mirror from the list maintained at <ulink url="http://mirrors.fedoraproject.org/publiclist"/>. This page lists mirrors according to geographic location. The mirrors geographically closest to you are likely to provide you with the fastest downloads. If the company or organization that provides your internet access maintains a mirror, this mirror is likely to provide you with the fastest downloads of all.
-      </para>
-
-<para>Mirrors publish Fedora software under a well-organized
-	hierarchy of folders. For example, the Fedora &PRODVER;
-	distribution normally appears in the directory <filename
-	  class="directory">fedora/linux/releases/&PRODVER;/</filename>. 
-	This directory contains a folder for each architecture supported
-	by that release of Fedora. CD and DVD media files appear
-	inside that folder, in a folder called
-	<filename>iso/</filename>. For example, you can find the file
-	for the DVD distribution of Fedora &PRODVER; for x86_64 at
-	<filename>fedora/linux/releases/&PRODVER;/Fedora/x86_64/iso/Fedora-&PRODVER;-x86_64-DVD.iso</filename>.</para>
-    </section>
-    <section id="sn-which-download-bt">
-      <title>From BitTorrent</title>
-      <indexterm>
-	<primary>BitTorrent</primary>
-      </indexterm>
-      <indexterm>
-	<primary>BitTorrent</primary>
-	<secondary>seeding</secondary>
-      </indexterm>
-      <para>BitTorrent is a way to download information in cooperation
-	with other computers. Each computer cooperating in the group
-	downloads pieces of the information in a particular torrent from
-	other peers in the group. Computers that have finished
-	downloading all the data in a torrent remain in the swarm to
-	<firstterm>seed</firstterm>, or provide data to other peers. If
-	you download using BitTorrent, as a courtesy you should seed the
-	torrent at least until you have uploaded the same
-	amount of data you downloaded.</para>
-      <para>If your computer does not have software installed for
-	BitTorrent, visit the BitTorrent home page at <ulink
-	  url="http://www.bittorrent.com/download/"/> to download it.
-	BitTorrent client software is available for Windows, Mac OS,
-	Linux, and many other operating systems.</para>
-	<para>You do not need to find a special mirror for BitTorrent
-	files. The BitTorrent protocol ensures that your computer
-	participates in a nearby group. To download and use the Fedora
-	BitTorrent files, visit <ulink
-	url="http://torrent.fedoraproject.org/"/>.</para>
-      <note>
-	<title>Minimal Boot Images</title>
-	<para>Minimal boot CD and USB flash disk images are not
-	  available through BitTorrent.</para>
-      </note>
-    </section>
-  </section>
-  <section id="sn-which-arch">
-    <title>Which Architecture Is My Computer?</title>
-    <indexterm>
-      <primary>architecture</primary>
-    </indexterm>
-    <para>Releases are separated by <firstterm>architecture</firstterm>,
-      or type of computer processor. Use the following table to
-      determine the architecture of your computer according to the type
-      of processor. Consult your manufacturer's documentation for
-      details on your processor, if necessary.</para>
-    <indexterm>
-      <primary>architecture</primary>
-      <secondary>determining</secondary>
-    </indexterm>
- 
-       <table id="List-Processor_and_Architecture_Types" frame='all'><title>Processor and architecture types</title>
-	<tgroup cols='2' align='left' colsep='1' rowsep='1'>
-	<colspec colnum="1" colwidth="3*"/>
-        <colspec colnum="2" colwidth="1*"/>
-	  <thead>
-	      <row>
-		<entry>Processor manufacturer and model</entry>
-		<entry>Architecture type for Fedora</entry>
-	      </row>
-	  </thead>
-	  <tbody>
-	      <row>
-		<entry>Intel (except Atom 230, Atom 330, Core 2 Duo, Centrino Core2 Duo, and recent vintage Xeon);
-		  AMD (except Athlon 64, Athlon x2, Sempron 64, and Opteron); VIA C3, C7</entry>
-		<entry><systemitem>i386</systemitem></entry>
-	      </row>
-	      <row>
-		<entry>Intel Atom 230, Atom 330, Core 2 Duo, Centrino Core 2 Duo, and Xeon; AMD
-		  Athlon 64, Athlon x2, Sempron64, and Opteron; Apple MacBook, MacBook Pro, and MacBook Air</entry>
-		<entry><systemitem>x86_64</systemitem></entry>
-	      </row>
-	      <row>
-		<entry>Apple Macintosh G3, G4, G5, PowerBook, and other non-Intel
-		  models</entry>
-		<entry><systemitem>ppc</systemitem></entry>
-	      </row>
-	  </tbody>
-	</tgroup>
-    </table>
-    <note>
-      <title><systemitem>i386</systemitem> Works for Most Windows
-	Compatible Computers</title>
-      <para>If you are unsure what type of processor your computer uses, choose
-	<systemitem>i386</systemitem>.</para>
-      <para>The exception is if your computer is a non-Intel based Apple
-	Macintosh.  Refer to <xref
-	linkend="List-Processor_and_Architecture_Types"/> for more information.</para>
-    </note>
-    <note>
-      <title>Intel Atom Processor Architectures Vary</title>
-      <para>The N and Z Series Atom processors are based on the 
-	<systemitem>i386</systemitem> architecture. The 230 and 330 Series 
-	Atom processors are based on the<systemitem>x86_64</systemitem> 
-	architecture. Refer to <ulink url="http://ark.intel.com/cpugroup.aspx?familyID=29035"/> for more details. </para>
-    </note>
-  </section>
-  <section id="sn-which-files">
-    <title>Which Files Do I Download?</title>
-    <para>You have several options to download Fedora. Read the
-      options below to decide the best one for you.</para>
-    <para>Each file available for download in a Fedora distribution 
-      includes the architecture type in the file name. For example, the file for
-      the DVD distribution of Fedora &PRODVER; for x86_64 is named
-      <filename>Fedora-&PRODVER;-x86_64-DVD.iso</filename>.  Refer to
-      <xref
-	linkend="sn-which-arch"/> if you are unsure of your computer's
-      architecture.</para>
-    <orderedlist>
-      <listitem>
-	<formalpara>
-	  <title>Full Distribution on DVD</title>
-	  <para>If you have plenty of time, a fast Internet connection,
-	    and wish a broader choice of software on the install media,
-	    download the full DVD version. Once burned to DVD, the media
-	    is bootable and includes an installation program. The DVD
-	    version contains a mode to perform rescue operations on your
-	    Fedora system in an emergency. You can download the DVD
-	    version directly from a mirror, or via BitTorrent.</para>
-	</formalpara>
-      </listitem>
-      <listitem>
-	<formalpara>
-	  <title>Live Image</title>
-	  <para>If you want to try Fedora before you install it on
-	    your computer, download the Live image version. If your
-	    computer supports booting from CD or USB, you can boot the
-	    operating system without making any changes to your hard
-	    disk. The Live image also provides an <literal>Install to
-	      Hard Disk</literal> desktop shortcut. If you decide you
-	    like what you see, and want to install it, simply activate
-	    the selection to copy Fedora to your hard disk.  You can
-	    download the Live image directly from a mirror, or using
-	    BitTorrent.</para>
-	</formalpara>
-	<!-- <note>
-	  <title>No Live Images for <systemitem>ppc</systemitem></title>
-	  <para>Fedora does not offer Live images available for the
-	    <systemitem>ppc</systemitem> architecture due to resource
-	    constraints.</para>
-	</note> -->
-      </listitem>
-      <listitem>
-	<formalpara>
-	  <title>Minimal Boot Media</title>
-	  <para>If you have a fast Internet connection but do not want
-	    to download the entire distribution, you can download a
-	    small boot image. Fedora offers images for a minimal boot
-	    environment on CD. Once you boot your system with the minimal
-	    media, you can install Fedora directly over the Internet.
-	    Although this method still involves downloading a
-	    significant amount of data over the Internet, it is almost
-	    always much less than the size of the full distribution
-	    media. Once you have finished installation, you can add or
-	    remove software to your system as desired.</para>
-	</formalpara>
-	<note>
-	  <title>Download Size</title>
-	  <para>Installing the default software for Fedora over the
-	    Internet requires more time than the Live image, but less
-	    time than the entire DVD distribution.  Actual results
-	    depend on the software you select and network traffic
-	    conditions.</para>
-	</note>
-      </listitem>
-    </orderedlist>
-    <para>The following table explains where to find the desired files
-      on a mirror site.  Replace <replaceable>arch</replaceable> with
-      the architecture of the computer being installed.</para>
-
-       <table id="tb-Locating_Files" frame='all'><title>Locating files</title>
-	<tgroup cols='2' align='left' colsep='1' rowsep='1'>
-	<colspec colnum="1" colwidth="1*"/>
-        <colspec colnum="2" colwidth="2*"/>
-	  <thead>
-	      <row>
-		<entry>Media type</entry>
-		<entry>File locations</entry>
-	      </row>
-	  </thead>
-	  <tbody>
-	      <row>
-		<entry>Full distribution on DVD</entry>
-		<entry><filename>fedora/linux/releases/&PRODVER;/Fedora/<replaceable>arch</replaceable>/iso/Fedora-&PRODVER;-<replaceable>arch</replaceable>-DVD.iso</filename></entry>
-	      </row>
-	      <row>
-		<entry>Live image</entry>
-		<entry><filename>fedora/linux/releases/&PRODVER;/Live/<replaceable>arch</replaceable>/iso/Fedora-&PRODVER;-<replaceable>arch</replaceable>-Live.iso</filename>, 
-		  <filename>fedora/linux/releases/&PRODVER;/Live/<replaceable>arch</replaceable>/iso/Fedora-&PRODVER;-KDE-<replaceable>arch</replaceable>-Live.iso</filename></entry>
-	      </row>
-	      <row>
-		<entry>Minimal CD boot media</entry>
-		<entry><filename>fedora/linux/releases/&PRODVER;/Fedora/<replaceable>arch</replaceable>/os/images/boot.iso</filename></entry>
-	      </row>
-	  </tbody>
-	</tgroup>
-    </table>
-  </section>
-  
-</section>
-  <section id="sect-Obtaining_Fedora-Obtaining_Fedora_on_CD_or_DVD">
-    <title>Obtaining Fedora on CD or DVD</title>
-    <para>If you do not have a fast Internet connection, or if you have
-      a problem creating boot media, downloading may not be an option.
-      Fedora DVD and CD distribution media is available from a number
-      of online sources around the world at a minimal cost. Use your
-      favorite Web search engine to locate a vendor, or refer to <ulink
-	url="http://fedoraproject.org/wiki/Distribution"/>.</para>
-  </section>
-
-</chapter>
diff --git a/en-US/nextsteps.xml b/en-US/nextsteps.xml
deleted file mode 100644
index 5cf9eda..0000000
--- a/en-US/nextsteps.xml
+++ /dev/null
@@ -1,591 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-
-<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
- "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
-]>
-
-<!-- $Id: -->
-
-<chapter id="ch-next-steps">
-  <title>Your Next Steps</title>
-  <para>
-    Fedora provides you with a complete operating system with a vast
-    range of capabilities, supported by a large community.
-  </para>
-  <section id="sn-system-updating">
-    <title>Updating Your System</title>
-
-    <para>
-      The Fedora Project releases updated software packages for Fedora
-      throughout the support period of each version. Updated packages
-      add new features, improve reliability, resolve bugs, or remove
-      security vulnerabilities. To ensure the security of your system,
-      update regularly, and as soon as possible after a security
-      announcement is issued. Refer to <xref
-      linkend="sn-news-subscriptions"/> for information on the Fedora
-      announcements services.
-    </para>
-    <para>
-      An update applet reminds you of updates when they are available.
-      This applet is installed by default in Fedora.  It checks for
-      software updates from all configured repositories, and runs as a
-      background service.  It generates a notification message on the
-      desktop if updates are found, and you can click the message to
-      update your system's software.
-    </para>
-    <para>
-      To update your system with the latest packages manually, use
-      <indexterm>
-        <primary>Update System</primary>
-      </indexterm> <application>Update System</application>:
-    </para>
-
-<figure float="0"><title>Updating your system</title>
-	<mediaobject>
-		<imageobject><imagedata fileref="images/nextsteps/updating.png" format="PNG"/></imageobject>
-		<textobject><para>
-				Updating your system screen
-			</para>
-		</textobject>
-	</mediaobject>
-</figure>
-
-<orderedlist>
-      <listitem>
-        <para>
-	  Choose <menuchoice>
-	  <guimenu>System</guimenu>
-	  <guisubmenu>Administration</guisubmenu>
-	  <guimenuitem>Update System</guimenuitem>
-	  </menuchoice>.
-        </para>
-      </listitem>
-      <listitem>
-        <para>
-          To review the list of updated packages, select
-          <guilabel>Review</guilabel>.
-        </para>
-      </listitem>
-      <listitem>
-        <para>
-          Click <guibutton>Update System</guibutton> to begin the update
-          process.
-        </para>
-      </listitem>
-      <listitem>
-        <para>
-          If one or more updates require a system reboot, the update
-          process displays a dialog with the option to <guibutton>Reboot
-          Now</guibutton>. Either select this option to reboot the
-          system immediately, or <guibutton>Cancel</guibutton> it and
-          reboot the system at a more convenient time.
-        </para>
-      </listitem>
-      <listitem>
-        <para>
-	  If a reboot is not required the update will conclude with a
-          dialog that indicates that the System Update Completed and all
-          selected updates have been successfully installed as well as
-          a button to <guibutton>Close</guibutton>
-            <indexterm><primary>Update System</primary></indexterm>
-            <application>Update System</application>
-	</para>
-      </listitem>
-    </orderedlist>
-    <para>
-      To update packages from the command-line, use the
-      <indexterm>
-        <primary>yum</primary>
-      </indexterm>
-      <command>yum</command> utility. Type this command to begin a full
-      update of your system with <command>yum</command>:
-    </para>
-<screen>
-<userinput>su -c 'yum update'</userinput>
-</screen>
-    <para>
-      Enter the <systemitem
-	class="username">root</systemitem> password
-      when prompted.
-    </para>
-
-    <para>
-      Refer to <ulink url="http://docs.fedoraproject.org/yum/"/> for
-      more information on <command>yum</command>.
-    </para>
-
-    <note>
-      <title>Network Connection Required</title>
-
-      <para>
-        Ensure that your system has an active network connection before
-        you run the <application>Update Software</application> tool, or the
-        <command>yum</command> utility. The update process downloads
-        information and packages from a network of servers.
-      </para>
-    </note>
-    <para>
-      If your Fedora system has a permanent network connection, you may
-      choose to enable daily system updates. To enable automatic
-      updates, follow the instructions on the webpage <ulink
-	url="http://docs.fedoraproject.org/yum/sn-updating-your-system.html"/>.
-    </para>
-    
-    <!-- <xi:include href="DU-Driver_update_rpm_packages.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/> -->
-
-  </section>
-  <section id="sn-finishing-upgrade">
-    <title>Finishing an Upgrade</title>
-    <important>
-      <title>System Updates Recommended</title>
-      <para>Once you have rebooted your system after performing an
-	upgrade, you should also perform a manual system update. Consult
-	<xref linkend="sn-system-updating"/> for more
-	information.</para>
-    </important>
-    <para>If you chose to upgrade your system from a previous release rather
-      than perform a fresh installation, you may want to examine the
-      differences in the package set.  <xref
-	linkend="sn-upgrade-tree-x86"/> advised you to create a package
-      listing for your original system.  You can now use that listing to
-      determine how to bring your new system close to the original
-      system state.</para>
-	<para>
-		You can obtain a list of <firstterm>orphaned</firstterm> packages (that is, packages that are no longer in the repositories) from the <application>package-cleanup</application> tool. Install the <package>yum-utils</package> package and then run <command>package-cleanup --orphans</command>. The tool will show you orphaned packages and packages that are partially uninstalled but for which the <application>%postun</application> script failed.
-	</para>
-    <para>Most software repository configurations are stored in packages
-      that end with the term <literal>release</literal>.  Check the old
-      package list for the repositories that were installed:</para>
-    <screen><command><![CDATA[awk '{print $1}' ~/old-pkglist.txt | grep 'release$']]></command></screen>
-    <para>If necessary, retrieve and install these software repository
-      packages from their original sources on the Internet.  Follow the
-      instructions at the originating site to install the repository
-      configuration packages for use by <command>yum</command> and other
-      software management tools on your Fedora system.</para>
-    <para>Then run the following commands to make a list of other
-      missing software packages:</para>
-
-    <screen><command>awk '{print $1}' ~/old-pkglist.txt | sort | uniq > ~/old-pkgnames.txt</command>
-<command>rpm -qa --qf '%{NAME}\n' | sort | uniq > ~/new-pkgnames.txt</command>
-<command>diff -u ~/old-pkgnames.txt ~/new-pkgnames.txt | grep '^-' | sed 's/^-//' > /tmp/pkgs-to-install.txt</command></screen>
-
-    <para>Now use the file <filename>/tmp/pkgs-to-install.txt</filename> with
-      the <command>yum</command> command to restore most or all of your
-      old software:</para>
-
-    <screen><command><![CDATA[su -c 'yum install `cat /tmp/pkgs-to-install.txt`']]></command></screen>
-
-    <important>
-      <title>Missing Software</title>
-      <para>Due to changes in package complements between Fedora
-	releases, it is possible this method may not restore all the
-	software on your system.  You can use the routines above to
-	again compare the software on your system, and remedy any
-	problems you find.</para>
-    </important>
-  </section>
-  <section id="sn-switching-to-gui-login">
-    <title>Switching to a Graphical Login</title>
-    <important>
-		<title>Important â€” Access to Software Repositories Might Be Required</title>
-		<para>
-			To switch to a graphical environment, you might need to install extra software from a <firstterm>repository</firstterm>. You can access Fedora repositories through the Internet or use a Fedora installation CD or DVD as a repository. Refer to <xref linkend="sn-enabling-repos"/>.
-		</para>
-	</important>
-    <para>
-      If you installed using a text login and wish to switch to a
-      graphical login, follow this procedure.
-    </para>
-    <procedure>
-      <step>
-	<para>
-	  If you are not already root, switch users to the <systemitem>root</systemitem> account:
-	</para>
-<screen><command>su -</command></screen>
-	<para>
-	  Provide the administrator password when prompted.
-	</para>
-      </step>
-      <step>
-	<para>
-	  If you have not already done so, install the <application>X Window System</application> and a graphical desktop environment. For example, to install the GNOME
-	  desktop environment, use this command:
-	</para>
-<screen><command>yum groupinstall "X Window System" "GNOME Desktop Environment"</command></screen> 
-	<para>
-		To install the KDE desktop environment, use:
-	</para>
-<screen><command>yum groupinstall "X Window System" KDE</command></screen> 
-	<para>
-		To install the XFCE desktop environment, use:
-	</para>
-<screen><command>yum groupinstall "X Window System" XFCE</command></screen> 
-	<para>
-	  This step may take some time as your Fedora system downloads
-	  and installs additional software.  You may be asked to provide
-	  the installation media depending on your original installation
-	  source.
-	</para>
-      </step>
-      <step>
-	<para>
-	  Run the following command to edit the
-	  <filename>/etc/inittab</filename> file:
-	</para>
-<screen><command>vi /etc/inittab</command></screen>
-      </step>
-      <step>
-	      <para>
-		      Press the <keycap>I</keycap> key to enter <literal>insert</literal> mode.
-	      </para>
-      </step>
-      <step>
-	<para>
-	  Find the line that includes the text <literal>initdefault</literal>.  Change the numeral <literal>3</literal> to <literal>5</literal>.
-	</para>
-      </step>
-	<step>
-		<para>
-			Type <literal>:wq</literal> and press the <keycap>Enter</keycap> key to save the file and exit the <application>vi</application> text editor.
-		</para>
-	</step>
-    </procedure>
-    <para>
-      Reboot the system using the
-      <command>reboot</command> command.  Your system will restart and
-      present a graphical login.
-    </para>
-	<para>
-		If you encounter any problems with the graphical login, refer to <xref linkend="ch-trouble-x86"/> or consult one of the help sources listed in <xref linkend="sn-additional-help"/>.
-	</para>
-	 <section id="sn-enabling-repos">
-	 <title>Enabling Access to Software Repositories from the Command Line</title>
-		<para>
-			The usual way to install new software on a Fedora system is through a software repository. You can access Fedora repositories through the Internet, or use a Fedora installation CD or DVD as a repository. The software that you access through online repositories is more up-to-date than what is available on an installation CD or DVD. Furthermore, configuring a Fedora system to access online repositories is generally easier than configuring the system to use an installation CD or DVD as a repository, as long as you have an existing, wired network connection available. 
-		</para>
-		<section id="sn-enabling-repos-internet">
-			<title>Enabling Access to Software Repositories Through the Internet</title>
-			<para>
-				By default, every Fedora installation is already configured to access Fedora repositories through the Internet. Therefore, all you must do is ensure that the system can access the Internet. If you have an existing, wired network connection available, this process is straightforward:
-			</para>
-			<procedure>
-				<step>
-					<para>
-						If you are not already root, switch users to the <systemitem>root</systemitem> account:
-					</para>
-<screen><command>su -</command></screen>
-				</step>
-				<step>
-					<para>
-						Ensure that the system is plugged into your network. Note that your network might be as small as two devices â€” a computer and an external modem/router.
-					</para>
-				</step>
-				<step>
-					<para>
-						Run <command>system-config-network</command>. The network configuration tool starts and displays the <guilabel>Select Action</guilabel> screen.
-					</para>
-				</step>
-				<step>
-					<para>
-						Select <guimenuitem>Edit a device params</guimenuitem> and press <keycap>Enter</keycap>. The network configuration tool displays the <guilabel>Select A Device</guilabel> screen with a list of network interfaces present on your system. The first interface is named <systemitem>eth0</systemitem> by default.
-					</para>
-				</step>
-				<step>
-					<para>
-						Select a network interface to configure and press <keycap>Enter</keycap>. The network configuration tool takes you to the <guilabel>Network Configuration</guilabel> screen.
-					</para>
-				</step>
-				<step>
-					<para>
-						You can manually configure a static IP, gateway, and DNS servers on this screen or leave these fields blank to accept the default values. When you have chosen a configuration, select <guibutton>OK</guibutton>, and press <keycap>Enter</keycap>. The network configuration tool takes you back to the <guilabel>Select A Device</guilabel> screen.
-					</para>
-				</step>
-				<step>
-					<para>
-						Select <guibutton>Save</guibutton> and press <keycap>Enter</keycap>. The network configuration tool takes you back to the <guilabel>Select Action</guilabel> screen.
-					</para>
-				</step>
-				<step>
-					<para>
-						Select <guibutton>Save&amp;Quit</guibutton> and press <keycap>Enter</keycap>. The network configuration tool saves your settings and exits.
-					</para>
-				</step>
-				<step>
-					<para>
-						Run <command>ifup <replaceable>interface</replaceable></command>, where <replaceable>interface</replaceable> is the network interface that you configured with the network configuration tool. For example, run <command>ifup eth0</command> to start <systemitem>eth0</systemitem>.
-					</para>
-				</step>
-			</procedure>
-			<para>
-				Configuration of dial-up or wireless Internet connections is more complicated and beyond the scope of this guide.
-			</para>
-		</section>
-		<section id="sn-enabling-repos-disc">
-			<title>Using a Fedora Installation CD or DVD as a Software Repository</title>
-			<para>
-				You can use a Fedora installation CD or DVD as a software repository, either in the form of a physical disc, or in the form of an ISO image file. 
-			</para>
-			<procedure>
-				<step>
-					<para>
-						If you are using a physical CD or DVD, insert the disc into your computer.
-					</para>
-				</step>
-				<step>
-					<para>
-						If you are not already root, switch users to the <systemitem>root</systemitem> account:
-					</para>
-<screen><command>su -</command></screen>
-				</step>
-				<step>
-					<para>
-						Create a <firstterm>mount point</firstterm> for the repository:
-					</para>
-<screen><command>mkdir -p <replaceable>/path/to/repo</replaceable></command></screen>
-					<para>
-						where <replaceable>/path/to/repo</replaceable> is a location for the repository, for example, <filename>/mnt/repo</filename>
-					</para>
-				</step>
-				<step>
-					<para>
-						<firstterm>Mount</firstterm> the CD or DVD on the mount point that you just created. If you are using a physical disc, you need to know the <firstterm>device name</firstterm> of your CD or DVD drive. You can find the names of any CD or DVD drives on your system with the command <command>cat /proc/sys/dev/cdrom/info</command>. The first CD or DVD drive on the system is typically named <literal>sr0</literal>. When you know the device name, mount the CD or DVD:
-					</para>
-<screen><command>mount -r -t iso9660 /dev/<replaceable>device_name</replaceable> <replaceable>/path/to/repo</replaceable></command></screen>
-					<para>
-						For example: <command>mount -r -t iso9660 /dev/sr0 /mnt/repo</command>
-					</para>
-					<para>
-						If you are using an ISO image file of a disc, mount the image file like this:
-					</para>
-<screen><command>mount -r -t iso9660 -o loop <replaceable>/path/to/image/file</replaceable>.iso <replaceable>/path/to/repo</replaceable></command></screen>
-					<para>
-						For example: <command>mount -r -o loop /home/root/Downloads/Fedora-&PRODVER;-i386-DVD.iso /mnt/repo</command>
-					</para>
-					<para>
-						Note that you can only mount an image file if the storage device that holds the image file is itself mounted. For example, if the image file is stored on a hard drive that it not mounted automatically when the system boots, you must mount the hard drive before you mount an image file stored on that hard drive. Consider a hard drive named <filename>/dev/sdb</filename> that is not automatically mounted at boot time and which has an image file stored in a directory named <filename>Downloads</filename> on its first partition:
-					</para>
-<screen><command>mkdir /mnt/temp</command>
-<command>mount /dev/sdb1 /mnt/temp</command>
-<command>mkdir /mnt/repo</command>
-<command>mount -r -t iso9660 -o loop mount -r -o loop /mnt/temp/Downloads/Fedora-&PRODVER;-i386-DVD.iso /mnt/repo</command></screen>
-					<para>
-						If you are not sure whether a storage device is mounted, run the <command>mount</command> command to obtain a list of current mounts. If you are not sure of the device name or partition number of a storage device, run <command>fdisk -l</command> and try to identify it in the output.
-					</para>
-				</step>
-				<step>
-					<para>
-						Edit the <filename>/etc/yum.repos.d/fedora.repo</filename> and <filename>/etc/yum.repos.d/fedora-updates.repo</filename> files to use the new repository. In each case:
-					</para>
-					<procedure>
-						<step>
-							<para>
-								Open the file with the <application>vi</application> text editor. For example:
-							</para>
-<screen><command>vi /etc/yum.repos.d/fedora.repo</command></screen>
-						</step>
-						<step>
-							<para>
-								Press the <keycap>I</keycap> key to enter <literal>insert</literal> mode.
-							</para>
-						</step>
-						<step>
-							<para>
-								Type a <literal>#</literal> character at the start of any line in the file that starts with <literal>baseurl</literal> or <literal>mirrorlist</literal>. The <literal>#</literal> character <firstterm>comments out</firstterm> the line so that the package management software ignores it.
-							</para>
-						</step>
-						<step>
-							<para>
-								Find the <literal>[fedora]</literal> section of the <filename>fedora.repo</filename> file or the <literal>[updates]</literal> section of the <filename>fedora-updates.repo</filename> file. Note that this section includes a line that now starts <literal># baseurl</literal> that you previously commented out.
-							</para>
-						</step>
-						<step>
-							<para>
-								Insert a new line after the line that starts <literal># baseurl</literal>:
-							</para>
-<screen>baseurl=file://<replaceable>/path/to/repo</replaceable></screen>
-							<para>
-								For example, <literal>baseurl=file:///mnt/repo</literal>
-							</para>
-						</step>
-						<step>
-							<para>
-								Press the <keycap>Esc</keycap> key to exit <literal>insert</literal> mode.
-							</para>
-						</step>
-						<step>
-							<para>
-								Type <literal>:wq</literal> and press the <keycap>Enter</keycap> key to save the file and exit the <application>vi</application> text editor.
-							</para>
-						</step>
-						<step>
-							<para>
-								After installing or upgrading software from the CD or DVD, edit the <filename>/etc/yum.repos.d/fedora.repo</filename> and <filename>/etc/yum.repos.d/fedora-updates.repo</filename> files again to undo the changes that you made.
-							</para>
-						</step>
-					</procedure>
-				</step>
-			</procedure>
-		</section>
-	 </section>
-  </section>
-  <section id="sn-news-subscriptions">
-    <title>Subscribing to Fedora Announcements and News</title>
-
-    <para>
-      To receive information about package updates, subscribe to either
-      the announcements mailing list, or the RSS feeds.
-    </para>
-
-    <variablelist>
-      <varlistentry>
-        <term>
-	    Fedora Project announcements mailing list
-	  </term>
-        <listitem>
-          <para>
-            <ulink url="https://www.redhat.com/mailman/listinfo/fedora-announce-list"/>
-          </para>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry>
-        <term>
-	    Fedora Project RSS feeds
-	  </term>
-        <listitem>
-          <para>
-            <ulink url="http://fedoraproject.org/infofeed/"/>
-          </para>
-        </listitem>
-      </varlistentry>
-    </variablelist>
-
-    <para>
-      The announcements mailing list also provides you with news on the
-      Fedora Project, and the Fedora community.
-    </para>
-
-    <important>
-      <title>Security Announcements</title>
-
-      <para>
-        Announcements with the keyword
-        <wordasword>[SECURITY]</wordasword> in the title identify
-        package updates that resolve security vulnerabilities.
-      </para>
-    </important>
-  </section>
-  <section id="sn-web-help">
-    <title>Finding Documentation and Support</title>
-
-    <para>
-      Members of the Fedora community provide support through mailing
-      lists, Web forums and Linux User Groups (LUGs) across the world.
-    </para>
-
-    <para>
-      The Web site for the formally endorsed forums is
-      <ulink
-	url="http://forums.fedoraforum.org/"/>.
-    </para>
-
-    <para>
-      The following resources provide information on many aspects of
-      Fedora:
-    </para>
-
-    <itemizedlist>
-      <listitem>
-        <variablelist>
-          <varlistentry>
-            <term>
-	      The FAQ on the Fedora Project website
-	    </term>
-            <listitem>
-              <para>
-                <ulink url="http://fedoraproject.org/wiki/FAQ/"/>
-              </para>
-            </listitem>
-          </varlistentry>
-        </variablelist>
-      </listitem>
-      <listitem>
-        <variablelist>
-          <varlistentry>
-            <term>
-	      The documents available from the Fedora Documentation Project Web site 
-	    </term>
-            <listitem>
-              <para>
-                <ulink url="http://docs.fedoraproject.org/"/>
-              </para>
-            </listitem>
-          </varlistentry>
-        </variablelist>
-      </listitem>
-      <listitem>
-        <variablelist>
-          <varlistentry>
-            <term>
-	      The Linux Documentation Project (LDP)	   
-	    </term>
-            <listitem>
-              <para>
-                <ulink url="http://www.tldp.org/"/>
-              </para>
-            </listitem>
-          </varlistentry>
-        </variablelist>
-      </listitem>
-      <listitem>
-        <variablelist>
-          <varlistentry>
-            <term>
-	      The Red Hat Enterprise Linux documentation, much of which also applies to
-	      Fedora
-	    </term>
-            <listitem>
-              <para>
-                <ulink
-		  url="http://www.redhat.com/docs/manuals/enterprise/"/>
-              </para>
-            </listitem>
-          </varlistentry>
-        </variablelist>
-      </listitem>
-    </itemizedlist>
-
-    <para>
-      Many other organizations and individuals also provide tutorials
-      and HOWTOs for Fedora on their Web sites. You can locate
-      information on any topic by using Google's Linux search site,
-      located at <ulink url="http://www.google.com/linux"/>.
-    </para>
-  </section>
-  <section id="sn-community">
-    <title>Joining the Fedora Community</title>
-
-    <para>
-      The Fedora Project is driven by the individuals that contribute to it.
-      Community members provide support and documentation to other
-      users, help to improve the software included in Fedora by testing,
-      and develop new software alongside the programmers employed by
-      Red Hat. The results of this work are available to all.
-    </para>
-
-    <para>
-      To make a difference, start here:
-    </para>
-
-    <para>
-      <ulink url="http://join.fedoraproject.org/"/>
-    </para>
-  </section>
-</chapter>
-
-<!--
-Local variables:
-mode: xml
-fill-column: 72
-End:
--->
diff --git a/en-US/pxe-server-manual.xml b/en-US/pxe-server-manual.xml
deleted file mode 100644
index f25ceed..0000000
--- a/en-US/pxe-server-manual.xml
+++ /dev/null
@@ -1,427 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<section id="sn-pxe-server-manual">
-<title>Manually configure a PXE server</title>
-	<indexterm significance="normal">
-		<primary>PXE installations</primary>
-		<secondary>overview</secondary>
-	</indexterm>
-	<para>
-		The following steps must be performed to prepare for a PXE installation:
-	</para>
-	<orderedlist inheritnum="ignore" continuation="restarts">
-		<listitem>
-			<para>
-				Configure the network (NFS, FTP, HTTP) server to export the installation tree.
-			</para>
-		</listitem>
-
-		<listitem>
-			<para>
-				Configure the files on the <command>tftp</command> server necessary for PXE booting.
-			</para>
-		</listitem>
-
-		<listitem>
-			<para>
-				Configure which hosts are allowed to boot from the PXE configuration.
-			</para>
-		</listitem>
-
-		<listitem>
-			<para>
-				Start the <command>tftp</command> service.
-			</para>
-		</listitem>
-
-		<listitem>
-			<para>
-				Configure DHCP.
-			</para>
-		</listitem>
-
-		<listitem>
-			<para>
-				Boot the client, and start the installation.
-			</para>
-		</listitem>
-	</orderedlist>
-	<section id="s1-netboot-netserver">
-		<title>Setting up the Network Server</title>
-		<indexterm significance="normal">
-			<primary>PXE installations</primary>
-			<secondary>setting up the network server</secondary>
-		</indexterm>
-		<para>
-			First, configure an NFS, FTP, or HTTP server to export the entire installation tree for the version and variant of Fedora to be installed. Refer to <xref linkend="s1-steps-network-installs-x86"/> for detailed instructions.
-		</para>
-	</section>
-	<section id="s1-netboot-pxe-config">
-		<title>PXE Boot Configuration</title>
-		<indexterm significance="normal">
-			<primary>PXE installations</primary>
-			<secondary>configuration</secondary>
-		</indexterm>
-		<para>
-			The next step is to copy the files necessary to start the installation to the <command>tftp</command> server so they can be found when the client requests them. The <command>tftp</command> server is usually the same
-			server as the network server exporting the installation tree.
-		</para>
-		 
-		<para>
-			To copy these files, run the <application>Network Booting Tool</application> on the NFS, FTP, or HTTP server. A separate PXE server is not necessary.
-		</para>
-		 
-		<!-- This next section has been commented out because system-config-netboot has been left out of the distro.
-		     We'll uncomment it when the component is reincluded. -->
-		
-		<!-- 
-		<para>
-			For the command line version of these instructions, refer to <xref linkend="s2-netboot-pxeos"/>.
-		</para>
-		<indexterm significance="normal">
-			<primary><command>system-config-netboot</command>
-			</primary>
-		</indexterm>
-		<indexterm significance="normal">
-			<primary><application>Network Booting Tool</application>
-			</primary>
-		</indexterm>
-		<indexterm significance="normal">
-			<primary><application>Network Booting Tool</application>
-			</primary>
-			<secondary>using with PXE installations</secondary>
-		</indexterm>
-		<indexterm significance="normal">
-			<primary>PXE installations</primary>
-			<secondary><application>Network Booting Tool</application>
-			</secondary>
-		</indexterm>
-		<para>
-			To use the graphical version of the <application>Network Booting Tool</application>, you must be running the X Window System, have root privileges, and have the <filename>system-config-netboot</filename> RPM package
-			installed. To start the <application>Network Booting Tool</application> from the desktop, go to <guimenu>Applications</guimenu> (the main menu on the panel) =&gt; <guimenuitem>System Settings</guimenuitem>
-			=&gt; <guimenuitem>Server Settings</guimenuitem> =&gt; <guimenuitem>Network Booting Service</guimenuitem>. Or, type the command <command>system-config-netboot</command> at a shell prompt (for example, in
-			an <application>XTerm</application> or a <application>GNOME terminal</application>).
-		</para>
-		 
-		<para>
-			If starting the <application>Network Booting Tool</application> for the first time, select <guibutton>Network Install</guibutton> from the <guilabel>First Time Druid</guilabel>. Otherwise, select
-			<guimenu>Configure</guimenu> =&gt; <guimenuitem>Network Installation</guimenuitem> from the pulldown menu, and then click <guibutton>Add</guibutton>. The dialog in
-			<xref linkend="fig-network-install-setup"/> is displayed.
-		</para>
-		<figure float="0" id="fig-network-install-setup"><title>Network Installation Setup</title>
-			<mediaobject>
-				<imageobject><imagedata fileref="images/pxe/network-install-setup.png" format="PNG"/></imageobject>
-				<textobject><para>
-						Network Installation Setup
-					</para>
-				</textobject>
-			</mediaobject>
-		</figure>
-		<itemizedlist>
-			<listitem>
-				<para>
-					<guilabel>Operating system identifier</guilabel> &mdash; Provide a unique name using one word to identify the Fedora version and variant. It is used as the directory name in the
-					<filename>/tftpboot/linux-install/</filename> directory.
-				</para>
-			</listitem>
-
-			<listitem>
-				<para>
-					<guilabel>Description</guilabel> &mdash; Provide a brief description of the Fedora version and variant.
-				</para>
-			</listitem>
-
-			<listitem>
-				<para>
-					<guilabel>Selects protocol for installation</guilabel> &mdash; Selects NFS, FTP, or HTTP as the network installation type depending on which one was configured previously. If FTP is selected and anonymous FTP is not being used,
-					uncheck <guilabel>Anonymous FTP</guilabel> and provide a valid username and password combination.
-				</para>
-			</listitem>
-
-			<listitem>
-				<para>
-					<guilabel>Kickstart</guilabel> &mdash; Specify the location of the kickstart file. The file can be a URL or a file stored locally (diskette). The kickstart file can be created with the <application>Kickstart
-					Configurator</application>. Refer to <xref linkend="ch-redhat-config-kickstart"/> for details.
-				</para>
-			</listitem>
-
-			<listitem>
-				<para>
-					<guilabel>Server</guilabel> &mdash; Provide the IP address or domain name of the NFS, FTP, or HTTP server.
-				</para>
-			</listitem>
-
-			<listitem>
-				<para>
-					<guilabel>Location</guilabel> &mdash; Provide the directory shared by the network server. If FTP or HTTP was selected, the directory must be relative to the default directory for the FTP server or the document root for the HTTP
-					server. For all network installations, the directory provided must contain the <filename>RedHat/</filename> directory of the installation tree.
-				</para>
-			</listitem>
-		</itemizedlist>
-		 
-		<para>
-			After clicking <guibutton>OK</guibutton>, the <filename>initrd.img</filename> and <filename>vmlinuz</filename> files necessary to boot the installation program are transfered from
-			<filename>images/pxeboot/</filename> in the provided installation tree to <filename>/tftpboot/linux-install/<replaceable>&lt;os-identifier&gt;</replaceable>/</filename> on the <command>tftp</command>
-			server (the one you are running the <application>Network Booting Tool</application> on).
-		</para>
-		 
-		
-		<section id="s2-netboot-pxeos">
-			<title>Command Line Configuration</title>
-			<indexterm significance="normal">
-				<primary><application>Network Booting Tool</application>
-				</primary>
-				<secondary><command>pxeos</command>
-				</secondary>
-			</indexterm>
-			<indexterm significance="normal">
-				<primary><command>pxeos</command>
-				</primary>
-			</indexterm>
-			<para>
-				If the network server is not running X, the <command>pxeos</command> command line utility, which is part of the <filename>system-config-netboot</filename> package, can be used to configure the
-				<command>tftp</command> server files as described in <xref linkend="s1-netboot-tftp"/>:
-			</para>
-<screen>pxeos -a -i "<replaceable>&lt;description&gt;</replaceable>" -p &lt;NFS|HTTP|FTP&gt; -D 0 -s <replaceable>client.example.com</replaceable> \ 
--L <replaceable>&lt;net-location&gt;</replaceable> -k <replaceable>&lt;kernel&gt;</replaceable> -K <replaceable>&lt;kickstart&gt;</replaceable> <replaceable>&lt;os-identifer&gt;</replaceable>
-</screen>
-			<para>
-				The following list explains the options:
-			</para>
-			 
-			<itemizedlist>
-				<listitem>
-					<para>
-						<option>-a</option> &mdash; Specifies that an OS instance is being added to the PXE configuration.
-					</para>
-				</listitem>
-
-				<listitem>
-					<para>
-						<option>-i</option> "<replaceable>&lt;description&gt;</replaceable>" &mdash; Replace "<replaceable>&lt;description&gt;</replaceable>" with a description of the OS instance. This corresponds to the <guilabel>Description</guilabel>
-						field in <xref linkend="fig-network-install-setup"/>. 
-					</para>
-				</listitem>
-
-				<listitem>
-					<para>
-						<option>-p</option> &lt;NFS|HTTP|FTP&gt; &mdash; Specify which of the NFS, FTP, or HTTP protocols to use for installation. Only one may be specified. This corresponds to the <guilabel>Select protocol for installation</guilabel>
-						menu in <xref linkend="fig-network-install-setup"/>.
-					</para>
-				</listitem>
-
-				<listitem>
-					<para>
-						<option>-D</option> &lt;0|1&gt; &mdash; Specify "<command>0</command>" which indicates that it is <emphasis>not</emphasis> a diskless configuration since <command>pxeos</command> can be used to configure a diskless
-						environment as well.
-					</para>
-				</listitem>
-
-				<listitem>
-					<para>
-						<option>-s</option> <replaceable>client.example.com</replaceable> &mdash; Provide the name of the NFS, FTP, or HTTP server after the <option>-s</option> option. This corresponds to the <guilabel>Server</guilabel> field in
-						<xref linkend="fig-network-install-setup"/>.
-					</para>
-				</listitem>
-
-				<listitem>
-					<para>
-						<option>-L</option> <replaceable>&lt;net-location&gt;</replaceable> &mdash; Provide the location of the installation tree on that server after the <option>-L</option> option. This corresponds to the <guilabel>Location</guilabel>
-						field in <xref linkend="fig-network-install-setup"/>. 
-					</para>
-				</listitem>
-
-				<listitem>
-					<para>
-						<option>-k</option> <replaceable>&lt;kernel&gt;</replaceable> &mdash; Provide the specific kernel version of the server installation tree for booting.
-					</para>
-				</listitem>
-
-				<listitem>
-					<para>
-						<option>-K</option> <replaceable>&lt;kickstart&gt;</replaceable> &mdash; Provide the location of the kickstart file, if available.
-					</para>
-				</listitem>
-
-				<listitem>
-					<para>
-						<replaceable>&lt;os-identifer&gt;</replaceable> &mdash; Specify the OS identifier, which is used as the directory name in the <filename>/tftpboot/linux-install/</filename> directory. This corresponds to the
-						<guilabel>Operating system identifier</guilabel> field in <xref linkend="fig-network-install-setup"/>.
-					</para>
-				</listitem>
-			</itemizedlist>
-			 
-			<para>
-				If FTP is selected as the installation protocol and anonymous login is not available, specify a username and password for login, with the following options before <replaceable>&lt;os-identifer&gt;</replaceable> in the previous command:
-			</para>
-<screen>
--A 0 -u <replaceable>&lt;username&gt;</replaceable> -p <replaceable>&lt;password&gt;</replaceable>
-</screen>
-			<para>
-				For more information on command line options available for the <command>pxeos</command> command, refer to the <command>pxeos</command> man page.
-			</para>
-		</section> -->
-	</section>
-	<section id="s1-netboot-add-hosts">
-		<title>Adding PXE Hosts</title>
-		<indexterm significance="normal">
-			<primary>PXE installations</primary>
-			<secondary>adding hosts</secondary>
-		</indexterm>
-		<para>
-			After configuring the network server, the interface as shown in <xref linkend="fig-netboot-add-hosts"/> is displayed.
-		</para>
-		<figure float="0" id="fig-netboot-add-hosts"><title>Add Hosts</title>
-			<mediaobject>
-				<imageobject><imagedata fileref="images/pxe/netboot-add-hosts.png" format="PNG"/></imageobject>
-				<textobject><para>
-						Add Hosts
-					</para>
-				</textobject>
-			</mediaobject>
-		</figure>
-		<para>
-			The next step is to configure which hosts are allowed to connect to the PXE boot server. <!-- For the command line version of this step, refer to <xref linkend="s2-netboot-pxeboot"/>. -->
-		</para>
-		 
-		<para>
-			To add hosts, click the <guibutton>New</guibutton> button.
-		</para>
-		<figure float="0" id="fig-netboot-add-host-dialog"><title>Add a Host</title>
-			<mediaobject>
-				<imageobject><imagedata fileref="images/pxe/netboot-add-host-dialog.png" format="PNG"/></imageobject>
-				<textobject><para>
-						Add a Host
-					</para>
-				</textobject>
-			</mediaobject>
-		</figure>
-		<para>
-			Enter the following information:
-		</para>
-		 
-		<itemizedlist>
-			<listitem>
-				<para>
-					<guilabel>Hostname or IP Address/Subnet</guilabel> &mdash; The IP address, fully qualified hostname, or a subnet of systems that should be allowed to connect to the PXE server for installations.
-				</para>
-			</listitem>
-
-			<listitem>
-				<para>
-					<guilabel>Operating System</guilabel> &mdash; The operating system identifier to install on this client. The list is populated from the network install instances created from the <guilabel>Network Installation
-					Dialog</guilabel>.
-				</para>
-			</listitem>
-
-			<listitem>
-				<para>
-					<guilabel>Serial Console</guilabel> &mdash; This option allows use of a serial console.
-				</para>
-			</listitem>
-
-			<listitem>
-				<para>
-					<guilabel>Kickstart File</guilabel> &mdash; The location of a kickstart file to use, such as <userinput>http://server.example.com/kickstart/ks.cfg</userinput>. This file can be created with the
-					<application>Kickstart Configurator</application>. Refer to <xref linkend="ch-redhat-config-kickstart"/> for details.
-				</para>
-			</listitem>
-		</itemizedlist>
-		 
-		<para>
-			Ignore the <guilabel>Snapshot name</guilabel> and <guilabel>Ethernet</guilabel> options. They are only used for diskless environments. 
-		</para>
-		 
-		<!-- <section id="s2-netboot-pxeboot">
-			<title>Command Line Configuration</title>
-			<indexterm significance="normal">
-				<primary><application>Network Booting Tool</application>
-				</primary>
-				<secondary><command>pxeboot</command>
-				</secondary>
-			</indexterm>
-			<indexterm significance="normal">
-				<primary><command>pxeboot</command>
-				</primary>
-			</indexterm>
-			<para>
-				If the network server is not running X, the <command>pxeboot</command> utility, a part of the <filename>system-config-netboot</filename> package, can be used to add hosts which are allowed to connect to the PXE server:
-			</para>
-<screen>
-pxeboot -a -K <replaceable>&lt;kickstart&gt;</replaceable> -O <replaceable>&lt;os-identifier&gt;</replaceable> -r <replaceable>&lt;value&gt;</replaceable> <replaceable>&lt;host&gt;</replaceable>
-</screen>
-			<para>
-				The following list explains the options:
-			</para>
-			 
-			<itemizedlist>
-				<listitem>
-					<para>
-						<option>-a</option> &mdash; Specifies that a host is to be added.
-					</para>
-				</listitem>
-
-				<listitem>
-					<para>
-						<option>-K</option> <replaceable>&lt;kickstart&gt;</replaceable> &mdash; The location of the kickstart file, if available.
-					</para>
-				</listitem>
-
-				<listitem>
-					<para>
-						<option>-O</option> <replaceable>&lt;os-identifier&gt;</replaceable> &mdash; Specifies the operating system identifier as defined in <xref linkend="s1-netboot-pxe-config"/>.
-					</para>
-				</listitem>
-
-				<listitem>
-					<para>
-						<option>-r</option> <replaceable>&lt;value&gt;</replaceable> &mdash; Specifies the ram disk size.
-					</para>
-				</listitem>
-
-				<listitem>
-					<para>
-						<replaceable>&lt;host&gt;</replaceable> &mdash; Specifies the IP address or hostname of the host to add.
-					</para>
-				</listitem>
-			</itemizedlist>
-			 
-			<para>
-				For more information on command line options available for the <command>pxeboot</command> command, refer to the <command>pxeboot</command> man page.
-			</para>
-		</section> -->
-	</section>
-	<section id="s1-netboot-tftp">
-		<title>TFTPD</title>
-<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Netboot_TFTP.xml"/>
-	</section>
-<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Netboot_DHCP.xml"/>
-	<section id="s2-netboot-custom-msg">
-		<title>Adding a Custom Boot Message</title>
-		<indexterm significance="normal">
-			<primary>PXE installations</primary>
-			<secondary>boot message, custom</secondary>
-		</indexterm>
-		<para>
-			Optionally, modify <filename>/tftpboot/linux-install/msgs/boot.msg</filename> to use a custom boot message.
-		</para>
-	</section>
-	<section id="netboot-performing">
-		<title>Performing the PXE Installation</title>
-		<indexterm significance="normal">
-			<primary>PXE installations</primary>
-			<secondary>performing</secondary>
-		</indexterm>
-		<para>
-			For instructions on how to configure the network interface card with PXE support to boot from the network, consult the documentation for the NIC. It varies slightly per card.
-		</para>
-		<para>
-			If your NIC does not support PXE booting, you can still PXE boot your system by using the <application>gPXE</application> bootloader. The Fedora Project does not distribute <application>gPXE</application> &mdash; refer to the Etherboot Project website at <ulink url="http://etherboot.org/wiki/start"></ulink> for more information.
-		</para>
-		<para>
-			After the system boots the installation program, refer to the <xref linkend="ch-guimode-x86"/>.
-		</para>
-	</section>
-</section>
\ No newline at end of file
diff --git a/en-US/pxe-server-para-1.xml b/en-US/pxe-server-para-1.xml
deleted file mode 100644
index dd89386..0000000
--- a/en-US/pxe-server-para-1.xml
+++ /dev/null
@@ -1,7 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<para>
-	Fedora allows for installation over a network using the NFS, FTP, or HTTP protocols. A network installation can be started from a boot CD-ROM, a bootable flash memory drive, or by using the <command>askmethod</command> boot option with the Fedora CD #1 or DVD. Alternatively, if the system to be installed contains a network interface card (NIC) with Pre-Execution Environment (PXE) support, it can be configured to boot from files on another networked system rather than local media such as a CD-ROM.
-</para>
\ No newline at end of file
diff --git a/en-US/pxe-server-para-2.xml b/en-US/pxe-server-para-2.xml
deleted file mode 100644
index e6ea745..0000000
--- a/en-US/pxe-server-para-2.xml
+++ /dev/null
@@ -1,7 +0,0 @@
-<?xml version="1.0"?>
-<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-
-<para>
-	For a PXE network installation, the client's NIC with PXE support sends out a broadcast request for DHCP information. The DHCP server provides the client with an IP address, other network information such as name server, the IP address or hostname of the <command>tftp</command> server (which provides the files necessary to start the installation program), and the location of the files on the <command>tftp</command> server. This is possible because of PXELINUX, which is part of the <filename>syslinux</filename> package.
-</para>
\ No newline at end of file
diff --git a/en-US/pxe-server.xml b/en-US/pxe-server.xml
deleted file mode 100644
index 88b3595..0000000
--- a/en-US/pxe-server.xml
+++ /dev/null
@@ -1,223 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE appendix PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
-"http://www.docbook.org/xml/4.4/docbookx.dtd" [
-]>
-
-<chapter id="ap-install-server">
-  <title>Setting Up an Installation Server</title>
-  <note>
-    <title>Experience Required</title>
-    <para>This appendix is intended for users with previous Linux
-      experience.  If you are a new user, you may want to install using
-      minimal boot media or the distribution DVD instead.</para>
-  </note>
-  <warning>
-    <title>Warning</title>
-    <para>The instructions in this appendix configures an automated 
-    install server. The default configuration includes destruction of
-    all existing data on all disks for hosts that install using this 
-    method. This is often different from other network install server
-    configurations which may provide for an interactive installation
-    experience.</para>
-  </warning>
-  
-  <xi:include href="pxe-server-para-1.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
-  <!-- Fedora allows for installation over a network using the NFS, FTP, or HTTP protocols. -->
-  
-  <xi:include href="pxe-server-para-2.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
-  <!-- For a PXE network installation, the client's NIC with PXE support sends out a broadcast request for DHCP information. -->
-  
-  <para>In the past, administrators needed to perform a great deal of
-    manual configuration to produce an installation server.  However, if
-    you have a Red Hat Enterprise Linux, CentOS, or Fedora server on your local network,
-    you can use <package>cobbler</package> to perform these
-    tasks. To configure a PXE server manually, see <xref linkend="sn-pxe-server-manual"/>.</para> 
-  <para>To perform the tasks in this section, switch to the <systemitem
-      class="username">root</systemitem> account with the command
-    <command>su -</command>.  As an alternative, you can run a command
-    with the <option>-c</option> option, using the form <command>su -c
-      '<replaceable>command</replaceable>'</command>.</para>
-      
-  <section id="sn-install-cobbler">
-    <title>Setting Up <package>cobbler</package></title>
-    <para>To install <package>cobbler</package> use the following
-      command:</para>
-      <screen><command><![CDATA[yum -y install cobbler]]></command></screen>
-      <para>The <command>cobbler</command> command can check its own
-	settings for validity and report the results.  Run the following
-	command to check the settings:</para>
-      <screen><command><![CDATA[cobbler check]]></command></screen>
-      <para>Change the settings in the
-      <filename>/etc/cobbler/settings</filename> file to reflect the
-      IP address information for the server.  You must change at least
-      the <option>server</option> and <option>next_server</option>
-      options, although these options may point to the same IP
-      address.</para>
-    <para>If you are not already running a DHCP server, you should also
-      change the <option>manage_dhcp</option> option to
-      <userinput>1</userinput>.  If you are running a DHCP server,
-      configure it according to the instructions found in the
-      <package>syslinux</package> package documentation.  For more
-      information, refer to your local files
-      <filename>/usr/share/doc/syslinux-<replaceable>version</replaceable>/syslinux.doc</filename> 
-      and
-      <filename>/usr/share/doc/syslinux-<replaceable>version</replaceable>/pxelinux.doc</filename>.</para>
-  </section>
-  <section id="sn-cobbler-setup-distro">
-    <title>Setting Up the Distribution</title>
-    <para>To set up a distribution from a full Fedora DVD or ISO
-      image, use this procedure.</para>
-    <note>
-      <title>Network Locations</title>
-      <para>To create a local mirror from an existing network source,
-	skip this section and refer instead to <xref
-	  linkend="sn-cobbler-mirror"/>.</para>
-    </note>
-    <procedure>
-      <step>
-	<para>If you are using a DVD disc or ISO image, Create a
-	  directory mount point:</para>
-	<screen><command><![CDATA[mkdir /mnt/dvd]]></command></screen>
-	<para>To mount a physical DVD disc, use the following
-	  command:</para>
-	<screen><command><![CDATA[mount -o context=system_u:object_r:httpd_sys_content_t:s0 /dev/dvd /mnt/dvd]]></command></screen>
-	<para>To mount a DVD ISO image, use the following
-	  command:</para>
-	<screen><command><![CDATA[mount -ro loop,context=system_u:object_r:httpd_sys_content_t:s0 /path/to/image.iso /mnt/dvd]]></command></screen>
-      </step>
-      <step>
-	<para>To support NFS installation, create a file
-	  <filename>/etc/exports</filename> and add the following line
-	  to it:</para>
-	<screen><![CDATA[/mnt/dvd *(ro,async)]]></screen>
-	<para>Start the NFS server using the following commands:</para>
-	<screen><command><![CDATA[/sbin/service rpcbind start
-/sbin/service nfs start]]></command></screen>
-      </step>
-      <step>
-	<para>To support HTTP installation, use <command>yum</command>
-	  to install the Apache web server if it is not already
-	  installed:</para>
-	<screen><command><![CDATA[yum -y install httpd]]></command></screen>
-	<para>Make a link to the mounted disc in the Apache public
-	  content area:</para>
-	<screen><command>ln -s /mnt/dvd /var/www/html/<replaceable>distro</replaceable></command></screen>
-      </step>
-    </procedure>
-  </section>
-  <section id="sn-cobbler-mirror">
-    <title>Mirroring a Network Location</title>
-    <para>If you do not have discs or ISO images for a distribution, you
-      can use <command>cobbler</command> to create an installation
-      server.  The <command>cobbler</command> command can fetch the
-      distribution over the network as part of the import
-      process.</para>
-    <para>Locate the distribution on the network.  The location may be
-      on the local network or reached at a remote site via FTP, HTTP, or
-      rsync protocols.  Note the URI, which will be in one of the
-      following forms:</para>
-    <itemizedlist>
-      <listitem>
-	<para><uri>http://mirror.example.com/pub/fedora/linux/releases/&PRODVER;/Fedora/<replaceable>arch</replaceable>/os</uri></para>
-      </listitem>
-      <listitem>
-	<para><uri>ftp://mirror.example.com/pub/fedora/linux/releases/&PRODVER;/Fedora/<replaceable>arch</replaceable>/os</uri></para>
-      </listitem>
-      <listitem>
-	<para><uri>rsync://mirror.example.com/fedora/linux/releases/&PRODVER;/Fedora/<replaceable>arch</replaceable>/os</uri></para>
-      </listitem>
-    </itemizedlist>
-  </section>
-  <section id="sn-cobbler-import">
-    <title>Importing the Distribution</title>
-    <para>To offer a distribution through more than one
-      installation method, perform additional <command>cobbler
-	import</command> tasks using a different name for each method.
-      For best results, use the installation method as part of the name,
-      so it appears in the client's boot menu.</para>
-    <procedure>
-      <step>
-	<para>To import the DVD disc or ISO distribution into
-	  <command>cobbler</command>, run this command:</para>
-	<screen><command>cobbler import --path=/mnt/dvd --name=<replaceable>distro_name</replaceable></command></screen>
-	<para>For <replaceable>distro_name</replaceable>, substitute a
-	  meaningful name for the distribution.</para>
-	<para>To import a local or remote network distribution into
-	  <command>cobbler</command>, run this command.  Replace
-	  <replaceable>network_URI</replaceable> with the URI you found
-	  in <xref linkend="sn-cobbler-mirror"/>, and
-	  <replaceable>distro_name</replaceable> as above:</para>
-	<screen><command>cobbler import --patch=<replaceable>network_URI</replaceable> --name=<replaceable>distro_name</replaceable></command></screen>
-	<important>
-	  <title>Importing a Source</title>
-	  <para>When <command>cobbler</command> imports a distribution
-	    with the commands above, it copies all the files to the
-	    server's local storage, which may take some time.</para>
-	</important>
-	<para>If you do not want to make local copies of the
-	  distribution because clients can already reach its location,
-	  use the <option>--available-as</option> option.</para>
-	<screen><command>cobbler import --path=/mnt/dvd --name=<replaceable>distro_name</replaceable> --available-as=<replaceable>network_URI</replaceable></command>
-<command>cobbler import --path=<replaceable>network_URI</replaceable> --name=<replaceable>distro_name</replaceable> --available-as=<replaceable>network_URI</replaceable></command>
-</screen>
-	<para>For <replaceable>nework_URI</replaceable>, substitute the
-	  appropriate network location of the distribution. This URI
-	  indicates how the server makes the distribution available to
-	  its clients.  The examples above assume that your
-	  <command>cobbler</command> server reaches the mirror location
-	  at the same URI as the clients.  If not, substitute an
-	  appropriate URI for the <option>--path</option> option.  The
-	  following examples are URI locations that work if you have
-	  been following the procedures in this section, and your
-	  server's IP address is <systemitem
-	    class="ipaddress">192.168.1.1</systemitem>:</para>
-	<itemizedlist>
-	  <listitem>
-	    <para><uri>nfs://<replaceable>192.168.1.1</replaceable>:/mnt/dvd</uri></para>
-	  </listitem>
-	  <listitem>
-	    <para><uri>http://<replaceable>192.168.1.1</replaceable>:/distro</uri></para>
-	  </listitem>
-	</itemizedlist>
-	<para>If necessary, replace
-	  <replaceable>192.168.1.1</replaceable> with the IP address for
-	  your <command>cobbler</command> server.</para>
-      </step>
-      <step>
-	<para>Run the command <command>cobbler sync</command> to apply
-	  the changes.  To check that your <command>cobbler</command>
-	  server is listening on the correct ports, use the
-	  <command>netstat -lp</command> command.</para>
-	<important>
-	  <title>Firewall Considerations</title>
-	  <para>Depending on your server's configuration, you may need
-	    to use the <command>system-config-securitylevel</command>
-	    command to permit access to some or all of these network
-	    services:</para>
-	  <itemizedlist>
-	    <listitem>
-	      <para>67 or bootps, for the DHCP/BOOTP server</para>
-	    </listitem>
-	    <listitem>
-	      <para>69 or tftp, for providing the PXE loader</para>
-	    </listitem>
-	    <listitem>
-	      <para>80 or http, if the <command>cobbler</command> server
-		is to provide HTTP installation service</para>
-	    </listitem>
-	    <listitem>
-	      <para>20 and 21 or ftp, if the <command>cobbler</command>
-		server is to provide FTP installation service</para>
-	    </listitem>
-	    <listitem>
-	      <para>111 or sunrpc, if the <command>cobbler</command>
-		server is to provide NFS installation service</para>
-	    </listitem>
-	  </itemizedlist>
-	</important>
-      </step>
-    </procedure>
-  </section>
-  <xi:include href="pxe-server-manual.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
-  <!-- The following steps must be performed to prepare for a PXE installation: -->
-</chapter>
diff --git a/en-US/techref.xml b/en-US/techref.xml
deleted file mode 100644
index 28c79f5..0000000
--- a/en-US/techref.xml
+++ /dev/null
@@ -1,240 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-
-<!DOCTYPE appendix PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
- "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
-]>
-
-<!-- $Id: -->
-
-<appendix id="ap-techref">
-  <title>Other Technical Documentation</title>
-  <para>
-    This document provides a reference for using the Fedora installation
-    software, known as <command>anaconda</command>. To learn more about
-    <indexterm>
-      <primary>Anaconda</primary>
-    </indexterm>
-    <command>anaconda</command>, visit the project Web page:
-    <ulink url="http://www.fedoraproject.org/wiki/Anaconda"/>.
-  </para>
-  <para>
-    Both <command>anaconda</command> and Fedora systems use a common set
-    of software components. For detailed information on key
-    technologies, refer to the Web sites listed below:
-  </para>
-  <variablelist>
-    <varlistentry>
-      <term>Boot Loader</term>
-      <listitem>
-        <para>
-          Fedora uses the
-          <indexterm>
-            <primary>GRUB</primary>
-            <secondary>documentation</secondary>
-          </indexterm>
-          <command>GRUB</command> boot loader. Refer to
-          <ulink url="http://www.gnu.org/software/grub/"/> for more
-          information.
-        </para>
-      </listitem>
-    </varlistentry>
-
-    <varlistentry>
-      <term>Disk Partitioning</term>
-      <listitem>
-        <para>
-          Fedora uses <command>parted</command> to partition disks. Refer
-          to <ulink url="http://www.gnu.org/software/parted/"/> for more
-          information.
-        </para>
-      </listitem>
-    </varlistentry>
-
-    <varlistentry>
-      <term>Storage Management</term>
-      <listitem>
-        <para>
-          <indexterm>
-            <primary>LVM</primary>
-            <secondary>documentation</secondary>
-          </indexterm>
-          Logical Volume Management (LVM) provides administrators with a
-          range of facilities to manage storage. By default, the Fedora
-          installation process formats drives as LVM volumes. Refer to
-          <ulink url="http://www.tldp.org/HOWTO/LVM-HOWTO/"/> for more
-          information.
-        </para>
-      </listitem>
-    </varlistentry>
-
-    <varlistentry>
-      <term>Audio Support</term>
-      <listitem>
-        <para>
-          The Linux kernel used by Fedora incorporates
-          <indexterm>
-            <primary>PulseAudio</primary>
-          </indexterm>
-          PulseAudio audio server. For more information
-          about PulseAudio, refer to the project documentation:
-          <ulink url="http://www.pulseaudio.org/wiki/Documentation"/>.
-        </para>
-      </listitem>
-    </varlistentry>
-
-    <varlistentry>
-      <term>Graphics System</term>
-      <listitem>
-        <para>
-          Both the installation system and Fedora use the
-          <indexterm>
-            <primary>Xorg</primary>
-          </indexterm>
-          <command>Xorg</command> suite to provide graphical
-          capabilities. Components of <command>Xorg</command> manage the
-          display, keyboard and mouse for the desktop environments that
-          users interact with. Refer to <ulink url="http://www.x.org/"/>
-          for more information.
-        </para>
-      </listitem>
-    </varlistentry>
-
-    <varlistentry>
-      <term>Remote Displays</term>
-      <listitem>
-        <para>
-          Fedora and <command>anaconda</command> include
-          <indexterm>
-            <primary>VNC (Virtual Network Computing)</primary>
-            <secondary>documentation</secondary>
-          </indexterm>
-          VNC (Virtual Network Computing) software to enable remote
-          access to graphical displays. For more information about VNC,
-          refer to the documentation on the RealVNC Web site:
-          <ulink url="http://www.realvnc.com/documentation.html"/>.
-        </para>
-      </listitem>
-    </varlistentry>
-
-    <varlistentry>
-      <term>Command-line Interface</term>
-      <listitem>
-        <para>
-          By default, Fedora uses the GNU <command>bash</command> shell to
-          provide a command-line interface. The GNU Core Utilities
-          complete the command-line environment. Refer to
-          <ulink url="http://www.gnu.org/software/bash/bash.html"/> for
-          more information on <command>bash</command>. To learn more
-          about the GNU Core Utilities, refer to
-          <ulink url="http://www.gnu.org/software/coreutils/"/>.
-        </para>
-      </listitem>
-    </varlistentry>
-
-    <varlistentry>
-      <term>Remote System Access</term>
-      <listitem>
-        <para>
-          Fedora incorporates the
-          <indexterm>
-            <primary>OpenSSH</primary>
-            <seealso>SSH</seealso>
-          </indexterm>
-          OpenSSH suite to provide remote access to the system. The SSH
-          <indexterm>
-            <primary>SSH (Secure SHell)</primary>
-            <secondary>documentation</secondary>
-          </indexterm>
-          service enables a number of functions, which include access to
-          the command-line from other systems, remote command execution,
-          and network file transfers. During the installation process
-          <command>anaconda</command> may use the <command>scp</command>
-          <indexterm>
-            <primary>scp</primary>
-            <seealso>SSH</seealso>
-          </indexterm>
-          feature of OpenSSH to transfer crash reports to remote
-          systems. Refer to the OpenSSH Web site for more information:
-          <ulink url="http://www.openssh.com/"/>.
-        </para>
-      </listitem>
-    </varlistentry>
-
-    <varlistentry>
-      <term>Access Control</term>
-      <listitem>
-        <para>
-          <indexterm>
-            <primary>SELinux</primary>
-            <secondary>documentation</secondary>
-          </indexterm>
-          SELinux provides Mandatory Access Control (MAC) capabilities
-          that supplement the standard Linux security features. Refer to
-          the SELinux Project Pages for more information:
-          <ulink url="http://docs.fedoraproject.org/selinux-guide"/>.
-        </para>
-      </listitem>
-    </varlistentry>
-
-    <varlistentry>
-      <term>Firewall</term>
-      <listitem>
-        <para>
-          The Linux kernel used by Fedora incorporates the
-          <command>netfilter</command> framework to provide
-          <indexterm>
-            <primary>firewall</primary>
-            <secondary>documentation</secondary>
-          </indexterm>
-          firewall features. The Netfilter project website provides
-          documentation for both <command>netfilter</command>, and the
-          <command>iptables</command> administration facilities:
-          <ulink url="http://netfilter.org/documentation/index.html"/>.
-        </para>
-      </listitem>
-    </varlistentry>
-
-    <varlistentry>
-      <term>Software Installation</term>
-      <listitem>
-        <para>
-          Fedora uses
-          <indexterm>
-            <primary>yum</primary>
-            <secondary>documentation</secondary>
-          </indexterm>
-          <command>yum</command> to manage the RPM packages that make up
-          the system. Refer to
-          <ulink url="http://docs.fedoraproject.org/yum/"/> for more
-          information.
-        </para>
-      </listitem>
-    </varlistentry>
-
-    <varlistentry>
-      <term>Virtualization</term>
-      <listitem>
-        <para>
-          <indexterm>
-            <primary>Virtualization</primary>
-            <secondary>documentation</secondary>
-          </indexterm> Virtualization provides the capability to
-	  simultaneously run multiple operating systems on the same
-	  computer. Fedora also includes tools to install and manage the
-	  secondary systems on a Fedora host. You may select
-	  virtualization support during the installation process, or at
-	  any time thereafter. Refer to <ulink
-	    url="http://www.fedoraproject.org/wiki/Tools/Virtualization"/> 
-	  for more information.
-        </para>
-      </listitem>
-    </varlistentry>
-  </variablelist>
-</appendix>
-
-<!--
-Local variables:
-mode: xml
-fill-column: 72
-End:
--->
diff --git a/en-US/upgrading-fedora.xml b/en-US/upgrading-fedora.xml
deleted file mode 100644
index 66acd86..0000000
--- a/en-US/upgrading-fedora.xml
+++ /dev/null
@@ -1,114 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
- "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
-]>
-
-<section id="sn-upgrading-system-x86">
-
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Upgrading-common-title-1.xml"/>
-	<!-- Upgrading an existing system -->
-
-	<note>
-		<title>Preupgrade</title>
-		<para>
-			Fedora includes <application>preupgrade</application>, a command-line tool that allows you to upgrade easily to a new version from within your existing Fedora installation. 
-		</para>
-	</note>
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Upgrading-common-para-1.xml"/>
-	<!-- The installation system automatically detects any existing installation of Red Hat Enterprise Linux. -->
-	
-	<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Upgrading-common-para-2.xml"/>
-	<!-- Note that the installation medium that you are using might not contain all the software packages that you need to upgrade your computer. -->
-	
-	<section id="sn-upgrade-examine-x86">
-	
-		<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Upgrading-common-title-2.xml"/>
-		<!-- The Upgrade Dialog -->
-		
-		<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Upgrading-common-para-3.xml"/>
-		<!-- If your system contains a Fedora or Red Hat Linux installation... -->
-		
-		<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Upgrading-common-figure-1.xml"/>
-		<!-- The Upgrade Dialog -->
-		
-		<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Upgrading-common-note-1.xml"/>
-		<!-- Manually Installed Software -->
-
-	</section>
-	
-	<section id="sn-upgrade-tree-x86">
-	
-		<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Upgrading-common-title-3.xml"/>
-		<!-- Upgrading Using the Installer -->
-		
-		<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Upgrading-common-note-2.xml"/>
-		<!-- Installations are Recommended -->
-		
-		<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Upgrading-common-para-4.xml"/>
-		<!-- If you choose to upgrade your system using the installation program... -->
-		
-<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Upgrading-common-screen-1.xml"/>
-
-		<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Upgrading-common-para-5.xml"/>
-		<!-- After installation, consult this list to discover which packages you may need to rebuild or retrieve... -->
-		
-		<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Upgrading-common-para-6.xml"/>
-		<!-- Next, make a backup of any system configuration data: -->
-
-<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Upgrading-common-screen-2.xml"/>
-
-		<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Upgrading-common-para-7.xml"/>
-		<!-- Make a complete backup of any important data before performing an upgrade. -->
-		
-		<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Upgrading-common-warning-1.xml"/>
-		<!-- Storing Backups -->
-
-		<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Upgrading-common-para-8.xml"/>
-		<!-- For more information on completing the upgrade process later... -->
-	</section>
-
-	<section id="sn-upgrading-bootloader-x86">
-	
-		<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Upgrading-common-title-4.xml"/>
-		<!-- Upgrading Boot Loader Configuration -->
-		
-		<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Upgrading-common-indexterm-1.xml"/>
-		
-		<indexterm>
-			<primary>boot loader</primary>
-			<seealso>GRUB</seealso>
-		</indexterm>
-		
-		<para>
-			Your completed Red Hat Enterprise Linux installation must be registered in the <firstterm>boot loader</firstterm> to boot properly. A boot loader is software on your machine that locates and starts the operating system.  Refer to <xref linkend="ch-grub" /> for more information about boot loaders.
-		</para>
-		
-		<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Upgrading-common-figure-2.xml"/>
-		<!-- The Update Boot Loader Dialog -->
-		
-		<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Upgrading-common-para-9.xml"/>
-		<!-- If the existing boot loader was installed by a Linux distribution... -->
-		
-		<para>
-			<firstterm>GRUB</firstterm> is the standard boot loader for Fedora on 32-bit and 64-bit x86 architectures. If your machine uses another boot loader, such as BootMagic, System Commander, or the loader installed by Microsoft Windows, then the Fedora installation system cannot update it. In this case, select <guilabel>Skip boot loader updating</guilabel>.  When the installation process completes, refer to the documentation for your product for assistance.
-		</para>
-
-		<para>
-			Install a new boot loader as part of an upgrade process only if you are certain you want to replace the existing boot loader. If you install a new boot loader, you may not be able to boot other operating systems on the same machine until you have configured the new boot loader. Select <guilabel>Create new boot loader configuration</guilabel> to remove the existing boot loader and install GRUB.
-		</para>
-
-		<para>
-			After you make your selection, click <guibutton>Next</guibutton> to continue. If you selected the <guilabel>Create new boot loader configuration</guilabel> option, refer to <xref linkend="s1-x86-bootloader"/>. If you chose to update or skip boot loader configuration, installation continues without further input from you. 
-		</para>
-
-	</section>
-
-</section>
-
-<!--
-Local variables:
-mode: xml
-fill-column: 72
-End:
--->
diff --git a/en-US/vnc_Installation_Chapter.xml b/en-US/vnc_Installation_Chapter.xml
deleted file mode 100644
index e8f3943..0000000
--- a/en-US/vnc_Installation_Chapter.xml
+++ /dev/null
@@ -1,239 +0,0 @@
-<?xml version='1.0'?>
-<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
-]>
-
-<section id="VNC_Whitepaper-installation">
-	<title>Installation Using VNC</title>
-	<para>
-		Now that you have installed a VNC viewer application and
-		selected a VNC mode for use in anaconda, you are ready to
-		begin the installation.
-	</para>
-
-	<section id="VNC_Whitepaper-installation-example">
-		<title>Installation Example</title>
-		<para>
-			The easiest way to perform an installation using
-			VNC is to connect another computer directly to the
-			network port on the target system.  The laptop on
-			a datacenter crash cart usually fills this role.
-			If you are performing your installation this way,
-			make sure you follow these steps:
-		</para>
-
-		<orderedlist>
-			<listitem>
-				<para>
-					Connect the laptop or other
-					workstation to the target system
-					using a crossover cable.  If you are
-					using regular patch cables, make sure
-					you connect the two systems using a
-					small hub or switch.  Most recent
-					Ethernet interfaces will
-					automatically detect if they need to
-					be crossover or not, so it may be
-					possible to connect the two systems
-					directly using a regular patch cable.
-				</para>
-			</listitem>
-
-			<listitem>
-				<para>
-					Configure the VNC viewer system to
-					use a RFC 1918 address with no
-					gateway.  This private network
-					connection will only be used for the
-					purpose of installation.  Configure
-					the VNC viewer system to be
-					192.168.100.1/24.  If that address
-					is in use, just pick something else
-					in the RFC 1918 address space that
-					is available to you.
-				</para>
-			</listitem>
-
-			<listitem>
-				<para>
-					Start the installation on the
-					target system.
-				</para>
-
-				<orderedlist>
-					<listitem>
-						<para>
-							Booting the
-							installation DVD or
-							CD.
-						</para>
-
-						<para>
-							If booting the
-							installation media
-							(CD or DVD), make
-							sure
-							<command>vnc</command>
-							is passed as a boot
-							parameter.  To add
-							the
-							<command>vnc</command>
-							parameter, you will
-							need a console
-							attached to the target
-							system that allows you
-							to interact with the
-							boot process.  Enter
-							the following at the
-							prompt:
-						</para>
-
-<screen>boot: <userinput>linux vnc</userinput></screen>
-
-					</listitem>
-
-					<listitem>
-						<para>
-							Boot over the
-							network.
-						</para>
-
-						<para>
-							If the target system
-							is configured with a
-							static IP address,
-							add the
-							<command>vnc</command>
-							command to the
-							kickstart file.  If
-							the target system is
-							using DHCP, add
-							<command>vncconnect=<replaceable>HOST</replaceable></command>
-							to the boot arguments
-							for the target system.
-							HOST is the IP address
-							or DNS host name of
-							the VNC viewer system.
-							Enter the following
-							at the prompt:
-						</para>
-
-
-<screen>boot: <userinput>linux vncconnect=<replaceable>HOST</replaceable></userinput></screen>
-
-					</listitem>
-				</orderedlist>
-			</listitem>
-
-			<listitem>
-				<para>
-					When prompted for the network
-					configuration on the target system,
-					assign it an available RFC 1918
-					address in the same network you used
-					for the VNC viewer system.  For
-					example, 192.168.100.2/24.
-				</para>
-
-				<note>
-					<title>Note</title>
-					<para>
-						This IP address is only used
-						during installation.  You will
-						have an opportunity to
-						configure the final network
-						settings, if any, later in
-						the installer.
-					</para>
-				</note>
-			</listitem>
-
-			<listitem>
-				<para>
-					Once the installer indicates it is
-					starting anaconda, you will be
-					instructed to connect to the system
-					using the VNC viewer.  Connect to the
-					viewer and follow the graphical
-					installation mode instructions found
-					in the product documentation.
-				</para>
-			</listitem>
-		</orderedlist>
-	</section>
-
-	<section id="VNC_Whitepaper-kickstart-installation">
-		<title>Kickstart Considerations</title>
-		<para>
-			If your target system will be booting over the
-			network, VNC is still available.  Just add the
-			<command>vnc</command> command to the kickstart file
-			for the system.  You will be able to connect to the
-			target system using your VNC viewer and monitor the
-			installation progress.  The address to use is the
-			one the system is configured with via the kickstart
-			file.
-		</para>
-
-		<para>
-			If you are using DHCP for the target system, the
-			reverse <command>vncconnect</command> method may work
-			better for you.  Rather than adding the
-			<command>vnc</command> boot parameter to the
-			kickstart file, add the
-			<command>vncconnect=<replaceable>HOST</replaceable></command>
-			parameter to the list of boot arguments for the target
-			system.  For HOST, put the IP address or DNS host name
-			of the VNC viewer system.  See the next section for
-			more details on using the vncconnect mode.
-		</para>
-	</section>
-
-	<section id="VNC_Whitepaper-firewall-considerations">
-		<title>Firewall Considerations</title>
-		<para>
-			If you are performing the installation where the VNC
-			viewer system is a workstation on a different subnet
-			from the target system, you may run in to network
-			routing problems.  VNC works fine so long as your
-			viewer system has a route to the target system and
-			ports 5900 and 5901 are open.  If your environment
-			has a firewall, make sure ports 5900 and 5901 are
-			open between your workstation and the target system.
-		</para>
-
-		<para>
-			In addition to passing the <command>vnc</command> boot
-			parameter, you may also want to pass the
-			<command>vncpassword</command> parameter in these
-			scenarios.  While the password is sent in plain text
-			over the network, it does provide an extra step before
-			a viewer can connect to a system.  Once the viewer
-			connects to the target system over VNC, no other
-			connections are permitted.  These limitations are
-			usually sufficient for installation purposes.
-		</para>
-
-		<important>
-			<title>Important</title>
-
-			<para>
-				Be sure to use a temporary password for the
-				<command>vncpassword</command> option.  It
-				should not be a password you use on any
-				systems, especially a real root password.
-			</para>
-		</important>
-
-		<para>
-			If you continue to have trouble, consider using the
-			<command>vncconnect</command> parameter.  In this
-			mode of operation, you start the viewer on your
-			system first telling it to listen for an incoming
-			connection.  Pass
-			<command>vncconnect=<replaceable>HOST</replaceable></command>
-			at the boot prompt and the installer will attempt to
-			connect to the specified HOST (either a hostname or
-			IP address).
-		</para>
-	</section>
-</section>
diff --git a/en-US/vnc_Modes_Chapter.xml b/en-US/vnc_Modes_Chapter.xml
deleted file mode 100644
index 988aec0..0000000
--- a/en-US/vnc_Modes_Chapter.xml
+++ /dev/null
@@ -1,134 +0,0 @@
-<?xml version='1.0'?>
-<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
-]>
-
-<section id="VNC_Whitepaper-vnc-modes-in-anaconda">
-	<title>VNC Modes in Anaconda</title>
-	<para>
-		Anaconda offers two modes for VNC installation.  The mode
-		you select will depend on the network configuration in
-		your environment.
-	</para>
-
-	<section id="VNC_Whitepaper-vnc-direct-mode">
-		<title>Direct Mode</title>
-		<para>
-			Direct mode VNC in anaconda is when the client
-			initiates a connection to the VNC server running in
-			anaconda.  Anaconda will tell you when to initiate
-			this connection in the VNC viewer.  Direct mode can
-			be activated by either of the following commands:
-		</para>
-
-		<itemizedlist>
-			<listitem>
-				<para>
-					Specify <command>vnc</command> as a
-					boot argument.
-				</para>
-			</listitem>
-			<listitem>
-				<para>
-					Specify the <command>vnc</command>
-					command in the kickstart file used
-					for installation.
-				</para>
-			</listitem>
-		</itemizedlist>
-
-		<para>
-			When you activate VNC mode, anaconda will complete
-			the first stage of the installer and then start VNC
-			to run the graphical installer.  The installer will
-			display a message on the console in the following
-			format:
-		</para>
-
-
-<screen>Running anaconda <replaceable>VERSION</replaceable>, the <replaceable>PRODUCT</replaceable> system installer - please wait...</screen>
-
-
-		<para>
-			Anaconda will also tell you the IP address and
-			display number to use in your VNC viewer.  At this
-			point, you need to start the VNC viewer and connect
-			to the target system to continue the installation.
-			The VNC viewer will present anaconda to you in
-			graphical mode.
-		</para>
-
-		<para>
-			There are some disadvantages to direct mode,
-			including:
-		</para>
-
-		<itemizedlist>
-			<listitem>
-				<para>
-					Requires visual access to the system
-					console to see the IP address and
-					port to connect the VNC viewer to.
-				</para>
-			</listitem>
-			<listitem>
-				<para>
-					Requires interactive access to the
-					system console to complete the first
-					stage of the installer.
-				</para>
-			</listitem>
-		</itemizedlist>
-
-		<para>
-			If either of these disadvantages would prevent you
-			from using direct mode VNC in anaconda, then
-			connect mode is probably more suited to your
-			environment.
-		</para>
-	</section>
-	
-	<section id="VNC_Whitepaper-vnc-connect-mode">
-		<title>Connect Mode</title>
-		<para>
-			Certain firewall configurations or instances where
-			the target system is configured to obtain a dynamic
-			IP address may cause trouble with the direct VNC mode
-			in anaconda.  In addition, if you lack a console on
-			the target system to see the message that tells you
-			the IP address to connect to, then you will not be
-			able to continue the installation.
-		</para>
-
-		<para>
-			The VNC connect mode changes how VNC is started.
-			Rather than anaconda starting up and waiting for you
-			to connect, the VNC connect mode allows anaconda to
-			automatically connect to your view.  You won't need
-			to know the IP address of the target system in this
-			case.
-		</para>
-
-		<para>
-			To activate the VNC connect mode, pass the
-			<command>vncconnect</command> boot parameter:
-		</para>
-
-
-<screen>boot: <userinput>linux vncconnect=<replaceable>HOST</replaceable></userinput></screen>
-
-
-		<para>
-			Replace HOST with your VNC viewer's IP address or
-			DNS host name.  Before starting the installation
-			process on the target system, start up your VNC
-			viewer and have it wait for an incoming
-			connection.
-		</para>
-
-		<para>
-			Start the installation and when your VNC viewer
-			displays the graphical installer, you are ready
-			to go.
-		</para>
-	</section>
-</section>
diff --git a/en-US/vnc_References_Chapter.xml b/en-US/vnc_References_Chapter.xml
deleted file mode 100644
index 871d556..0000000
--- a/en-US/vnc_References_Chapter.xml
+++ /dev/null
@@ -1,39 +0,0 @@
-<?xml version='1.0'?>
-<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
-]>
-
-<section id="VNC_Whitepaper-references">
-	<title>References</title>
-
-	<itemizedlist>
-		<listitem>
-			<para>
-				VNC description at Wikipedia: <ulink url="http://en.wikipedia.org/wiki/Vnc">http://en.wikipedia.org/wiki/Vnc</ulink>
-			</para>
-		</listitem>
-
-		<listitem>
-			<para>
-				TigerVNC: <ulink url="http://tigervnc.sourceforge.net/">http://tigervnc.sourceforge.net/</ulink>
-			</para>
-		</listitem>
-
-		<listitem>
-			<para>
-				RFC 1918 - Address Allocation for Private Networks: <ulink url="http://www.ietf.org/rfc/rfc1918.txt">http://www.ietf.org/rfc/rfc1918.txt</ulink>
-			</para>
-		</listitem>
-
-		<listitem>
-			<para>
-				Anaconda boot options: <ulink url="http://fedoraproject.org/wiki/Anaconda/Options">http://fedoraproject.org/wiki/Anaconda/Options</ulink>
-			</para>
-		</listitem>
-
-		<listitem>
-			<para>
-				Kickstart documentation: <ulink url="http://fedoraproject.org/wiki/Anaconda/Kickstart">http://fedoraproject.org/wiki/Anaconda/Kickstart</ulink>
-			</para>
-		</listitem>
-	</itemizedlist>
-</section>
diff --git a/en-US/vnc_VNC_Whitepaper.xml b/en-US/vnc_VNC_Whitepaper.xml
deleted file mode 100644
index 2cf59e0..0000000
--- a/en-US/vnc_VNC_Whitepaper.xml
+++ /dev/null
@@ -1,75 +0,0 @@
-<?xml version='1.0'?>
-<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
-]>
-
-<chapter id="vncwhitepaperadded">
-<title>Installing Through VNC</title>
-<!-- 	<xi:include href="vnc_Preface.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> -->
-
-<para>
-	The Red Hat Enterprise Linux and Fedora installer
-	(<application>anaconda</application>) offers you two
-	interactive modes of operation.  The original mode is a
-	text-based interface.  The newer mode uses GTK+ and runs in
-	the X Window environment. This chapter explains how you can use the graphical installation mode 
-	in environments where the system lacks a
-	proper display and input devices typically associated with
-	a workstation. This scenario is typical of systems in datacenters, which are often
-	installed in a rack environment and do not have a
-	display, keyboard, or mouse.  Additionally, a lot of these
-	systems even lack the ability to connect a graphical display.
-	Given that enterprise hardware rarely needs that ability at
-	the physical system, this hardware configuration is
-	acceptable.
-</para>
-
-<para>
-	Even in these environments, however, the graphical installer remains
-	the recommended method of installation. 
-	The text mode environment lacks a lot of capabilities found
-	in the graphical mode.  Many users still feel that the text
-	mode interface provides them with additional power or
-	configuration ability not found in the graphical version.
-	The opposite is true.  Much less development effort is put
-	in to the text-mode environment and specific things (for example,
-	LVM configuration, partition layout, package selection, and bootloader
-	configuration) are deliberately left out of the text
-	mode environment.  The reasons for this are:
-</para>
-
-<itemizedlist>
-	<listitem>
-		<para>
-			Less screen real estate for creating user
-			interfaces similar to those found in the
-			graphical mode.
-		</para>
-	</listitem>
-	<listitem>
-		<para>
-			Difficult internationalization support.
-		</para>
-	</listitem>
-	<listitem>
-		<para>
-			Desire to maintain a single interactive
-			installation code path.
-		</para>
-	</listitem>
-</itemizedlist>
-
-<para>
-	<application>Anaconda</application> therefore includes a <application>Virtual
-	Network Computing</application> (VNC) mode that allows the
-	graphical mode of the installer to run locally, but display
-	on a system connected to the network. Installing in VNC mode
-	provides you with the full range of installation options, even
-	in situations where the system lacks a display or input devices.
-</para>
-
-	<xi:include href="vnc_Viewer_Chapter.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
-	<xi:include href="vnc_Modes_Chapter.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
-	<xi:include href="vnc_Installation_Chapter.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
-	<xi:include href="vnc_References_Chapter.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
-<!-- 	<xi:include href="vnc_Revision_History.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> -->
-</chapter>
diff --git a/en-US/vnc_Viewer_Chapter.xml b/en-US/vnc_Viewer_Chapter.xml
deleted file mode 100644
index 92553dd..0000000
--- a/en-US/vnc_Viewer_Chapter.xml
+++ /dev/null
@@ -1,69 +0,0 @@
-<?xml version='1.0'?>
-<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
-]>
-
-<section id="VNC_Whitepaper-vnc-viewer">
-	<title>VNC Viewer</title>
-	<para>
-		Performing a VNC installation requires a VNC viewer running
-		on your workstation or other terminal computer.  Locations
-		where you might want a VNC viewer installed:
-	</para>
-
-	<itemizedlist>
-		<listitem>
-			<para>
-				Your workstation
-			</para>
-		</listitem>
-		<listitem>
-			<para>
-				Laptop on a datacenter crash cart
-			</para>
-		</listitem>
-	</itemizedlist>
-
-	<para>
-		VNC is open source software licensed under the GNU General
-		Public License.  Versions exist for Linux, Windows, and
-		MacOS X.  Here are some recommended VNC viewers:
-	</para>
-
-	<itemizedlist>
-		<listitem>
-			<para>
-				VNC clients are available in the repositories of most Linux distributions. Use your package manager to search for a client for your chosen distribution. For example, on Fedora, install the <!-- RHEL vnc --><package>tigervnc</package> package:
-			</para>
-
-<screen># <userinput>yum install tigervnc</userinput><!-- RHEL vnc --></screen>
-
-		</listitem>
-		<listitem>
-			<para>
-				TightVNC is available for Windows at
-				<ulink url="http://www.tightvnc.com/">http://www.tightvnc.com/</ulink>
-			</para>
-		</listitem>
-		<listitem>
-			<para>
-				MacOS X includes built-in VNC support as of
-				version 10.5.  In the
-				<application>Finder</application>, click the
-				<guilabel>Go</guilabel> menu and choose
-				<guilabel>Connect to Server</guilabel>.  In
-				the server address field, you can type
-				<command>vnc://<replaceable>SERVER</replaceable>:<replaceable>DISPLAY</replaceable></command>,
-				where SERVER is the IP address or DNS host
-				name of the VNC server you wish to connect to
-				and DISPLAY is the VNC display number
-				(usually 1), and click
-				<guilabel>Connect</guilabel>.
-			</para>
-		</listitem>
-	</itemizedlist>
-
-	<para>
-		Once you have verified you have a VNC viewer available,
-		it's time to start the installation.
-	</para>
-</section>
diff --git a/publican.cfg b/publican.cfg
deleted file mode 100644
index 06cced5..0000000
--- a/publican.cfg
+++ /dev/null
@@ -1,7 +0,0 @@
-# Config::Simple 4.59
-# Tue Dec  1 12:48:41 2009
-
-debug: 1
-xml_lang: en-US
-brand: fedora
-


